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

Re: [Sip] Reason header simplification

To: Rohan Mahy <rohan@cisco.com>
Subject: Re: [Sip] Reason header simplification
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Date: Tue, 19 Mar 2002 16:45:07 -0600
CC: gonzalo.camarillo@ericsson.com, sip@ietf.org
List-Id: Session Initiation Protocol <sip.ietf.org>
Organization: Columbia University
References: <Pine.WNT.4.44.0203191216270.-645261@chorizo.rapidconvergence.com>
Sender: sip-admin@ietf.org

> Also I don't like to idea of sending ISUP (Q.850) or ISDN (Q.931) response
> codes around inside a SIP network.  I'd rather use standard ISUP-SIP or
> ISDN-SIP cause code translation, so that an ordinary SIP UA can just use a
> set of well-defined SIP cause codes.
> 

Is this translation one-to-one? Which table did you have in mind? I
suspect that unless there's a one-to-one translation, you might want to
include both, with the user agent displaying whatever makes sense (and
leaving Q.850 codes for debugging).

_______________________________________________
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

References:
- [Sip] Reason header simplification
  - From: Rohan Mahy

Prev by Date: [Sip] REFER ABNF issues
Next by Date: [Sip] Conferencing Bar Ad Hoc
Previous by thread: Re: [Sip] Thoughts on the reason header field scope
Next by thread: RE: [Sip] Reason header simplification
Index(es):
- Date
- Thread