Technology: Cisco Unity Connection | Category: Unity Connection
External Voice mail access, using Unity Connection
External voice mail access. Yes, often requested, hardly ever used in my experience. The solution described below is also good for VM that gets dumped on shared mail boxes, where people don’t have the extension configured on the phone (for instance IVR overflow, or no agents logged in). This access will allow a user not only to listen to messages, but also to change greetings and other set up options. Again, very handy for changing greetings for shared mail box users
Â
So pick a free number in your DID number range. You can feed this  into a translation pattern and translate it into a system number, please note that this is optional, you can also feed the number straight into a call handler. Let’s assume we have chosen 1112 as the system number for external voice mail access (for instance when 1111 is you regular VM pilot point).
Â
Below are the configuration steps:
1-Create a dummy phone and Call Forward all to Voice mail (CUCM)
I don’t think this needs a lot of explanation. Just tick the CFWD ALL Voicemail box under the line configuration. What is important is that the extension on this phone’s line will need to be 1112.Â
Â
So all this does it any inbound call to the external Voicemail access DID number, will now be delivered on your unity box (assuming this is already set up in terms of VM profiles and CTI ports etc. etc.).
2-Create a system Call Handler (CUC)
Add a new call handler to CUC and call it, for example “External Voice mail access”. Some tweaking required here. This call handler will facilitate the playing of a message (essentially a greeting) that can be something along the lines of: “to access your messages, press *”. After which the caller will authenticate and will be allowed access to his/her Voicemail box.  Very similar to pressing the envelope button on a phone.Â
Â
So going to the Greetings menu of our external voicemail access call handler, you can see that the standard greeting is a Recording (namely our personalised “to access your messages, press *).
| Figure 1 |
| Figure 2- Standard Greetings configuration. |
| Figure 3 – Caller Input for the call handler |
| Figure 4 – Caller input * to sign in. |
OK, so that concludes the configuration of the call handler. Most of this is very generic stuff, but I just wanted to show the whole call logic from start to finish.
3 Create a forwarded Routing rule (CUC)
Remember that up to this point we still will not have access to our CUC call handler by dialing into 1112. This, because 1112 does not yet exist anywhere within Unity connection, not as a user and not as anything really. Because extension 1112’s only role is to deliver a call into CUC, it shouldn’t actually identify itself to CUC as a user. So to make sure our call handler from step 2 gets triggered we need to add a forwarded routing rule, that ties 1112 with our call handler
| Figure 5 – Forwarded Routing Rule |