Vijay, Too many hops errors are normally a result of a loop, so you probably want to trace a SIP message through the system to see where it’s being routed. You should be able to do this by increasing the log level on the Sprout and Bono nodes, and then looking for the messages in the logs. Alternatively, you can capture the messages in a packet capture using TCP dump if they are being routed between Sprout and Bono, and then viewing it in Wireshark.
The maximum hop count isn’t a configuration option – instead it’s provided by the SIP endpoint on the “Max-Forwards” header. If it’s not set, it’ll be defaulted to 70, as per the SIP RFC – see section 16.6, step 3 https://tools.ietf.org/html/rfc3261#section-16.6. Cheers, Richard From: Clearwater [mailto:[email protected]] On Behalf Of Vijay Sent: 12 August 2016 21:12 To: [email protected] Subject: [Project Clearwater] Too many hops error Hello, I am using Kubernetes to deploy clearwater. I have scscf.sprout kubernetes service created. In bono and sprout /etc/clearwater/shared_config, for upstream_hostname, if I use the full address of the service, I get "too many Hop"s error when the clients try to register. I had to replace that by ip address of the container (which may change if it crashes or restarts). Is there a way to set the hop count or any other configuration settings? Thanks!
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
