Inbound route problem with VOIPNOW trunk

edschofield

New Member
Jul 7, 2023
6
0
1
31
I'm trying to setup the inbound routes for a trunk from my provider who use VoIPNow. I have the trunk up and can see calls coming in. The problem I'm having is that the DID Destination number for the inbound calls isn't in the sip_to_user field. It's actually in a field called X-voipnow-did. I think what I need to do is have this field treated as the destination number, but this is where I'm running into a brick wall. I've enabled parse-all-invite-headers in my external profile, which has given me sip_i_x_voipnow_did (Which for some reason has the DID number in twice) as well as sip_h_X-voipnow-did in the CDR logs. I've tried adding this field in Default Settings -> destination then saving my Destination entries again, which I could see changed to use the voipnow header, but it still wasn't picking up the correct destination number. I also tried creating a destination with the number repeated twice, but this didn't help either. I've attempted to duplicate the caller-details dialplan (Allthough I'm not sure if I should be duplicating and editing the one in Inbound Routes or the one in Dialplan Manager, or both) then changing where caller_destination is usually set to sip_to_user to use one of the various instances of the voipnow header, but I couldn't get this to work either.
Could anyone give me some pointers on this?
 
@edschofield why not just ask your trunk provider to enable the option "A PBX is connected to this extension"? This will make VoipNOW treat your extension as a trunk, and will populate the TO header with the actual dialed phone number instead of the extension number in the INVITE requests it'll send you.

1777481364316.png
 
  • Like
Reactions: RTL