We have 3640 with T1/PRI(NM-HDV) and Analog (NM-HDA 4 FXS and 8FXO). Also we have Callmanager(Primary and secondary). IP Phone (7960 or 7940) use T1/PRI to make call and recieve call. I configure 3640 as h.323.
Now my questions is that:
Our client will order 8 analog lines(attach to NM-HDA) for fax or backup in case T1/PRI goes down, Can "IP Phone" use those analog lines to make call or recieve call????? IF does, how?? Any documentation I can read??
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.
If the 3640 is an H.323 gateway, you should set it up as an H.323 gateway in the CallManager, create a route pattern for calls going out FXO and then point this route pattern at the 3640/H.323 gateway. You'll will need to set up dial-peers on the 3640 for each FXO port and use dial-peer preference command (see: http://www.cisco.com/univercd/cc/td/doc/product/access/multicon/3810soft/cmdref/dpeerref.htm#xtocid313733) to roll through each of your FXO port until a non-busy one is found. Remember that with H.323, CallManager has no concept of the individual FXO's on the gateway, so all calls are simply routed to the gateway and the gateway's dial-peers will have to take care of the rest.
If the 3640 is an MGCP gateway, you should set it up as an MGCP gateway in CallManager and configure each FXO port as an endpoint. Then simply set up the route pattern and point to the appropriate endpoint/FXO port. If you want all of the FXO ports to be used (in case one or more is busy) then set up a Route List and Route Group and point to this with your route pattern. The CallManager will then hit the first MGCP endpoint in the Route List/Route Group and if it is busy, go on to the next one, etc.
Forgot to mention that you'll need CallManager version 3.2.2c (Support Patch A) to use the NM-HDA as an MGCP gateway. This support was just added. If that's not an option, you'll have to use the NM-HDA in H.323 mode.
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.