Hi Chen-Che,
I know what the RFC says, but unfortunately the real life (out there is
the SIP wild) is totally different - Consider you have a user calling to
PSTN (a call you will have to pay to carrier); if you detect the user
dropped, would you simply stop your billing without being 100% that the
PSTN side also stopped ? if you do not BYE the PSTN, would you take the
risk of having a ghost call in the PSTN that you will get charged for ??
My 2 cents on the matter....
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 04/10/2013 04:16 AM, microx wrote:
Hi Max and Bogdan-Andrei,
Very grateful for your comments. However, at a first glance, I find that RFC
4208 says in Section 8.3:
"When the current time equals or passes the session expiration for a
session, the proxy MAY remove associated call state, and MAY free any
resources associated with the call. Unlike the UA, it *MUST NOT* send a
BYE."
If I don't misunderstand it, RFC 4208 requires a proxy server not to send a
BYE to the other user agent in my issue. RFC 4208 seems to suggest that the
two UAs are responsible for whether their session has timeout. So I guess I
don't have to implement any mechanism to terminate that kind of dialog in my
issue. Any comment is appreciated.
Best wishes,
Chen-Che
--
View this message in context:
http://opensips-open-sip-server.1449251.n2.nabble.com/What-to-do-when-one-user-agent-leaves-suddenly-tp7585727p7585758.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users