Parse SIP header for actual called DID?

[dvanaken]

I am setting up a system with 100 DIDs - all concurrent numbers (6400-6499). The provider is Anveo. In the Anveo config each of the 100 DIDs is pointed to the same trunk which sends the INVITE. However, the only place that the "called DID" is shown in the INVITE is in an X- header so every called number looks the same to 3cx and all calls go to the default inbound extension for that trunk. I have DIDs set up in 3cx associating the called DID with the destination extension, but 3cx doesn't know the actual DID. I can't find a way to access the X- header to discriminate and route each call to its correct extension. Is there a way that 3cx can parse this?

 

[leejor]

Who is your provider? 3CX Supported?

Something similar, involving X-DID field...
.
https://www.3cx.com/community/threads/identification-did-in-sip-packet.49190/

 

[dvanaken]

Thank you. Anveo is not supported but is evidently used somewhat according to other forums posts. It looks like in the post you linked it was solved by referring to INVITE header. In my case, the ONLY place the called number is given is in the X- header.

 

[leejor]

Sorry, later noticed that you had mentioned the provider. You might ask them why their sent DID format is different from most others, if that is indeed the case.

 

[leejor]

Came across this thread...
https://www.3cx.com/community/threads/does-3cx-work-with-anveo-direct.74061/

There are others, involving that provider, if you search.

 

[dvanaken]

Thank you. I will ask the provider....!

 

[dvanaken]

Where would be the appropriate place in the SIP header to present the DID when it's different than the one in INVITE, is it typically in To: (user)?

"trunk number"
INVITE sip:[email protected]:5060 SIP/2.0

"caller"
From: <sip:[email protected]>;tag=d5e64450d77de930be3741b52c7583c2

"called"
To: <sip:15554444567@1.2.3.4>

 

[leejor]

Yes, In the To: header. Are you seeing it there?

 

[dvanaken]

No, but it turns out that Anveo has a "variable" to be used for trunk initiation which will substitute in the actual DID rather than using the trunk number. It works fine. Thanks for your help.