I've got an elevator phone that I'm trying to create. The phone is analog connected to a VG224. When someone in the elevator picks up the phone, the phone needs to hotdial a specific extension. The phone also needs to allow for receiving calls, too, as per code.
I have the phone configured per the hotdial configuration example and works fine for dialing out. However, when we try to call the phone, we get an error message from the system. We did put the phone line in the partition that all of the phones that need to dial it are in. We continue to get the same error.
How do we configure this phone to allow someone to dial the phone directly while allowing on hotdial dial out??
I followed the config verbatim in the doc. That worked fine. Then I just changed the line partition to the partition where all of the extensions are. Picked up the "elevator" phone and it dialed the other phone. Took a third phone and tried to call the elevator phone (both lines are in the same partition) and got the "That number can not be dialed" error message.
"...config verbatim in the doc." Could you be more specific on which document? The error message you hear is coming from the Annunciator and is triggered when the number you are trying to dial is not reachable from the station placing the call. Can you take a look at DNA (https://yourPubIP/dna) to see what the call path should be? The tool is pretty intuitive. You can actually dissect the dial plan from the perspective of the line which you are testing your call from.
If the DNA tool shows everything is fine, then the gateway may be rejecting the call. But I am not sure if that jives up with what I am assuming is your config. Are you using SCCP, H.323 , or MGCP on your voice gateway. I suspect either SCCP or MGCP since you were speculating about partition assignments.
Check DNA first, let us know if you need clarification.
Yeah, I did do DNA and everything should route correctly. I first tried this out using my ATA186. Tomorrow, I'll be trying it with the VG224... just waiting for the contractor to finish with the 66-blocks.
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.