You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When a device registers to the OpenSIPS registrar and nathelper is pinging it using the OPTIONS method, each SIP OPTIONS packet sent will have the same "branch=" value in the SIP Via header and same "CSeq: 1 OPTIONS"
The "branch" is meant to be unique for each transaction.
OpenSIPS will even use the same "branch=" value when sending SIP OPTIONS to multiple different endpoint devices registered with the same username.
This confuses some endpoint devices that then reply with a Call-ID associated with the incorrect OPTIONS and OpenSIPS thinks that the device has become unreachable.
To Reproduce
Set up OpenSIPS as a registrar with nathelper enabled and register an endpoint device using SIP over UDP (5060).
Expected behavior
The "branch" should be unique for each transaction and, accordingly, each SIP OPTIONS packet sent by OpenSIPS (with the possible exception of retransmissions within the retransmission timer).
Relevant System Logs
No logs
OS/environment information
Operating System: Ubuntu Linux 22.04.5, kernel 5.15.0-91-generic, x86_64
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days.
OpenSIPS version you are running
Describe the bug
When a device registers to the OpenSIPS registrar and nathelper is pinging it using the OPTIONS method, each SIP OPTIONS packet sent will have the same "branch=" value in the SIP Via header and same "CSeq: 1 OPTIONS"
The "branch" is meant to be unique for each transaction.
OpenSIPS will even use the same "branch=" value when sending SIP OPTIONS to multiple different endpoint devices registered with the same username.
This confuses some endpoint devices that then reply with a Call-ID associated with the incorrect OPTIONS and OpenSIPS thinks that the device has become unreachable.
To Reproduce
Set up OpenSIPS as a registrar with nathelper enabled and register an endpoint device using SIP over UDP (5060).
loadmodule "nathelper.so"
modparam("nathelper", "max_pings_lost", 3)
modparam("nathelper", "natping_interval", 60)
modparam("nathelper", "natping_partitions", 8)
modparam("nathelper", "natping_tcp", 1)
modparam("nathelper", "ping_nated_only", 0)
modparam("nathelper", "ping_threshold", 3)
modparam("nathelper", "sipping_bflag", "SIP_PING_FLAG")
modparam("nathelper", "sipping_from", "sip:[email protected]")
modparam("nathelper", "sipping_latency_flag", "SIP_PING_FLAG")
modparam("nathelper", "remove_on_timeout_bflag", "SIP_PING_FLAG")
modparam("nathelper", "sipping_method", "OPTIONS")
modparam("nathelper", "received_avp", "$avp(received_nh)")
Expected behavior
The "branch" should be unique for each transaction and, accordingly, each SIP OPTIONS packet sent by OpenSIPS (with the possible exception of retransmissions within the retransmission timer).
Relevant System Logs
No logs
OS/environment information
Additional context
The text was updated successfully, but these errors were encountered: