Configuring an Egress Route for Prefix Routing

Use this procedure to configure an egress route for prefix routing.

If your CSR routing type for the Administrative Domain (AD) is set for trunk-label or carrier, refer to Configuring an Egress Route for CSR.

Prerequisites:

Procedure

  1. Add an egress route to the zone.

  2. Specify a VRC feature set (must be dp1.0 for prefix routing).

  3. Set a destination pattern for the route.

  4. Define an ANI (answer address) and a DNIS (incoming called-number) for the route. An inbound VoIP dial peer is only created if one of these two is set.

  5. Specify a translation profile (optional).

  6. Specify a route scope. Choose from the route scope or the managed zone. If you choose route scope, the feature sets must match.

  7. Specify a call block (optional).  

  8. Select a technology prefix (optional).

  9. Specify a voice class codec (optional).

  10. Set the hunt-stop behavior (optional).

  11. Define the necessary route parameters for the route (optional).