[asterisk-users] Two Extensions showing as Busy

[--[ UxBoD ]--]

----- "Danny Nicholas" <danny at debsinc.com> wrote:

> Could be a call-limit setting problem (just a WAG)
> --
> Danny Nicholas
> --
> 
> 
> -----Original Message-----
> From: asterisk-users-bounces at lists.digium.com
> [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of --[
> UxBoD ]--
> Sent: Tuesday, February 02, 2010 11:10 AM
> To: asterisk-users at lists.digium.com
> Subject: [asterisk-users] Two Extensions showing as Busy
> 
> Hi,
> 
> had a very strange issue today where two extensions called each other,
> hung
> up, but on another extension the two parties continued to show as
> busy.
> 
> This was running Asterisk 1.6.1.12 and when connecting to the console
> we saw
> :-
> 
> [Feb  1 09:18:38] WARNING[17474]: chan_sip.c:17046
> handle_response_invite:
> just did sched_add waitid(577921) for sip_reinvite_retry for dialog
> 3c711a8f0456-oa3xwb6nxknk in handle_response_invite
> [Feb  1 09:18:40] WARNING[17474]: chan_sip.c:17046
> handle_response_invite:
> just did sched_add waitid(577923) for sip_reinvite_retry for dialog
> 3c711a8f0456-oa3xwb6nxknk in handle_response_invite
> [Feb  1 09:18:42] WARNING[17474]: chan_sip.c:17046
> handle_response_invite:
> just did sched_add waitid(577925) for sip_reinvite_retry for dialog
> 3c711a8f0456-oa3xwb6nxknk in handle_response_invite
> XXX*CLI> sip show channels
> Peer             User/ANR    Call ID          Format           Hold   
>  Last
> Message    Expiry
> 10.XX.X.XXX      USER1       214d5e15267a17f  0x4 (ulaw)       No     
>  Tx:
> ACK
> 10.XX.X.XXX      (none)      2071025406       0x0 (nothing)    No     
>  Rx:
> REGISTER
> 10.XX.X.XXX      USER2       3c711a8f0456-oa  0x4 (ulaw)       No     
>  Tx:
> ACK
> 10.XX.X.XXX      USER3       0bbd02e95245bda  0x4 (ulaw)       No     
>  Tx:
> ACK
> 10.XX.X.XXX      USER4       3c64d1451cbb-dr  0x4 (ulaw)       No     
>  Rx:
> ACK
> 5 active SIP dialogs
> [Feb  1 09:18:43] WARNING[17474]: chan_sip.c:17046
> handle_response_invite:
> just did sched_add waitid(577927) for sip_reinvite_retry for dialog
> 3c711a8f0456-oa3xwb6nxknk in handle_response_invite
> [Feb  1 09:18:45] WARNING[17474]: chan_sip.c:17046
> handle_response_invite:
> just did sched_add waitid(577929) for sip_reinvite_retry for dialog
> 3c711a8f0456-oa3xwb6nxknk in handle_response_invite
> [Feb  1 09:18:47] WARNING[17474]: chan_sip.c:17046
> handle_response_invite:
> just did sched_add waitid(577931) for sip_reinvite_retry for dialog
> 3c711a8f0456-oa3xwb6nxknk in handle_response_invite
> [Feb  1 09:18:49] WARNING[17474]: chan_sip.c:17046
> handle_response_invite:
> just did sched_add waitid(577933) for sip_reinvite_retry for dialog
> 3c711a8f0456-oa3xwb6nxknk in handle_response_invite
> 
> All extensions were within the same context.
> 
> Has anybody seen this behavior before and what could cause it ? we
> resolved
> the issue by sending a SIP notify reboot to the SNOM phones.
> 
call-limit is deprecated in this version so I would have thought it would not effect it.

-- 
Thanks, Phil