Avaya BCM 2.0 Programming Guide de l'utilisateur télécharger pdf (Page 361)

100

101

Appendix A: Network Examples 361

P0911588 Issue 01 Enterprise Edge 2.0 Programming Operations Guide

Routing information for DPNSS network example

For more information on creating a private numbering plan with DPNSS, refer to

• Guidelines for creating a private numbering plan with DPNSS on page 361

• Customizing the routing service on page 362

Guidelines for creating a private numbering plan with DPNSS

Use the following guidelines when creating a private numbering plan with DPNSS.

• When creating HLCs for the nodes in your system, avoid numbering conflicts

between network nodes and internal DNs, Hunt Group DNs.

• Program a Private Access Code into your dest routing tables to avoid conflicts

with your internal HLC and dest code numbering plan. For example, if a dialout

HLC is 848, but this number already exists in the Norstar system for an

extension, the routing tables should add a Private Access Code to the dest code.

If the code is programmed as “6”, the dest code becomes 6848. 6848 uses a

route to dial out 888 using the DPNSS line pool, allowing the call to be placed.

Note that a Private Access Codes is required only for specific DPNSS features

such as Diversion, Route Optimization, and Redirection.

Heading Parameter Setting

Private Network: (for each branch Enterprise Edge)

Routing Service Route 001

Dial out # No number

Use Pool N

DN type none (private access code 6 is programmed)

Destination Code 6

Normal route 001

Absorb 1

Public Network:

Routing Service Route 002

Dial out # No number

Use Pool N

DN type public

Destination Code 9

Normal route 002

Absorb 1

1 2 ... 356 357 358 359 360 361 362 363 364 365 366 ... 445 446

Commentaires sur ces manuels

Pas de commentaire

Avaya BCM 2.0 Programming Guide de l'utilisateur Page 361

Commentaires sur ces manuels

Produits connexes et manuels pour Passerelles/contrôleurs Avaya BCM 2.0 Programming