Status green to grey, back to green

Reply to Status green to grey, back to green on Thu, 12 Jan 2012 18:53:40 GMT

nicolas — Thu, 12 Jan 2012 18:53:40 GMT

I do not know if lagged events are logged into the full log. I am reading AMI events, specifically sip qualify events. Doing a "sip show peers" in the asterisk cli will show lagged peers.

Best regards,

Reply to Status green to grey, back to green on Wed, 04 Jan 2012 20:38:00 GMT

banditti — Wed, 04 Jan 2012 20:38:00 GMT

I am following what you are saying. I did grep my /var/log/asterisk/full and full.1 and have zero references to LAGGED

Would your program catch something that asterisk didn't?

Thank you for your feedback and help, I appreciate it.

Reply to Status green to grey, back to green on Wed, 04 Jan 2012 17:56:11 GMT

nicolas — Wed, 04 Jan 2012 17:56:11 GMT

I have a new FOP2 install. It all seems to work great with one exception.

I have a couple of extensions that will drop to grey for a bit and then back to green. If I look at it in command line from Asterisk, all seems ok. Thoughts?

Thank you in advance,

Your sip peers are probably becoming LAGGED and then back online again. FOP2 does not invent those states, they are reported by asterisk. I think you are actually seeing something you did not notice before.

Be careful as your extensions are not going to receive calls if they become Lagged (they can dial out, but usually inbound calls fail).

Best regards,