I would recommend session timer (RFC 4028). The two UAs (your B2BUA and the
other endpoint), and any proxies in the signaling path, negotiate to agree
on the session refresh interval and who will send the refresh request.
Then, periodically one UA sends a refresh request (re-INVITE or UPDATE) and
the other sends a response. If the timer times out with no refresh request
or response seen, those remaining alive can kill the call.
There are other mechanisms a UA can use, too. I've seem some that send a
periodic INFO request to the other UA, and if they don't get a response,
they kill the call. And any UA, B2BUA or not, can periodically send a
re-INVITE or UPDATE as a session refresh request. Even if nobody else on
the signaling path supports 4028.
But I like 4028 because if both UAs support it, they can agree on how often
to do a session refresh and who will do it.
Dave Robbins
Verizon Laboratories
40 Sylvan Rd.
Waltham, MA 02451-1128
781 466 4188
[EMAIL PROTECTED]
st.net
Sent by: To
sip-implementors- [email protected]
[EMAIL PROTECTED] cc
ia.edu
Subject
Re: [Sip-implementors] Releasing a
09/29/06 08:09 AM Call by B2BUserAgent when one of
the endpoints reboots during the
active call
From: HemalShah <[EMAIL PROTECTED]>
I have to implement Releasing of the call from B2BUserAgent when one of
the endpoints involved in the call is reboots.
I want to know that, Is there any draft or RFC available for this?
Or what should be the best way to implement this.
In general, a SIP UA can't tell if the UA at the other end has ceased
participating in a dialog unless the far-end UA sends a BYE. But if
both UAs support the "session timer" mechanism, a UA can determine if
the other UA has stopped responding.
Some B2BUAs and PSTN gateways will assume that if the other UA stops
sending RTP for long enough, the other UA has abandoned the dialog,
but this method is not reliable and I've heard of B2BUAs that hang up
when the other UA puts the call on hold.
Dale
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
