Trunk Configuration Sample Clauses

Trunk Configuration. 4.3.1.1 Where available and upon the request of the other Party, each Party shall cooperate to ensure that its trunk groups are configured utilizing the B8ZS ESF protocol for 64 kbps Clear Channel Capability (64CCC) transmission to allow for ISDN interoperability between the Parties’ respective networks. Trunk groups configured for 64CCC and carrying Circuit Switched Data (CSD) ISDN calls shall carry the appropriate Trunk Type Modifier in the CLCI-Message code. Trunk groups configured for 64CCC and not used to carry CSD ISDN calls shall carry a different appropriate Trunk Type Modifier in the CLCI-Message code.
View SourceView Similar (24)
Trunk Configuration. SBC SOUTHWEST REGION 5-STATE, SBC MIDWEST REGION 5-STATE and SBC CONNECTICUT 4.6.1.1 Where available and upon the request of the other Party, each Party shall cooperate to ensure that its trunk groups are configured utilizing the Bipolar 8 Zero Substitution Extended Super Frame (B8ZS ESF) protocol for 64 kbps Clear Channel Capability (64CCC) transmission to allow for ISDN interoperability between the Parties’ respective networks. Trunk groups configured for 64CCC and carrying Circuit Switched Data (CSD) ISDN calls shall carry the appropriate Trunk Type Modifier in the CLCI-Message code. Trunk groups configured for 64CCC and not used to carry CSD ISDN calls shall carry a different appropriate Trunk Type Modifier in the CLCI- Message code. 4.6.1.2 The Lucent 1AESS switch is incapable of handling 64CCC traffic. Therefore, all trunk groups established to the 1AESS switches must use Alternate ▇▇▇▇ Inversion (AMI).
View Source
Trunk Configuration. AT&T SOUTHWEST REGION 5-STATE, AT&T MIDWEST REGION 5- STATE and AT&T CONNECTICUT 4.5.1.1 Where available and upon the request of the other Party, each Party shall cooperate to ensure that its trunk groups are configured utilizing the Bipolar 8 Zero Substitution Extended Super Frame (B8ZS ESF) protocol for 64 kbps Clear Channel Capability (64CCC) transmission to allow for ISDN interoperability between the Parties’ respective networks. Trunk groups configured for 64CCC and carrying Circuit Switched Data (CSD) ISDN calls shall carry the appropriate Trunk Type Modifier in the CLCI-Message code. Trunk groups configured for 64CCC and not used to carry CSD ISDN calls shall carry a different appropriate Trunk Type Modifier in the CLCI-Message code.
View Source
Trunk Configuration. 4.3.1.1 Where available and upon the request of the other Party, each Party shall cooperate to ensure that its trunk groups are configured utilizing the B8ZS ESF protocol for 64 kbps Clear Channel Capability (64CCC) transmission to allow for ISDN interoperability between the Parties’ respective networks. Trunk groups configured for 64CCC and carrying Circuit Switched Data
View Source

Related to Trunk Configuration

  • Configuration Agency will work independently to configure Agency’s API Client with API Service for Agency’s applicable Use. Agency will be required to provide certain information (such as identification or contact details) as part of the registration. Registration information provided to Axon must be accurate. Agency will inform Axon promptly of any updates. Upon Agency’s registration, Axon will provide documentation outlining API Service information.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Functionality Customer is entitled to additional functionality previously purchased or bundled with the software if available in the version or update released on or after the start date of the Agreement. Customer acknowledges that certain functionality in current and previous software versions may not be available in future upgrades. Added functionality may require additional paid services (clinical and technical) to configure and support.