[Asterisk-Users] Grandstreams randomly go busy with Asterisk?

[Kyle Hagan]

I have one of 2 doing the same thing.

Kyle

Robert Withrow wrote:

>I've searched the lists but I didn't find anything exactly like this.
>
>I have two Grandstream BT101 phones connected to an Asterisk. 
>Periodically, for reasons that I can't determine, one or the other (or
>both) of the BT101s decide(s) to go on permanent busy.  Dialing that
>phone gives:
>
>    -- Executing Macro("SIP/24567-7856", "dialphone|SIP/27654") in new stack
>    -- Executing Dial("SIP/24567-7856", "SIP/27654|10|tr") in new stack
>Jun 15 14:23:41 NOTICE[1343506]: app_dial.c:536 dial_exec: Unable to create channel of type 'SIP'
>  == Everyone is busy at this time
>
>But dialing in the other direction (from the busy phone out) gives
>normal (good) results:
> 
>    -- Executing Macro("SIP/27654-6e2b", "dialphone|SIP/24567") in new stack
>    -- Executing Dial("SIP/27654-6e2b", "SIP/24567|10|tr") in new stack
>    -- Called 24567
>
>I have noticed that when the problem is happening I see this:
>
>CLI> sip show peers
>Name/username    Host                 Mask             Port     Status
>24567/24567      192.168.2.253   (D)  255.255.255.255  5060     Unmonitored
>27654/27654      (Unspecified)   (D)  255.255.255.255  0        Unmonitored
>
>Rebooting the offending phone always fixes the problem for a while. 
>After rebooting I see:
>
>CLI> sip show peers
>Name/username    Host                 Mask             Port     Status
>24567/24567      192.168.2.253   (D)  255.255.255.255  5060     Unmonitored
>27654/27654      192.168.2.254   (D)  255.255.255.255  5060     Unmonitored
>
>The BT101s are running 1.0.4.55.  Asterisk is 0.9.0.
>
>Any suggestions?
>
>  
>