CME 4.2 Transfer Direct To Voice Mail

Answered Question
Apr 29th, 2008

We have a customer/site requirement- Transfer Direct to Voice Mail. Is this a standard feature available in Call Manager Express? In Call Manager we create an CTI Route Point to handle the task. Is this a supported feature in CME?

From what I can find on the forums, it seems that we would need to create additional (secondary) extensions and forward all to VM of subscribers. Is this the cleanest way to do this?

Thanks for the help,

Mark

----------------------

Example from forum:

!

ephone-dn 130

number 2..

description DN to transfer directly to CUE voicemail

call-forward all 18900

!

Notice that we have configured number "2..". In this example, we want the operator (or anyone) to be able to transfer to anyone's voicemail box. Each call transfered to a "2.." extension will go directly to voicemail. So each user will need to be configured with a proper "2.." extension. For simplicity, since all of our ephone-dn's are in the 1XX range, we create this number with a different first digit, so to tranfer directly to extension 156's voicemailbox, the admin would know to dial 256 when transfering.

Correct Answer by Kenneth Mohammed about 8 years 9 months ago

How are the transfer options for ext 110 configured in unity. Is it set to ring subscriber at ext 110 or is it set to send directly to users greeting?

Correct Answer by Kenneth Mohammed about 8 years 9 months ago

Check the transfer options under the subscriber in unity, see if its configured to ring a subscriber or transfer to users greeting.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
Kenneth Mohammed Tue, 04/29/2008 - 08:46

OK..here goes:

ephone-dn 130

number 2...

descrip DN to transfer directly to CUE voicemail

call-forward all 18900

in the CUE, you need to configure the E164 numbers ..example

username user1 phonenumber 156

username user1 phonenumbere164 2156

therefore when anyone transfers to 2156, the call will go directly to the voicemail of the user at ext 156.

Hope that helped.

mfcornett Tue, 04/29/2008 - 09:47

Kenneth-

My mistake- CME 4.2 is integrated with Unity 5.0, not CUE. I should have clarified that, forgot to add it to my post.

Thanks for the help,

Mark

Kenneth Mohammed Tue, 04/29/2008 - 10:06

Unity integrates with CME as SCCP controlled IP phone endpoints. Each voicemail port on unity is configured as an ephone on CME, and the voicemail pilot number is configured as an ephone-dn that appears on each of the phones(ports). The unity ports register witht eh CME router using a voice mail device ID (vm-device-id) such as Cisco UM-VI2. for example:

telephony-service

voicemail 18900

ephone-dn 32

number 18900

name VM Port 1

preference 0

no huntstop

ephone-dn 33

number 18900

name VM Port 2

preference 1

no huntstop

ephone-dn 34

number 18900

name VM Port 3

preference 2

no huntstop

ephone-dn 35

number 18900

name VM Port 4

preference 3

ephone 5

vm-device-id CiscoUM-VI1

button 1:32

ephone 6

vm-device-id CiscoUM-VI2

button 1:33

ephone 7

vm-device-id CiscoUM-VI3

button 1:34

ephone 8

vm-device-id CiscoUM-VI4

button 1:35

The voicemail 18900 command defines the voice mail pilot number as extension 18900. You can define an ephone-dn for each of the four ports; these definitions control call routing to Cisco Unity. All the ephone-dns have 18900 as the extension and are tagged with preference 0 to preference 3. You need four individual ephone-dns, one per port, to route and deliver four calls to the Cisco Unity system simultaneously. Form CME's point of view, four IP phones have an appearance of extension 18900; therefore, four individual calls to 18900 cna be busy at the same time.

The preference and no huntstop designations ensure that Cisco CME system hunts across the available phones if some of them are busy.

Each of the physical ports is defined as an ephone. To CME, Unity ports look like an IP phone, and they register as such. The vm-device-id defined for each ephone must match the device ID configured in the Unity configuration.

You configure call forwarding to voicemail on your IP phones exactly as you would for Cisco UE.

-Taken from Cisco Press "Cisco IP Communications Express: Call Manager Express with Cisco Unity Express"

Now, Im guessing here, but to transfer directly to voicemail, you would still do the following:

ephone-dn 130

number 2...

call-forward all 18900

and then in Unity, you would have to define an alternate extension for the subscriber at ext 156 as 2156.

Hope that helped.

mfcornett Tue, 04/29/2008 - 10:38

Kenneth-

Thanks for the clarification.

I configured the ephone-dn in CME and defined alternate extension in Unity, but it rings through rather than forwarding to VM.

I opened a case with PDI and they advised to create dummy ephone-dn (no phone associated), with a CFA set on it...tried that as well. Still ringing phone.

Awaiting clarification from PDI Help Desk as well.

Thanks for the help,

Mark

Correct Answer
Kenneth Mohammed Tue, 04/29/2008 - 12:33

Check the transfer options under the subscriber in unity, see if its configured to ring a subscriber or transfer to users greeting.

mfcornett Tue, 04/29/2008 - 12:42

The ext. used for testing is the receptionist and main number is set to ring ext.110

Dummy ext. is 2110.

Correct Answer
Kenneth Mohammed Tue, 04/29/2008 - 12:57

How are the transfer options for ext 110 configured in unity. Is it set to ring subscriber at ext 110 or is it set to send directly to users greeting?

mfcornett Tue, 04/29/2008 - 13:39

Ext. 110 (receptionist) is set to ring her extension (Call Transfer), not greeting.

mfcornett Wed, 04/30/2008 - 17:40

Kenneth-

Finally got it working. Double-checked Subscriber Call Transfer settings and discovered 'Alternate' was set to ring Ext.

and was overriding voicemail settings.

Once I disabled Alternate and set Standard to ring extension it worked.

Thanks for the help,

Mark

Actions

This Discussion