Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - jmccall

Pages: [1]
1
Came to this same conclusion after giving it a bit more thought. Thank you.  :) works great.

2
Sorry I guess I'm not the best @ advanced * or QM configuration, hence the freebpx install  :). Can you point me in the right direction?

Thank you
Jason

3
Yeah I do have the outbound route going to the queue dial. I'm talking about in the dial plan the manual that I've seen so far only gives info on one trunk...


Quote
Will let you call number 012345678 as Zap/g0/012345678 that is, will dial it on the fist available channel in your Zaptel card.
You may otherwise have a format like SIP/myprovider/012345678 that will dial numer 012345678 through a SIP trunk called "myprovider".
You should also add the following piece of code to your extensions_queuemetrics.conf file (make sure it’s not already present):

on http://queuemetrics.com/manuals/QM_Trixbox-chunked/ar01s03.html what I'd like to setup is if 'myprovider' fails that it will try 'myproviderbackup'.

Thank you
Jason

4
I've recently implemented the QM outbound dialing on my FreePBX 2.8/Asterisk 1.4 box and had a problem when my providers primary server was not accepting calls, I have a fail over server setup for them in the trunks and normal outbound routes can use the fail over.

My question is how do I setup the [queuedial] to fail over if the primary is down.

Thank you
Jason

5
I've done a clean install of AsteriskNow 1.7 with all updates applied afterward. I'm running Asterisk 1.4 and FreePBX 2.8. Everything seems to be working fine except the live monitoring. The system doesn't seem to know the sip channel to attach to when using chainspy. Any suggestions on this?

Pages: [1]