Re: [Asterisk-Users] Re: Codec Issue on IAX trunk? (Solved)

2005-02-13 Thread Martijn van Oosterhout
On Sat, Feb 12, 2005 at 10:44:11AM -0600, Rich Adamson wrote:
 I haven't tried to keep track of the code changes involving reloads
 (or cli restarts for that matter), but having been around * for a fair
 amount of time and having been caught with making changes that have
 had no affect, I'll usually play it very safe and simply stop / start
 asterisk for many different changes. Iax and sip def's in particular.
 
 Reloads are fine for lots of things, but experience is the only way
 to know what's acceptable at this point.

I've noticed this myself. However, I have been able to acheive a
similar effect by unloading and then reloading the module. In my case I
was testing H323, it might be trickier if you're actually using what
you're playing with...

Hope this helps,
-- 
Martijn van Oosterhout
___
Asterisk-Users mailing list
Asterisk-Users@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


[Asterisk-Users] Re: Codec Issue on IAX trunk? (Solved)

2005-02-12 Thread Noah Miller
Hi Rich - 

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.
Ahh!  That's a very important piece of information!

Were you previously doing the CLI restart?
I did lots a CLI reloads, and few cold restarts to the ast33 machine, but no cold 
restarts on the ast551 machine until after business hours (it's a production machine), and then I 
did a cold restart at the same time I did the recompile.  That explains things.  Hopefully, I won't 
have to make any more changes like this, although I guess I could use the restart when 
convenient command.  Now I just have to figure out why a cold restart is needed.
Thanks Again,
Noah
___
Asterisk-Users mailing list
Asterisk-Users@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


Re: [Asterisk-Users] Re: Codec Issue on IAX trunk? (Solved)

2005-02-12 Thread Rich Adamson
  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.
 
 Ahh!  That's a very important piece of information!
 
 
  Were you previously doing the CLI restart?
 
 I did lots a CLI reloads, and few cold restarts to the ast33 machine, but 
 no cold restarts 
on the ast551 machine until after business hours (it's a production machine), 
and then I did a 
cold restart at the same time I did the recompile.  That explains things.  
Hopefully, I won't 
have to make any more changes like this, although I guess I could use the 
restart when 
convenient command.  Now I just have to figure out why a cold restart is 
needed.
 

I haven't tried to keep track of the code changes involving reloads
(or cli restarts for that matter), but having been around * for a fair
amount of time and having been caught with making changes that have
had no affect, I'll usually play it very safe and simply stop / start
asterisk for many different changes. Iax and sip def's in particular.

Reloads are fine for lots of things, but experience is the only way
to know what's acceptable at this point.


___
Asterisk-Users mailing list
Asterisk-Users@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


[Asterisk-Users] Re: Codec Issue on IAX trunk? (Solved)

2005-02-11 Thread Noah Miller
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
___
Asterisk-Users mailing list
Asterisk-Users@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


Re: [Asterisk-Users] Re: Codec Issue on IAX trunk? (Solved)

2005-02-11 Thread Rich Adamson
  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


___
Asterisk-Users mailing list
Asterisk-Users@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