Re: [Megaco] Last Call On Four Documents
Christian Groves <Christian.Groves@ericsson.com.au> Wed, 17 October 2001 07:22 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA15620 for <megaco-archive@odin.ietf.org>; Wed, 17 Oct 2001 03:22:30 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA13933; Wed, 17 Oct 2001 02:59:59 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA13906 for <megaco@ns.ietf.org>; Wed, 17 Oct 2001 02:59:57 -0400 (EDT)
Received: from newish7.ericsson.com.au (newish7.ericsson.com.au [203.61.155.116]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14598 for <megaco@ietf.org>; Wed, 17 Oct 2001 02:59:54 -0400 (EDT)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10]) by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id QAA09534; Wed, 17 Oct 2001 16:58:41 +1000 (EST)
Received: from ericsson.com.au (mcdh126.epa.ericsson.se [146.11.81.126]) by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id QAA01720; Wed, 17 Oct 2001 16:59:48 +1000 (EST)
Message-ID: <3BCD2C87.88CE8D85@ericsson.com.au>
Date: Wed, 17 Oct 2001 17:00:23 +1000
From: Christian Groves <Christian.Groves@ericsson.com.au>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "'megaco@ietf.org'" <megaco@ietf.org>
CC: Tom-PT Taylor <taylor@nortelnetworks.com>, Rune Boman <Rune.Boman@etx.ericsson.se>
Subject: Re: [Megaco] Last Call On Four Documents
References: <28560036253BD41191A10000F8BCBD110514FC51@zcard00g.ca.nortel.com>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org
Content-Transfer-Encoding: 8bit
G'Day, Below are some questions on the CAS package from a colleague. Cheers, Christian COMMENTS TO H.248 CAS PACKAGE These comments relates to draft-manyfolks-megaco-caspackage-01.txt Section 4, introduction: What is "feature group D (FGD) MF signalling sigle stage dialling". Does it prevents overlap signalling? Is feature group D a certain functionality package in north amerika (like class 4, class 5 exchanges?) What is FGD operator services ? Is it assistance operators or trunk offering operators or call centers? Section 5, 4th part: "For some applications, CAS package provides all of the functionality neededÂ…". What is actualy meant with "some applications". Is functionality missing for other applications ? Is R2 counted as other applications ? Section 6.3.4, Event name Clear back; and also section 7: Is "robbed bit signalling digital interface interface" the same thing as "bit stealing in TS16 in T1" ? It seemes to be something else knitted to the on-hook condition on an access only ? Section 6.6.1 Glare procedures: Is glare exactly the same procedure as "double seizure" in R1/R2 specifications for ITU-T ? Section 8.4.1 Ringback: Is this signalling to calling user from an assistance operator ? This is not covered in ITU-T R1 Rec. Section 9.3.1 Recall: Is this the same as a reanswer signal from the called user. It seems to be something else, since it is mentioned in the Operator services package. Section 9 general: All the operator services and signals mentioned, are not specified in ITU-T R1 and R2. Are they all related to american operator services. Why is trunk-offering and cancelling missing, or is that the same as "operator attached" and "operator released" ? Section 15.1 Basic single-stage MF or wink start or immediate start: "Wink start" and "immediate start" is not part of the ITU-T R2 signalling , where "seizure acknowledgement" signal is always used and not part of ITU-T R1, where "Delay dialling and start dialling (proceed-to-send) are used. "Wink start sounds like a signal used nationally (or within a region). No reference: Is also CAS signalling system number 5 and 5bis covered by this draft. Where are the key pulses for transit and terminating indication specified? In R1 and C5 the KP is like a normal MF digit. Is it regarded as a digit also in this specification? In system C5 the line signals are compelled (like the register signalling in R2). Is the intention that the MGW handles these compelled cycles autonomuously? Tom-PT Taylor wrote: > > I would like to declare List Last Call on the following documents: > > draft-manyfolks-megaco-caspackage-01.txt, Megaco/H.248 Basic CAS > Packages > draft-bothwell-megaco-mftonepkgs-02.txt, MF Tone Generation and > Detection Packages > draft-boyle-megaco-tonepkgs-06.txt, Supplemental Tones Packages for > Megaco/H.248 > draft-ietf-megaco-naspkg-03.txt, Megaco/H.248 NAS Packages > > The latter two documents have already had a last call, but were > revised. The tones package, in particular, had the Q.1950 packages > stripped out in response to IESG concerns. The remaining packages are > unchanged from before, but the complete document is much shorter. I > have had one comment that the phrasing of the document should state > clearly that Q.1950 provides a number of packages suitable for > Megaco/H.248 use, to which these are a supplement. > > I will forward each document to the IESG at the later of October 24 or > the date all outstanding issues are resolved. > > Tom Taylor > taylor@nortelnetworks.com > Ph. +1 613 736 0961 (ESN 396 1490) > _______________________________________________ Megaco mailing list Megaco@ietf.org http://www1.ietf.org/mailman/listinfo/megaco
- [Megaco] Last Call On Four Documents Tom-PT Taylor
- Re: [Megaco] Last Call On Four Documents Christian Groves
- FW: [Megaco] Last Call On Four Documents Tom-PT Taylor
- RE: [Megaco] Last Call On Four Documents Kevin Boyle