outbound CID also used for internal calls about sccp_manager HOT 3 OPEN

Chan-sccp does not know about internal cid's or outbound cid's, it has no knowledge of such worldly things. From the log above, the CID is being set during dialplan interaction, ie: FreePBX is setting/overriding the cid information during the call. This means the issue you raised is more FreePBX / sccp_manager related. Sounds like i am passing the buck and in this case i think that is valid.

@steve-lad : There are to moments where the cid needs to be set. During device/line registration (ie: chan-sccp realtime db). And during dialplan interaction, ie FreePBX dialplan handling. Only the latter can deal with INBOUND, INTERNAL and OUTBOUND, because FreePBX/Dialplan know where an entered phonenumber/extension is/might be, and ought to take the appropriate action based on that knowledge.

Moving the ticket to sccp_manager repo

from sccp_manager.

This problem also happens when you don't enter anything on Outbound Caller ID. When you try to make an internal call with an extension like this, only the Extension Name appears on the called party, so if it is a missed call, they can't dial back because no number is shown on the screen, just the name.

from sccp_manager.

We're no longer using sccp phones, so I can't be of any further assistance.

from sccp_manager.