________________________________________ From: [email protected] [[email protected]] On Behalf Of Burden, Mike [[email protected]]
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? __________________________________________ You should also check into how the originating calls have such a small number of hops. It would be a Bad Idea for any component to add to the Max-Forwards count. If you did that, a forwarding loop might generate a message that would pass through SIP components an infinite number of times. One place to reduce the number of hops that sipXecs consumes is to combine the "forwarding" and "authentication" passes of a message through sipXproxy. We have been intending to fix that for a long time, but have never gotten around to doing the work. That would reduce the consumption of hops in sipXecs by a factor of 2. Dale _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
