[asterisk-dev] Asterisk accept wrong Codec

Steve Underwood steveu at coppice.org
Wed Apr 12 17:40:51 MST 2006


Hi,

G.721 == G.726-32. The ITU renamed G.721 as G.726 some years ago, but a
number of things still refer to it as G.721. That is what you are seeing
in the Ethereal log. If you want to disallow this codec you need to
refer to it as G.726, as Asterisk doesn't recognise the name G.721. As
Joshua said, what you have shown is a system working properly. If it
doesn't work end to end, your problem appears to be in another part of
the signal chain.

Steve


Thomas Winter wrote:

>On Wednesday 12 April 2006 20:19, Joshua Colp wrote:
>  
>
>>Thomas Winter wrote:
>>    
>>
>>>Hi,
>>>
>>>I receive from an SIP Proxy an Session progress with session description.
>>>
>>>from Ethereal log
>>>
>>>Media description:
>>>.
>>>Media Format: ITU-T G.721
>>>.
>>>Media Attribute (a) rtpmap G726-32/8000
>>>
>>>After this Asterisk sends to the Gateway an  G.721 RTP stream.
>>>Because the internal Caller has G.711 there is no sound going through.
>>>
>>>Iam not sure whats happend here, is the SIP Proxy doing wrong or is
>>>Asterisk doing the wrong thing.
>>>
>>>g.721 is disallowed in sip.conf . I also tried to force with SIP_CODEC to
>>>G.726, but Asterisk still sending g.721 to the Gatway on the request of
>>>the Sip-Proxy.
>>>
>>>
>>>In the other direction the Gateway is sending with g.726 to Asterisk and
>>>I have sound.
>>>
>>>thank you.
>>>
>>>best regards
>>>
>>>Thomas
>>>
>>>
>>>_______________________________________________
>>>--Bandwidth and Colocation provided by Easynews.com --
>>>
>>>asterisk-dev mailing list
>>>To UNSUBSCRIBE or update options visit:
>>>   http://lists.digium.com/mailman/listinfo/asterisk-dev
>>>      
>>>
>>That's G726-32. It's perfectly fine... your problem is elsewhere. Have
>>you done an rtp debug to see if you can see the packets going out?
>>    
>>
>
>
>
>Hi,
>
>Iam using Ethereal and can see that the packets are going through.
>
>Ethereal shows me Payload type ITU-T G.721 for these packets, but I did not 
>allow adpcm.
>
>If Iam using Asterisk (same configuration) with another provider g.726 is 
>working perfect in both direction and Ethereal shows me ITU-T G.726
>
>So I assume it must be related to the disallowed but used G.721 format?
>
>
>
>sound ONLY from Gateway to internal phone:
>
>Sent RTP packet to 192.168.2.210:5004 (type 0, seq 58137, ts 281120, len 160)
>Got RTP packet from 194.221.62.163:25058 (type 111, seq 47352, ts 1601345809, 
>len 80)
>Sent RTP packet to 192.168.2.210:5004 (type 0, seq 58138, ts 281280, len 160)
>Got RTP packet from 194.221.62.163:25058 (type 111, seq 47353, ts 1601345969, 
>len 80)
>Sent RTP packet to 192.168.2.210:5004 (type 0, seq 58139, ts 281440, len 160)
>Got RTP packet from 194.221.62.163:25058 (type 111, seq 47354, ts 1601346129, 
>len 80)
>Sent RTP packet to 192.168.2.210:5004 (type 0, seq 58140, ts 281600, len 160)
>Got RTP packet from 194.221.62.163:25058 (type 111, seq 47355, ts 1601346289, 
>len 80)
>Sent RTP packet to 192.168.2.210:5004 (type 0, seq 58141, ts 281760, len 160)
>Got RTP packet from 194.221.62.163:25058 (type 111, seq 47356, ts 1601346449, 
>len 80)
>Sent RTP packet to 192.168.2.210:5004 (type 0, seq 58142, ts 281920, len 160)
>Got RTP packet from 194.221.62.163:25058 (type 111, seq 47357, ts 1601346609, 
>len 80)
>
>Any idea for additional possibilities to find out what is going on here. 
>  
>





More information about the asterisk-dev mailing list