With a recent update to Asterisk CVS, and versions 2.02r and t of the
Snom 200 firmware, I'm getting the Snom phones stuck reporting
"Busy.":
-- Got SIP response 486 "Busy Here" back from 10.12.34.248
-- SIP/3064-b07d is busy
They're on-hook, not doing anything. They are registered fine. I can
pick them up and call out over Zap or IAX fine. I just can't call the
extensions because they always report busy.
Has anyone else observed this?
- Matt
> With a recent update to Asterisk CVS, and versions 2.02r and t of the > Snom 200 firmware, I'm getting the Snom phones stuck reporting "Busy.": > > -- Got SIP response 486 "Busy Here" back from 10.12.34.248 > -- SIP/3064-b07d is busy > > They're on-hook, not doing anything. They are registered fine. I can > pick them up and call out over Zap or IAX fine. I just can't call the > extensions because they always report busy.I worked with a client with snom 200 they claim this occurs after using "Do not Disturb" on the phone they say they must reboot it to not return a busy ...
> With a recent update to Asterisk CVS, and versions 2.02r and t of the > Snom 200 firmware, I'm getting the Snom phones stuck reporting "Busy.":I'm not sure if you got this answered on IRC..It'll be nice to have it in the archives too. One of the recent 2.02 firmwares from SNOM was badly broken. I'm running 2.02t and all seems fine. They also fixed the annoying 'time corruption if running with a static IP' bug. --Justin