HT-386 Registered but busy after idle for a while

callinectes
Posts: 209
Member Since:
2007-05-12

I am having a problem where my HT-386 will, after booting, register, send calls, and receive calls fine for a while and then for no reason (that I have been able to track down) the ATA stops accepting calls (they are rejected with "Got SIP response 486 "Busy" back from 192.168.0.168"). Funny thing - while it is rejecting calls if you pick up an attached handset you will hear no dial tone, however, if you hang up and pick it up again you will hear a dial tone and it starts accepting calls again (for a short time). Also - no matter what state the ATA is in, rejecting calls or accepting them, the device stays registered.

I had this device working for a long time then I messed with its settings and have not been able to get it to work again - even when set back to identical settings. Anyone have any ideas? This is connected to a trixbox Pro server.

FYI...
Software Version: Program-- 1.0.4.2 Bootloader-- 1.1.0.1 HTML-- 1.0.4.2 VOC-- 1.0.0.13
Note - i was running an earlier firmware and just updated to this recently while troubleshooting but it hasn't helped.

Thanks in advance for any help.
Kevin



channeldrunk
Posts: 2
Member Since:
2009-09-14
Kevin, I'm having the exact

Kevin, I'm having the exact same problem. Did you ever find a fix for this thanks, eric



callinectes
Posts: 209
Member Since:
2007-05-12
If I remember correctly I

If I remember correctly I eventually set "SUBSCRIBE for MWI" to "No" and the problems went away. Funny thing, MWI still functions properly.

Kevin



callinectes
Posts: 209
Member Since:
2007-05-12
Wow - sorry for the late

Wow - sorry for the late response, I just received the e-mail notification of your comment. Sorry - hope you were able to resolve your issue.

Kevin



channeldrunk
Posts: 2
Member Since:
2009-09-14
no problem and thanks

I actually boxed the thing up, because it was so annoying. but I may take it out again. I even tryed it behind a 3cx( this may be a bad word on this forum) box and it did the same thing. Grandstream doesnt support the 386 anymore , so I thought it was another device for my electronics boneyard. I'll let you know if it gets resurrected. thanks again



keith.burgoyne
Posts: 3
Member Since:
2008-07-02
I have the same issue.

Kevin and channeldrunk,

I've noticed the same issue with my 386, and my 496. I've just set Subscribe to MWI to off, and am waiting for the necessary idle time to pass before I try calling the box again. I'll post the results here - from my experience, this bug affects a lot of people, so it might help to have the final results posted here for all to see.

Thanks,

Keith



keith.burgoyne
Posts: 3
Member Since:
2008-07-02
386 Fixed.

I've let my 386 sit idle for several hours, and with Subscribe for MWI set to Off, it has worked perfectly for a couple of days now. I did the same operation on another 386, and it also solved the "busy after a few hours of idleness" bug. What's more is that the message waiting indication continues to work (which I assume is the the pulsing dial tone that alerts you of voicemails, and possibly tells your cordless phone's LCD to display the presence of VMs in your mailbox).

Anyone with that same issue should just follow callinectes's suggestion.

Thanks!



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.