I have Unity 3.1.5 8 port 100 user with Call manager 3.2.2spE. When I look at call viewer on Unity the port ID on calls that hit Unity always starts at 4 and continue with 5,6,7,8. On several occasions my ports fill up and users cannot access voicemail. Is there anything I can look at why 1,2,3, ports are not beeing used?
I thought it might of been a calling search space issues but I have looked at my settings on VM ports on call manager and all settings are identical.
make sure there's no call forward all or something configured on the first port. They should have the same partition/calling search space.
When you call into voicemail, what phone number does it reach? Is that phone number the first port? If not, then you'll have to look at the callmanager configiuration and possibly traces as to why it's not going to the first port. Some possible causes...the first 4 ports aren't registered; there is forwarding (call forward all) set; some ports are in a different partition; etc.
All ports have identical search spaces and partitions. All ports say registered in call manager. No ports say call forward all. 5000 is my Voicemail DN. when you hit the messages button or dial 5000 it automatically goes to 5003 which has trunk ID of 4. Any ideas??
The ports are in a hung state, still showing idle. If a reset of the individual ports will not release the ports then a reboot of the Unity server will release all hung ports. A bug has been noted with Cisco. This worked for us.
not sure? I never really found out. I ended up getting the latest TSP installed that was compatible with the version of unity that I am running. I did find some bug ID's about unity port lockups if you are running G.729 codec.
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...