> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/create-an-sccp-route.md). # Create an SCCP Route This step in the Web Portal configuration exists to create a route to a specific destination point code (DPC). ### Description of parameters General explanation of the configuration parameters: * The **Handle SCCP LSAP** parameter specifies the handle of the SCCP LSAP *** * The **Protocol variant** parameter specifies the SCCP route protocol variant for this destination point code. Allowable values: | Route Protocol Variant | Description | | ---------------------- | ----------------------------------- | | ANSI 88 | Used for ANSI88 | | ANSI 92 | Used for ANSI92 | | ANSI 96 | Used for ANSI96 | | TELCORDIA | Used for TELCORDIA | | ITU 88 | Used for ITU88 | | ITU 92 | Used for ITU92 | | ITU 96 | Used for ITU96 | | GSM 0806 | Valid in both ITU and ANSI networks | *** * The SCCP **Replicate mode** parameter specifies the mode of replicated nodes/subsystems. Allowable values: | Replicate mode | Description | | ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Dominant | In this mode, each backup node/subsystem is assigned a unique priority. The node/subsystem on this route is the primary node/subsystem and is selected as the preferred node/subsystem when accessible. On failure of the preferred node/subsystem the next higher priority available backup node/subsystem is selected as the preferred node/subsystem. | | Loadshare | In this mode, each backup node/subsystem together with the node/subsystem configured on the route is assigned equal priority and load is distributed among nodes/subsystems on the basis of: 1) SLS for class1 traffic, and 2) in round-robin fashion for class 0 traffic. Loadshare mode is applicable in TELCORDIA only. | | Dominant alternate | This mode is significant only for class 0 traffic. In this mode, class 0 traffic is prevented from reaching an accessible but congested node. For class 1 traffic, this mode is same as DOMINANT mode. In this mode, each backup node/subsystem is assigned a unique priority. The node/subsystem configured on the route is selected as the primary node/subsystem and is the preffered node/subsystem when accessible and not congested. On failure or congestion of the preferred node/subsystem the next higher priority available and uncongested backup node/subsystem is selected as the preferred node/subsystem. This mode of operation is applicable only in ANSI96 and TELCORDIA. | | Loadshare alternate | This mode is significant only for class 0 traffic. In this mode, class 0 traffic is prevented from reaching an accessible, but congested node. For class 1 traffic, this mode is same as LOADSHARE mode. In this mode, each backup node/subsystem together with the node/subsystem configured on the route is assigned equal priority and load is distributed among nodes/subsystems on the basis of: 1) SLS for class 1 traffic, and 2) in round-robin fashion for class 0 traffic. For class 0 traffic, a node/subsystem is selected when it is accessible and uncongested. On failure or congestion of the node, next available and uncongested node/subsystem is selected. This mode of operation is applicable only in TELCORDIA. | **Note:** Only used with ANSI96 and TELCORDIA. *** * The **Destination point code** ([DPC](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/signalling/dpc/README.md)) parameter specifies the point code of the node where the route is terminating. Proper point code length is described in [MTP2:Point Code Length](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/point-code-length/README.md). **Note:** The destination point code 0.0.0 is reserved for default routing. When no explicit route exists for a destination point code and the default route 0.0.0 is present, the message is passed to MTP3 for delivery in place of being dropped. If the MTP3 layer is unable to deliver the message for any reason, the message is dropped and no notification is given to the application that originated the message. *** * The **Options** parameter specifies the route options. Allowable values: | Route Options | Description | | ----------------- | ------------------------------- | | None | None (no options) | | Online by default | Node is online by default | | Translator node | Translator node | | Adjacent node | Adjacent node | | INS capable node | INS capable. Only in TELCORDIA. | **Note:** These values can be ORed together. *** * The **Broadband support flag** parameter. Flag to indicate whether the peer SCCP on the route has broadband support. Allowable values are 'True' or 'False'. **Note:** For ITU88, ITU92, ANSI88, ANSI92 and ANSI96 network this flag should always be 'False'. *** * The **Signaling link selector mask** parameter specifies, in ANSI and TELCORDIA networks, if the SLS can be either 5 bits or 8 bits. Allowable values: | Route SLS Mask | Description | | -------------- | ----------------------- | | 5 bits | Networks SLS is 5 bits. | | 8 bits | Networks SLS is 8 bits | **Note:** For ANSI and TELCORDIA only. *** * The **Number backup point code** parameter specifies the number of backup point code entries in the Backup Point Code and Priority Backup Point Code arrays * The **Array of backup point code entries** parameter specifies the list of backup point code for this route *** * The **Array of priority of backup point code entries** parameter specifies the list of priority of each backup point code for this route. Allowable values are from 0 to 255. **Note:** Zero being the lowest priority *** * The **Number subsystem number** parameter specifies the number of subsystem number entries in the Subsystem Number array * The **Array of subsystem number entries** parameter specifies the list of subsystem number for this route ### Description of SSN specific parameters General explanation of the parameters of SSN specific configuration: * The **Subsystem number** parameter specifies a subsystem number for this route. Allowable values are from 1 to 255. | SSN value | SSN SCCP user | Description | | --------- | ------------------ | --------------------------------------------------------- | | 0 | Unknown | SSN not known or not used. | | 1 | SCCP management | SCCP management | | 3 | ISUP | ISDN user part | | 4 | OMAP | Operation, Maintenance and Administration Part | | 5 | MAP | Mobile Application Part | | 6 | HLR | Home Location Register (MAP) | | 7 | VLR | Visitor Location Register (MAP) | | 8 | MSC | Mobile Switching Center (MAP) | | 9 | EIR | Equipment Identifier Register (MAP) | | 10 | AUC | Authentication Center | | 11 | ISDN supplementary | ISDN Supplementary services | | 13 | BISDNE2EAPP | Broadband ISDN Edge-to-Edge Application | | 14 | TCTR | TC Test Responder | | 142 | RANAP | Radio Access Network Application Part | | 143 | RNSAP | Radio Network Subsystem Application Part | | 145 | GMLC | Gateway Mobile Location Centre (MAP) | | 146 | CAP | CAMEL application part | | 147 | gsmSCF | Global System for Mobile Service Control Function (MAP) | | 148 | SIWF | Serving GPRS Support Node (MAP) | | 149 | SGSN | Serving GPRS Support Node (MAP) | | 150 | GGSN | Gateway GPRS Support Node (MAP) | | 249 | PCAP | Positioning Calculation Application Part | | 250 | BSC BSSAP | BSC Base Station System Application Part (BSSAP-LE) | | 251 | MSC BSSAP | MSC Base Station System Application Part (BSSAP-LE) | | 252 | SMLC BSSAP | Serving Mobile Location Center (BSSAP-LE) | | 253 | BSSOM | Base Station System Operation & Maintenance (A-interface) | | 254 | BSSAP | Base Station System Application Part (A-interface) | *** * The **Subsystem number options** parameter specifies the subsystem number options. Allowable values include: | Route options / SSN options | Description | | --------------------------- | ------------------------------------------------------------------ | | Accessible by default | Subsystem is accessible by default | | Normal routed | Subsystem normal routed - valid in ANSI and TELCORDIA network only | **Note:** These values can be ORed together *** * The **Replicate mode** parameter specifies the mode of replicated nodes/subsystems. Allowable values: see the 'SCCP replicate mode' earlier in this page * The **Number backup point code** parameter specifies the number of backup point code entries in the 'Backup Point Code' and 'Priority Backup Point Code' arrays * The **Array of backup point code entries** parameter specifies the list of backup point code for this SSN *** * The **Array of priority of backup point code entries** parameter specifies the list of priority of each backup point code for this SSN. Allowable values are from 0 to 255 **Note:** Zero being the lowest priority. *** * The **Number concerned point code** parameter specifies the number of concerned point code entries in the Concerned Point Code array * The **Array of concerned point code entries** parameter specifies the list of concerned point code for this SSN --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://prosbcdocs.telcobridges.com/tmedia-documentation/configuration/create-an-sccp-route.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.