Any sip trace would work.. text.. or what not.. /b On Jan 28, 2010, at 12:46 PM, RR wrote:

Hi brian,

Do you need the sip trace from within FS or just any packet capture like from snoop/tcpdump etc will do? I don’t know how to do a sip trace from within FS

\R

Any ideas? Anyone? All I can tell is that the Contact Header looks a bit dodgey but how that's causing a 409 is what I don't get. Help please? \RR From: RR [mailto:ranjtech@gmail.com] Sent: Friday, January 29, 2010 12:57 AM To: freeswitch-users@lists.freeswitch.org Subject: RE: [Freeswitch-users] 409 Conflict When registering FS with Softswitch Hi Brian, Ok here's the sip trace captured at the softswitch. BTW, I noticed that during startup, I see FS printing out this message: 2010-01-29 01:30:05.634220 [NOTICE] sofia_reg.c:2267 Added gateway 'Test-Inbound' to profile 'external' 2010-01-29 01:30:05.634547 [ERR] sofia.c:1663 ERROR: username param is REQUIRED! 2010-01-29 01:30:05.634657 [ERR] sofia.c:1663 ERROR: username param is REQUIRED! Which is weird, because as you can see from the config, the username is infact present. Weird! Anyway, here's the trace REGISTER sip:myswitch.net.au SIP/2.0 Via: SIP/2.0/UDP 173.xxx.xxx.xxx:5080;rport;branch=z9hG4bK1U32gpr9vj5eF Max-Forwards: 70 From: <sip:user1@myswitch.net.au;transport=udp>;tag=11Qey4tcrUH9g To: <sip:user1@myswitch.net.au;transport=udp> Call-ID: cd589b73-031e-445f-a4d8-2fe334d81bbc CSeq: 126255215 REGISTER Contact: <sip:gw+Test-Inbound@173.xxx.xxx.xxx:5080;transport=udp;gw=Test-Inbound> Expires: 60 User-Agent: FreeSWITCH-mod_sofia/1.0.trunk-15980 Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, REGISTER, REFER, NOTIFY Supported: timer, precondition, path, replaces Content-Length: 0 SIP/2.0 409 Conflict Via: SIP/2.0/UDP 173.xxx.xxx.xxx:5080;rport;branch=z9hG4bK1U32gpr9vj5eF From: <sip:user1@10.1.3.20;transport=udp>;tag=11Qey4tcrUH9g To: <sip:user1@10.1.3.20;transport=udp> Call-ID: cd589b73-031e-445f-a4d8-2fe334d81bbc CSeq: 126255215 REGISTER Content-Length: 0 .and then this message just repeats again and again with every REGISTER request. Thanks for your help \RR From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Brian West Sent: Thursday, January 28, 2010 2:00 PM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] 409 Conflict When registering FS with Softswitch Any sip trace would work.. text.. or what not.. /b On Jan 28, 2010, at 12:46 PM, RR wrote: Hi brian, Do you need the sip trace from within FS or just any packet capture like from snoop/tcpdump etc will do? I don't know how to do a sip trace from within FS \R __________ Information from ESET NOD32 Antivirus, version of virus signature database 4815 (20100128) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 4816 (20100128) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 4818 (20100129) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com

Thanks mate! Specifying the extension same as the username and then using extension-in-contact fixed the problem. It now registers successfully with the switch. I do though still get the message: 2010-01-29 01:30:05.634220 [NOTICE] sofia_reg.c:2267 Added gateway 'Test-Inbound' to profile 'external' 2010-01-29 01:30:05.634547 [ERR] sofia.c:1663 ERROR: username param is REQUIRED! 2010-01-29 01:30:05.634657 [ERR] sofia.c:1663 ERROR: username param is REQUIRED! What is that about? I have the username param stated in the gateway profile!! From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Brian West Sent: Friday, January 29, 2010 1:05 PM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] 409 Conflict When registering FS with Softswitch contact header is fine... but if your switch requires the username in the contact then you can set extension-in-contact on the gateway to force that. /b On Jan 29, 2010, at 11:57 AM, RR wrote: Any ideas? Anyone? All I can tell is that the Contact Header looks a bit dodgey but how that's causing a 409 is what I don't get. Help please? \RR __________ Information from ESET NOD32 Antivirus, version of virus signature database 4818 (20100129) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com

On Fri, Jan 29, 2010 at 10:44 AM, RR <ranjtech@gmail.com> wrote:

Thanks mate! Specifying the extension same as the username and then using extension-in-contact fixed the problem. It now registers successfully with the switch.

I do though still get the message:

*2010-01-29 01:30:05.634220 [NOTICE] sofia_reg.c:2267 Added gateway 'Test-Inbound' to profile 'external'*

*2010-01-29 01:30:05.634547 [ERR] sofia.c:1663 ERROR: username param is REQUIRED!*

*2010-01-29 01:30:05.634657 [ERR] sofia.c:1663 ERROR: username param is REQUIRED!*

What is that about? I have the username param stated in the gateway profile!!

Do you possibly have some other XML files floating around that don't have a username param? It's curious that it said this error twice. It makes me think that possibly a different file or files is causing that... -MC

Hi Folks, As I continue to learn configuring FS, I am trying to use FS as a peering switch sending a call to our SBC on the other side of the pond (across the pacific) where the IP address of the FS (in the US) is configured to receive traffic from. In this case no registration is required by the sending gateway to make calls through the system overseas as its IP address is in the "known" gateways (ACL) list. Two questions: a) Where must the configuration of this overseas gateway be? Currently I have it in $FREESWITCH_HOME/conf/sip_profiles/external. Is that the right location for it? b) Looking at the gateway configuration that was present in that directory for the sample gateway, I didn't see any of the params that were relevant other than the "realm" and maybe the "proxy". Hence my configuration is extremely simple (2 Lines). As I mentioned, I don't need to register with the overseas SBC. The problem with this now is that this gateway is not being picked up by FS when I do a reloadxml OR restart FS. On typing "sofia status gateway MyGW", I get "Invalid Gateway". Following from this then, when the dialplan is configured to send the call using this gateway, I see the messages like 2010-02-01 12:42:50.138444 [ERR] mod_sofia.c:3108 Invalid Gateway 2010-02-01 12:42:50.138444 [ERR] switch_ivr_originate.c:2411 Cannot create outgoing channel of type [sofia] cause: [INVALID_NUMBER_FORMAT] 2010-02-01 12:42:50.138444 [DEBUG] switch_ivr_originate.c:3209 Originate Resulted in Error Cause: 28 [INVALID_NUMBER_FORMAT] 2010-02-01 12:42:50.138444 [INFO] mod_dptools.c:2346 Originate Failed. Cause: INVALID_NUMBER_FORMAT 2010-02-01 12:42:50.138444 [NOTICE] mod_dptools.c:2409 Hangup sofia/internal/1000@10.1.2.110 [CS_EXECUTE] [INVALID_NUMBER_FORMAT] c) Please note that the call has NOT even left FS so this message is not coming from the remote gateway/SBC as I have a trace running there as well and it never sees the call. Also, when I start FS, I see the error "username is a required param". Upon entering a bogus username and password field, I am able to load the gateway and the prfile status looks good. However, when I try and make a call I get the following: d) 2010-02-01 12:49:03.118479 [DEBUG] sofia.c:4011 Channel sofia/external/0061434144942 entering state [terminated][403] 2010-02-01 12:49:03.118479 [NOTICE] sofia.c:4655 Hangup sofia/external/0061434144942 [CS_CONSUME_MEDIA] [CALL_REJECTED] 2010-02-01 12:49:03.118479 [DEBUG] switch_channel.c:1947 Send signal sofia/external/0061434144942 [KILL] 2010-02-01 12:49:03.118479 [DEBUG] switch_core_session.c:1019 Send signal sofia/external/0061434144942 [BREAK] 2010-02-01 12:49:03.118479 [DEBUG] switch_ivr_originate.c:3209 Originate Resulted in Error Cause: 21 [CALL_REJECTED] 2010-02-01 12:49:03.118479 [INFO] mod_dptools.c:2346 Originate Failed. Cause: CALL_REJECTED 2010-02-01 12:49:03.118479 [NOTICE] mod_dptools.c:2409 Hangup sofia/internal/1000@10.1.2.110 [CS_EXECUTE] [CALL_REJECTED] Any ideas? Thanks \R

Hi Frank, Thanks for the response. The remote gateway is not running FreeSWITCH. But that's ok, I figured out the problem. I was capturing packets from the wrong IP address so after adding the username/password, the call did manage to get to the other end (after I realized the source IP was wrong) and realized that my dialplan at the other side wasn't setup correctly. Should be able to fix that. BTW, before I go hunting in the Wiki, can you off the top of your head tell me how I can manipulate numbers in the dialplan? If my destination number = 00614xxxxxxxx but I want to send 120#614xxxxxxx instead, how would I do that? Thanks \R -----Original Message----- From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Frank Carmickle Sent: Monday, February 01, 2010 2:35 PM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] Outbound Call (No Registration) On Mon, Feb 01, RR wrote:

Hi Folks,

As I continue to learn configuring FS, I am trying to use FS as a peering switch sending a call to our SBC on the other side of the pond (across the pacific) where the IP address of the FS (in the US) is configured to receive traffic from. In this case no registration is required by the sending gateway to make calls through the system overseas as its IP address is in the "known" gateways (ACL) list.

I allowed calls in to my pbx from a specific ip in the dialplan with out an acl or a gateway by putting a statement like <extension name="fjc-pbx-inbound"> <condition field="network_addr" expression="^2001\:470\:XXXX\:XXXX\:X:X\:X\:X$"/> <condition field="destination_number" expression="^(.*)$"> <action application="transfer" data="$1 xml default"/> </condition> </extension> in the public section of the dialplan. In this example you see that it is a ipv6 address. This could easily be replaced with a ipv4 address like the level3 address 4.3.2.1. There are other ways to do this with a gateway if you so choose. --FC _______________________________________________ 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 __________ Information from ESET NOD32 Antivirus, version of virus signature database 4824 (20100201) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 4825 (20100201) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com