Information Technology Reference
In-Depth Information
Default entries for the voicemail profile and voicemail pilot exist, which are used by all
users of the CUCM system; these may be used and customized, or others may be added
for other integrations and used by different subsets of users. The Voicemail Port Wizard
has all but eliminated a common problem in CUCM-to-CUC integrations with SCCP: Of-
ten, administrators would forget one or more of the critical steps of creating the Voicemail
Pilot and linking it to the Hunt Pilot, and creating the Voicemail Profile and linking it to
the Voicemail Pilot. Miss one of these, and the Messages button on the phones won't
work, even though you can dial the CUC Hunt Pilot number directly and reach CUC.
On the CUC server, a set of ports (the number of available ports being limited by the server
hardware capacity, and then by licensing) is defined, and each port is configured for various
call-behavior options, including whether the port should answer calls, perform Message
Waiting Indicator (MWI) or Message Notification, and other settings. Call routing within
CUC can be controlled by (among other things) the phone system or the port group.
MWI uses a separate and unique Directory Number (DN) for MWI On and MWI Off.
The DNs must be configured (and match) in both CUCM and CUC. One of the tricks you
can play on your co-workers is to dial the MWI On DN from their phone; their MWI light
will come on (dial MWI off and it turns off, too). This practical joke is also an effective
way to test MWI functionality.
An integration using Skinny Client Control Protocol (SCCP) may be secured using digital
certificates and SCCP over port 2448. (Nonsecure SCCP uses port 2000.)
CUC Integration Using SIP
The Session Initiation Protocol (SIP) integration components are slightly different from
SCCP: Instead of the voicemail pilot pointing to a Hunt Pilot, it points to a Route Pattern,
which in turn points to a SIP trunk. The SIP trunk is configured to connect to CUC. The
number of ports is not defined on the CUCM server as it is for SCCP integration; rather,
they are only defined in CUC. Each port is configured to register with a SIP server (which
is the CUCM server). A significant difference with a SIP integration is that there are no
separate DNs for MWI On/Off; instead, SIP itself handles the signaling of the MWI lamp
state. SIP can also be secured using port 5061. (Nonsecure SIP uses port 5060.) Figure
13-2 illustrates the SIP integration components on CUCM.
Voice Mail Profile
Voice Mail Pilot
Route Pattern
SIP Trunk
Figure 13-2
SIP Voicemail Integration Components in CUCM
