Your sequence diagram is wrong, below is what should happen

> Caller--------------------------------------------------Callee
> 
> INVITE---------------------------------------------------->
> <-------------------------------------------------------100 Trying
>                              +--------------------------200 OK
>                              |
> CANCEL-----------------------|--------------------------->
>                              |
> <----------------------------|--------------------------200 (To CANCEL)
>                              |
> <----------------------------+
> ACK(to 200)---------------------------------------------->
> BYE --------------------------------------------------------->
> <--------------------------------------------------------------- 200 ok to BYE

Regards,
Hisham


> -----Original Message-----
> From: ext nicky [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, March 07, 2002 2:00 AM
> To: [EMAIL PROTECTED]
> Subject: [Sip-implementors] transaction questions
> 
> 
> I have two transaction questions:
> 
> 1. Consider the following scenario:
> 
> Caller--------------------------------------------------Callee
> 
> INVITE---------------------------------------------------->
> <-------------------------------------------------------100 Trying
>                              +--------------------------200 OK
>                              |
> CANCEL-----------------------|--------------------------->
>                              |
> <----------------------------|--------------------------481(To CANCEL)
>                              |
> <----------------------------+
> ACK(to 200)---------------------------------------------->
> 
> Here, the 200 response is delayed until the CANCEL's 481 
> response is received. Firstly, is this call flow correct? 
> Secondly, What should the callee do on receipt of the ACK? 
> Should it drop or accept the ACK? Why?
> 
> 2. I don't know why the "Proceeding" state on the figure of 
> INVITE client transaction doesn't contain a timer. If the 
> client's network is disconnected in this state, it seems the 
> client will remain in "Proceeding" forever.
> 
> 
>             nicky
>             [EMAIL PROTECTED]
> 
> _______________________________________________
> Sip-implementors mailing list
> [EMAIL PROTECTED]
> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
> 
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Reply via email to