Contstant Log On and Log Off in Asterisk

I’'ve seen this issue a couple times now.

If I restart Asterisk, and then log in to the asterisk console, by doing an ‘‘asterisk -r’’. My screen starts to fill up with:

== Connect attempt from ‘‘192.168.1.205’’ unable to authenticate

== Manager ‘‘wildfire’’ logged off from 192.168.1.205

== Connect attempt from ‘‘192.168.1.205’’ unable to authenticate

== Parsing ‘’/etc/asterisk/manager.conf’’: Found

== Manager ‘‘wildfire’’ logged on from 192.168.1.205

== Connect attempt from ‘‘192.168.1.205’’ unable to authenticate

== Parsing ‘’/etc/asterisk/manager.conf’’: Found

== Manager ‘‘wildfire’’ logged on from 192.168.1.205

== Parsing ‘’/etc/asterisk/manager.conf’’: Found

== Manager ‘‘wildfire’’ logged on from 192.168.1.205

This continues till I restart the Wildfire service, if I don’‘t it eventually crashes. The manager.conf should be setup correctly, it functions just fine, as long as I don’'t restart Asterisk.

Manager.conf:

(has brackets around it)

secret=jive

deny=0.0.0.0/0.0.0.0

permit=192.168.1.205/255.255.255.0

read = system,call,log,verbose,command,agent,user

write = system,call,log,verbose,command,agent,user

Any Thoughts?

Thanks–

Message was edited by: shawdog

My only thought is, are you running the Asterisk & Wildfire on the same box? If so, use localhost instead… not ever had a problem this way.

Your manager.conf should be fine tho, here’'s for localhost of course:

secret = password

deny=0.0.0.0/0.0.0.0

permit=127.0.0.1/255.255.255.0

read = system,call,log,verbose,command,agent,user

write = system,call,log,verbose,command,agent,user

  • J

They are not on the same box.

My current work around is to simply stop the Asterisk service, then start it, instead of doing a restart. My guess is it has to do with a timing issue of Wildfire and Asterisk, since restarting the Asterisk service is so quick. By doing a stop it gives the Asterisk plugin time to disconnect.

Who knows…

No real answer, but the work around seems to work.