Hello we are running Verizon SIP into CUBE gateways and have run into the following issue:
Verizon's techs are testing with this sequence:
- Call gets connected with G729 codec. Both parties hear each other fine
- Verizon tech sends a fax tone through the line.
- Verizon's gateway sends a G711 request to CUBE gateway, and the call gets distorted.
- If we remove the G711 option, the CUBE gateway doesnt respond to the G711 request and the call will drop after 2 minutes.
So on our end, what needs to happen is:
- If Verizon sends us a G711 request, our CUBE router/gateway should send a REJECT back to Verizon, so that the call stays G729, however what the CUBE gateway is doing is just sitting there and not responding, causing Verizon to disconnect the call after 2 minutes because it is not getting a response.
- Upon doing further research, Cisco had come back and told us that the renegotiation issue was fixed in 12.4.20.T2, which is what we are running on all the CUBE gateways.
Hard to say - the correct configuration would look something like this:
voice service voip
and also either:
depending on sip-sip or sip-h323.
then your outgoing dial peers to verizon should look like:
dial-peer voice 100 voip
session protocol sip
(no codec listed, as g729 is default)
fax protocol none
For a fax call, the terminating gateway is responsible for sending the switchover request. Thus, it doesn't make sense for Verizon to both generate the tone and send the re-invite request from their side. They should only send a switchover request if the tone is generated from your side of the equipment and you placed the call outbound. Otherwise the gateway may act a little strange to an inbound switchover request for a call it terminated.
I will attach the debug and config tomorrow. The reason Verizon is generating a fax tone is for troubleshooting purposes. They can reproduce the call distortion by sending the fax tone.
I understand for a fax call, the gateway is responsible for sending the switchover request, however in the debugs, it shows the codec renegotiation when they generate the tone.
What i dont get is why the call gets connected successfully at the G729 codec and even though there is a fax tone generated, verizon is sending a G711 codec for renegotiation? Shouldn't a connected call at G729 stay G729, regardless of whatever tone generated after?
There's nothing in the logs that would indicate that there is a fax switchover going on. Whatever your devices are that have DSPs in this call flow (the PSTN gateway in the SIP provider network and the IP phone) are causing this problem.
Likely, it will be the SIP provider's equipment that is causing the voice quality problem.
I appreciate your time, Here is the bug ID that i found. Bugs CSCsm34933 and CSCsq01966. However, cisco said it was corrected in IOS 12.4.20.T2
Im trying to get the provider to realize that everything was working fine for at least a few months before the distortion started happening. I am almost positive that Vz patched something on thier gateways, but im stuck here.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...