[asterisk-users] how to determine if a SIP extension has DNDonoroff

[Eric "ManxPower" Wieling]

SIP response 486 is "Busy Here" according to RFC 3326.  Polycoms at 
least (and I think Cisco phones) do not send back a different message 
depending on if DND is enabled .vs. the line appearance simply being busy.

Personally I can't see how the people that designed SIP could justify 
not being able to get the DND status or CFWD status of a SIP device.


Steve Langstaff wrote:
> The OP was asking whether they could update Asterisk's DND status for
> the extension to mirror a DND button on the (SIP) phone. I suggested
> that they might act on the response code to an OPTIONS.
> 
> I think that they *actually* want to do some queue management based on
> the DND button of the (SIP) phone.
> 
>> -----Original Message-----
>> From: asterisk-users-bounces at lists.digium.com 
>> [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of 
>> Joshua Colp
>> Sent: 14 September 2007 08:43
>> To: Asterisk Users Mailing List - Non-Commercial Discussion
>> Subject: Re: [asterisk-users] how to determine if a SIP 
>> extension has DNDonoroff
>>
>>> --- Steve Langstaff <steve.langstaff at citel.com> wrote:
>>>
>>>> I don't know about the 1.4 source, but in 1.2 I guess you 
>> would have 
>>>> to add some more code to
>>>>
>>>> handle_response_peerpoke()
>>>>
>>>> to handle the case where you got a 486 response from the peer.
>>> ok thanks, so that just seems to confirm that Asterisk
>>> 1.2 DND's behavior can't be modified/customized without 
>> patching the 
>>> source code. I might forward this issue to asterisk-devel.
>>>
>> What do you mean modified/customized exactly?
>>
>> If you mean can you know whether a device has DND enabled or 
>> not before sending a call then no, even an OPTIONS packet 
>> won't tell you that. You send a call, they reject (and 
>> sometimes they even use a response code that doesn't indicate 
>> it's DND). Same goes for call forwarding. You send a call, 
>> they reject saying "go here instead".