Since there has been no response to your post, it appears to be either too complex or too rare an issue for other forum members to assist you. If you don't get a suitable response to your post, you may wish to review our resources at the online Technical Assistance Center (http://www.cisco.com/tac) or speak with a TAC engineer. You can open a TAC case online at http://www.cisco.com/tac/caseopen
If anyone else in the forum has some advice, please reply to this thread.
Yep, I've done this at a few schools. You will use an FXS card on your gateway router that will tie into some type of junction box between your Paging System and the FXS port. Viking makes these junction boxes. You then setup an H323 device. Assign that DN to your FXS dial-peer. Share that DN on another phone ie. you main receptionist phone. Then when calls are transfered to this shared line, it will ring on your paging system and the shared extension on the receptionist phone. You will then assign that shared DN to a Call pickup group. This works great but as you can imagine, its very complex.
Would you clarify what you mean by setting up an h323 device?
In this case we have a 4224 where the fxs port is terminated. It is already acting as an h323 gateway. Do I set up an h323 client on the gateway through ios, and associate that with an h323 client phone on call manager? I just tried that with no success.... maybe there are commands on the 4224 I'm not aware of.
If you are using MGCP, simply setup a call pickup group and assign all the extensions (bell and phones) to that group. Then forward the calls to the extension that has the bell attached. When the bell rings, someone picks up the phone presses more, then call pickup and the call is transferred the their phone.
However, the gateway in question needs to run h.323 for SRST. Which brings me to another question: can you run two control protocols (mgcp and h.323) at the same time on the same gateway? I tried to do this with the 4224 with no success. Has anyone else been able to do it?
That was the same problem I ran into with the SRST code. You need to create a secondary IP address on your router's interface that the "h323-bind" command is currently applied. Then you create a new "h323-bind" command to this secondary IP address. In CM, create an H323 device with this IP address. Assign this device a DN that is shared with your receptionist phone and assign this DN to your FXS port. It takes some playing around but it has worked great for me.
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.