As a follow up to my earlier posting, the problem with the Snom 200 Busy signal was the firmware! I reverted back to 1.16x and everything's OK. That made today pretty complicated, since I already had a new kernel and a new Asterisk build I was trying all at once.... Hopefully someone else will benefit... - Matt
-----Original Message----->From: asterisk-users-admin@lists.digium.com[mailto:asterisk-users-admin@lists.digium.com] On Behalf Of Matt Lawson>Sent: Thursday, November 20, 2003 7:03 PM >To: asterisk-users@lists.digium.com >Subject: [Asterisk-Users] Solved! Snom 200 Busy signal>As a follow up to my earlier posting, the problem with the Snom 200Busy>signal was the firmware! I reverted back to 1.16x and everything's OK.>That made today pretty complicated, since I already had a new kerneland>a new Asterisk build I was trying all at once....>Hopefully someone else will benefit...>- MattI had the same type of problem you did when I first upgraded to 2.02t. But I did a CVS update on 11/19/03, and everything is fine now. What I did notice (and I have a customer that saw the same thing) is that that version 2.02t has added a new SIP "Publish" message. I still haven't been able to determine what they're publishing with it. But Asterisk didn't seem to like it until I did a CVS update. It didn't seem to respond to it. Now Asterisk sends back a "Status: 405 Method Not Allowed" message, and everything is fine. I can't definitively say this was the cause because I didn't go back to the old Asterisk code and verify. But I can tell you that my Snom 200 phones with version 2.02t work fine now. Jerry
Now that you mention it, I did observe the PUBLISH message. Can someone please tell me exactly the change that was made that fixed this? (file/lines) I can do a diff -r and see a few changes from CVS but I'd like to be sure. We have a lot of custom changes as well so it's non-trivial to update to CVS. I would definitely like to check on this one patch though. Thanks. - Matt -----Original Message----->>From: asterisk-users-admin@lists.digium.com > >[mailto:asterisk-users-admin@lists.digium.com] On Behalf Of Matt Lawson>>Sent: Thursday, November 20, 2003 7:03 PM >>To: asterisk-users@lists.digium.com >>Subject: [Asterisk-Users] Solved! Snom 200 Busy signal > >>>As a follow up to my earlier posting, the problem with the Snom 200 > >Busy>>signal was the firmware! I reverted back to 1.16x and everything's OK > >>>- Matt > >>I had the same type of problem you did when I first upgraded to 2.02t. >But I did a CVS update on 11/19/03, and everything is fine now. What I >did notice (and I have a customer that saw the same thing) is that that >been able to determine what they're publishing with it. But Asterisk >didn't seem to like it until I did a CVS update. It didn't seem to >respond to it. Now Asterisk sends back a "Status: 405 Method Not >Allowed" message, and everything is fine. I can't definitively say this >was the cause because I didn't go back to the old Asterisk code and >verify. But I can tell you that my Snom 200 phones with version 2.02t >work fine now. > >Jerry