Hi all I googled the problem(RECOVERY_ON_TIMER_EXPIRE) and it seems it is related to NAT, but how can I fix it? I've changed: <param name="enable-timer" value="false"/> but it is not working thanx
What device device is performing the NAT? Does it have a SIP ALG you can turn off? See "ALG" on the wiki. Sent from my iPhone On May 26, 2010, at 11:01 PM, babak yakhchali <babak.freeswitch@gmail.com
wrote:
Hi all I googled the problem(RECOVERY_ON_TIMER_EXPIRE) and it seems it is related to NAT, but how can I fix it? I've changed: <param name="enable-timer" value="false"/>
but it is not working thanx _______________________________________________ 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
traffic from my ipphones to freeswitch is not passing through nat, cause there are just some vlans. ipphones and freeswitch are not in the same vlan, is the problem related to this structure?or is the problem just caused by nat problems??
yes you are right my ip phones are behind nat is there anyway to solve this? I checked the packet captures and found out that only the udp port is changed from 5060 to 49761. I'm using cisco 7941 ip phones. thanx
May you check if the Cisco sets the rport flag in the Via field of the INVITE ? David Ponzone Direction Technique email: david.ponzone@ipeva.fr tel: 01 74 03 18 97 gsm: 06 66 98 76 34 Service Client IPeva tel: 0811 46 26 26 www.ipeva.fr - www.ipeva-studio.com Ce message et toutes les pièces jointes sont confidentiels et établis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisée est interdite. Tout message électronique est susceptible d'altération. IPeva décline toute responsabilité au titre de ce message s'il a été altéré, déformé ou falsifié. Si vous n'êtes pas destinataire de ce message, merci de le détruire immédiatement et d'avertir l'expéditeur. Le 27/05/2010 à 11:58, babak yakhchali a écrit :
yes you are right my ip phones are behind nat is there anyway to solve this? I checked the packet captures and found out that only the udp port is changed from 5060 to 49761. I'm using cisco 7941 ip phones. thanx _______________________________________________ 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
finally I found out what the scenario is: I captured packets on registration and I found out when registering, freeswitch uses port 5060 as destination even if incoming udp packets are from ports other than 5060. but during the call freeswitch uses the source port of the incoming packet and the problem arises. Is there anyway that I can force freeswitch to always use the port specified in via header? thanx
yes it's called rport On Thu, May 27, 2010 at 11:39 AM, babak yakhchali < babak.freeswitch@gmail.com> wrote:
finally I found out what the scenario is: I captured packets on registration and I found out when registering, freeswitch uses port 5060 as destination even if incoming udp packets are from ports other than 5060. but during the call freeswitch uses the source port of the incoming packet and the problem arises. Is there anyway that I can force freeswitch to always use the port specified in via header? thanx
_______________________________________________ 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
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900
force-rport David Ponzone Direction Technique email: david.ponzone@ipeva.fr tel: 01 74 03 18 97 gsm: 06 66 98 76 34 Service Client IPeva tel: 0811 46 26 26 www.ipeva.fr - www.ipeva-studio.com Ce message et toutes les pièces jointes sont confidentiels et établis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisée est interdite. Tout message électronique est susceptible d'altération. IPeva décline toute responsabilité au titre de ce message s'il a été altéré, déformé ou falsifié. Si vous n'êtes pas destinataire de ce message, merci de le détruire immédiatement et d'avertir l'expéditeur. Le 27/05/2010 à 18:39, babak yakhchali a écrit :
finally I found out what the scenario is: I captured packets on registration and I found out when registering, freeswitch uses port 5060 as destination even if incoming udp packets are from ports other than 5060. but during the call freeswitch uses the source port of the incoming packet and the problem arises. Is there anyway that I can force freeswitch to always use the port specified in via header? thanx _______________________________________________ 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
On May 27, 2010, at 11:39 AM, babak yakhchali wrote:
finally I found out what the scenario is: I captured packets on registration and I found out when registering, freeswitch uses port 5060 as destination even if incoming udp packets are from ports other than 5060. but during the call freeswitch uses the source port of the incoming packet and the problem arises.
That is why the client needs to enable rport. because when they register I suspect the contact said 5060 in it. We tend to do exactly what you tell us in the contact field unless rport is on.
Is there anyway that I can force freeswitch to always use the port specified in via header?
NDLB-force-rport on the profile but that can break some devices.
thanx
force-rport David Ponzone Direction Technique email: david.ponzone@ipeva.fr tel: 01 74 03 18 97 gsm: 06 66 98 76 34 Service Client IPeva tel: 0811 46 26 26 www.ipeva.fr - www.ipeva-studio.com Ce message et toutes les pièces jointes sont confidentiels et établis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisée est interdite. Tout message électronique est susceptible d'altération. IPeva décline toute responsabilité au titre de ce message s'il a été altéré, déformé ou falsifié. Si vous n'êtes pas destinataire de ce message, merci de le détruire immédiatement et d'avertir l'expéditeur. Le 27/05/2010 à 18:39, babak yakhchali a écrit :
finally I found out what the scenario is: I captured packets on registration and I found out when registering, freeswitch uses port 5060 as destination even if incoming udp packets are from ports other than 5060. but during the call freeswitch uses the source port of the incoming packet and the problem arises. Is there anyway that I can force freeswitch to always use the port specified in via header? thanx _______________________________________________ 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
thanx for ur answers but when I set ndlb force rport to true freeswitch responses with: 5060 (0x13C4) 49834 (0xC2AA) 192.168.11.30 192.168.7.211 SIP SIP:Response: SIP/2.0 407 Proxy Authentication Required
That means its send a challenge and the far end isn't answering check your username or password. /b On May 29, 2010, at 7:58 AM, babak yakhchali wrote:
thanx for ur answers but when I set ndlb force rport to true freeswitch responses with: 5060 (0x13C4) 49834 (0xC2AA) 192.168.11.30 192.168.7.211 SIP SIP:Response: SIP/2.0 407 Proxy Authentication Required
Hi brian I'm in a really bad situation. as I said before when I captured packets I found out: on first invite: every things good (responses to ip phones are sent to 5060 and ipphones work fine) on reinvites(invites during the call): problem! (invites are sent to 48796 and no response come from ipphones) on bye: (byes are sent to 48899):problem same as above! why freeswitch is changing behaviour?? thanx
Insufficient information. You need to pastebin everything relevant to the situation: Topology - the layout of your network, with routers/firewalls as well as the SIP endpoints Model numbers of all devices doing NAT in this scenario Model numbers of all IP phones in this scenario The complete SIP trace from start to finish -MC On Sat, May 29, 2010 at 6:19 AM, babak yakhchali <babak.freeswitch@gmail.com
wrote:
Hi brian I'm in a really bad situation. as I said before when I captured packets I found out: on first invite: every things good (responses to ip phones are sent to 5060 and ipphones work fine) on reinvites(invites during the call): problem! (invites are sent to 48796 and no response come from ipphones) on bye: (byes are sent to 48899):problem same as above! why freeswitch is changing behaviour?? thanx
_______________________________________________ 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
Hi all thanx for ur answers. problem solved (thanx to stkn on IRC) by disabling apply-nat-acl and setting external ip for sip and rtp to local-ipv4 (I think the acl was the problem). thank u all
participants (7)
-
Anthony Minessale
-
babak yakhchali
-
Brian West
-
David Ponzone
-
David Ponzone
-
Michael Collins
-
Michael S Collins