1、 ETSI TS 103 161-15 V1.1.1 (2011-10) Access, Terminals, Transmission and Multiplexing (ATTM); Integrated Broadband Cable and Television Networks; IPCablecom 1.5; Part 15: Analog Trunking for PBX Specification Technical Specification ETSI ETSI TS 103 161-15 V1.1.1 (2011-10)2Reference DTS/ATTM-003011-
2、15 Keywords access, broadband, cable, IP, multimedia, PSTN ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Impor
3、tant notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the
4、 Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Infor
5、mation on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No pa
6、rt may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2011. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered
7、 for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 103 161-15 V1.1.1 (2011-10)3Contents Intellectual
8、Property Rights 5g3Foreword . 5g31 Scope 7g31.1 Introduction and Purpose 7g31.2 Relation to Other IPCablecom Specifications 7g31.3 NCS Package Requirements . 8g32 References 8g32.1 Normative references . 8g32.2 Informative references 8g33 Definitions and abbreviations . 9g33.1 Definitions 9g33.2 Abb
9、reviations . 9g34 Void 9g35 Overview 9g35.1 Functional Responsibility . 9g35.2 Physical Endpoint Interface 10g35.2.1 Loop-Start Line Interface 10g35.2.2 Ground-Start Line Interface 10g35.2.3 DID PBX Trunk Interface . 10g35.2.4 E Essential, or potentially Essential, IPRs notified to ETSI in respect o
10、f ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/ipr.etsi.org). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other I
11、PRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI Technical Committee Access, Terminals, Transmission and Multiplexing (ATTM). The
12、present document is part 15 of a multi-part IPCablecom 1.5 deliverable covering the Digital Broadband Cable Access to the Public Telecommunications Network; IP Multimedia Time Critical Services, as identified below: Part 1: “Overview“; Part 2: “Architectural framework for the delivery of time critic
13、al services over Cable Television Networks using Cable Modems“; Part 3: “Audio Codec Requirements for the Provision of Bi-Directional Audio Service over Cable Television Networks using Cable Modems“; Part 4: “Network Call Signalling Protocol“; Part 5: “Dynamic Quality of Service for the Provision of
14、 Real Time Services over Cable Television Networks using Cable Modems“; Part 6: “Event Message Specification“; Part 7: “Media Terminal Adapter (MTA Management Information Base (MIB)“; Part 8: “Network Call Signalling (NCS) MIB Requirements“; Part 9: “Security“; Part 10: “Management Information Base
15、(MIB) Framework“; Part 11: “Media terminal adapter (MTA) device provisioning“; Part 12: “Management Event Mechanism“; Part 13: “Trunking Gateway Control Protocol - MGCP option“; Part 14: “Embedded MTA Analog Interface and Powering Specification“ Part 15: “Analog Trunking for PBX Specification“; Part
16、 16: “Signalling for Call Management Server“; Part 17: “CMS Subscriber Provisioning Specification“; Part 18: “Media Terminal Adapter Extension MIB“; Part 19: “IPCablecom Audio Server Protocol Specification - MGCP option“; Part 20: “Management Event MIB Specification“; ETSI ETSI TS 103 161-15 V1.1.1
17、(2011-10)6Part 21: “Signalling Extension MIB Specification“. NOTE 1: Additional parts may be proposed and will be added to the list in future versions. NOTE 2: The choice of a multi-part format for this deliverable is to facilitate maintenance and future enhancements. ETSI ETSI TS 103 161-15 V1.1.1
18、(2011-10)71 Scope 1.1 Introduction and Purpose The present document defines extensions to the IPCablecom Network-based Call Signalling (NCS) 2 protocol to support the following analogue trunking for PBX interfaces on an embedded Voice-Over-IP client device in a IPCablecom environment: Ground-start l
19、ines. PBX one-way and two-way DTMF (dual-tone multi frequency tones) trunks. As shown in figure 1, the IPCablecom NCS specification 2 already defines the Loop-Start line interface typically used for residential services today. The present document is designed for additional line/trunk interfaces to
20、support analogue trunking for PBX so that the MTA (multimedia terminal adapter) may be used to interface directly to a Legacy PBX via a Ground-Start line or other trunk interface (E Integrated Broadband Cable and Television Networks; IPCablecom 1.5; Part 4: Network Call Signalling Protocol“.“. 3 TIA
21、-464-C: “Requirements for Private Branch Exchange (PBX) Switching Equipment“. 4 IETF RFC 2833: “RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals“, May 2000. 5 ITU-T Recommendation T.38: “Procedures for real-time group 3 facsimile communication over IP networks“, September 2010. 2.2
22、 Informative references The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. i.1 Telcordia GR-31-CORE LSSGR, Issue 4: “CLASS Feature: Calling Number Delivery“, June 2006. i.2 Telcordia GR-1
23、188: “LSSGR CLASS Feature: Calling Name Delivery, Generic Requirements“, April 2009. i.3 ANSI 0600407: “Network-to-Customer Installation Interfaces - Direct Inward Dialing Analog Voicegrade Switched Access Using Loop Reverse-Battery Signaling“, formerly T1.405. i.4 Telcordia GR-506: “LSSGR: Signalin
24、g for Analog Interfaces“, December 2006. ETSI ETSI TS 103 161-15 V1.1.1 (2011-10)93 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions following apply: endpoint: terminal, gateway or Multipoint Conference Unit (MCU) gateway: devices brid
25、ging between the IPCablecom IP Voice Communication world and the PSTN NOTE: Examples are the Media Gateway, which provides the bearer circuit interfaces to the PSTN and transcodes the media stream, and the Signalling Gateway, which sends and receives circuit switched network signalling to the edge o
26、f the IPCablecom network. trunk: analogue or digital connection from a circuit switch that carries user media content and may carry voice signalling (MF, R2, etc.) 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CAS Channel Associated Signalling CMS Cal
27、l Management Server DID Direct Inward Dialling DOD Direct Outward Dialling DTMF Dual-tone Multi Frequency (tones) E however, other interfaces may also be used. The following clauses describe each physical interface that may be provided on an MTA to support one or more of the above defined PBX trunks
28、. 5.2.1 Loop-Start Line Interface The NCS Line package defined in the IPCablecom NCS specification 2 is used to support loop-start lines. Loop-start lines are typically used for residential voice services, but may be used to support analogue trunking for PBX. 5.2.2 Ground-Start Line Interface Ground
29、-start signalling interfaces are used to provide two-way service to customer-installation switching systems, e.g. legacy PBX systems. According to 1 ground-start signalling for two-way dial facilities was introduced to reduce the likelihood of seizure of the line at both ends during the silent inter
30、val of the alerting signal. Ground-start signalling is typically used on one-way or two-way seizure PBX lines with Direct Outward Dialling (DOD) and attendant-handled incoming call service. Ground-start lines are also used for automatically originated data service. The two-wire ground-start line con
31、ductors transmit common-battery loop supervision, loop dial pulses or DTMF address signals, alerting signals, and voice-band signals. Ground-start lines are often used rather than loop-start lines for the following reasons: To avoid simultaneous seizure, i.e. glare conditions. To allow the applicati
32、on of a dc voltage between tip and ring and the closure of a path from the tip conductor to ground as a start dial signal. To provide a positive indication of network disconnect. See 1 for the network interface requirements for ground-start access lines. 5.2.3 DID PBX Trunk Interface A one-way Direc
33、t Inward Dialling (DID) trunk interface as described in 3 is required to support a DID interface of a PBX. DID trunks can only make calls in the direction from the network towards the PBX. Electrically, a DID trunk looks similar to the reverse of a 2-wire loop-start interface. The PBX provides loop
34、current by applying -48 volt battery to the ring lead and grounding the tip lead. The MTA signals off-hook and on-hook towards the PBX by closing and opening the loop. The PBX signals answer supervision (off-hook) by reversing battery and ground on the tip and ring leads i.3. The PBX signals call re
35、lease (on-hook) by restoring battery to ring and ground to tip. Since this is a one-way trunk, there is no ringing voltage as seen on a loop-start interface. The MTA may dial using either dial-pulse at 10 pulses per second with 300 ms between digits or DTMF at 10 tones per second. Dial-pulse may be
36、done either by opening and closing the loop in a manner similar to loop-start dialling; or it may use battery and ground pulsing. With dial-pulse interfaces, the network typically only dials the last 2 or 3 address digits to minimize call setup delay. ETSI ETSI TS 103 161-15 V1.1.1 (2011-10)11The in
37、terface has three methods for start of dialling: Immediate start - The MTA starts dial-pulsing shortly after closing the loop indicating off-hook condition. This method cannot be used for DTMF. Wink start - The MTA waits for the PBX to signal that it is ready to accept digits. The signal from the PB
38、X is a 200 ms battery reversal (off-hook). Delay start - The MTA waits for the PBX to signal that it is ready to accept digits. The signal from the PBX is a battery reversal of at least 100 ms (off-hook) followed by restoration of battery (on-hook) some time later. Of the three start-of-dialling met
39、hods, wink start is most common. 5.2.4 E however, the Call Agent may alternatively use the Line package Caller ID signal to provide caller ID information. Though the PBX typically only expects to receive caller ID information during call setup, the Call Agent may use the Line package Caller ID signa
40、l to attempt to display caller ID when the PBX is off-hook (e.g. Caller ID with Call Waiting). To maintain as much flexibility as possible with the use of the NCS Line package the endpoint must honour such a request and attempt to deliver the caller ID information as defined in NCS. The same is true
41、 of VMWI. Though the PBX typically does not expect to receive VMWI information, the Call Agent may use the Line package VMWI signal. To maintain as much flexibility as possible with the use of the NCS Line package the endpoint must honour such a request and attempt to deliver the VMWI information as
42、 defined in NCS. 6.2.5 Hook Events For all physical interface types, the NCS Line package hook events (L/hd, L/hf, L/hu) are used to indicate hook state at the PBX. For LS/GS, hook events are detected and generated as defined in NCS. Similarly, for E however, an off-hook event must not be generated
43、when this condition occurs. Instead the endpoint must be taken out of service and an RSIP Forced must be sent to the Call Agent. 6.2.6 Open Signal Interval For loop-start lines the L/osi NCS Line package signal is used as a trigger for the endpoint to perform a “timed disconnect release“. For ground
44、-start lines, the signal is used as a trigger for the endpoint to provide a “guard release“ which has similar characteristics to the loop-start “timed disconnect release“. This signal is defined in i.4 in general terms as an “open signal interval“ for both loop-start and ground-start interfaces. ETS
45、I ETSI TS 103 161-15 V1.1.1 (2011-10)17For all PBX trunks, the PAT/rel signal is used as a trigger for the PBX to release the call. For LS/GS the semantics are identical to the L/osi signal. In order to maintain the concept of a physical layer abstraction to the Call Agent and to provide the increas
46、ed flexibility of the L/osi signal for LS/GS, the L/osi signal is further defined to be identical to the PAT/rel signal for E however, the Call Agent may alternatively use the Line package RG signal to provide ringing. Though the PBX typically only expects to receive standard ringing, the Call Agent
47、 may request other defined the Line package ring signals (R0 - R7, RS) to seize the trunk. To maintain as much flexibility as possible with the use of the NCS Line package the endpoint must honour such a request and attempt to seize the trunk using the defined ring signal. 6.2.8 T1 Trunk Signalling
48、Requirements T1 is a digital trunk interface. As such, the signalling between the MTA and PBX required to support one-way incoming, one-way outgoing and two-way PBX trunks is emulated using Channel Associated Signalling (CAS). The signalling between the MTA and Call Agent, however, remains unchanged
49、. In other words, the fact that the physical interface is emulated digitally is of no consequence to the Call Agent. ETSI ETSI TS 103 161-15 V1.1.1 (2011-10)18Annex A (normative): Event Packages This clause defines a set of event packages for the various types of endpoints currently defined by IPCablecom for embedded clients. Each package defines a package name for the package and event codes and definitions for each of the events in the package. In the tables of events/signals for each package, there are five columns: Code The pac
