| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index | Next in Thread > |
|
onTerminated is meant to be symetric to onNewSession.
Since there is no onNewSession call, there is no onTerminated
call.
Scott From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Dillip Sent: Friday, April 07, 2006 2:06 PM To: 'Dillip'; resiprocate-devel@xxxxxxxxxxxxxxxxxxx Subject: RE: [reSIProcate] Cancel a Call before receiving 180. Hi
All, The
use case here I have is bit different : è
User
A makes a call to B. è
At the
user A’s end, before it
receives 180 from the server (
immediately after it
receives “100 – Trying ..” )
, sends CANCEL to terminate the call( using AppDialogSetHandle::end()). Note
that ,at this point of time, the session has not yet been
created.
The request was successfully processed and gets the response back
from the server with “487 Request
Terminated”. But, the problem here was.. it never sends a
termination event to the higher layer. This is probably due to DUM object was
being deleted inside DialogSet::end() function and thus was unable to dispatch
onTerminated() event to the higher layer. The changes I made here
are : In DialogSet::end()
function ,I commented out mDum->destroy() to keep mDum alive and added a
case On487Invite in
ClientInviteSession::dispatchStart() function and it seems to be working fine. I
would like to know, whether it is the right way to do
this. Thank you very
much.! -Dillip
From:
resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Dillip Hello, How do I CANCEL an OUTGOING
Call before it receives 180 from the server or the session is
initiated? Thanks in
advance. -Dillip |