I am trying to get an external trunk paging system to work on an FXO port off of a vg-200. The paging system is a loopstart trunk system. I can't get the FXO port to go off hook and connect to the paging system. Any thoughts out there???
I know most of the external paging systems that we hook up to we are fxs on our side. This is poor example but do they want us to provide ring voltage or do they want us to emulate something like you home phone. Fxs would provide ring voltage and fxo would be like you home home.
This is a really old paging system. I don't have exact documentation on it of course, that would be too easy. I talked to the PBX guy (its a old Comdial system) and he says its a loopstart trunk that requires my FXO port to go off hook only. I programmed the callmanager to send *1 to the vg200 and then it routes the call to the FXO port. He says it doesn't require ring voltage to make a connection.
For any paging system (even the ones that claim to support trunk/station side ports) it's always a good idea to use a device like Bogen's TAM-B adaptor. It works directly with an FXS port, or you just add a 48v transformer (also sold by bogen) for an FXO port. It will enable a proper talk path with adjustable load settings for almost any paging system. Other features like 'beep on connect', auto hangup after 'x' seconds, and other things.
I've used it on quite a few paging systems with Cisco FXS/FXO ports. Although always try to use FXS ports since a seperate adaptor is not needed.
It shouldn't require anything special. I would recommend using H.323 configuration and set the dial-peer to forward 0 digits. If the paging system is designed for loop-start trunks, it should provide the appropriate talk battery to the FXO port without any further adapters. I'm not sure if the FXO cards for the VG200 expect to have on-hook voltage prior to going off-hook; if so then you will need to change to FXS and install a station level paging adapter like the Bogen TAM-B or Valcom V-9970.
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.