Callpilot VPIM integration to Cisco unity

[mrusso64]

Having problems making this work. Can anyone tell me the settings on the callpilot side to make sure I'm not missing anything. When I try to send a message to Cisco mail box. I get a return message saying that it could not send message because the Cisco mailbox is is not accepting messages at this time.

Mark

 

[KCFLHRC]

Maybe something as simple as the Unity Mailbox has not been initialized?

 

[mrusso64]

This is a new install to network with Cisco. It wasn't the only mailbox and the problem was both ways, Anyway, Cisco recommended a software patch on there side and it seemed to work. Able to send and receive messages now. Only a few kinks to work out now.

For anybody reading this threat for the same reasons, here's what you should know on the callpilot side.

1- You need to have a Fully Qualified Domain Name from the customer network (FQDM) for your CallPilot. Not just a server name. Example callpilot@business.com

2- Build a remote server in (Messaging / Message Network Configuration) settings, and in properties define there Cisco Unity FQDM, a site ID number and type of matching protocol used (VPIM) for both V/mails systems.

3- Your might need to define a prefix in the server location properties settings as well as VPIM network short cuts(The DN ranges of the other sides mailboxes).

4- In the (Messaging / Message Delivery Configuration) settings you need to define the customers SMTP Mail Proxy Server in the SMTP/VPIM section.

These are the basic settings needed to do this. Some tweaking are your part might be needed. But this will get you going and save a lot of time that I wasted figuring it out by trial and error.

From what I understand there is no documentation on networking a Callpilot with a Cisco Unity.

Mark

 

[KCFLHRC]

Yep, VPIM uses FQDN

 

[KCFLHRC]

Details

CallPilot VPIM not working between CallPilotl 5.0 and Cisco Unity voice mail system.
Reviewed remote Cisco server created in Networking. Cisco server set as a CallPilot system.
Problem Clarification

CallPilot VPIM not working between CallPilotl 5.0 and Cisco Unity voice mail system
Cause

Incorrect configuration.
Solution

As per NTP NN44200.201 - Avaya CallPilot Networking Planning Guide, Chapter 4: Understanding Avaya CallPilot Networking Solutions, on the VPIM Networking section:
VPIM Networking provides CallPilot with the capability to exchange multimedia messages using an IP intranet or the Internet. VPIM Networking can exchange messages with any other system that uses the same data communications protocol, regardless of vendor. VPIM Networking formats and sends messages using industry-standard application protocols. Messages are sent across either a private data network, such as an intranet, or a public data network, the Internet, for delivery. With VPIM Networking, users can exchange messages with both open and integrated sites. For VPIM Networking to work within a private network, the destination must support VPIM and must be in the local network database.

Issue was corrected by changing Server Type on the Remote server: Cisco Unity, from CallPilot to Other.