Hi all,
sorry to rehash this - but I'm having similar issues. I'm on Asterisk 1.0
and have been using Queues without any problems locally. I mean, all the
SIP devices on my local server can be added to queues using AddQueueMember.
However, I now need to allow agents from other servers to log in
I believe that using the Local/[EMAIL PROTECTED] format will give you a bit
more
flexibility in the dialplan design, as there is an added degree of
indirection. In the end I think this is only marginally costier than the
"raw" channel format (unless you use the /n option) and should provide
On Tuesday 02 October 2007 19:30:44 Thomas Kenyon wrote:
> Is there an advantage to having a Queue members URI in the form:
>
> SIP/User (or indeed IAX2/User)
> Over
> Local/@context
>
> ?
>
> I know that the latter will allow you to do things like set counting
> logic etc. through dialplan operat
Thomas Kenyon wrote:
> Is there an advantage to having a Queue members URI in the form:
>
> SIP/User (or indeed IAX2/User)
> Over
> Local/@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 b
Is there an advantage to having a Queue members URI in the form:
SIP/User (or indeed IAX2/User)
Over
Local/@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 part
