If your Cisco 2620 is operating as an H323 gateway, it could be the pid used for the outbound leg of the outbound call.
Make an call to the outside through the gateway. If you then issue a "Show call active voice brief"
This will display several lines corresponding to the call legs of the h323 call. You should notice the listed pid number for each call leg. If you notice any of the pids showing pid(0) then it is using the default pid. The default pid has VAD enabled. The default cannot be modified, so you have to tell your h323 gateway which dial-peer configuration you want to use for the outgoing leg of your h323 calls.
This can be done by adding an incoming called-number statement to one of your dial-peers
For example if you the following dial-peer configured:
dial-peer voice 10 voip
destination pattern 2000
session target ipv4:10.1.1.1
You could add the following line to that dial-peer
incoming called-number .
and any outbound call would then have a match and would use the no vad statement from this dial-peer.
If you again place a call and show the active call you should see the outbound call leg on pid(10) instead of pid(0).
I have configured " incoming called-number .. "on the Voip dial-peer it works fine regarding VAD. But the problem is i have still 2 other dial-peers for fax transmission. The command "incoming called-number.. " on the voip dial-peer in direction call-manager effectuar that all calls take this dial-peer in the backward direction. The consequence of that is that i can receive fax but not send any fax.
Can I disable VAD when i set the command "voice vad-time " to 65536 ?
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...