SCC Service Centralisation Configuration.


The context of service-centralisation within the schema tree is shown. Italicised links are to other pages.


The originating SCCP address.


A restart is required for changes to this value to take effect.

This node is mandatory.

Type sccp-address-type


A type representing an SCCP address in string form. The basic form of an SCCP address is:

type=<variant>,ri=<address type>,<parameter>=<value>,…​

where <variant> is A7 for ANSI-variant SCCP or C7 for ITU-variant SCCP, and <address type> is one of gt or pcssn (for an address specified by Global Title (GT), or Point Code (PC) and Subsystem Number (SSN), respectively).

The <parameter> options are:

  • Point code: pc=<point code in network-cluster-member (ANSI) or integer (ITU) format>

  • Subsystem number: ssn=<subsystem number 0-255>

  • Global title address digits: digits=<address digits, one or more 0-9>

  • Nature of address: nature=<nature> where <nature> is unknown, international, national, or subscriber

  • Numbering plan: numbering=<numbering> where <numbering> is unknown, isdn, generic, data, telex, maritime-mobile, land-mobile, isdn-mobile, or private

  • Global title translation type: tt=<integer 0-255>

  • National indicator: national=<true or false>.

    parameter names are separated from their values by an equals sign, and all <parameter>=<value> pairs are separated by commas. Do not include any whitespace anywhere in the address.

    Only the ssn and national parameters are mandatory; the others are optional, depending on the details of the address - see below.

    Note carefully the following:

  • For ANSI addresses, ALWAYS specify national=true, unless using ITU-format addresses in an ANSI-variant network.

  • For ITU addresses, ALWAYS specify national=false.

  • All SCCP addresses across the deployment’s configuration must use the same variant (A7 or C7).

  • Be sure to update the SGC’s SCCP variant in sgc-config.yaml to match the variant of the addresses.

    For PC/SSN addresses (with ri=pcssn), you need to specify the point code and SSN. For GT addresses (with ri=gt), you must specify the global title digits and SSN in addition to the fields listed below (choose one option).

    There are two options for ANSI GT addresses:

  • translation type only

  • numbering plan and translation type.

    There are four options for ITU GT addresses:

  • nature of address only

  • translation type only

  • numbering plan and translation type

  • nature of address with either or both of numbering plan and translation type.

    Some valid ANSI address examples are:

  • type=A7,ri=pcssn,pc=0-0-5,ssn=147,national=true

  • type=A7,ri=gt,ssn=146,tt=8,digits=12012223333,national=true

    Some valid ITU address examples are:

  • type=C7,ri=pcssn,pc=1434,ssn=147,national=false

  • type=C7,ri=gt,ssn=146,nature=INTERNATIONAL,numbering=ISDN,tt=0, digits=123456,national=false

  • type=C7,ri=gt,ssn=148,numbering=ISDN,tt=0,digits=0778899,national=false


a string with length 0 or more matching (.,)*type=(A|C)7. and matching (.,)*ri=(gt|pcssn). and matching (.,)*ssn=[0-2]?[0-9]?[0-9]. and matching .=.(,.=.)*


If 'true', the configured I-CSCF URI will be added to the route header of the reoriginated INVITE. If 'false', the HSS will be queried for the S-CSCF URI to use for the subscriber.

This node is mandatory.

Type boolean


'true' or 'false'


A template string for the P-Visited-Network-Information header generated in the reorigination, where {mnc} and {mcc} are replaced with the MNC and MCC respectively.

This node is mandatory.

Type string


a string


Police incoming originating requests, and reject attempts to hijack the call.

This node is mandatory.

Type boolean


'true' or 'false'


See simple-imrn-pool for details of this node and its descendants.


See scc-gsm-service-centralisation for details of this node and its descendants.


See scc-cdma-service-centralisation for details of this node and its descendants.

Previous page Next page
Rhino VoLTE TAS Version 4.0.0