RE: [reSIProcate] NAT SIP keep alives

["Matthias Moetje - TERASENS GmbH" <moetje@xxxxxxxxxxxx>]

Sergio,

to make this work you must also

    auto_ptr<KeepAliveManager> keepAlive(new KeepAliveManager());
    mDum->setKeepAliveManager(keepAlive);


Best regards,

Matthias Moetje

> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On 
> Behalf Of Scott Godin
> Sent: Friday, March 31, 2006 4:08 PM
> To: 'Sergio García Murillo'; resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [reSIProcate] NAT SIP keep alives
> 
> Yes DUM has support for this - have a look at the various 
> Profile settings - there are 2 related to keepalives.  One 
> setting for UDP packets and one for TCP.  Use these settings 
> to tell resip to send CRLF packets.
> 
> Scott 
> 
> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On 
> Behalf Of Sergio García Murillo
> Sent: Friday, March 31, 2006 7:00 AM
> To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [reSIProcate] NAT SIP keep alives
> 
> Hi all
> 
> I'm running a client behind a NAT firewall connected with an 
> external proxy doing symmetric signaling to avoid the nat.
> The problem is that after some short time the client stops 
> receiving invites from the proxy because of the firewall 
> drops the nat entry.
> Is it possible to periodically send an empty packet to the 
> proxy (a keep alive as x-lite does) to maintain the nat open 
> at the firewall??
> I can't use register whit short time values because the proxy 
> rejects registering with shorts expiration values.
> 
> Greetings
>               Sergio
> --------------------------------------------------------------
> --------------
> ----------
> This message and any files transmitted with it are 
> confidential and intended solely for the use of the 
> individual or entity to whom they are addressed.
> No confidentiality or privilege is waived or lost by any 
> wrong transmission.
> 
> If you have received this message in error, please 
> immediately destroy it and kindly notify the sender by reply email.
> You must not, directly or indirectly, use, disclose, 
> distribute, print, or copy any part of this message if you 
> are not the intended recipient.
> Opinions, conclusions and other information in this message 
> that do not relate to the official business of Ydilo Advanced 
> Voice Solutions, S.A.
> shall be understood as neither given nor endorsed by it. 
> --------------------------------------------------------------
> --------------
> ----------
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
> 
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>