![]() ![]() ![]() I believe that the 5 monitoring channels did not hangup and between Unable to write to alert pipe WARNINGS I've seen a lot of Exceptionally long voice queue length queuing warnings referring to same channels despite the fact that there was no agents logged on to the server at that time (4 AM EST) The WARNINGS continued overnight all the way until crontab rebooted the server. In last 2 days I have noticed new WARNING in asterisk logs :Ĭhannel.c: Unable to write to alert pipe on (qlen = 90): Resource temporarily unavailable!īy it self this message is harmless, however Local/58600072 is an extension of quiet monitor-only extensions for meetme rooms: Asterisk 1.8 workaroundĪnd 58600072 was not the only one listed in logs with same warning I can see 4 other quiet monitor extensions. If there is just a fief during a day there is no issue, but when I see lots of these the asterisk stops responding, not crashing, but not accepting any more sip messages. Server is rebooted every night, pv6 disabled, unused ram is released drop_caches from crotab every minute.Īnd there is no external attacks on the server.įrom time to time I see "Exceptionally long voice queue length queuing" errors in asterisk logs. Timer card Amfeltec VoiceSync (pcie) installed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |