unable to forward the calls to unity connection, extension has +e164 number pattern

Unanswered Question
Nov 25th, 2009


I have installed unity connection (v7.0) and integrated with active directory, and callmanager (v7.0) integrated with active directory and created user device profile for all users and having +e164 numbers for the extension. In unity connection i have users imported from active directory without +.

Much appreciated if anyone can provide solution/work around for the following

1. I cant send voce messages to unity ( extension on unity is without + and in cucm its with +), so want to know how to remove this + while forwarding calls to unity, i tried with translation pattern, but didnt work

2. unable to retirve voice mail. if am clicking the message button, it playing the default greeting, not asking to enter the id or pin number so that i can check my voice message (it should ask only to enter the pin while calling from known extension)

any help on these issues is highly appreciated.?



I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Jonathan Schulenberg Wed, 11/25/2009 - 13:09

You need to specify the E.164 formatted number in the Alternate Extension and Message Waiting Indicator Destination fields on the mailbox to make this work.

kim_beadle Thu, 11/26/2009 - 07:01

I have similar issue.

I have OCS integration with CUPS and CUCM 7.1(3).

I have changed my extension to +XXXX and used a translation pattern so that callers dial me as normal.

Cisco Unity Connection 2 is not able to send MWi to +XXXX;

I am able to configure and alternate extension as mine with the \+XXXX.

I cannot configure a MWi for  \+XXXX as Unity Connection says "Mwi Extension contains invalid characters.".

I wonder if there is some way of getting CUCM to prefix the incoming MWi from Cisco Unity with the +.


Peter Cresswell Mon, 03/08/2010 - 09:36

Hi Kim,

Did you find a solution for the MWI issue when using DNs with a + pref

ix in CUCM?



Nick Richards Wed, 03/21/2012 - 06:42

To close the loop on this for reference, the full solution is here:


In a nutshell:

1) Create a MWI Translations partition in CUCM

2) Create a translation profile to prefix the + (or, in my case, +1)

3) Assign the partition to the vm outdial port's CSS

4) Enable "Multiple Tenant MWI Modes" in the CUCM Call Manager Service parameters (enables calls from the VM system to access the Translation Patterns)


This Discussion