02-14-2005 07:52 AM - edited 03-18-2019 04:12 PM
All,
We had, up until recently, a Unity 3.1 and CM 3.1 system integrated. The CM version was bumped to 4 last weekend. Since then, the following behavior has been noticed:
When a caller calls in from the outside, they get the automated attendant. If the subscriber is logged in, and release to switch is set for the user, everything works great. If the subscriber is not logged in, however, and the release to switch is set for the user, you hear nine rings and then the call is terminated.
It did not work this way before. Before the upgrade, whether you were logged in or not, it worked the same way.
In the meanwhile, the CM administrator has set the supervise transfer setting for all users, but the downside to this is that the user no longer see caller ID information when being transfered from the automated attendant.
Anyone have any ideas what we can do to fix the situation? I just want the functionality we had before.
Thanks in advance,
Craig
02-14-2005 06:03 PM
Hi Craig -
You didn't mention which 3.1 version you are running, but I would make sure you are running a compatible TSP version for Unity and CallManager 4.x - http://www.cisco.com/en/US/customer/products/sw/voicesw/ps2237/prod_pre_installation_guide09186a00800f1e98.html
I'm not sure if this could impact you or be related to the problem you are experiencing, but the voice port configuration for Unity with CallManager 4.x changed to take advantage of the hunt and line group features in 4.x. See this hyperlink - http://www.cisco.com/en/US/customer/products/sw/voicesw/ps556/products_administration_guide_chapter09186a00802deb09.html#wp1032198
to see if it applies to your environment.
Best wishes,
Ginger