Installation guide

Planning for WaveNet 25-6
Chapter 25: Connecting Wave Servers via WaveNet
WaveNet Administrator Guide
Trunking considerations
Important: In the current version, only SIP trunking is supported.
This section describes the following:
• SIP signaling control point (SCP) issues. See page 25-6.
SIP signaling control point (SCP) issues
When you publish a user to one or more remote nodes, WaveNet automatically creates one SIP
SCP on each remote node (as described in “About automatic trunking and routing
configuration” on page 25-3).
Important: The current version does not support two SCPs that point to the same endpoint and
port. (An “endpoint” is a Wave Server, a WaveNet node, or another system.) The IP Telephony
applet in the Global Administrator Management Console will not allow you to create such
duplicates, and WaveNet will not automatically create any duplicate SCPs.
You may have pre-existing non-WaveNet SCPs to support off-premise extensions, external
dialing, private networking, and so forth. If any of these pre-existing SCPs point to any of the
Wave Servers that you plan to add as nodes in the WaveNet network, and they are configured to
use the same port as the default SIP listener port on those nodes, you must manually delete the
pre-existing SCPs or move them to a different port, to allow WaveNet to create the SCPs that it
needs to point to these nodes in order to deliver calls to published Gateway users.
After the WaveNet SCPs have been automatically created, you can do either of the following to
restore off-premise extensions, external dialing, or private networking previously associated
with any SCPs that were deleted:
• Create new SCPs with the same endpoint address, but with different ports.
• Share the WaveNet SCPs for those other purposes. Note that while the WaveNet SCPs
can be used this way, they cannot be edited in any way. This method is not recommended,
because future changes might create a confusing situation involving the WaveNet created
SCPs.
Release 2.0
September 2010