JT
Have you made a bug report on this? What is the number?
John Todd wrote:
Did you find any solutions to this? I've recently discovered the same problem with my server here. I had 499 "sip show channels" entries, and then Asterisk refused to start up any new sessions due to "Too many files open". In fact, 'reload' worked but didn't work, due to the inability of the system to open any of the config files. I had to shut Asterisk down to get things working again. My CVS version was four days old.
I've updated to CVS as of two hours ago, and am watching to see if this happens any more. I think it has something to do with "REGISTER" requests outbound from * not being cleared correctly, somehow.
JT
I'm seeing a case where I get a large number of 'stuck' channels as it relates to users that sit behind poorly behaving nat devices.
these calls tend to be initiated and have unidirectional voice (eg: we can hear the user behind the nat, but not the other way around ..)
this means that messages can't be sent to them (and get ACK) saying that they will terminate the call, etc..
is there a way that i'm unaware of to time these out, or is this what I think it is which is a bug where the call/channel gets stuck until such time as it can be terminated?
- jared
-- snip --
peer and dialed numbers munged to protect the innocent ;-)
sip-server*CLI> sip show channels Peer User/ANR Call ID Seq (Tx/Rx) Lag Jitter Format [big mess deleted]
-- Jared Mauch | pgp key available via finger from [EMAIL PROTECTED] clue++; | http://puck.nether.net/~jared/ My statements are only mine.
_______________________________________________ Asterisk-Dev mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-dev
