Interconnecting on SS7

From Yate Documentation
(Difference between revisions)
Jump to: navigation, search
(Created page with "To connect to another SS7 network you will need to configure some parameters so the two sides speak the same language. You will need to know this information in advance so you...")
 
Line 27: Line 27:
 
'''See also'''
 
'''See also'''
  
*[[SS7 Tutorials]]
+
* [[How_To's#SS7_Setups | SS7 Setups]]

Revision as of 14:55, 26 October 2017

To connect to another SS7 network you will need to configure some parameters so the two sides speak the same language. You will need to know this information in advance so you can plan your network or at least its border components.

You should get the following information from your upstream provider or, if you are that provider, give this information to your customers:

  • MTP Interconnect
    • Type of signaling interconnect: TDM or SIGTRAN
    • Type of SS7 network at MTP level: ITU, ANSI, etc. (determines the Point Code type)
    • Network Indicator of MSUs: national, national-reserved, international
    • Point Codes of the STPs on the provider side
    • Point Codes of the STPs on the customer side (if applicable)
    • Point Codes of the Signaling EndPoints (ISUP, SCCP, etc.) for each side
    • Link numbering in each linkset (if more than one link in linkset)
    • Load balancing rules between linksets
    • Trunks and timeslots used in signaling, identification of Point Codes at each end of the link and Signaling Circuit Code
  • ISUP Interconnect
    • National ISUP dialect used
    • Circuits codes between each pair of ISUPs and their allocation on TDM trunks and timeslots
    • Controlled circuits for each side (for glare avoidance)
    • Type of Continuity Check (if applicable)
    • Nature of Address Indicators
    • Type and format of numbers used (subscriber, national, international)
    • Area code (used for number in Subscriber format - if applicable)
    • Additional procedures applicable (Hop Counter, Diversion Information)
    • Additional services required (Caller Identification, Number Portability)
    • Charging information type (if applicable)


See also

Personal tools
Namespaces

Variants
Actions
Preface
Configuration
Administrators
Developers