Signaling Transfer Points (STPs Sample Clauses

Signaling Transfer Points (STPs. 9.4.1 Definition - Signaling Transfer Points is a signaling network function that includes all of the capabilities provided by the signaling transfer point switches (STPs) and their associated signaling links which enable the exchange of SS7 messages among and between switching elements, database elements and signaling transfer point switches.
View SourceView Similar (69)
Signaling Transfer Points (STPs. 2.10.1 The STP element is a signaling network function that includes all of the capabilities provided by the STP switches which enable the exchange of SS7 messages between switching elements, database elements and signaling transfer point switches via associated signaling links. STP includes the associated link interfaces. 2.10.2 The STP routes signaling traffic generated by action of Carrier to the destination defined by the SBC-12STATE’s signaling network. Integrated services digital network user (ISUP) and Translational Capabilities Application Part (TCAP) signaling traffic addressed to SPs associated with Carrier set of links will be routed to Carrier. 2.10.3 SS7 Transport will apply to SS7 messages transported on behalf of Carrier from an SBC-12STATE designated STP pair to a to an SBC- 12STATE STP pair located in a different LATA. In SBC- AMERITECH this arrangement will only be provided for STPs located in the same state. In SBC-7STATE, the rate, per octet, will apply to octets comprising ISUP and TCAP messages. In SBC- AMERITECH the Signal Switching and Signal Transport rates will apply to ISUP and TCAP messages. In SBC-2STATE, SS7 transport is not available. However, transit signaling provides the ability for an interconnecting network (ICN) to pass signaling information through the SBC-2STATE network to a third party without requiring a trunking connection by a third party with SBC- 2STATE.
View SourceView Similar (13)
Signaling Transfer Points (STPs. 9.2.8.2.7.1 The STP element is a signaling network functio n that includes all of the capabilities provided by the STP switches which enable the exchange of SS7 messages between switching elements, database elements and signaling transfer point switches via associated signaling links. STP includes the associated link interfaces. 9.2.8.2.7.2 SS7 Transport will apply to SS7 messages transported on behalf of CLEC from a SBC-AMERITECH designated STP pair to a SBC-AMERITECH STP pair located in a different LATA. In SBC-AMERITECH this arrangement will only be provided for STPs located in the same state. The Signal Switching and Signal Transport rates will apply to ISUP and TCAP messages. 9.2.8.2.7.3 In such instance as CLEC utilizes SBC- AMERITECH’s Local Switching Network Element, CLEC does not separately order SS7 signaling under this method. CLEC will be charged for the use of the SBC-AMERITECH SS7 signaling on a per call basis.
View SourceView Similar (6)
Signaling Transfer Points (STPs. 12.1 Definition: 12.1.1 BA’s CCS Access Service (CCSAS) allows interconnected carriers to exchange signaling information over a communications path which is separate from the message path. The discretely rated network termination point where this interconnection takes place is called the BA STP port termination. 12.1.2 Each CCSAS signaling connection provides for two-way digital transmission at speeds of 56 kbps. The connection to BA’s STP pair can be made from either the carrier’s SP, which requires a minimum of two 56 kbps circuits, or from the carrier’s STP pair, which requires a minimum of four 56 kbps circuits. 12.1.3 STP locations are set forth in National Exchange Carrier Association (NECA) Tariff F.C.C. No.
View Source
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 ...
View Source
Signaling Transfer Points (STPs. BA will provide MCIm with unbundled access to its STPs enabling MCIm to activate its own signaling link transport in lieu of BA provided signaling link transport. In addition, STP connections will be provided to MCIm as requested to support interconnection at either or both MCIm’s STPs or switches to BA’s STPs.
View Source
Signaling Transfer Points (STPs. The STP element is a signaling network function that includes all of the capabilities provided by the STP switches which enable the exchange of SS7 messages between switching elements, database elements and signaling transfer point switches via associated signaling links. STP includes the associated link interfaces.
View Source
Signaling Transfer Points (STPs 
View SourceView Similar (3)

Related to Signaling Transfer Points (STPs

  • Traffic Measurement and Billing over Interconnection Trunks 6.1 For billing purposes, each Party shall pass Calling Party Number (CPN) information on at least ninety-five percent (95%) of calls carried over the Interconnection Trunks. 6.1.1 As used in this Section 6, “Traffic Rate” means the applicable Reciprocal Compensation Traffic rate, Measured Internet Traffic rate, intrastate Switched Exchange Access Service rate, interstate Switched Exchange Access Service rate, or intrastate/interstate Tandem Transit Traffic rate, as provided in the Pricing Attachment, an applicable Tariff, or, for Measured Internet Traffic, the FCC Internet Order. 6.1.2 If the originating Party passes CPN on ninety-five percent (95%) or more of its calls, the receiving Party shall ▇▇▇▇ the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. For any remaining (up to 5%) calls without CPN information, the receiving Party shall ▇▇▇▇ the originating Party for such traffic at the Traffic Rate applicable to each relevant minute of traffic, in direct proportion to the minutes of use of calls passed with CPN information. 6.1.3 If the originating Party passes CPN on less than ninety-five percent (95%) of its calls and the originating Party chooses to combine Reciprocal Compensation Traffic and Toll Traffic on the same trunk group, the receiving Party shall ▇▇▇▇ the higher of its interstate Switched Exchange Access Service rates or its intrastate Switched Exchange Access Services rates for all traffic that is passed without CPN, unless the Parties agree that other rates should apply to such traffic. 6.2 At such time as a receiving Party has the capability, on an automated basis, to use such CPN to classify traffic delivered over Interconnection Trunks by the other Party by Traffic Rate type (e.g., Reciprocal Compensation Traffic/Measured Internet Traffic, intrastate Switched Exchange Access Service, interstate Switched Exchange Access Service, or intrastate/interstate Tandem Transit Traffic), such receiving Party shall ▇▇▇▇ the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. If the receiving Party lacks the capability, on an automated basis, to use CPN information on an automated basis to classify traffic delivered by the other Party by Traffic Rate type, the originating Party will supply Traffic Factor 1 and Traffic Factor

  • One-Way Interconnection Trunks 2.3.1 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Onvoy to Frontier, Onvoy, at Onvoy’s own expense, shall: 2.3.1.1 provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.3.1.2 obtain transport for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.3.2 For each Tandem or End Office One-Way Interconnection Trunk group for delivery of traffic from Onvoy to Frontier with a utilization level of less than sixty percent (60%) for final trunk groups and eighty-five percent (85%) for high usage trunk groups, unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for all final trunk groups and eighty-five percent (85%) for all high usage trunk groups. In the event Onvoy fails to submit an ASR to disconnect One-Way Interconnection Trunks as required by this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the rates set forth in the Pricing Attachment. 2.3.3 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Frontier to Onvoy, Frontier, at Frontier’s own expense, shall provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA.

  • Compressed Work Week The Company and Union recognize the concept of the compressed work week. It is further understood that the compressed work week conditions will apply only to those departments that are on the compressed work week.

  • Two-Way Interconnection Trunks 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and KDL, KDL, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and KDL, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, KDL shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, KDL shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that KDL anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between KDL and Verizon. KDL’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Verizon and KDL shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Freedom has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Freedom. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Freedom (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Freedom, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Freedom will then have the option of paying the one-time SC rates to place the Loop.