SIP OPTIONS PING messages return 483 with hops=0. 200 ok with hops=70 (default)
I am a relatively new Voice Tech in charge of setup, monitoring, and troubleshooting our company's NN3820 SBCs running ECx6.4.0 MR3 P1.
I'm starting to monitor Sessions using the Web-interface 'Monitor and Trace' > Sessions after noticing that we're getting very many sessions with state = FAILED, where status received is 483 - Too Many Hops. These are occuring in response to SIP OPTIONS Pings sent to our Carrier.
In checking, i've determined we were sending these with hops=0 which i've also researched to find seems to be defacto standard for OPTIONS PING messages. I have determined that Pings sent from our carrier to our SBCs are returning Status 200 Ok. These also i've noticed have hops=70 which seems to be default if not specified for heartbeat / keep alive.