Hi Tito,
A ping cannot be empty - if it is empty, it is not a ping :) . Maybe it
is the UDP ping (the 4 bytes of zero value) ?? If so, it means you did
not set the NAT_SIP_PINGS branch flag when the contact was registered
(before the save(location)).
IF you do opensipsctl ul show, you should see the saved branch flags.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS Summit 2018
http://www.opensips.org/events/Summit-2018Amsterdam
On 04/13/2018 01:28 AM, Tito Cumpen wrote:
Hello,
I am using opensips 2.3 git rev. 3a66b9c and I am noticing that sip
options pings to wss clients are sent with no body at all. I am using
SIP.js/0.7. and see that the options sent when using :
modparam("nathelper", "natping_interval", 10)
modparam("nathelper", "natping_tcp", 1)
modparam("nathelper", "sipping_from", "sip:pin...@mydomain.net
")
modparam("nathelper", "remove_on_timeout_bflag", "RM_ONTO_FLAG")
modparam("nathelper", "sipping_bflag", "NAT_SIP_PINGS")
are empty and therefore the these clients cannot be monitored because
sipjs dismisses the empty messages
Thu Apr 12 2018 18:27:14 GMT-0400 (EDT) | sip.parser | no CRLF found,
not a SIP message, discarded
sip-0.7.7.min.js:36 Thu Apr 12 2018 18:27:23 GMT-0400 (EDT) |
sip.transport | received WebSocket text message:
Thanks,
Tito
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
