Ohh ya. I have just disabled nat_traversal and removed nat_keepalive();
Need to add the bflag properly which actually fixed my issue.
Thank your help!
On Wed, Mar 11, 2020 at 6:59 PM Liviu Chircu <li...@opensips.org> wrote:
> On 09.03.2020 02:24, Jehanzaib Younis wrote:
> > if (is_method("REGISTER")) {
> > fix_nated_register();
> > nat_keepalive();
>
> Hi, Jehanzaib!
>
> Bingo! This is the cause of your strange double-pinging. You are using
> two NAT pinging modules at the same time: nathelper + nat_traversal.
> And, of course, nat_traversal will keep on pinging the old value until
> its "virtual expiration" timer kicks in, ignoring the fact that the
> contact actually got refreshed within the user location by a new
> binding, xx.xxx.xx.xx:25004.
>
> Possible solutions:
>
> * stop using nat_traversal
> * stop using nathelper
> * keep using them both, but be careful not to arm them simultaneously
> (can be tricky)
>
> Regards,
>
> --
> Liviu Chircu
> www.twitter.com/liviuchircu | www.opensips-solutions.com
>
> OpenSIPS Summit, Amsterdam, May 2020
> www.opensips.org/events
>
>
> _______________________________________________
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
--
Regards,
Jehanzaib
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
