Sorry for the details below, this is all very new to me.
I have a remote site that has a 2811 router with a four port FXO card in it. This router had a channelized t1 back to the telco (verizon) and a point to point t1 back to one of our campuses. We recently updated that channelized T1 to a full T1. Is there any thing else that needs to be configured on this router or the call manager to take advantage of the extra channels?
Also, I'm seeing quite a few of the following in syslog and they always appear on the same voice-port.
Im confused as to why the first three channels of the circuit are E&M wink, and the rest are digit FXOGS. Is that a misconfiguration? Or is the other side of this circuit actually provisioned like this?
The error message means that we're waiting for the other side to ground their tip, and we never see it. That's required for an outbound call to work for answer supervision. 'debug vpm sig' and 'debug voip ccapi inout' would show more detail into this behavior, but it looks like something isn't provisioned right if you're seeing that message and the timer for that state pop. Verify that the channels are all configured for the right signaling type (should they all be e&m wink, perhaps? Is the other side configured for FXSGS on those other channels [because FXO always connects to FXS]?).
Oh and since this is H323, no changes are necessary on CM.
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...