RE: [reSIProcate] KeepAliveManager usage
To enable keep alive messages you only need to call:
auto_prt<KeepAliveManager> keepAlive(new KeepAliveManager);
dum->setKeepAliveManager(keepAlive);
and
dum->getMasterProfile()->setKeepAliveTime(30); // 30 seconds
There is no notification to the application if sending the keep alive
results in a TCP disconnection or a failed UDP send - although the next
SIP message sent, will likely cause a 4xx response to be returned from
the stack (if the connection is still lost).
Scott
PS. I've added these notes to:
http://warsaw.sjc.purplecomm.com/wiki/index.php?title=DUM_Keep_Alive_Man
ager
-----Original Message-----
From: Sandro Bordacchini [mailto:sandro@xxxxxx]
Sent: Monday, August 01, 2005 12:08 PM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate] KeepAliveManager usage
Hi all.
I'm currently developing a SIP application with dum.
I'd like to add a keep alive check on active UAs.
Where can I find some hints on KeepAliveManager usage?
I suppose it had to be initialized with setDialogUsageManager and
"started"/"stopped" (on a single UA) with 'add' and 'remove' methods.
But how (and when) the 'process' method has to be called?
What type of messages/exceptions does it throws when a UA becomes
unreachable...?
Thanks a lot.
--
Ing. Sandro Bordacchini
SIS s.r.l.
Via Cottolengo, 21
56100 Pisa (Italy)
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel