[asterisk-users] Hints custom:abcdef

[Jonas Kellens]

In other words : is it correct to say that hints need to be unique, even 
if they are defined in different contexts ?




On 05/20/2011 12:07 PM, Jonas Kellens wrote:
> Hello list,
>
> I want certain devices to monitor certain extensions/SIPaccounts and 
> other devices to monitor other extensions/SIPaccounts.
>
> Therefore I do the following :
>
> [from-TEST1]
>
> include => test1-blf
>
> [from-TEST2]
>
> include => test2-blf
>
> [test1-blf]
> exten => 10,hint,SIP/testcorp1
> exten => 20,hint,SIP/testcorp2
>
> [test2-blf]
> exten => 10,hint,SIP/testcorp110
> exten => 20,hint,SIP/testcorp120
>
>
> SIPaccounts with a context definition of "from-TEST1" can not monitor 
> the extensions of test2-blf.
> SIPaccounts with a context definition of "from-TEST2" can not monitor 
> the extensions of test1-blf.
>
>
> This works great. But now I have a problem with custom hints.
>
> When I do the following :
>
> [test1-blf]
> exten => 10,hint,SIP/testcorp1
> exten => 20,hint,SIP/testcorp2
> exten => 80,hint,custom:light1
>
> I see that SIPaccounts which enter the dialplan in context 
> [from-TEST2] also see the state (Green/Red) of hints defined in test1-blf.
>
> So how can I make a difference between custom hints in one context and 
> custom hints in another context ??
>
> Is there something like : 
> Set(DEVSTATE(*Custom:light1 at test1-blf*)=INUSE)* *  ??
>
> Or can there be only one custom:light1 label ??
>
>
>
> Kind regards,
> Jonas.
>
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
>                 http://www.asterisk.org/hello
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>     http://lists.digium.com/mailman/listinfo/asterisk-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20110520/eed25aa7/attachment.htm>