6.1.2 UDR Redundancy

In cases where there is one Connection Group on vENUM NO (with default priority set to 10) and no provision to configure one interface as the priority route and another interface as the secondary (when the primary interface fails).

The Connection Group feature provides redundancy between the local site and remote site for ENUM, where the following three priorities are provided for the Connection group for UDR lookup on vENUM NO GUI:

• STPSvcGroup=30 (default value) indicates highest priority.
• STPSvcBackGroup=20 indicates a lesser priority.
• STPSvcSpareGroup=10 indicates a much lesser priority.

Figure 6-1 Priorities for Connection Group

Operator can add UDR connected with primary route in the highest priority Connection Group. For redundancy, the other UDR can be added to other connection groups.

Note:

These priority values are hardcoded through the loader and cannot be modified. If all UDRs are added to the same Connection Group, the load is distributed between these UDRs.

For example:

To configure the IMI as the priority route, the UDR connected with this Interface must be added to STPSvcGroup (highest priority) Connection Group.

The UDR connected with another Interface(XSI2) can be added to another Connection Group (STPSvcBackGroup) for redundancy.

Figure 6-2 IMI as the Priority Route

Caution:

During connection group switch over, all UDRs in that connection group might go down, and this occurs when a message transfers from a UDR in one connection group to a UDR in another connection group. During such a switch over, message can be lost due to ComAgent limitation.