Configuring ANSI Routing

Checkpoint your configuration using the checkpointing tool.

Run the cfgMtp command with the -pcRoute option set to cluster.

Stop and restart the stack on both hosts. The checkpointed configuration is loaded automatically.

Some DPC creations are refused because when Full Point Code routing is disabled, there can be only 1 DPC (N.C.0) in a remote cluster DPC. This does not matter as DPC N.C.0 can stand for any DPC. You don’t have to add anything to the configuration.

If your Full Point Code routing configuration does not have a DPC N.C.0 in the remote clusters (for example, if you have N.C.1, N.C.2 and N.C.3) all DPCs are refused and you have to reconfigure N.C.0.

Checkpoint your configuration again, then propagate it if necessary.

Run the cfgMtp command with the -pcRoute option set to cluster.

Use the SS7 Monitor, to configure your SS7 network. In remote clusters only the N.C.0 DPC is allowed.

Checkpoint your network configuration.

Run the cfgMtp command with the -pcRoute option set to full.

Stop and restart the stack on both hosts. The checkpointed configuration is automatically reloaded, but the system is now running in Full Point Code routing mode.

Add all the DPCs and routes that were previously implicitly handled by DPC with member ID set to 0. For example, if in a remote cluster you have DPC 2.5.0, 2.5.1 and 2.5.2, you must add DPC 2.5.1 and 2.5.2 (2.5.0 being already declared in the file generated by ss7CheckPoint). You must also declare the corresponding routes.

Checkpoint your configuration again, and propagate it if necessary.

Run the cfgMtp command with the -pcRoute option set to full.

Stop and restart the stack on both hosts. The checkpointed configuration is automatically reloaded, but the system is now running in Full Point Code routing mode.

Use the SS7 Monitor to configure your SS7 network. Define all DPC and routes one by one.

Checkpoint your configuration, and propagate it if necessary.