Installation guide

Planning for WaveNet 25-7
Chapter 25: Connecting Wave Servers via WaveNet
WaveNet Administrator Guide
Example: Centralized Trunking SCPs
If SIP trunking between WaveNet nodes is required to deliver calls to a node with centralized
trunking, then define a separate reciprocal pair of SCPs using a different port. Each node should
have a new non-WaveNet SCP defined with the endpoint address of the reciprocal node, but use
a different port (examples: 5061, 5070, etc.) Route calls for the centralized trunks (or any other
non-WaveNet purposes) over this non-WaveNet pair of SCPs.
Dial plan considerations
Defining a comprehensive dialing plan is critical to the success of your WaveNet network, as
well as for continued or future support of non-WaveNet dialing functionality.
This section describes the following:
• Local and network extension plan issues. See page 25-7.
• First Digit Table issues. See page 25-8.
• External dialing issues. See page 25-9.
• Non-WaveNet off-premise extension issues. See page 25-9.
• Private networking issues. See page 25-10.
Local and network extension plan issues
No two extensions, whether local user extensions or Gateway user extensions, can be exactly
the same if they are shared to the same node. Careful planning can avoid future “collisions” of
duplicate extension numbers when users are published to other nodes that will then need to be
resolved one by one.
•
Number of extensions required. How many local user extensions do you need? How
many Gateway user extensions do you need?
•
Extension length. Extension length determines the maximum number of extensions
possible locally, and across the network. Any WaveNet location-based prefixes, for
example “Store Number” should be taken into consideration when deciding on extension
length.
•
Same length. Making both local user extensions and Gateway user extensions the
same length is easiest to explain to users, because there is no difference between
dialing a local user vs. a published Gateway user. However, you must ensure that
there are no duplicated extensions anywhere.
Release 2.0
September 2010