09-12-2002 07:55 AM - edited 03-12-2019 08:44 PM
I have a problem whereby when you hit the 'messages' button on the ip phone, it tries to dial the first voicemail assigned # (eg 7000). However, if this port is in use, it is configures (in ccm) to roll over to the next available port (eg 7001). However, it does not attempt to dial the next available port, but simply tries the first listed port of 7000, and returns a busy signal until it is free. If you manually dial 7001, it works ok.
I've tried deleting the voicemail ports on ccm 3.1(1) and recreating them, but to no avail. I'm going to upgrade the TSP on unity (build 2.4.6.126), but am not sure if there something else worth checking on the ccm?
Regards
Azam
Solved! Go to Solution.
09-12-2002 08:14 AM
Make sure you don't have Cisco Messaging Interface Configured. I would stop this service. If you're using Unity, chances are you don't need this service. I had the same issue that you are having and it turned out that I configured this service thinking it was related to Unity. If you put 7000 in the CMI config then it's giving you the busy signal.
09-12-2002 08:14 AM
Make sure you don't have Cisco Messaging Interface Configured. I would stop this service. If you're using Unity, chances are you don't need this service. I had the same issue that you are having and it turned out that I configured this service thinking it was related to Unity. If you put 7000 in the CMI config then it's giving you the busy signal.
09-12-2002 10:31 AM
I have the same problem. I deleted CMI, didn't need it.
I have verified:
CallManager(s)
AdvancedCallForwardHopFlag
VoiceMailMaximumHopCount
Cisco Messaging Interface Configuration
All Ports are accessible from Phone
Occurs on-net and PSTN calls
Unity
Port Configurations
Suggestions ??
Thanks
09-12-2002 01:30 PM
Thanks for your feedback guys. I'll give your suggestions a try and let you know the outcome.
09-22-2002 12:18 PM
Sorry for the delay in replying.
I disabled the Cisco Messaging Service as you suggested, and it done the trick immediately. Everything is now working ok.
Thanks again for your input.
09-12-2002 12:12 PM
I had the same issue a couple of days ago. I resolved it by "updating" the first port (7000). I changed its extension updated, and then changed it back the correct port number. I have not had any issues since.
geoff
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide