[Asterisk-Users] Teliax users, g729 question

[Chris Coulthurst]

FYI, Im using g729 with Teliax, and have been for about 1 week with no 
problems, good audio quality.

They DO seem to drop registrations unexpectedly at times, but as for codec 
usage, so far so good.

Chris Coulthurst
chris at shuksan.com

----- Original Message ----- 
From: "Rich Adamson" <radamson at routers.com>
To: "Asterisk-users-list" <asterisk-users at lists.digium.com>
Sent: Monday, October 10, 2005 6:58 PM
Subject: Re: [Asterisk-Users] Teliax users, g729 question


>
>> > > > I am using Teliax to terminate my calls, and I have 3 licenses' for
>> > > > g729 from Digium. "show translations" verifies that the 
>> > > > registration
>> > > > took place.
>> > > >
>> > > > When I place a call, having "allow=g729" as the only allow option 
>> > > > in
>> > > > iax.conf, I get the following error:
>> > > >
>> > > > WARNING[361]: chan_iax2.c:6017 socket_read: Call rejected by
>> > > > 208.139.204.228: Unable to negotiate codec
>> > > >
>> > > > If I place a call with g726 as the only allow line, then the call
>> > > > completes as desired. I realize I could just use that (g726), but
>> > > > it seems odd that I cannot connect using g729 when both of us 
>> > > > support
>> > > > it.
>> > > >
>> > > > I have checked, double checked, triple checked my account with 
>> > > > teliax,
>> > > > and made sure that the g729 box is checked for both sip and iax. I
>> > > > have also contacted support, they have responded, but not with
>> > > > anything that would be considered helpful.
>> > > >
>> > > > My question then to you all is this: Are you connecting to Teliax 
>> > > > via
>> > > > g729? if so, how... what are you doing that I might be missing?
>> > > >
>> > > > Your guidance will be most appreciated.
>> > >
>> > > I just tried g729 with teliax this morning. It worked fine in both
>> > > directions using three different did's from them.  I did have one
>> > > test call where audio was one way though.
>> > >
>> > > During those test calls I watched the CLI and the calls definitely
>> > > were g729 without a doubt. I used the exact same teliax server you
>> > > show above.
>> > >
>> > > I'm running cvs-head from yesterday.
>> > >
>> > > If you do a iax2 debug, you should be able to spot which system is
>> > > not compat with g729. That should lead you into diagnosing the
>> > > problem a little deeper.
>> > >
>> >
>> > Rich,
>> >
>> > Thanks for taking the time to check and respond, and for your advise.
>> >
>> > I did as you said, and here is the output:
>> >
>> > ============================
>> > pbx*CLI> iax2 debug
>> > IAX2 Debugging Enabled
>> > Tx-Frame Retry[000] -- OSeqno: 000 ISeqno: 000 Type: IAX     Subclass: 
>> > NEW
>> >    Timestamp: 00016ms  SCall: 00002  DCall: 00000 
>> > [208.139.204.228:4569]
>> >    VERSION         : 2
>> >    CALLED NUMBER   : 1917XXXXXXXX   (I XXX out the number)
>> >    CODEC_PREFS     : (g729)
>> >    CALLING NUMBER  : 4401
>> >    CALLING PRESNTN : 0
>> >    CALLING TYPEOFN : 0
>> >    CALLING TRANSIT : 0
>> >    CALLING NAME    : John Reynolds
>> >    LANGUAGE        : en
>> >    USERNAME        : reynj
>> >    FORMAT          : 256
>> >    CAPABILITY      : 63744
>> >    ADSICPE         : 2
>> >    DATE TIME       : 189432385
>> >
>> > Rx-Frame Retry[ No] -- OSeqno: 000 ISeqno: 001 Type: IAX     Subclass: 
>> > AUTHREQ
>> >    Timestamp: 00003ms  SCall: 00073  DCall: 00002 
>> > [208.139.204.228:4569]
>> >    AUTHMETHODS     : 2
>> >    CHALLENGE       : 303570605
>> >    USERNAME        : reynj
>> >
>> > Tx-Frame Retry[000] -- OSeqno: 001 ISeqno: 001 Type: IAX     Subclass: 
>> > AUTHREP
>> >    Timestamp: 00080ms  SCall: 00002  DCall: 00073 
>> > [208.139.204.228:4569]
>> >    MD5 RESULT      : 6006ef53daa295d58f5292837a4edb60
>> >
>> > Rx-Frame Retry[ No] -- OSeqno: 001 ISeqno: 002 Type: IAX     Subclass: 
>> > REJECT
>> >    Timestamp: 00060ms  SCall: 00073  DCall: 00002 
>> > [208.139.204.228:4569]
>> >    CAUSE           : Unable to negotiate codec
>> >    CAUSE CODE      : 58
>> >
>> > Oct 10 16:18:03 WARNING[364]: chan_iax2.c:6017 socket_read: Call
>> > rejected by 208.139.204.228: Unable to negotiate codec
>> > =================
>> >
>> > I am I wrong in thinking that I my call is trying to connect via g729,
>> > but that Teliax is rejecting it?
>
> Okay, in the above, you transmit a packet that has FORMAT : 256 which
> is g729 (see 'show codecs'). After the challenge/response, they send you
> 'REJECT, Unable to negotiate codec'. So, yes, teliax is rejecting your
> call due to the lack of g729 support on their side.
>
> I was just going to log into their web site to check my settings, and
> their web server is broken right now. I've also been experiencing many
> errors with teliax.com in the form of no call progress when dialing any
> call. So, they are either having serious problems, went broke, or
> something.
>
> On the g729 issue, the folks at teliax.com would have had to either 
> purchase
> codecs from digium, or, installed an illegal codec. Presumably, if they
> installed xx number of g729 licenses and those licenses were already
> consumed, would they reject the next call (like above)? Probably.
>
> So, can't tell if they simply ran out of licenses, have a configuration
> problem for your account, or their system is simply broken. In any case,
> you can't do anything to fix it other then to open a problem case with
> them or use a different codec. Gsm is pretty good. :)
>
> Rich
>
>
> _______________________________________________
> --Bandwidth and Colocation sponsored by Easynews.com --
>
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>