Here is your response in the IP messaging 183 Session in Progress to the codec negotiation. Your equipment is not responding w/the correct DTMF Option. Please see highlighted below. This shows the G.729 codec w/in-band DTMF, because there is no 100 telephone event in your response.
The voice class codec 55 puts the g729a as the preferred one.
Your answer gave me the idea where to look and found that the calls that doesn't match the dial peer 4000 and go by the default (PeerID= 0) are shown at the show call history voice command as using tx_DtmfRelay=rtp-nte
while the calls that do match the dp 4000 for an unknown reason are shown as using tx_DtmfRelay=inband-voice.
I am looking for a reason but I think it is with the supplier of the DIDs as another supplier using the same dp4000 and also G729a codec looks like using rtp-nte.
The calls that match the dial peer 4000 do not use the dtmf relay rtp-nte so they do not accept the RFC 2833. If I edit the FROM header at Sip server level in a way that it do not match the dial peer 4000 and go to the default the call is shown as accepting the RFC2833.
I don't find a cause to this. So because I need the calls using the RFC 2833 I am editing the headers and making them use the default DP. Not the solution I like but is working.
Introduction: The "external-out enable" command is available for
configuration under the "router ospf process" in case of the IOS-XR
operating system. This command basically enables advertisement of
intra-area routes on the device as external routes in th...
IntroductionIn this article we'll discuss how to troubleshoot packet
loss in the asr9000 and specifically understanding the NP drop counters,
what they mean and what you can do to mitigate them. This document will
be an ongoing effort to improve troublesh...