When we have a call from Avaya PBX to CCM extension, on our phone, we can see only the name of other end extension but it is not showing corresponding number. As per Avaya support team, they have allowed to display Name and Number from their end. If we make a call to Avaya's Extension:, They are able to see only the number but not the name.
When there is a call between CCM and Avaya, we should be able to get both the caller ID Number and the Name.
Remote end Avaya Model: Avaya S8300 with Gateway G450 Ver. CM5.2
1. Signaling H323
2. VOIP CODECs : G.729A PT : 20ms
3. UDP port range used: From 16384 to 32767
4. Send any prefix before the extension number: NO
CallManager version 6.1
CUCM 6.1 and awaya Pbx connected via VPN
tunnel. We directly registered Awaya PBX as a h323 gateway (just like H323 router gateway).Calls are working fine from both end.
It could be an issue with the software version Avaya is using on their switch. I know it will not work if you are using some "software package" I think they call it that is not (I think it's a networking package) a high enough release.
Can you please clarify more regarding this.As per Avaya support team, they have allowed to display Name and Number from their end. Avaya Team checked their logs and confirmed that, when there is a call from Avaya PBX extension to CCM's extension, Avaya system is successfully sending corresponding name and extension number information to CCM.
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...