Common use of Signaling Requirements Clause in Contracts

Signaling Requirements. ‌ 3.1 Signaling protocol. The Parties will interconnect their networks using SS7 signaling where technically feasible and available as defined in FR 905 Bellcore Standards including ISDN user part ("ISUP") for trunk signaling and Transaction Capabilities Application Part ("TCAP") for CCS-based features in the interconnection of their networks. All Network Interoperability Interface Forum (NIIF) adopted standards shall be adhered to. 3.2 Where available, CCS signaling shall be used by the Parties to set up calls between the Parties' Telephone Exchange Service networks. If CCS signaling is unavailable, the Parties shall use MF (Multi-Frequency) signaling. 3.3 The following list of publications describe the practices, procedures and specifications generally utilized by the industry for signaling purposes and are listed herein to assist the Parties in meeting their respective interconnection responsibilities related to signaling: GR-000246-CORE, Xxxx Communications Research Specifications of Signaling System 7 (“SS7”) GR-000317-CORE, Switching System Requirements for Call Control Using the Integrated Services Digital Network User Part GR-000394-CORE, Switching System Requirements for Interexchange Carrier Interconnection Using the Integrated Services Digital Network User Part GR-000606-CORE, LATA Switching Systems Generic Requirements- Common Channel Signaling-§6.5 GR-000905-CORE, Common Channel Signaling Network Interface Specification Supporting Network Interconnection Message Transfer Part (“MTP”) and Integrated Digital Services Network User Part (“ISDNUP”) 3.4 The Parties will cooperate on the exchange of Transactional Capabilities Application Part (TCAP) messages to facilitate interoperability of CCS-based features between their respective networks, including all CLASS features and functions, to the extent each Party offers such features and functions to its end users. All CCS signaling parameters will be provided including, without limitation, Calling Party Number (CPN), Originating Line Information (“OLI”), calling party category and charge number. 3.5 Where available each Party shall cooperate to ensure that all of its trunk groups are configured utilizing the B8ZS ESF protocol for 64 kbps clear channel transmission to allow for ISDN interoperability between the Parties' respective networks. 3.6 The Parties shall jointly develop a grooming plan (the "Joint Grooming Plan") which shall define and detail, inter alia, 3.6.1 disaster recovery provisions and escalations; 3.6.2 direct/high usage trunk engineering guidelines; and 3.6.3 such other matters as the Parties may agree. 3.7 If a Party makes a change in its network, which it believes will materially affect the interoperability of its network with the other Party, the Party making the change shall provide thirty- (30) days advance written notice of such change to the other Party.

Signaling Requirements. ‌ 3.1 Signaling protocol. The Parties will interconnect their networks using SS7 signaling where technically feasible and available as defined in FR 905 Bellcore Standards including ISDN user part ("ISUP") for trunk signaling and Transaction Capabilities Application Part ("TCAP") for CCS-based features in the interconnection of their networks. All Network Interoperability Interface Forum (NIIF) adopted standards shall be adhered to. 3.2 Where available, CCS signaling shall be used by the Parties to set up calls between the Parties' Telephone Exchange Service networks. If CCS signaling is unavailable, the Parties shall use MF (Multi-Frequency) signaling. 3.3 The following list of publications describe the practices, procedures and specifications generally utilized by the industry for signaling purposes and are listed herein to assist the Parties in meeting their respective interconnection responsibilities related to signaling: GR-000246-CORE, Xxxx Communications Research Specifications of Signaling System 7 (“SS7”) GR-000317-CORE, Switching System Requirements for Call Control Using the Integrated Services Digital Network User Part GR-000394-CORE, Switching System Requirements for Interexchange Carrier Interconnection Using the Integrated Services Digital Network User Part GR-000606-CORE, LATA Switching Systems Generic Requirements- Common Channel Signaling-§6.5 GR-000905-CORE, Common Channel Signaling Network Interface Specification Supporting Network Interconnection Message Transfer Part (“MTP”) and Integrated Digital Services Network User Part (“ISDNUP”) 3.4 The Parties will cooperate on the exchange of Transactional Capabilities Application Part (TCAP) messages to facilitate interoperability of CCS-based features between their respective networks, including all CLASS features and functions, to the extent each Party offers such features and functions to its end usersEnd Users. All CCS signaling parameters will be provided including, without limitation, Calling Party Number (CPN), Originating Line Information (“OLI”), calling party category and charge number. 3.5 Where available each Party shall cooperate to ensure that all of its trunk groups are configured utilizing the B8ZS ESF protocol for 64 kbps clear channel transmission to allow for ISDN interoperability between the Parties' respective networks. 3.6 The Parties shall jointly develop a grooming plan (the "Joint Grooming Plan") which shall define and detail, inter alia, 3.6.1 disaster recovery provisions and escalations; 3.6.2 direct/high usage trunk engineering guidelines; and 3.6.3 such other matters as the Parties may agree. 3.7 If a Party makes a change in its network, which it believes will materially affect the interoperability of its network with the other Party, the Party making the change shall provide thirty- thirty (30) days advance written notice of such change to the other Party.

Signaling Requirements. ‌ 3.1 Signaling protocol. The Parties will interconnect their networks using SS7 signaling where technically feasible and available as defined in FR 905 Bellcore Standards including ISDN user part ("ISUP") for trunk signaling and Transaction Capabilities Application Part ("TCAP") for CCS-based features in the interconnection of their networks. All Network Interoperability Interface Forum (NIIF) adopted standards shall be adhered to. 3.2 Where available, CCS signaling shall be used by the Parties to set up calls between the Parties' Telephone Exchange Service networks. If CCS signaling is unavailable, the Parties shall use MF (Multi-Frequency) signaling. 3.3 The following list of publications describe the practices, procedures and specifications generally utilized by the industry for signaling purposes and are listed herein to assist the Parties in meeting their respective interconnection responsibilities related to signaling: GR-000246-CORE, Xxxx Bell Communications Research Specifications of Signaling System 7 (“SS7”) GR-000317-CORE, Switching System Requirements for Call Control Using the Integrated Services Digital Network User Part GR-000394-CORE, Switching System Requirements for Interexchange Carrier Interconnection Using the Integrated Services Digital Network User Part GR-000606-CORE, LATA Switching Systems Generic Requirements- Common Channel Signaling-§6.5 GR-000905-CORE, Common Channel Signaling Network Interface Specification Supporting Network Interconnection Message Transfer Part (“MTP”) and Integrated Digital Services Network User Part (“ISDNUP”) 3.4 The Parties will cooperate on the exchange of Transactional Capabilities Application Part (TCAP) messages to facilitate interoperability of CCS-based features between their respective networks, including all CLASS features and functions, to the extent each Party offers such features and functions to its end users. All CCS signaling parameters will be provided including, without limitation, Calling Party Number (CPN), Originating Line Information (“OLI”), calling party category and charge number. 3.5 Where available each Party shall cooperate to ensure that all of its trunk groups are configured utilizing the B8ZS ESF protocol for 64 kbps clear channel transmission to allow for ISDN interoperability between the Parties' respective networks. 3.6 The Parties shall jointly develop a grooming plan (the "Joint Grooming Plan") which shall define and detail, inter alia, 3.6.1 disaster recovery provisions and escalations; 3.6.2 direct/high usage trunk engineering guidelines; and 3.6.3 such other matters as the Parties may agree. 3.7 If a Party makes a change in its network, which it believes will materially affect the interoperability of its network with the other Party, the Party making the change shall provide thirty- thirty (30) days advance written notice of such change to the other Party.