RE: Signaling MIB - Draft 3 - Last Call - pktcSigDevToneT ype (Issue 3)
Beacham Gordon-CGB005 <[email protected]>
| Newsgroups | gmane.ietf.ipcdn |
|---|---|
| Message-ID | <D5A7E45D575DD61180130002A5DB377C06528BA7@ca25exm01> |
Upon review of ITU spec, supplement 2, and ES 201 970, Motorola further disagrees with the deletion of the following additional items from the pktcSigDevToneType object: alertingSignal(17), specialDial(18), specialInfo(19), release(20), congestion(21) To ensure these objects can also be signaled, Motorola is initiating a proposal to modify TS 909-101 part 4, appendix B.4 to include NCS line codes and other parameters. Gordon -----Original Message----- From: Beacham Gordon-CGB005 Sent: Friday, January 23, 2004 10:11 AM To: '[email protected]' Subject: RE: [ipcdn] Signaling MIB - Draft 3 - Last Call - pktcSigDevToneType (Issue 3) Motorola disagrees with the deletion of the following items from the pktcSigDevToneType object: userDefined1 (13), userDefined2 (14), userDefined3 (15), userDefined4 (16) These objects are required by several international operators to support additional signals for their networks. To ensure these user defined objects can be signaled, Motorola is initiating a proposal to modify TS 909-101 part 4, appendix B.4 to include NCS line codes and other parameters. For example: Code Description Signal ps1 Programmable Signal 1 TO ps2 Programmable Signal 2 TO ps3 Programmable Signal 3 TO ps4 Programmable Signal 4 TO The ITU spec, supplement 2 to 180 will also be reviewed to see if more than four user defined signals are required for the pktcSigDevToneType object. Gordon Beacham Digital Core Gateways, BCS Motorola, Inc. 858-404-2335 [email protected]