Ben Lear wrote:
** UPDATE **
Thanks for the informative response Michael, looking through the code I
can see what has transpired in my absence from the Asterisk scene.
Though I'm still undecided if moving the codec support from the driver
into the Asterisk core is the overall best solution, but
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
As other have reported before, it's not straight forward to get
kphone to properly register at an Asterisk server.
http://lists.digium.com/pipermail/asterisk-users/2003-March/009441.html
I've traced this a bit and have come to the following conclusion:
# ngrep REGISTER udp
U 193.80.224.82:32816
No, not yet. I was waiting to confirm that it was still happening in
the absolute latest CVS. I did see more symptoms last night, and I
will report the bug later today as soon as I get a nice fat list of
stuck SIP channels built up.
JT
Have you made a bug report on this? What is the
Hi all!
I've included a diff that will give you two new CLI options:
1) sip reset phone all
2) sip reset phone 1000
These two features will either reboot all your SIP phones or just the extension you
specified.
This will help whenever you've added a new firmware image into your /tftpboot
On Fri, 29 Aug 2003, DUSTIN WILDES wrote:
Hi all!
I've included a diff that will give you two new CLI options:
1) sip reset phone all
2) sip reset phone 1000
These two features will either reboot all your SIP phones or just the extension you
specified.
This will help whenever
Or - we could put a small notice like Only for phones that support the check-sync
NOTIFY message?
If anyone has any specs on other SIP phones on remote rebooting, I'll be happy to add
it in. Granted I won't be able to fully test it out - but I'll be willing to help.
:-)
-Original
