Thank you Fernando for suggesting the process to better understand this issue. I now understand the issue, but don't have the FS knowledge to fix it. *The gw requires:* *a) All packets go to -> udp/[204.101.5.67]:5065* *b) The realm to be: sip.babytel.ca <http://sip.babytel.ca>* I can't find the gw profile that will satisfy both requirements, for both REGISTER and outbound calling (INVITE). SCENARIO 1: Set gw <register-proxy> only: REGISTER works, but INVITE fails <gateway name="babytel"> <param name="username" value="16477240904"/> <param name="password" value="xxxxxx"/> <param name="realm" value="sip.babytel.ca"/> <param name="register-proxy" value="nat.babytel.ca:5065"/> <param name="register" value="true"/> </gateway> RESULT: The REGISTER packet is correct. Packet goes to correct address/port, and the REGISTER packet is addressed to correct realm. Log file: send 856 bytes to *udp/[204.101.5.67]:5065* at 16:33:32.049675: ------------------------------------------------------------------------ REGISTER *sip:sip.babytel.ca <http://sip.babytel.ca>*;transport=udp SIP/2.0 However, the problem is outbound calling. The packets are NOT sent to the proxy: send 1085 bytes to *udp/[204.101.5.20]:5060* at 16:39:28.697709: ------------------------------------------------------------------------ INVITE sip:19058305602@sip.babytel.ca SIP/2.0 SCENARIO 2: Set gw <proxy>: <gateway name="babytel"> <param name="username" value="16477240904"/> <param name="password" value="xxxxxx"/> <param name="realm" value="sip.babytel.ca"/> <param name="proxy" value="nat.babytel.ca:5065"/> <param name="register-proxy" value="nat.babytel.ca:5065"/> <param name="register" value="true"/> </gateway> Result: send 651 bytes to *udp/[204.101.5.67]:5065* at 16:43:59.536788: ------------------------------------------------------------------------ REGISTER *sip:nat.babytel.ca:5065 <http://nat.babytel.ca:5065>*;transport=udp SIP/2.0 Problem is that the realm switches to the proxy, and I don't get registered. I have tried removing <register-proxy> (i.e. just have <proxy>) and get the exact same problem. SUMMARY: Does anyone know how to configure the gateway such the realm is consistently set to the realm configuration for both REGISTER and INVITE, and have the proxy works consistently? Thank you so much, Ian. On Wed, Jan 15, 2014 at 5:48 AM, Fernando - NextBilling IP Solutions < freeswitch@nextbilling.com.br> wrote:
Hello.
Try to set the loglevel to 7 ( */log 7 *) and enable siptrace on sofia profile (*sofia profile external siptrace on*).
WIth a good level of debug and the siptrace we can know if the call reached your gateway and what kind of response FS receive from gw.
*Best regards,Fernando da Silva Santos* *CIO - NextBilling IP Solutions* *$ 55 (11) 3090-0077* *$ 55 (21) 3090-0017*
*$ 0800 580-9200 *
Em 14/01/2014, à(s) 19:31, Ian McMaster <ian.mcmaster@gmail.com> escreveu:
I have tried two dialplan routes:
1) Freeswitch cookbook suggests putting in conf/dialplan/default.xml
<extension name="dial-10-digit-number no prefix"> <condition field="destination_number" expression="^(\d{10})$"> <action application="bridge" data="sofia/gateway/babytel/$1"/> </condition> </extension>
2) Freeswitch 1.0.6 book suggest putting in conf/default/01_babytel.xml
<extension name="Outbound Babytel calls - prefix 91"> <condition field="destination_number" expression="^9(1\d{10})$"> <action application="bridge" data="sofia/gateway/babytel/$1"/> </condition> </extension>
Both give the same symptom: freeswitch@internal> /log 6 +OK log level 6 [6] freeswitch@internal> 2014-01-14 16:28:33.238770 [NOTICE] switch_channel.c:1055 New Channel sofia/internal/101@192.168.2.7 [b5bdf358-5142-4b0e-8753-d15a84922e18] 2014-01-14 16:28:33.378781 [INFO] mod_dialplan_xml.c:558 Processing 101 <101>->9058305602 in context default 2014-01-14 16:28:33.378781 [NOTICE] switch_channel.c:1055 New Channel sofia/external/9058305602 [9ddd008b-3e75-46ed-a864-858554737aeb] <then nothing....> After about 30 seconds, 2014-01-14 16:29:33.019000 [INFO] mod_dptools.c:3201 Originate Failed. Cause: NO_ANSWER
On Tue, Jan 14, 2014 at 3:59 PM, Vik Killa <vipkilla@gmail.com> wrote:
What dialplan entry is executing?
On Tue, Jan 14, 2014 at 3:39 PM, Ian McMaster <ian.mcmaster@gmail.com>wrote:
Apologies for a simple newbie question. Following examples in the first two FreeSWITCH books, have been able to set up a SIP gateway, register, and receive calls. However I can't make calls. The dialplan is being entered, but 'hangs' at
switch_channel.c:1055 New Channel sofia/external/16475551212
a) The provider name is "babytel". b) The dial plan bridge is to data="sofia/gateway/babytel/$1" (as per the books) c) The provider xml file is in conf/sip_profiles/external (as per the books)
d) sofia status Name: external::babytel Type: gateway State: REGED
Why is the bridge channel called "sofia/external/...."? And not "sofia/babytel/..."? Why does sofia status show "external::<provider>" (the books just show the provider name)?
Can anyone explain why the bridge to the gateway does not occur?
Thank you, Ian.
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org