Skipping past voicemail message header?

[gergs00]

We've just rolled out our IP Telephony (CCM + Unity 4.03) solution to a user community that is coming from the Avaya Intuity Audix system. When listening to voicemail messages, is there any way to skip past the message header and just listen to the message itself? This was a feature of the Intuity system that people used often.

[gergs00]

I've attempted pressing 9 to fast forward, but this does not necessarily get you right to the start of the message. In fact, it is a few seconds past it.

[lindborg]

one way I think you can get around this is to use the "replay message" key and set the system to not replay the message header. In the Advanced settings tool you'll find a setting for "Conversation - Do no replay message summary". Set it to "1" for true and then when you're listening to a message (even during the header) you can hit "1" (standard conversation) to replay the message - this will have the effect of winding the message to the start of the body I believe which shoul do what you want.

[lindborg]

Follow up to this - you'll need 4.0(3) SR1 if you don't have it already.... here's the release notes section that talks about this feature:

http://www.cisco.com/en/US/customer/products/sw/voicesw/ps2237/prod_release_note09186a0080205a1e.html#wp58656

[gergs00]

I believe this will work. I used the Unity Tools and looked for the topic in Advanced Settings and found it. I set the value to 1, and waited until after hours to restart the primary Unity server. In the meantime, the secondary Unity server Failed Over. As the primary came back online, I noticed that the AvCsMgr could no longer start. Obviously, without this service, Unity will not work. I tried starting the service manually, but no luck. The failover monitor showed the primary server as Inactive - Not running. So I set the value back to 0 and restarted the server once more. Fortunately, the servers are now operating normally, and I was able to fail back to the primary. Was I missing something? Should it have worked? Or will I need to shut down both servers? I noticed the secondary Unity server Unity Tools does not show the same advance settings field. They both show 4.03 SR1. What gives?

[lindborg]

Setting a conversation option like that would have no bearing at all on AvCsMgr starting (or it shouldn't). In fact you shouldn't even have to restart Unity at all for the registry key entry there to take effect - just change it in AST and give it a try, don't restart.

The generic "you may have to restart..." message there is because some settings _do_ require this and it changes across versions (later versions require this less and less over previous versions). In fact, for 4.0(4) and later I'm removing that message entirely except for a few system related keys.

[gergs00]

Great. I was hoping a restart was unneccessary. I'll give it a shot.

What about the AvCsMgr service? If I should need to restart the Unity server in the future, I'd like to know why this setting would prevent the service from starting. Do you believe the change to the registry key is not impacting the service at all? I can try it again to be sure, but I attempted restarting the server twice last night, and the service failed to start each time. Only when I switched the registry setting back to 0 was I able to restart the server without a failure.

[lindborg]

I'm not sure - I'd have to see the event log messages during startup to get an idea of what component was failing - there will be a series of creates followed by inits followed by runs of each of the various Unity components - one of them was getting cranky at startup and would have thrown an error - this would at least give us a clue.

You _are_ at 4.0(3) SR1, right? Not just 4.0(3)?

[gergs00]

Correct. We're using 4.0(3) SR1. I'm attaching a copy of the application event log. The time to focus on is 10:04 PM on Aug 9th.

By the way, the registry setting worked. We can press 1 to skip to the beginning of the message body.

[lindborg]

Unfortunately the text dump there is just the error titles and such - I need to see the error body (the things that have component names, lines of code throwing errors and such) to get much use from the startup messages.

[gergs00]

Can I send this to you off line? I don't want my dirty laundry out on the net.

It's an 8Mb file.

[lindborg]

sure... lindborg at cisco dot com

[kleo]

you should of gone with Avaya Modular Messaging 2.0 instead or stuck with intuity.

[tabbott]

Are you saying to use the Avaya Modular Messaging rather than Unity? I was thinking about that. Have you done it?

[kleo]

Yes i have via qsig. What i like about the Avaya MM is the Intuity TUI (happy endusers)and IMAP4 integration . Here's two configuration docs depending on ccm version.

http://www.cisco.com/application/pdf/en/us/guest/products/ps5820/c1072/ccmigration_09186a008039073b.pdf

http://www.avaya.com/gcm/master-usa/en-us/resource/assets/applicationnotes/mm-ccm.pdf