Re: [reSIProcate-users] Sending CANCEL does not trigger onTerminated?

[Francesco Lamonica <alienpenguin@xxxxxxxxx>]

Thanks for you explanations :)

On Thu, Jun 1, 2017 at 3:13 PM, Scott Godin <sgodin@xxxxxxxxxxxxxxx> wrote:

Hi Francesco,

It is expected.  You should only receive an onTerminated callback if you ever received an onNewSession callback, and that doesn't some until the first dialog-creating non-100 response.  If you created an AppDialogSet for the call, it will be deleted when the cancel is performed.  If needed you could use that as form of notification.

http://www.resiprocate.org/DUM_Ending_an_Invite_Session

Scott

On Wed, May 31, 2017 at 1:16 PM, Francesco Lamonica <alienpenguin@xxxxxxxxx> wrote:

Hi Scott and all,

i was experimenting with resiprocate on linux64 and in a simple app i have a CallData class derived from AppDialogSet and i am using that to end the SIP call for sending both CANCEL and BYE using the end() method (is this the correct way to end the call?)

however i noticed that when CANCEL is sent (because session is not yet set up) then the onTerminated callback is never called.

Is this expected behaviour?

best regards

Francesco 

_______________________________________________
resiprocate-users mailing list
resiprocate-users@resiprocate.org
List Archive: http://list.resiprocate.org/archive/resiprocate-users/