[asterisk-dev] devicestate

[Mark Michelson]

Atis Lezdins wrote:
> On 1/16/08, Atis Lezdins <atis at iq-labs.net> wrote:
>> On 1/16/08, Joel Vandal <jvandal at infoteck.qc.ca> wrote:
>>> Hi Clod,
>>>
>>> Here the patch against asterisk 1.4.17.
>>>
>>> http://www.scopserv.com/download/asterisk-1.4.17-state_interface.diff
>>>
>>>> would you like to provide your patch somewhere so users can use it?
>>>>
>>>> On Jan 16, 2008 11:32 AM, Joel Vandal <jvandal at infoteck.qc.ca
>>>> <mailto:jvandal at infoteck.qc.ca>> wrote:
>>>>
>>>>     I've made several test using the 'queue-state' branches (now
>>>>     integrated
>>>>     on SVN trunk) and I can confirm that this solve all our problems
>>>>     using
>>>>     Queue and Local channels, we can now specify an alternate device to
>>>>     monitor the state. I have also "backport" the change to Asterisk
>>>>     1.4.17
>>>>     and already using it on multiple call center since last week.
>>>>
>> Great, thanks. That's exactly what i've been looking for. I was
>> confused and looking/writing something that would help to fix this for
>> last month..
> 
> in create_queue_member() there's:
> 
>     if (!strchr(cur->interface, '/'))
>       ast_log(LOG_WARNING, "No location at interface '%s'\n", interface);
>     cur->status = ast_device_state(interface);
> 
> I wonder - shouldn't that use state from state_interface if it exists?
> 
> Regards,
> Atis
> 

I can add a similar check for the state interface as well. Thanks for pointing 
that out.

Mark Michelson