hi,
yes, this is the way, asterisk / the channeldriver handles it.
you can simulate the failure of one span by just pulling out the cable
and see what happens..
on top, you can influence the order, the channels are used by using
dahdi/g1 or dahdi/G1...
regards,
yves
Am 05.03.2013 07:31, schrie
On Tue, Mar 05, 2013 at 12:31:09AM -0600, Hose wrote:
> Hello,
>
> If I put two spans' worth of channels, say 1-23 from span 1 and 25-47 in
> span 2, in one group, but only span 2 was showing OK and the other was
> down / showing a RED alarm, would asterisk automatically skip over
> trying to use
Hello,
If I put two spans' worth of channels, say 1-23 from span 1 and 25-47 in
span 2, in one group, but only span 2 was showing OK and the other was
down / showing a RED alarm, would asterisk automatically skip over
trying to use channels 1-23 when doing outbound calls? e.g.,
dial(dahdi/g1/(numb
Unless you need every byte of memory available, the easiest thing to is have
autoload enabled and specifically noload => the modules you know you don't need.
-Original Message-
From: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Oli
Can you post the message when it fails?
On Mon, Mar 4, 2013 at 4:37 PM, Olivier wrote:
> Hi,
>
> I've got a brand new Asterisk 11 setup for which I would like to keep the
> number of loaded modules to a minimum.
> My goal is to this setup in a pure SIP environment, for switching incoming
> calls
Hi,
I've got a brand new Asterisk 11 setup for which I would like to keep the
number of loaded modules to a minimum.
My goal is to this setup in a pure SIP environment, for switching incoming
calls to outgoing tSIP trunks.
When I leave autoload=yes in /etc/asterisk/modules.conf, I can handle an
i
On 3/4/2013 8:00 AM, Gertjan Baarda wrote:
This will only work with the n option in the queue command and retry=0
in queue.conf. Is it not?
On Mon, Mar 4, 2013 at 2:55 PM, Alex Kauffmann mailto:akauf...@prodigy.net.mx>> wrote:
On 3/4/2013 7:27 AM, Gertjan Baarda wrote:
ok, resumé:
This will only work with the n option in the queue command and retry=0 in
queue.conf. Is it not?
On Mon, Mar 4, 2013 at 2:55 PM, Alex Kauffmann wrote:
> On 3/4/2013 7:27 AM, Gertjan Baarda wrote:
>
>> ok, resumé: When I use the n option in the queue command I can let the
>> caller exit the queue
On 3/4/2013 7:27 AM, Gertjan Baarda wrote:
ok, resumé: When I use the n option in the queue command I can let the
caller exit the queue and send the call to a IVR-ish context and ask if
he wants to leave a message. I can timeout this an then place the call
back in the queue. When I use this appro
yes, its start with new position in queue, not in his actual position
earlier he gets in the queue.
As i mentioned earlier, if you dont want to put user back in queue,
then use context parameter in you queues.conf file. On pressing any
digit caller redirects to that context where he can leave voic
ok, resumé: When I use the n option in the queue command I can let the
caller exit the queue and send the call to a IVR-ish context and ask if he
wants to leave a message. I can timeout this an then place the call back in
the queue. When I use this approach, what will the new position be of the
cal
yes,
context parameter in queue.conf is more likely option for you. It will
work during MOH too.
On Mon, Mar 4, 2013 at 6:33 PM, Bharat Lalcheta
wrote:
> No its again place into queue so its start with new available position.
>
> However, mostly all users remain in same position if he come agai
No its again place into queue so its start with new available position.
However, mostly all users remain in same position if he come again in
queue using below scenario.
Regards,
Bharat Lalcheta
On Mon, Mar 4, 2013 at 6:22 PM, Gertjan Baarda wrote:
> Ah.. thanks! That was the light I neede
On 3/4/2013 6:27 AM, Gertjan Baarda wrote:
Dear guru's
Hopefully someone can shed some light in my issue. I have created a
queue with a ringall strategy and all works fine. I want a caller to be
able to exit the queue so they can leave a message. I've added the H
option in queue command so calle
That is correct, retry=15 and timeout=15 (for testingpurposes)
On Mon, Mar 4, 2013 at 1:51 PM, Chris Bagnall wrote:
> On 4/3/13 12:27 pm, Gertjan Baarda wrote:
>
>> After extensively googling the issue, I've found everything (also bug
>> related), accept my answer. What am I missing here?
>>
>
>
Ah.. thanks! That was the light I needed. When the caller is placed back in
the queue, I presume the caller remain it's position in the queue?
On Mon, Mar 4, 2013 at 1:45 PM, Bharat Lalcheta wrote:
> Hii,
>
> Queue(testq,H) feature works once call connected with agent i.e. not
> work during MOH.
On 4/3/13 12:27 pm, Gertjan Baarda wrote:
After extensively googling the issue, I've found everything (also bug
related), accept my answer. What am I missing here?
It sounds like the call is being caught by a retry cycle on the queue.
Try adding n to your queue command from your dialplan.
Also
Hii,
Queue(testq,H) feature works once call connected with agent i.e. not
work during MOH.
Also once you disconnect call using H (*) option, it will not useful
to leave voicemail.
Instead you use, queue timeout option and ask caller to leave voice
mail if he wants else put back him to queue agai
Dear guru's
Hopefully someone can shed some light in my issue. I have created a queue
with a ringall strategy and all works fine. I want a caller to be able to
exit the queue so they can leave a message. I've added the H option in
queue command so callers can press * to exit. So far all well, on t
You could dynamically change the queue penalties (QUEUE_MIN_PENALTY and
QUEUE_MAX_PENALTY) through queuerules.conf - check [1].
HTH,
Ioan
[1]
http://www.asteriskdocs.org/en/3rd_Edition/asterisk-book-html-chunk/ACD_id288932.html
--
__
20 matches
Mail list logo
