Common use of Signaling Transfer Points (STPs Clause in Contracts

Signaling Transfer Points (STPs. 3.1 Definition. Signaling Transfer Points (STPs) provide functionality that enable the exchange of SS7 messages among and between switching elements, database elements and signaling transfer points. 3.2 Technical Requirements - Signaling Transfer Points 3.2.1 STPs must provide access to all other Network Elements connected to the SBC MISSOURI SS7 network. These include: 3.2.1.1 SBC MISSOURI Local Switching or Tandem Switching; 3.2.1.2 SBC MISSOURI Service Control Points/DataBases; 3.2.1.3 Third-party local or Tandem Switching Systems; and 3.2.1.4 Third-party-provided STPs. 3.2.2 The connectivity provided by STPs must fully support the functions of all other Network Elements connected to SBC MISSOURI's SS7 network. This explicitly includes the use of SBC MISSOURI's SS7 network to convey messages which neither originate nor terminate at a signaling end point directly connected to the SBC MISSOURI SS7 network (i.e., transit messages). When the SBC MISSOURI SS7 network is used to convey transit messages, there must be no alteration of the Integrated Services Digital Network User Part (ISDNUP) or Transaction Capabilities Application Part (TCAP) user data that constitutes the content of the message. 3.2.3 If a SBC MISSOURI tandem Switch routes calling traffic, based on dialed or translated digits, on SS7 trunks between an MCIm local Switch and third party local Switch, SBC MISSOURI's SS7 network must convey the TCAP messages that are necessary to provide Call Management features (Automatic Callback, Automatic Recall, and Screening List Editing) between the MCIm local STPs and the STPs that provide connectivity with the third party local Switch, even if the third party local Switch is not directly connected to SBC MISSOURI's STPs. 3.2.4 STPs must provide all functions of the Message Transfer Port (“MTP”). This includes: 3.2.4.1 Signaling Data Link functions; 3.2.4.2 Signaling Link functions; and 3.2.4.3 Signaling Network Management functions. 3.2.5 STPs must provide all functions of the SCCP necessary for Class 0 (basic connectionless) service. In particular, this includes Global Title Translation (GTT) and SCCP Management procedures. 3.2.6 In cases where the destination signaling point is a SBC MISSOURI local or tandem switching system or database, or is an MCIm or third party local or tandem switching system directly connected to SBC MISSOURI's SS7 network, SBC MISSOURI STPs must perform final GTT of messages to the destination and SCCP Subsystem Management of the destination. In all other cases, STPs must perform intermediate GTT of messages to a gateway pair of STPs in an SS7 network connected with the SBC MISSOURI SS7 network, and must not perform SCCP Subsystem Management of the destination. 3.2.7 STPs must also provide the capability to route SCCP messages based on ISNI and intermediate network selection messages when these capabilities become available on SBC MISSOURI STPs. 3.2.8 STPs must provide all functions of the OMAP commonly provided by STPs, including the following: 3.2.8.1 MTP Routing Verification Test (MRVT); and, 3.2.8.2 SCCP Routing Verification Test (SRVT). 3.2.9 In cases where the destination signaling point is a SBC MISSOURI local or tandem switching system or DB, or is an MCIm or third party local or tandem switching system directly connected to the SBC MISSOURI SS7 network, STPs must perform MRVT and SRVT to the destination signaling point. In all other cases, STPs must perform MRVT and SRVT to a gateway pair of STPs in an SS7 network connected with the SBC MISSOURI SS7 network. This requirement will be superseded by the specifications for Internetwork MRVT and SRVT if and when these become approved ANSI standards and available capabilities of SBC MISSOURI STPs. 3.3 Interface Requirements - Signaling Transport Points 3.3.1 SBC MISSOURI shall provide the following STPs options to connect MCIm or MCIm- designated local switching systems or STPs to the SBC MISSOURI SS7 network: 3.3.1.1 An A-link interface from MCIm local switching systems; and, 3.3.2 Each type of interface must be provided by one or more sets (layers) of signaling links, as follows: 3.3.2.1 An A-link layer shall consist of two links. 3.3.3 The Signaling point of Interconnection (SPOI) for each link must be located at a cross- connect element, such as a DSX-1, in the Central Office (CO) where the SBC MISSOURI STPs is located. There must be a DSl or higher rate transport interface at each of the SPOIs. Each signaling link shall appear as a DS0 channel within the DS1 or higher rate interface. SBC MISSOURI shall offer higher rate DS1 signaling for interconnecting MCIm local switching systems or STPs with SBC MISSOURI STPs as soon as these become approved ANSI standards and available capabilities of SBC MISSOURI STPs. 3.3.4 SBC MISSOURI shall provide MTP and SCCP protocol interfaces. 3.4 Message Screening 3.4.1 SBC MISSOURI shall set message screening parameters so as to accept messages from MCIm local or tandem switching systems destined to any signaling point in the SBC MISSOURI SS7 network with which the MCIm switching system has a legitimate signaling relation. 3.4.2 SBC MISSOURI shall set message screening parameters so as to accept messages from MCIm local or tandem switching systems destined to any signaling point or network interconnected to the SBC MISSOURI SS7 network with which the MCIm switching system has a legitimate signaling relation. 3.4.3 SBC MISSOURI shall set message screening parameters so as to accept messages destined to an MCIm local or tandem switching system from any signaling point or network interconnected to the SBC MISSOURI SS7 network with which the MCIm switching system has a legitimate signaling relation. 3.4.4 SBC MISSOURI shall set message screening parameters so as to accept and send messages destined to an MCIm SCP from any signaling point or network interconnected to the SBC MISSOURI SS7 network with which the MCIm SCP has a legitimate signaling relation.

Appears in 1 contract

Samples: Ss7 Signaling Agreement

AutoNDA by SimpleDocs
Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!