Installation guide

Installing WaveNet 25-13
Chapter 25: Connecting Wave Servers via WaveNet
WaveNet Administrator Guide
• Any remote node First Digits set to External that utilize an SCP that points to a
Wave Server that is also a WaveNet node must be manually deleted before
publishing any users to the Server. Once the WaveNet SCP has been automatically
created, the First Digit can be re-added sharing the WaveNet SCP to restore
external dialing.
See “First Digit Table issues” on page 25-8 for more information.
5 Manually eliminate SCP conflicts to prevent possible inbound SIP call routing problems.
•
Local SCP conflicts. For any remaining SCPs on the local node that point to other
Wave Servers that are also WaveNet nodes (for example SCPs used for off-premise
extensions, private networking, and so forth), manually delete those SCPs or move
them to a different port than the default SIP listener port on those nodes.
•
Remote SCP conflicts. For any remaining SCPs on any remote node that point to
other Wave Servers that are also WaveNet nodes (for example SCPs used for
off-premise extensions, private networking, and so forth), manually delete those SCPs
or move them to a different port than the default SIP listener port on those nodes.
See “SIP signaling control points (SCPs) issues” in “Trunking considerations” on page
25-6 for more information.
6 In the General Settings applet, on the PBX (Advanced) tab select the
Allow Trunk-To-Trunk
Connections
checkbox. (This setting allows inbound calls on the Wave Server to be routed
to Gateway users on other WaveNet nodes.)
7 If you are using anti-virus software, configure that software to exclude the following
Microsoft Message Queue (MSMQ) folders from virus scanning:
%SystemRoot%\system32\MSMQ
%SystemRoot%\system32\MSMQ\storage
Release 2.0
September 2010