[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Sip] RFC 3326 question

To: sip@ietf.org
Subject: [Sip] RFC 3326 question
From: Oleg_Levy@vocaltec.com
Date: Thu, 20 Feb 2003 13:56:46 +0200
Cc: Alex_Fishman@vocaltec.com, Michael_Fortinsky@vocaltec.com, Avi_Damri@vocaltec.com
List-help: <mailto:sip-request@ietf.org?subject=help>
List-id: Session Initiation Protocol <sip.ietf.org>
List-post: <mailto:sip@ietf.org>
List-subscribe: <https://www1.ietf.org/mailman/listinfo/sip>,<mailto:sip-request@ietf.org?subject=subscribe>
List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>,<mailto:sip-request@ietf.org?subject=unsubscribe>
Sender: sip-admin@ietf.org

Hi

RFC3326 specifies a method for transferring the Cause parameter defined in Q.850. In ISUP interworking scenarios the Reason header is used in CANCEL requests to specify the cause value, however other parameters like Location are still not transferred.

What is the correct way to transfer the rest of the parameters?

regards

Oleg Levy
Team Leader
----------------------------------------------
VocalTec Communications Ltd.
Tel: +972-9-9707832
Cell: +972-55-655199
Fax: +972-9-9708505
eMail: buskila@vocaltec.com
----------------------------------------------

Prev by Date: RE: [Sip] I-D ACTION:draft-ietf-sip-congestsafe-01.txt
Next by Date: [Sip] Questions
Previous by thread: [Sip] I-D ACTION:draft-ietf-sip-congestsafe-01.txt
Next by thread: [Sip] Questions
Index(es):
- Date
- Thread