We have had an ongoing situation where a caller will finish a call, hang up, Unity releases the voicemail port, but the phone switch still shows the port as busy. This will cause the calls to voicemail to roll ports, and if the system is busy, will play the opening greeting and not the subscriber log in once they get an open port. This happens most often when the system has been busy with calls. I can go into the phone switch and release the port manually and it will be working properly for a few days and the problem begins again.
We are running Unity 2.4.6 on a Windows 2000/Exchange 5.5 box. Our phone switch is a Nortel Meridian 1, option 11 C and we are using Calista boxes for integration.
Of course, the phone people say it's the voicemail system. Any suggestions? Thanks.
I am very interested in your busy port situation. From your description, we have had almost the exact same scenario for the past 8 months since we have been running Unity 2.4.6. We have had a case open with TAC (C285575) for almost as long. We've reinstalled the Dialogic board and drivers and verified all the Dialogic hardware settings, upgraded/replaced the PBXLink 3 with a PBXLink4 box. About the only difference is that we are using an Meridian Option 61.
We had a TAC case open and just let it close. We moved all the cards on the voicemail system, we moved the analog cards in the switch, we've replaced cables. The only thing we did not do was change the Calista boxes. I just go into both systems regularly and disable the ports in the phone switch and re-enable and it solves the problem for a few days. If I get it resolved, I'll let you know.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...