We have CCM 3.3 which has been integrated with avaya s8700 on an ip trunk. The avaya CLAN has been configured as a H323 gateway and a route pattern has been defined to route the calls towards it.
Now i am able to use this route pattern and seize any avaya trunk for making calls but the reverse is not happening i.e from the avaya ip phones i am not able to utilize the channels configured on my VoIP gateway to make outbound calls
Can anyone tell me the configurations that is required to make this happen
I will happy to provide more information if required
I suppose you configured already the DPs as necessary. Why don't you take a "debug voice dialpeer" and perhaps "show dialplan number" to see if configuration is right. If not sure post the above with config here and explain how the dialplan is.
this config is for the outbound DP. For inbound, you need should configure as per previous message. Actually you can leave out the direct-inward-dial because it does not apply to incoming voip. The alternative is to configure the avaya so calls intended POTS outbound on cisco GW are sent directly to it, and not to the CCM. Kind of like having two DP on the avaya. This is especially true in the case CCM 3.2 is not able to route the calls on the h.323 trunks, or it does not supports redirection, or the latter is not supported by avaya.
Thanks for the nice rating and let us know if it works!
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...