asterisk users - Feb 2005 - Re: Codec Issue on IAX trunk? (Solved)

Hi Rich -
> Personal opinion (and everyone has one) is the problem is a little
> deeper then just a codec. Try 'iax2 debug', place a call, and look
> through the early part of that trace. Are IP's right, etc?
>
> I believe the native 0 is simply suggesting there is no match when
> negotiating the codec. The "4" is ulaw (show codecs).
>
> If you can, post the appropriate iax contexts from both sides (change
> the passwords) and maybe some of the debug. (Or better yet for now,
> email that to me directly and save the list a little bandwidth.)

I believe you are right that there was a deeper problem.  
Unfortunately, I don't know what it was, but at least things are 
working right now.

I got really suspicious when the iax2 debug showed.... nothing!  I 
screwed around with the config a little more and found that the error 
message I got was really only coming from one side, and not the other.  
I restarted asterisk, no dice.  I stopped asterisk, recompiled from 
exactly the same source, started up again, and all is well.  Don't know 
what's behind that.  Hmm.

Anyhoo, thanks for the user/peer setup and your time!

Thanks,
Noah

> > Personal opinion (and everyone has one) is the problem is a little
> > deeper then just a codec. Try 'iax2 debug', place a call, and
look
> > through the early part of that trace. Are IP's right, etc?
> >
> > I believe the native 0 is simply suggesting there is no match when
> > negotiating the codec. The "4" is ulaw (show codecs).
> >
> > If you can, post the appropriate iax contexts from both sides (change
> > the passwords) and maybe some of the debug. (Or better yet for now,
> > email that to me directly and save the list a little bandwidth.)
> 
> 
> I believe you are right that there was a deeper problem.  
> Unfortunately, I don't know what it was, but at least things are 
> working right now.
> 
> I got really suspicious when the iax2 debug showed.... nothing!  I 
> screwed around with the config a little more and found that the error 
> message I got was really only coming from one side, and not the other.  
> I restarted asterisk, no dice.  I stopped asterisk, recompiled from 
> exactly the same source, started up again, and all is well.  Don't know
> what's behind that.  Hmm.
> 
> Anyhoo, thanks for the user/peer setup and your time!
Those type changes to iax.conf require a full stop of asterisk followed
by a cold asterisk startup. A restart from the CLI won't cut it.

Were you previously doing the CLI restart?

Rich