It doesn't have to be SIP OPTIONS. It can be anything as long as it's
sent to the server from the same UDP socket. For example, the MicroSIP
windows client sends 2 bytes 0x0D 0x0A every dozen of seconds.
This keeps a NAT state and allows subsequent SIP Register messages to be
sent to the server from the same source port.
Since dispatcher is a different module than UAC Registrant, I assume it
creates its own UDP connections meaning the packets will be sent to the
server from a different source port and will be treated as a new
session/binding.
I want to sent all subsequent SIP register messages from the same source
port. Otherwise, the VoIP provider will terminate the ongoing phone call.
W dniu 15.04.2025 o 15:05, Pavel Eremin pisze:
if i understood, you whant to send options to provider you registered to?
May be this is some kind of workaround, but you can add providers into
dispatcher module and check their statuses via OPTIONS.
пн, 14 апр. 2025 г. в 19:26, Thomas <[email protected]>:
Hi everyone.
Is there any keepalive feature available to keep a NAT state for UAC
Registrant module which connects through UDP to VoIP provider?
Something like Asterisk's pjsip qualify_frequency that sends SIP OPTIONS
message every xx seconds.
It is useful if you use opensips as a proxy and it's behind NAT.
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
