[Sip] INVITE after terminated dialog?

"Jane Jiang" <janej@hq.speakeasy.net> Wed, 02 January 2008 01:29 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J9sPm-0006yI-Hb; Tue, 01 Jan 2008 20:29:02 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1J4Uuy-0007Ey-PO for sip-confirm+ok@megatron.ietf.org; Tue, 18 Dec 2007 00:23:00 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1J4Uuy-0007Eo-Fw for sip@ietf.org; Tue, 18 Dec 2007 00:23:00 -0500
Received: from [] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J4UuI-00074I-LM for sip@ietf.org; Tue, 18 Dec 2007 00:22:18 -0500
Received: from itclus2.sea5.speakeasy.net ([] helo=EXCHANGE-BE2.speakeasy.net) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J4UuI-00047i-1T for sip@ietf.org; Tue, 18 Dec 2007 00:22:18 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 17 Dec 2007 21:22:16 -0800
Message-ID: <DED0424C02C83A4AB0419517605CD11E02F5D329@EXCHANGE-BE2.speakeasy.hq>
Thread-Topic: INVITE after terminated dialog?
Thread-Index: AchBNfSdslABBfwHRKqeaIPMhx+1OA==
From: Jane Jiang <janej@hq.speakeasy.net>
To: sip@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c
X-TMDA-Confirmed: Tue, 18 Dec 2007 00:23:00 -0500
X-Mailman-Approved-At: Tue, 01 Jan 2008 20:29:00 -0500
Subject: [Sip] INVITE after terminated dialog?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0257386767=="
Errors-To: sip-bounces@ietf.org

Hi All,
There is a weird situation with us:
(1) A Linksys phone sends an INVITE out with incorrect destination TN.
As a result, our application server will set up a call between the
Linksys phone and an IVR
(2) A user incorrectly hits the on-hold key, which is basically sending
a re-INVITE to the IVR
(3) Our server seems to have answered the re-INVITE with a BYE
(4) The Linksys phone responds to the BYE with a 200
(5) Afterwards, the Linksys phone still thinks that its original
re-INVITE has not been responded.  So, it will keep resend re-INVITE
The consequence of these re-INVITEs is a registration migration, which
we don't like.  We have been trying to figure out which side is not
following RFC 3261, the phone, the SBCs are wrong, or the application
I am wondering:
(A) Is it legal for a server to ignore the re-INVITE and respond with a
BYE and has nothing in between?
(B) If a UA has responded to a BYE with 200, is it supposed to forget
about the re-INVITE request that it has sent out and not try to resend
the re-INVITE, assuming a dialog has already been terminated with the
BYE/200 transaction?  Maybe in another sentence, is it legal to send our
re-INVITEs outside an dialog, even if these re-INVITEs are the repeats
of an original in-dialog re-INVITE?
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip