I don't think this is configurable now.  However, I think this is a good point.   Why don't you create a jira feature request perhaps we can catch it one of the future iterations.


On Thursday, 04 November, 2010 09:46 PM, Burden, Mike wrote:

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?

 

cid:image001.jpg@01C85750.45790B60

 Mike Burden

Lynk.gif
Lynk Systems, Inc

 Phone: 616-532-4985

 www.lynk.com






 

_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/



_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to