Call Manager 3.0(5a) Leaving and retrieving VM

[mslaga]

We are integrating CCM 3.0(5a) and are having an issue with subscribers retrieving their voice mail. When Unity is called (Messages or extension) they are given the generic voice mail requesting their ID. Is there any way to send them directly to their Voice mail? <br><br>We are getting the same issue when you call a subscriber and are sent to voicemail. It again asks for the subscribers ID. It does not appear to be sending the extenstion information with the call.<br><br>Thanks for your help, <br><br>Matt Slaga<br>TimeBridge Technologies<br>MCNE, MCSE2k-4.0-3.51, CCNA, CIPT2.0

[#2]

Since Call Manager 3.0(5a) just came out a few days ago we have not finished testing our integration with it.

But I have it running in my office and I was not able to reproduce this problem. If you run the Call Viewer utility in the "Start Menu"->Programs->Unity->"Call Viewer" it will let you see the extension information that Unity is seeing.

If the extension information is not showing up, your key is probably not setup to do a TAPI integration. Contact Our technical support about upgrading your key.

If the extensions are showing up correctly, then you the probably set the extension of the Open Greeting equal the extension of the first Unity port. Change the extension of the Opening Greeting and this will fix the problem.

You can also contact out technical support and they will help you trouble shoot the problem.

Aaron Belcher
Software Engineer
Active Voice
abelcher@activevoice.com

[#3]

This means that 2.4.5's integration to Call Manager 3.0(5) is now 'true' TAPI? Not Skinny?

If so, has there been any call measurements on this integration yet? (How many simultaneous call per second)

Of course, everyone currently running Unity 2.4 and Call Manager 3.0(4b) or earlier together, will NOT be using TAPI integration. Is Skinny integration no longer an option?

Thanks
John.

[#4]

Actually, this just means we’re looking for the “TAPI” integration type on the key. The integration itself still uses the “skinny” protocol… up till 2.4.5 we allowed the integration type of “None” to still fire up the connection to CM. Starting with 2.4.5 you have to order the TAPI integration to be able to do this. This way the marketing and sales guys can charge for it now ;->.

If you run the Key Dump utility in the Unity programs folder and your integration type is "None", the integration with CM (via Skinny) wont work fully. You have to get a key upgrade so it says "TAPI".

When you order 2.4.5, you should request a key upgrade code at the same time. New orders will come with keys properly programmed, of course.



Jeff Lindborg
Unity Product Architect
Active Voice
jlindborg@activevoice.com
http://members.home.net/jlindborg