we have CCM 7.1 and one H323 voice gateway connect to AVAYA BPX with PRI E1.another H323 VG connect to PSTN with PRI E1.
our all ipphone in region A, PSTN's voice gateway in region B AVAYA's voice gateway in region C.
codec design as next: G.711: A<-->A,A<-->B,B<-->B,C<-->C G.729: A<-->c,B<-->C
it works well when 7911 call to AVAYA BPX and all ipphone call to PSTN. But 7975 call to AVAYA BPX, the Call immediately disconnect after avaya's phone one ring,I can not know what's current codec on 7975.
next I take a call from 7975 to 7911, it's ok,and the call status of 7975 display current codec is g.711,then I use 7911 transfer the call to AVAYA BPX,7975 call to AVAYA PBX successfully ,now the call status of 7975 change to g.729.
show call histroy voice with a successful call from 7911(DN:1002) to AVAYA(DN:117000) at next :
I had similar problem when my ATA 186 could not call to Avaya (one ring on avaya phone, and that is all), and other phones did. I also had capture in wireshark with code "no resource available".
Problem was slolved by changing the codec on ATA to g729 despite the settings on Avaya was the G711.
I'm guessing that both 7911 and 7975 are in same device pool and had same CSS and partitions apllied to phone and lines.
Maybe you can try to look at the stream on the web page of the 7975 phone when the phone is transfered and connected to the avaya gw, and see what IP address is remote IP address - maybe it is dsp resource address on voice gateways, and because that the call is posible in that case.
Maybe 7975 is trying to use some defferent flavour of g729 codec, where the 7911 uses g729br8.
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...