I'm trying to understand some odd behavior we were experiencing to a Valcom V-1109RTVA in our pre-cutover testing last night.
The Valcom is connected via an FXO port on an MGCP-configured gateway. It is a 9-zone system and I beleive it only requires a single digit once tip/ring is closed. Our goal is to have users dial 79x, where x=zone. I received the following behaviors for each of the following route-pattern configurations:
Result: Busy Signal
Result: Nothing, but if you dial another digit (e.g., 7900, 7901, 7902, etc.) it pages to the proper zone.
If I waited a couple of seconds between 790 and the last digit "x", I would get a tone back from the Valcom unit, and no page worked. I assume this is a timeout.
So it appeared the only way I could get the Valcom to work was to send it a 0 first. Is this a timing thing with the Valcom? Is there another RP config I should try?
I had also tried RPs like 79.5 (discard predot) 79.2, etc. etc. without success.
I have the same Valcom and an MGCP configured Gateway with FXO port. Exception is CM4. I can't get any response from the Valcom. Did you do anything unusual in the setup of the port to get the Valcom to respond?
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.