I am running CallManager 3.3 and have tried to configure a hunt group to roll over to Unity if all agents are busy. The DN of my voice mail pilot point is 1020, as is the first port of the Unity system. When all agents are busy, the hunt group works fine and will forward to voice mail. However, if somebody dialed into voice mail on port 1 (the one with DN 1020), the user calling the pilot number receives a busy signal. If I configure the hunt group to point at the second voice mail port directly, everything works fine and multiple users can be in the voice mail system and roll over from the hunt group at the same time. I have tried configuring the hunt group with the check box "Always Route Member" checked and unchecked with the same results.
I would think that I should be able to point the hunt group at the pilot point number of the voice mail system instead of having to point it at a subsequent port to get it to work. Does anybody have any suggestions on how to make this work?
Re: hunt group problem with voice mail pilot number
There was a configuration in CMI for the voicemail DN and partition. I removed it, restarted the CMI service and everything worked. Why would the CMI configuration have anything to do with hunting to the next port?
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...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.