Outbound Caller ID

[charliethepbx]

Hi,

I am unable to get outbound caller ID working. It is showing up as Private Number / Unknown.

- 3CX Phone System for Windows Version 12.5
- IP Phones are Cisco SPA504G
- SIP Trunk provider: didlogic

I have set the Caller ID with didlogic to 'No CallerID' under their web portal. I have requested and its has been confirmed that didlogic will accept custom CLI. "Your account is now provisioned for custom CLI. Our gateway will obey the "FROM" string you're sending. Please set the SIP account CLI option to "No caller ID"."

I have configured each user extension 'Outbound Caller ID' under the SIP tab to the 10 digit DID they have assigned. VoIP Providers -> didlogic -> xxxxxxxxxx -> Port Details -> Port Identification is empty. Other Options -> Outbound Caller ID is also empty. I have tried setting the following Outbound Paramaters under the didlogic trunk:

From : Display Name - "outboundCallerId" outbound caller id taken from Extension settings in management console
From : User Part - "outboundCallerId" outbound caller id taken from Extension settings in management console
P Asserted Identity : Display Name - "outboundCallerId" outbound caller id taken from Extension settings in management console
P Asserted Identity : User Part - "outboundCallerId" outbound caller id taken from Extension settings in management console

The following is an example test call, it is internaitonal but the same thing happens domestically:

30-Apr-2015 22:17:42.434 Leg L:969.2[Line:10000>>011xxxxxxxx] is terminated: Cause: 487 Request Terminated/INVITE from x.x.x.x:5060
30-Apr-2015 22:17:42.262 [CM503008]: Call(C:969): Call is terminated
30-Apr-2015 22:17:42.262 Leg L:969.1[Extn] is terminated: Cause: CANCEL from x.x.x.x:5064
30-Apr-2015 22:17:37.235 [CM505003]: Provider:[didlogic] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [DIDLogic SBC] PBX contact: [sip:[email protected]:5060]
30-Apr-2015 22:17:30.809 [CM503025]: Call(C:969): Calling T:Line:10000>>01161402805358@[Dev:sip:[email protected]:5060] for L:969.1[Extn]
30-Apr-2015 22:17:30.761 [CM503027]: Call(C:969): From: Extn:160 ("Conference Room" <sip:[email protected]:5060>) to T:Line:10000>>01161402805358@[Dev:sip:[email protected]:5060]
30-Apr-2015 22:17:30.761 [CM503004]: Call(C:969): Route 1: from L:969.1[Extn] to T:Line:10000>>01161402805358@[Dev:sip:[email protected]:5060]
30-Apr-2015 22:17:30.761 Line limit check: Current # of calls for line Lc:10000(@didlogic[<sip:[email protected]:5060>]) is 0; limit is 20
30-Apr-2015 22:17:30.760 Call(C:969): Call from Extn:160 to 011xxxxxxxxxxx matches outbound rule 'International'
30-Apr-2015 22:17:30.760 [CM503001]: Call(C:969): Incoming call from Extn:160 to <sip:[email protected]:5060>


Can anyone suggest what I might be doing wrong to get the configured DID to show as the outbound caller ID instead of Private Number / Unknown.

Thanks.

 

[lneblett]

First - log into the 3CX console and look at the ports/trunks status page and make a call and see what 3CX is sending as the callerID. You may want to try this a couple of times using a different callerID to ensure that it is getting the setting from the extension and not something else.

The SIP provider should be able to advise which fields in the SIP header they use to pick up the callerID and assuming that all is well from the instructions they provided (as you have below), you may need to do a wireshark capture and send it to them.

There setting of "no callerID" seems a little odd as to me it implies just that. Others I have seen indicate more along the lines of 1) Use Trunk, 2) Use User provided or 3) None.

The" none" is used to prevent callerID from going out at all, but each provider likely uses their own terminology and definition.

The log you posted is only showing the internal activities of the 3CX system in making the call. Try using the verbose mode. While I do not recall if it will show all the pertinent information related to the CallerID, it might. A wirehsark will however.

 

[charliethepbx]

Thank InebIett. I didnt realise I could check what the PBX was sending from the Ports/Trunks page. That is really helpful.

It is sending '10000' which is the virtual extension of the didlogic SIP trunk. I guess this means that the caller ID problem is a configuration issue on the PBX. Is there a guide anywhere which shows exactly what options need to be modified to have this use the value configured under the extension? I have tried several 3CX walkthroughs and didnt seen anything in the 3CX administrator guide.

Thanks.

 

[lneblett]

I do not think there is a one size fits all solution as various providers may use different SIP header fields. I am a little confused as to where the changes you indicated earlier were made. I am assuming at the provider. But then I do not understand how you "configured each user extension with the 10digit DID they have assigned". I am not sure that this is needed as this seems to be more related to a hosted system and not for a SIP trunk.

If you will get into the 3CX console and go to the VoIP Provider tab and then select DIDLOGIC and go to the outbound parameters, you will see similar entries as to what you mentioned earlier. These are the fields that comprise parts of the SIP message that is sent to the provider so that you can customize to their requirements and/or to what they will allow.

As I indicated earlier, you should first modify an extension within 3CX under the other Tab and enter whatever callerId you want associated to that extension and then make a test call while looking at the VoIP/Trunk status page. If you see the callerID that you entered, then you "may" be on the right track (I say may as this is what 3CX is sending, but may not be what the provider wants).

If this does show the callerID, then it could be that is all that is needed. If not, then you may need to alter some of the outbound parameters, but the provider should be able to advise as to which settings are needed.

DIDLOGIC and 3CX recently announced their interoperability agreement (April 23), so there should be no reason that it will not work given the correct settings. I assume you set up 3CX using the provisioning templatefor DIDLOGIC? I just looked in my system and there is one.