Telnyx Outbound Caller ID Issue

[vectra]

Does anyone have a solution to resolve the issue with the Telnyx template? Since V20, the outbound caller ID is showing only the trunk number instead of the DID number. P-assertion identity override DIDI number and putting trunk number. Some PBC instance doing that correctly. When I compare template no difference.

 

[SweetAction]

You either have....
1. A number specified in the outbound rule
2. In Telnyx Mission Control a override outbound caller ID set on the trunk
3. Trying to use a number you are not allowed to use

All this to say, Telnyx on v20 works fine with outbound CID set to user DID

 

[vectra]

Hi Sweet Action. I do not have a number specified in the outbound rule. I do not have a caller id override in telnyx mission. Look at this example.

INVITE sip:[email protected] SIP/2.0<br>
Via: SIP/2.0/UDP 10.128.0.2:5060;branch=z9hG4bK-524287-1---b1ade349d9de2956;rport<br>
Max-Forwards: 70<br>
Contact: &lt;sip:[email protected]:5060&gt;<br>
To: &lt;sip:[email protected]&gt;<br>
From: "+1224xxxx316"&lt;sip:[email protected]&gt;;tag=e8c44a48<br>Call-ID: vdeovuZUIeJMCJArCL8sKg..<br>CSeq: 1 INVITE<br>Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE, UPDATE<br>Content-Type: application/sdp<br>
Supported: replaces, timer<br>User-Agent: 3CXPhoneSystem 20.0.7.1080 (1080)<br>
P-Asserted-Identity: "+1224xxxx316"&lt;sip:[email protected]&gt;<br>
Remote-Party-ID: "+1224xxxx316"&lt;sip:[email protected]:5060&gt;;party=calling<br>Content-Length: 311

So, for some reason, P-asserting identity overrides outbound DID number

 

[SweetAction]

Is that invite from 3CX logging or Telnyx?

So there's like 3 places in 3CX to set outbound caller ID, including user, outbound rule, default trunk. I think there might be 4th place too somewhere.

I would check the trunk XML itself to see if someone hardcoded it into the XML. 3 dots, export.

 

[vectra]

This is on the Telnyx side. When the template is working fine, P asserted integrity is not modified.

 

[SweetAction]

This is on the Telnyx side.

Recommend you check the SIP request from the 3CX side to see if p-asserted is set by 3CX or not and what it is set to then.