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

RE: [Sipping] Comments of draft-ietf-sipping-isup-02

Title: RE: [Sipping] Comments of draft-ietf-sipping-isup-02
Adam,
Not really.  In the configuration of IP origination and PSTN termination, yes CANCEL occurs because of calling party abandon.  However in others, CANCEL may also be generated by MGC at the receipt of ISUP REL message containing various cause value.  The cause value can be
- 16 'normal call clearing', if it's a normal call release originating from PSTN caller, callee, or networks
- others, if it's an abnormal call release, e.g., timer fires, call setup failed, etc.
 
Jon,
However I do not understand why these ISUP cause values have to be conveyed in the Reason header.  Does it imply some SIP user agents would have appropriate ISUP functionality and like to react upon various ISUP causes?  Where would be that SIP user agents applied?
 
As the use of Content-Type header in CANCEL request is forbidden, some words in 6.2.3 have to be removed "...In SIP briding situations, a REL might arrive in the CANCEL...".
 
There would be nation-specific usage based on the ITU-T standard.  It would be easier to follow if there's another draft to describe how to do interworking between SIP and ITU-T ISUP.  But it seems not to be IETF's jobs to define for each variant, does it?
 
Moter
 
 
-----Original Message-----
From: Adam Roach [mailto:adam@dynamicsoft.com]
Sent: Tuesday, June 18, 2002 9:08 AM
To: 'Peterson, Jon'; 'Moter Du'; 'sipping@ietf.org'
Subject: RE: [Sipping] Comments of draft-ietf-sipping-isup-02

I'm a bit confused. In ISUP interworking, CANCEL will only ever occur because of calling party abandon -- right? Why do we need to convey cause codes in this situation? Won't it always be 16?
 
Also, the earlier versions of the ISUP draft actually included the concept of encapsulating ISUP in the CANCEL requests. We were soundly taunted for putting bodies in hop-by-hop messages (which are often generated anew at each hop), and finally removed it. 2543bis has further made this all but impossible by forbiding (in tables 2 & 3) the use of a "Content-Type" header in CANCEL requests.
 
/a
-----Original Message-----
From: Peterson, Jon [mailto:jon.peterson@neustar.biz]
Sent: Monday, June 17, 2002 19:17
To: 'Moter Du'; 'sipping@ietf.org'
Subject: RE: [Sipping] Comments of draft-ietf-sipping-isup-02

Thanks for both of these rounds of comments below. We'll make editorial changes as appropriate.
 
Note that work on the Reason header will allow a CANCEL to carry the cause code from an REL - effectively, the Reason header provides a way to preserve the cause code with translation rather than encapsulation. A BYE, on the other hand, is always normal clearing (16), as far as I know.
 
Thanks also for the tips on number portability mapping - capturing all of the conceivable national variants for NP is very difficult.
 
Jon Peterson
NeuStar, Inc.
-----Original Message-----
From: Moter Du [mailto:moter.du@siemens.com]
Sent: Friday, June 14, 2002 4:54 AM
To: 'sipping@ietf.org'
Subject: RE: [Sipping] Comments of draft-ietf-sipping-isup-02

trivia:

7.2.3 If no ACM..., "then" ISUP message...

8.2 The 200 in the figure should be right-to-left.  The ACK should be left-to-right.

Moter

-----Original Message-----
From: Moter Du [mailto:moter.du@siemens.com]
Sent: Wednesday, June 12, 2002 6:20 PM
To: 'sipping@ietf.org'
Subject: [Sipping] Comments of draft-ietf-sipping-isup-02


6.2.4 In the SIP bridging situation, the ISUP REL message may be included in the body of SIP responses, or SIP requests such as CANCEL or BYE.  The latter is applied when REL cause value is 16.

6.2.9 Reason phrase of 183 is "session" progress.
7.2.1.1 Just for your information.  Concerning number portability of the ITU-T variant, translated number can be found in either

- The digits prepended to called party number of CPN, if Nature of Address (NoA) is 8; the number of digits prepended are defined for national use, or determinated by a delimiter which is also for national use only.

- The optional Network Routing Number (NRN) parameter; in this case CPN would represent priorly called party number
- The Called Party Number (CPN) parameter, if an optional Called Directory Number (CDN) representing priorly called party number is present


Moter