10 Apr
2013
10 Apr
'13
5:11 p.m.
Remember that Outbound also works for UDP. In that case:
a) The Outbound Flow Token (the URI username in the Record-Route) must
encode the public source IP:port of the request, and the Outbound
proxy must be capable of encoding and decoding it for routing the
request to the client (OverSIP does it).
b) The client should keepalive via STUN PING requests.
Anyhow, nothing prevents Kamailio to mantain the keepalive by sending
OPTIONS or whatever, as currently it does when using other NAT-fix
custom mechanisms.
Regards.
2013/4/10 Peter Dunkley <peter.dunkley(a)crocodile-rcs.com>om>:
When using a non-outbound client like Jitsi you can
keep-alive by getting it
to re-REGISTER, OPTIONS ping, or '\r\n' frequently.
IMHO that is far better solution than having the server run timers and
generate keep-alives.
Regards,
Peter
On 10/04/13 13:53, Klaus Darilion wrote:
--
Iñaki Baz Castillo
<ibc(a)aliax.net>
Who does keep-alive when outbound is used? If it is the client, then there
still must be some tweaks in the server as the non-outbound client will not
send keep-alive.
regards
klaus
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users