> Is there an advantage to having a Queue members URI in the form:
>
> SIP/User (or indeed IAX2/User)
> Over
> Local/<number>@context
>
> ?
>
> I know that the latter will allow you to do things like set counting
> logic etc. through dialplan operations, but the former appears to be a
> more direct route to calling the party. (and if need be, there is the
> ability in queues to run a script on connection iirc).
I'm migrating to Local/<number>@context right now (from Agent/ channels), and
it seems to me that Local channels doesn't show (busy) in "show queues". This
will probably require for me to do some overhead work for correctly
displaying agent status in monitoring software, but i think i will be able to
do it by combining "core show channels" with "show queues".
I'm not sure is it related to Agent channels that could accept only one call
or SIP channel status. I would expect queue to show even Local channel as
busy if there is active call trough it. I think this really can't be
accomplished by dialplan logics, as dialplan is not executed upon "show
queues"
Regards,
Atis
--
Atis Lezdins
VoIP Developer,
IQ Labs Inc.
atis@iq-labs.net
Skype: atis.lezdins
Cell Phone: +371 28806004
Work phone: +1 800 7502835
_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
No comments:
Post a Comment