nvite is in the chain.
Cheers, Johan.
From: Jan Bollen [mailto:jan.bol...@scarlet.be]
Sent: dinsdag 8 oktober 2013 9:15
To: sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip-implementors] Terminating early dialog with BYE. - Email
found in subject
Hello,
The question is: where is the &qu
Hi Jan ,
First of all let me clarify diff between CANCEL and BYE ,then we will be in
better position to understand what to use when ..
As you know multiple early dialogs might be present due to forking
1. BYE is sent to terminate a specific dialog(early or confirmed) as to-tag
present in BYE
Hello,
The question is: where is the "pending" request in the presented
scenario with the BYE sent in a early dialogue.
The same RFC also states:
"The notion of "hanging up" is not well defined within SIP.
It is
specific to a partic
Hi Pravin
It is recommended for UAS to send 487 for pending requests in such
scenarios.
Refer Section 15.1.2 of RFC 3261:
" The UAS MUST still respond to any pending requests received for that
dialog. It is RECOMMENDED that a 487 (Request Terminated) response be
generated to those pending request
According to RFC 3261:
Early Dialog can be terminate sending by BYE or CANCEL for UAC side.
In case of CANCEL we should send 487 for INVITE
UAC UAS
-INVITE->
< -180--
--CANCEL--- >
< -200
