Some calls are coming into sipXecs with a low number (5 of less, sometimes 3 or less) hops remaining.
The ITSP says that the calls arrive at their switch that way. Looking at the sipxtrace, it looks like the modular architecture of sipXecs "eats" a lot of hops (ITSP to sipXbridge, sipXbridge to sipXproxy, sipXproxy to sipXregistrar), causing the call to fail with "Too many hops." Is there a way to cause the sipXecs system as a whole to only treat itself as one Hop (I hope that some other means of loop detection is in place?) Alternately, is there some way for the sipXbridge to add a few extra hops to the incoming call to account for this? Mike Burden [cid:image002.gif@01CB7C05.299432D0] Lynk Systems, Inc Phone: 616-532-4985 www.lynk.com<http://www.lynk.com>
<<inline: image001.jpg>>
<<inline: image002.gif>>
_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
