I have a translation pattern set to send my main number to a pilot point with several hunt group members and then to voice mail. The voice mail is the last option and is set to always route, but sometimes I get a message from the phone company saying this is not a working number. I assume that there is an issue getting the number to the pilot point, I'm just not sure why. Any suggestion would help!!!
First thing, if you're running CallManager 3.3(3), is to make sure you are running the latest service release. That is SR4A as of this writing. The initial SR4 release had a very critical bug which caused route points and route patterns to occasionally disappear out of the route plan. We have worked together in the past on a customer in Rosemont, IL who I know was running SR4; if this is about them, you should upgrade them ASAP.
After that, you need to narrow it down to a TCD issue or a gateway/codec/location issue. Take some number of phones in the same Region and Location as the TCD hunt group, and fill up the TCD hunt group repeatedly until you spill over into voicemail, preferably multiple calls into voicemail simultaneously.
If you can't get through an internal test successfully, your problem domain has been reduced to something wrong with TCD and you'll want to work with Cisco TAC. If that test does work, you probably have a problem with a gateway CSS, codec/region or location. You're having trouble finding the voicemail pilot partition, or you're having trouble getting a transcoder in the loop for a g729 call into the g711 Unity system, or you're out of location call admission control bandwidth.
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.