mxc wrote: > Hi all, > > We have a strange problem. The architecture is for a SIP trunk with a fail > over link as backup. The setup is as follows: > > 1) Asterisk box registers with SIP provider using endian as its default > gateway, > 2)Endian box is set to has a wifi and 2 ADSL links, > 3) WIFI link is set to fail over to one of the ADSL line, > 4) On Endian we have a routing policy rule to route all traffic by WIFI > coming from the Asterisk box, > 5) When WIFI link is up - all works as designed, > 4) When the WIFI link goes down, which is often, we can see the change in > the IPTABLEs mangle table is set correctly to mark traffic from the asterisk > box. We can also see that the right routing database is being used by > matching the mark from iptables to the ip rule which tells it to use the > correct route > 5) From the Asterisk box traceroute shows that icmp messages are being > routed over the correct link when the WIFI link goes up and down. > > However the asterisk box will not register over the new route. Its > registration requests just time out. If we reboot the endian box then the > registrations go through over which ever link is appropriate i.e. over ADSL > if the wifi link is down and over WIFI if it is up. I am at a loss of how to > explain this from a technical point of view. The SIP provider claims that > they are not getting any registration requests but they could wrong on this. > Basically I don' trust them. I am pretty sure its not Endians problem but am > stuck to explain why rebooting sorts this out. One of the reasons I don't > believe its endian is because we had a similar problem when they were just > using an ADSL modem and we tried to change the ADSL account. It simply > refused to register over the new ADSL account until we put the old one back. > What I am trying to understand is what could be happening? > > The only explanation I can think of is that somehow the SIP server > (external)/ or endian is holding a TCP session open and that this is > preventing the new session from being established? But according to my > understanding of TCP/IP this should not be possible when the one link goes > down. > > Any help appreciated. > > > I don't know if this is exactly the same problem, but it may help.
I had a similar problem with registration with a sip provider when my dynamic ip address changed. If my net connection dropped out for whatever reason, it was assigned a new IP address. This process usually takes a few seconds. My asterisk box would drop its registration and start trying to register again, but I would never receive any replys from the SIP provider. (gotalk in Aus). Pings etc worked fine from the asterisk box, and every other type of connection I could think of at the time. I found that if I rebooted my asterisk server it would register happily. What was happening was that the SIP provider had somehow kept the last IP address I had and was sending replies to that address, even though the new IP was properly sent in the registration request. I found out that they used a system that decided if you were behind a NAT router to set a timeout of 3 minutes for your session. After this period expired they would forget my old IP and use whatever new one the register request came from. Rebooting my asterisk server took a bit longer than 3 minutes so the period had expired. ( I think that a non-NAT session had a timeout of 30 mins) I used iftop mostly to find this out with captures from tcpdump and wireshark, and lots and lots of googling. Maybe its a similar thing ? Hope this helps, Col ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Efw-user mailing list Efw-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/efw-user
