Re: [Serusers] Too Many Hops

Greger I am trying to get a cascading hierarchy of geographically separated SIP servers. The reason for this is that I am providing services to a wireless community that connect to the internet via many different gateways to the internet. Most of the users are behind a nat device, and connect to a SER proxy on the wireless net work on the 10.0.0.0/8 network. Each SER server keeps a local location database, but forwards any requests that it cannot complete to a sip proxy on the internet (to which each SER proxy replicates all REGISTER's). It looks a bit like this: UAC(192.168.0.123)--->WIFI_AP(10.1.2.3)---->WIFI_GATEWAY_1--->INTERNET for browsing / email / ftp etc | | v SER_SERVER on WiFi network (10.0.0.123) also has (public IP Address)--->INTERNET GATEWAY for VOIP 1--->SER_SERVER on internet ^ | UAC(192.168.0.234)--->WIFI_AP(10.3.4.5)---->WIFI_GATEWAY_2--->INTERNET for browsing / email / ftp etc | | | | | v | SER_SERVER on WiFi network (10.3.4.123) | also has (public IP Address)--->INTERNET GATEWAY for VOIP 2----- Each SER server implements it's own far end nat traversal based on nathelper/rtpproxy, which means that expensive internet links are not used to terminate calls between subscribers on the same wifi network. The issue I was having with loose routing appeared to be because the SER_SERVER on the WiFi network was multihomed. When a reply cam back from the ser server on the internet (I think it was only ACK's causing the problem), SER tried to loose_route the reply and the next hop was infact the servers own internal ip address. After loosing much hair, I worked out that if I included the condition I could get the packet to route through to the correct final destination. I am not sure if it's because there is a REAL issue with loose_route not working with mhomed properly, or if it's a peculiarity of my setup. Noel Greger V. Teigre wrote: