Igor, Who are your users? The implementers of the software on the other end?
Perhaps you could send a 491 Request Pending (ref RFC3261 section 14.2). The dialog is still there, waiting for 487 (CANCEL OK only signals that the CANCEL was succesful, it should not trigger any logic such as removing the dialog). 200 OK could be OK depending on what the INFO achieves in your scenario (eg if it contains some message for the user, and you display it, then OK would seem appropriate) Regards, Jeroen Igor Vanin wrote: > Hello, All > > My softphone supports incoming requests in outgoing dialogs in early > state. For example, the following scenario: Sent: INVITE > Received: 183 (INVITE) > Received: INFO (in the early dialog with the same tags as in 183) > Sent: 200 (INFO) > [...] > Received: 200 (INVITE) > Sent: ACK > It's ok. > > My question is related to the use case when the caller hangs up > (cancels the INVITE) before INFO is received: Sent: INVITE > Received: 183 (INVITE) > Sent: CANCEL > Received: 200 (CANCEL) > Received: INFO (with the same tags as in 183) > My softphone responds to this INFO with the 481 response code because > it considers that the early dialog and the call were destroyed when > the remote servers answered to my CANCEL with 200. > But my users are complaining to this behavior. They want to receive > 200 OK response to the INFO request. > What do you think, is this correct? MAY my softphone respond to the > INFO with 200 response when the initial INVITE was cancelled, or it > MUST respond to the INFO with 481 response because the early dialog > was terminated after successfull cancellation? _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
