i assume u have configured ur new gateway for the new T1 in the GW part, now in ur CCM admin page, u have to add this gateway, go to Device -> Gateway -> ur 3745 gateway -> besides subunit u will find like two ports -> configure the new gateway (the new t1 card) settings.
then under call routing - route hunt - route group add this new port (new t1) in ur existing route group
now calls will be circulated (default) between the two t1's
no other config in ccm required (assuming the 2 T1s have the same expected digits when receiving/sending digits). it uses the existing h323 gateway device in ccm and all existing Route patterns pointing to your gateway.
from your configuration, the outgoing dial-peers should be okay. by adding preference command to your second dial-peer, VG will forward all calls to port 1/0. if all ports are busy, h323 gateway will automatically use the T1 in 2/0.
by using trunk group hunt scheme, you can manipulate the selection of the ports.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...