[Freeswitch-users] Getting destination number

[Ken Rice]

Check out the info dialplan application…

 

You’re provider is doing something unusual here as the invite URI is what you use to route the call, the to: uri is supposed to be the original dialed digits

 

From: freeswitch-users-bounces at lists.freeswitch.org [mailto:freeswitch-users-bounces at lists.freeswitch.org] On Behalf Of Allan Kristensen
Sent: Wednesday, September 7, 2016 10:39 AM
To: FreeSWITCH Users Help <freeswitch-users at lists.freeswitch.org>
Subject: [Freeswitch-users] Getting destination number

 

Hello,

 

I've just setup a sip trunk with a new provider, however there are some issues receiving calls.

 

The INVITE looks like this:

 

   INVITE sip:NCdWXsdSsaF2B at 192.168.0.190:52284 <http://sip:NCdWXsdSsaF2B@192.168.0.190:52284>  SIP/2.0

   ....

   From: <sip:+XXXXXXXXXX at x.x.x.x>;tag=Ud8ghaXg01821203

   To: <sip:+YYYYYYYYYY at x.x.x.x>

   ...

 

The invite has my account name, instead of the destination number and the real destination number is in the "To:" field (which it normally is I guess ;-)

 

Then Freeswitch does this of cause:

 

[INFO] mod_dialplan_xml.c:637 Processing +XXXXXXXXXX <+XXXXXXXXXX>->NCdWXsdSsaF2B in context inbound

 

That is undesirable, so Is there any way for Freeswitch to grab the destination number from the to field instead of the INVITE string ?

I could make a special sip profile for that provider with it's own dialplan and then set destination_number from the "sip_to_user" variable and transfer to the real dialplan, but it just seems so messy...

Or is it my provider that is doing it wrong?

 

Best regards,

  Allan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20160907/e53ffa41/attachment.html