Solved Outbound Number is Randomized and Unknown Caller ID

[dapico]

When making outbound calls the number is randomized and caller id is displayed as Unknown.

I have tested with two different SIP Trunk Services.
I have the Caller ID set to the registered SIP Trunk Number as provided.
I have tried with and without the + (+1XXX-XXX-XXXX and 1XXX-XXX-XXXX), I have tried setting the Caller ID as a name.
I have manually edited the Outbound Parameters for both SIP Trunk settings to a specific display ID.

Will be happy to post logs and configuration details as requested.

 

[cobaltit]

You can't push a name, only a number. No need to post anything here. Since you are making trunk changes I'm assuming you aren't using supported trunks. Pick the trunking provider you want to use and engage them to ask why caller-id isn't working and how to fix.

 

[dapico]

You can't push a name, only a number. No need to post anything here. Since you are making trunk changes I'm assuming you aren't using supported trunks. Pick the trunking provider you want to use and engage them to ask why caller-id isn't working and how to fix.

I am using nexmo (which may or may not be supported for outgoing) and Twilio which is supported under worldwide option.
The Caller ID Display Name is optional, the outgoing number that keeps getting randomized is a slight issue.

 

[YiannisH_3CX]

Hello @dapico

What do you mean by randomised? Where do you see that the caller ID is randomised? Are you trying to display a different outbound caller ID for each extension or one caller ID for all extensions?
What PBX version are you running? You can see the exact build number on the Dashboard, under the Information column next to the licence version. For example 15.5.15502.6.

 

[dapico]

Hello @dapico

What do you mean by randomised? Where do you see that the caller ID is randomised? Are you trying to display a different outbound caller ID for each extension or one caller ID for all extensions?
What PBX version are you running? You can see the exact build number on the Dashboard, under the Information column next to the licence version. For example 15.5.15502.6.

15.5.15502.6

I have 1 number and when I make calls I want that number to show up.
Instead the number that the call is made from is random each time.
I use 1-800-444-4444 to test what number it shows up as, and it is always different when calling from 3CX.

 

[craigreilly]

Which one is showing the Caller ID issue?
NexMo, Twilio, Both?

 

[dapico]

Which one is showing the Caller ID issue?
NexMo, Twilio, Both?

I'm in direct communications with Twilio's support team at the moment to debug other issues.
So, currently it's just nexmo.

 

[YiannisH_3CX]

Is that number setup under the trunk settings or the extension settings? Did you use the 3CX template to setup the trunk? I would recommend running a wireshark capture and see what the PBX is sending to the provider each call.

 

[dapico]

Is that number setup under the trunk settings or the extension settings? Did you use the 3CX template to setup the trunk? I would recommend running a wireshark capture and see what the PBX is sending to the provider each call.

The number is setup under the SIP Trunks via the official template provided by 3CX.
The logs from 3CX Activity Log through Verbose seem normal.
No errors or weird settings, everything seems to be forwarded properly.

 

[YiannisH_3CX]

Then you will need to use wireshark as mentioned and capture a couple of outbound calls. If the calls sent by the PBX are the same and have the correct number then you should probably contact your provider ask them if they see anything wrong.

 

[dapico]

Finally figured out the issue.
Nexmo only supports inbound routing, all outbound calls are only linked to the account but are unable to verify which number it should be sent from.
Twilio needed a + in the Caller ID. Simple as that.

 

[YiannisH_3CX]

Finally figured out the issue.
Nexmo only supports inbound routing, all outbound calls are only linked to the account but are unable to verify which number it should be sent from.
Twilio needed a + in the Caller ID. Simple as that.

Glad to see the issue has been resolved and thank you for updating the thread with your solution.