Related articles:

The Level 4 Converter can be used for phased migration of STPs, hence, avoiding flash cuts and system isolation as legacy STPs are retired. This method of STP migration has the following advantages:

  • cost effective because it avoids configuration changes at the remote nodes

  • ensures lower load on the existing STPs

  • migration and testing of STPs takes place without disrupting the interconnecting networks

  • existing functionality and routing services are continued for the involved STPs

  • reconfiguration of  SS7 nodes is transparent
     

Consider the following for this STP migration method:

  • bidirectional point code mapping is applied
     
  • ANSI to ANSI or ITU to ITU conversion is supported

  • ISUP, SCCP, and BICC messages are supported by the L4 Converter
     

  • Level 4 Converter cannot be used for STP migration if

    • the converter is already licensed and deployed for an SS7 protocol conversion
       

    • the migration is configured for networks other than ANSI or ITU
       

For detailed information about the STP migration process, refer to STP Migration Process.

Caution

Any Point Code (PC), including the Local Point Code (LPC), configured by the GTT (GTT NA Manager > GTT NA > PC Registrations) cannot be defined by the L4 Converter as the Mirror PC in a Route Mapping in the other NA (L4 Converter SS7 Variant > Route Mappings).

Conflicting registrations for Signaling Indicator (SI) 3 would result and depending on which application registers first on a per slot basis, the traffic would either hit the GTT or the L4 Converter. 

It is recommended a new VNode on NA 1 (as seen in the following diagram) is used instead of the conflicting LPC, so traffic from NA 1 can reach NA 2 through the L4 Converter.

GTT and L4 Converter Deployment Example

  • No labels