AutoAttendant not responding for calls from H323 GW
I have a 3662 configured as H.323 GW. Outgoing calls are going OK. For incoming I dont have the DID enabled. Over the campus I have configured the CCM 3.2(2c) with the AutoAttendant. AA is working just fine if someone dials the Directory No. assigned to the CTI-RP from an IP Phone installed inside the campus. But when the calls coming in from PSTN through the H323 GW come in, the caller gets a busy tone when he dials the DN assigned to the CTI-RP. I tried to configure PLAR connection on the GW (to simulate a one-stage dialing), but did not work. Then I configured the dial-peers for this specific DN of the AA-CTI-RP, but still user gets the same error. Debugs show the cause code of "Resource not available".. Though the
What could be the problem. Is there some bug in the H.323 GW and AA's interfaction etc.
Re: AutoAttendant not responding for calls from H323 GW
The problem is probably codec related. The CRA Applications (AA, IVR, ICD, CCC) were designed to handle only g711 codec and not low bit rate codecs. Verify (through debug voip ccapi inout) that the dial peer on the H.323 gateway that sends the call to the CM is configured for G.711. The default codec on a voip dial-peer is g.729.
To work around the problem, either configure g.711 on the outbound voip dial peer, or introduce a transcoder resource.
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...