VoIP Mailing List Archives

[andy at fabulous4.co.uk]

Hi folks, I know this problem comes up all the time so sorry to bring it up again but I can't seem to find the answer in previous posts. I have my freeswitch installation behind a DLink firewall so the freeswitch server is natted. I have added what I believe are all the necessary rules to the firewall to handle SIP correctly and the firewall isn't showing any blocked traffic when calls come in. Calls are forwarded to my public ip address from my VOIP provider Voiptalk. Here's the problem: Incoming calls are successfully forwarded to the freeswitch server and answered. I can hear the IVR message played down the phone line so outgoing audio is ok. When I try to send DTMF key presses from my phone none of these register on the switch. When I hangup the call the call hangup is also not picked up by the switch. I have followed the auto-nat instrcutions and have verified that the switch correctly grabs and sets the external ip address. I have also tried setting the external ip address manually but without success. Can anyone offer any guidance as to what might be causing this problem or what I could try to resolve it? I can post log/config snippets if that helps. Many thanks Andy

[brian at freeswitch.org]

Bet you its inband dtmf and you need to start the dtmf detector.

/b

On Oct 7, 2009, at 8:11 AM, Andy wrote:

[andy at fabulous4.co.uk]

Thanks Brian, sorry should have pre-empted that one as I've issue before. start_dtmf is in the dialplan and occurs at the start of every call. On closer inspection however it appears that only part of the nat setup is taking place. sofia status gives: Name Type Data State================================================================================================= internal profile sip:mod_sofia@10.10.0.2:5080 RUNNING (0) external profile sip:mod_sofia@10.10.0.2:5060 RUNNING (0) default alias internal ALIASED 10.10.0.2 alias internal ALIASED=================================================================================================2 profiles 2 aliases sofia status profile external gives (the external ip addresses are correct): API CALL [sofia(status profile external)] output:=================================================================================================Name externalDomain Name N/ADBName sofia_reg_externalPres HostsDialplan XML,enumContext defaultChallenge Realm auto_toRTP-IP 10.10.0.2Ext-RTP-IP 82.5.159.138SIP-IP 10.10.0.2Ext-SIP-IP 82.5.159.138URL sip:mod_sofia@10.10.0.2:5060BIND-URL sip:mod_sofia@10.10.0.2:5060HOLD-MUSIC N/AOUTBOUND-PROXY N/ACODECS PCMU,PCMA,GSMTEL-EVENT 101DTMF-MODE rfc2833CNG 13SESSION-TO 0MAX-DIALOG 0NOMEDIA falseLATE-NEG falsePROXY-MEDIA falseAGGRESSIVENAT falseSTUN-ENABLED trueSTUN-AUTO-DISABLE falseCALLS-IN 0FAILED-CALLS-IN 0CALLS-OUT 0FAILED-CALLS-OUT 0 BUT...... nat_map status, gives: API CALL [nat_map(status)] output:false And there is no mention of nat detection in the startup log. Is this because I'm using port 5060 externally? Cheers Andy From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Brian WestSent: 07 October 2009 15:22To: freeswitch-users@lists.freeswitch.orgSubject: Re: [Freeswitch-users] NAT problems - sorry Bet you its inband dtmf and you need to start the dtmf detector. /b On Oct 7, 2009, at 8:11 AM, Andy wrote: I can hear the IVR message played down the phone line so outgoing audio is ok.

[brian at freeswitch.org]

No its because you're not behind a upnp/nat-pmp router so you'll have to manually forward everything... All the info you showed displaying the profile status is correct.

/b

On Oct 7, 2009, at 12:44 PM, Andy wrote:

[andy at fabulous4.co.uk]

Many thanks Brian, the firewall docs assure me it is uPnp but is probably lying or a poor implementation. Could you point me to the right section of the Wiki to tell me how to do this manually as I've been scouting for some time and can;t seem to find the right thing. sorry if I'm being blind. From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Brian WestSent: 07 October 2009 18:49To: freeswitch-users@lists.freeswitch.orgSubject: Re: [Freeswitch-users] NAT problems - sorry No its because you're not behind a upnp/nat-pmp router so you'll have to manually forward everything... All the info you showed displaying the profile status is correct. /b On Oct 7, 2009, at 12:44 PM, Andy wrote: Is this because I'm using port 5060 externally? Cheers Andy

[brian at freeswitch.org]

s/auto-nat/$realip/ then forward the rtp ports and sip ports.

/b
PS chances are you have to ENABLE upnp.
On Oct 7, 2009, at 12:58 PM, Andy wrote:

[andy at fabulous4.co.uk]

Thanks Brian, I've now set the external ips manually to be my external ip and have forward all ports through my firewall to the FS server. It's actually set up as a DMZ to everything is being forwarded without restriction but sadly DTMF and HANGUP messages are still not getting through. Have I misunderstood what is required. Is there some additional forwarding within FS required. I'm really sorry to keep coming back but I've been wrestling with this for a long time now and not getting anywhere. Many thanks Andy From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Brian WestSent: 07 October 2009 19:07To: freeswitch-users@lists.freeswitch.orgSubject: Re: [Freeswitch-users] NAT problems - sorry s/auto-nat/$realip/ then forward the rtp ports and sip ports. /b PS chances are you have to ENABLE upnp. On Oct 7, 2009, at 12:58 PM, Andy wrote: Many thanks Brian, the firewall docs assure me it is uPnp but is probably lying or a poor implementation. Could you point me to the right section of the Wiki to tell me how to do this manually as I've been scouting for some time and can;t seem to find the right thing. sorry if I'm being blind.

[rupa at rupa.com]

Double check your firewall and:

1) ensure you've actually enabled UPNP
and
2) Ensure that any mention of a SIP ALG (application level gateway) is
turned off. SIP ALGs tend to really screw things up.

On Wed, Oct 7, 2009 at 12:48 PM, Andy <andy@fabulous4.co.uk> wrote:

[andy at fabulous4.co.uk]

Hi folks, Just thought I'd post the solution to this problem. In my case the problem was that my config was based on an older version and so was missing a crucial parameter that exists in the default config wirth a new install. The external.xml profile needed to contain the parameter: <param name="local-network-acl" value="localnet.auto"/> With this in place, DTMF and hangup messages traverse the nat firewall correctly. Without it they don't. I searched the Wiki and couldn't find any info on this parameter. Can anyone provide a description of what it does and why it's significant that can be added to the WIKI? Cheers Andy From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Brian WestSent: 07 October 2009 19:07To: freeswitch-users@lists.freeswitch.orgSubject: Re: [Freeswitch-users] NAT problems - sorry s/auto-nat/$realip/ then forward the rtp ports and sip ports. /b PS chances are you have to ENABLE upnp. On Oct 7, 2009, at 12:58 PM, Andy wrote: Many thanks Brian, the firewall docs assure me it is uPnp but is probably lying or a poor implementation. Could you point me to the right section of the Wiki to tell me how to do this manually as I've been scouting for some time and can;t seem to find the right thing. sorry if I'm being blind.