Hello Vallimamod,
The best way to keep a user behind nat, is sending OPTIONS:
modparam("nathelper", "natping_interval", 30)
modparam("nathelper", "ping_nated_only", 0)
modparam("nathelper", "sipping_bflag", 7)
modparam("nathelper", "sipping_from", "sip:pinger@PROXY_IP")
>From the book: "Building Telephony Systems with OpenSIPS" Flavio E
Goncalves:
"The parameters natping_interval, ping_nated_only, sipping_bflag, and
sipping_from, controls how to ping the clients to maintain the NAT mapping
open. Most of these parameters are self explanatory, but pay attention to
the
sipping_bflag. If the bflag is set to 7, the NATHELPER module will ping
using an OPTIONS SIP request from the address established in the parameter
sipping_from. It is much safer to use the OPTIONS request instead of a dummy
UDP packet, because some NAT implementations require an outbound packet to
keep the NAT mapping open and the client will answer the OPTIONS request
with
any SIP response, which will do the trick."
Regards!
2011/2/4 Vallimamod ABDULLAH <[email protected]>
> Hello,
>
> On Feb 4, 2011, at 11:03 AM, Iñaki Baz Castillo wrote:
>
> > [...]
> > And the server is responsible for keeping the registrations and not
> > loosing them when restarting.
> > [...]
>
> Just a related question: what about the nat binding ?
> Does the nathelper module keep sending the keep-alive message for natted
> phones after restart ?
>
> I have noticed that sometime phones behind nat are not able to receive
> incoming calls or presence notifications upon server restart but I did not
> have time to look at it yet.
>
> Regards,
> Vallimamod Abdullah
> .
> _______________________________________________
> 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
