[EME] SIP signalling and 3GPP
Gaguk Zakaria <gzakaria@hns.com> Mon, 16 July 2007 18:03 UTC
Return-path: <eme-bounces@irtf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAUvJ-00059e-U4; Mon, 16 Jul 2007 14:03:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAUvI-00057f-Lv for eme@irtf.org; Mon, 16 Jul 2007 14:03:52 -0400
Received: from hnse2.hns.com ([208.236.67.201]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IAUvE-0005nT-B4 for eme@irtf.org; Mon, 16 Jul 2007 14:03:52 -0400
Received: from excore8.hns.com (excore8.hns.com [139.85.52.126]) by hnse2.hns.com (Switch-3.1.9/Switch-3.1.9) with ESMTP id l6GI3kj7009305 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for <eme@irtf.org>; Mon, 16 Jul 2007 14:03:47 -0400 (EDT)
Received: from atlas (atlas.hns.com [139.85.177.110]) by excore8.hns.com (Switch-3.1.9/Switch-3.1.9) with ESMTP id l6GI3jEd012019 for <eme@irtf.org>; Mon, 16 Jul 2007 14:03:45 -0400 (EDT)
To: eme@irtf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001
Message-ID: <OFD2C272FC.396D66F6-ON8525731A.0061DD3C@notesgw.hns.com>
From: Gaguk Zakaria <gzakaria@hns.com>
Date: Mon, 16 Jul 2007 14:03:41 -0400
X-MIMETrack: S/MIME Sign by Notes Client on Gaguk Zakaria/HNS(Release 5.0.8 |June 18, 2001) at 07/16/2007 02:03:47 PM, Serialize by Notes Client on Gaguk Zakaria/HNS(Release 5.0.8 |June 18, 2001) at 07/16/2007 02:03:47 PM, Serialize complete at 07/16/2007 02:03:47 PM, S/MIME Sign failed at 07/16/2007 02:03:47 PM: The cryptographic key was not found, Serialize by Router on Atlas/HNS(Release 6.5.1|January 21, 2004) at 07/16/2007 14:03:45, Serialize complete at 07/16/2007 14:03:45
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Subject: [EME] SIP signalling and 3GPP
X-BeenThere: eme@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: end-middle-end research group <eme.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/eme>, <mailto:eme-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/eme>
List-Post: <mailto:eme@irtf.org>
List-Help: <mailto:eme-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/eme>, <mailto:eme-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2037421504=="
Errors-To: eme-bounces@irtf.org
Hi I have question regarding SIP signalling and its application at 3gpp IMS 1. In almost all examples in the 3GPP doc regarding SIP signalling, when a UA sends an INVITE message, the called party usually replies it with a provisional response 183 Session Progress. My question is that if the INVITE message consists of only ONE media type, meaning there is no need of media negotiation, does the called party still need to reply it with 183 Session Progress. Can the called party just reply with 200 OK or nor acceptable? 2. Does the P-CSCF require the arrival of 183 Session Progress message, as the provisional response of the INVITE, to authorize reource (authorize QoS). Can P-CSCF authorize resource (QoS) based on the INVITE message if the INVITE message consists of only one media type. Gaguk
_______________________________________________ EME mailing list EME@irtf.org https://www1.ietf.org/mailman/listinfo/eme
- [EME] SIP signalling and 3GPP Gaguk Zakaria
- RE: [EME] SIP signalling and 3GPP Paul Francis