CUC (6) CUCM (28) Jabber (6) Python (2) Routing (3) Solarwinds Orion NPM (4) switching (1) Video (6) voice (3)

Monday, 22 October 2012

Jabber for Windows Voice Mail integration

Quick post on how to configure Voicemail integration, using Jabber for Windows (9.0.5) and Unity Connection (8.6.2). As you can see in the picture below, Jabber uses IMAP to communicate with Unity Connection.

I will start off with what needs to be configured on the Unity Side.

Allow IMAP access to a user's voicemail box
Go into the Class of Service in Unity Connection and set the following below


Also I suggest to use LDAP for authentication, this is the authentication that is used in the Jabber client to connect to Unity for IMAP connections. Before you set this up you might want to telnet to the Unity Connection server on port 143 to see if it accepts connections.

Ok, so now go into Unity Connection and set up the authentication for end users

You can test this by login into https://<ip address of unity>/ciscopca

So now you can use LDAP authentication to have Jabber connect to Unity IMAP.  In essence these credentials are the same as you would use when you log into the Jabber client itself  (if EDI is used).

so set the following in CUPS:

(Application  > Cisco Jabber > Settings )

Setting CUP ad the credentials source essentially passes on the Jabber Client login credentials on to Unity (which then pases them on to AD, using the LDAP authentication configuration in Unity).

If this is successful, you will notice that the Phone Accounts option in the Jabber Client, the Voicemail account has disappeared. This is because the VM server is pushed out to the client as per  CUPS voicemail profile and the login credentials are passed on to LDAP at the moment the user logs in.

So this is What it looks like:


1 comment:

  1. I am on CUPS 9.1.1 and do not have an Application > Cisco Jabber > Settings to enter the credential source. Any idea where this is configured in CUPS 9.1.1? Thanks.