09.08.2013 Views

TC Systems, Inc. South Carolina - AT&T Clec Online

TC Systems, Inc. South Carolina - AT&T Clec Online

TC Systems, Inc. South Carolina - AT&T Clec Online

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

6/23/04<br />

Attachment 3<br />

Page 24<br />

Environment and Service Management System (SCE/SMS) application databases and<br />

Directory Assistance.<br />

4.4.4.2 If <strong>TC</strong> SYTEMS chooses to gain access to Bell<strong>South</strong>’s call related databases, it may<br />

do so by connecting to Bell<strong>South</strong>’s network at the regional STP level. <strong>TC</strong> SYTEMS<br />

will not be required to connect to Bell<strong>South</strong>’s databases at each SCP.<br />

4.4.4.3 A SCP is deployed in a SS7 network that executes service application logic in<br />

response to SS7 queries sent to it by a switching system also connected to the SS7<br />

network. Service Management <strong>Systems</strong> provide operational interfaces to allow for<br />

provisioning, administration and maintenance of subscriber data and service<br />

application data stored in SCPs.<br />

4.4.5 Technical Requirements for SCPs/Databases<br />

4.4.5.1 Bell<strong>South</strong> shall provide physical access to SCPs through the SS7 network and<br />

protocols with <strong>TC</strong>AP as the application layer protocol.<br />

4.4.5.2 Bell<strong>South</strong> shall provide physical interconnection to databases via industry standard<br />

interfaces and protocols (e.g. SS7, ISDN and X.25).<br />

4.4.5.3 The reliability of interconnection options shall be consistent with requirements for<br />

diversity and survivability.<br />

4.4.6 Both Parties will provide LEC-to-LEC Common Channel Signaling (“CCS”) to each<br />

other, where available, in conjunction with all traffic in order to enable full<br />

interoperability of CLASS features and functions except for call return. All CCS<br />

signaling parameters will be provided, including automatic number identification<br />

(“ANI”), originating line information (“OLI”) calling company category, charge<br />

number, etc. All privacy indicators will be honored, and each Party will cooperate<br />

with each other on the exchange of Transactional Capabilities Application Part<br />

(“<strong>TC</strong>AP”) messages to facilitate full interoperability of CCS-based features between<br />

the respective networks. The Parties will provide all line information signaling<br />

parameters including, but not limited to, Calling Party Number, Charge Number (if it is<br />

different from calling party number), and originating line information ("OLI"). For<br />

terminating FGD, either Party will pass any CPN it receives from other carriers. All<br />

privacy indicators will be honored. Where available, network signaling information<br />

such as Transit Network Selection ("TNS") parameter (SS7 environment) will be<br />

provided by the end office Party wherever such information is needed for call routing<br />

or billing. Where TNS information has not been provided by the end office Party, the<br />

tandem Party will route originating exchange access traffic to the IXC using available<br />

translations. The Parties will follow all industry Ordering and Billing Forum (“OBF”)<br />

adopted guidelines pertaining to TNS codes.<br />

4.4.7 Bell<strong>South</strong> Common Channel Signaling Access Service (CCSAS) allows<br />

interconnected carriers to exchange signaling information over a communications path<br />

that is separate from the message path.<br />

CCCS 200 of 433

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!