ANSI SCTE 165-11:2019 pdf download.IPCablecom 1.5-Part 11: Analog Trunking for PBX Specification.
As shown in Figure 1 below, the lPCablecom NCS specification [NCS] already defines the Loop-Start line interface typically used for residential services today. This specification is designed for additional line/tnink interfaces to support analog trun king for PBX so that the MTA may be used to interface directly to a Legacy PBX via a Ground- Start line or other trunk interface (E&M or DID). Example PBX trunk interfaces are shown below.
1.3 NCS Package Requirements
The IPCablecorn analog trunking for PBX (PAT) package is defined in this specification as an extension to the NCS Line package to provide the needed functionality specific to analog trunking for PBX. Both packages arc required to support analog trunking for PL3X. It should bc noted that the PAT package is designed in such a way as to provide a complete abstraction of the physical characteristics of an endpoint to the Call Agent. For example, the Call Agent is unaware of the physical endpoint interface (e.g., E&M or DID), start of dialing method (e.g., wink start), and out- pulse dialing type (e.g., DTMF). This abstraction exists due to time-to-market considerations. As such, the endpoint is required to alter its behavior based on these physical characteristics given a particular command from the Call Agent. In some cases this behavior breaks the general rules of NCS. The exceptions to NCS are documented in this specification and apply only to analog trunking for PBX.
1.4 Requirements and Conventions
Throughout this document, the words that are used to define the significance of particular requirements are capitalized. These words are:
“MUST” This word means that the item is an absolute requirement of this specification.
“MUST NOT” This phrase means that the item is an absolute prohibition of this specification.
“SHOULD” This word means that there may exist valid reasons in particular circumstances to ignore this item, but the full implications should be understood and the case carefully weighed before choosing a different course.
“SHOULD NOT” This phrase means that there may exist valid reasons in particular circumstances when the listed behavior is acceptable or even useful, but the full implications should be understood and the case careftilly weighed before implementing any behavior described with this label.
“MAY” This word means that this item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because it enhances the product, for example; another vendor may omit the same item.ANSI SCTE 165-11 pdf download.