I have a hunt group setup for all my sup in which they log every day. I have created a new vdn/vector to send calls to this hunt group. I don't not want the calls to go to the most idle agent which is how the hunt group is configured at this time.
My client would like to be able to call this...
I re-configured everything from scratch and replaced the PC that was running netcat. I'm also now running it from CDR1 instead of CDR2. Everything is great now. No more date/time issues.
I'm running netcat and everything appears to be running fine. My txt file keeps growing as the day goes along. I have one small issue, the date and time in my txt file are showing up as 000432 (for the date) and 8224 (for the time). It has been this all day. Here is an extract of my txt file...
I have been successfull in sending faxes through message manager. When entering the phone number in your address book, you have to use the following format for a fax: 91XXXXXXXXXX@Fax
P.S. it is case sensitive
I have encountered this problem in the past. Personel visiting Spain and using cisco VPN 4.6 all experienced one way audio issues. The resolve was to remove VPN 4.6 and install an older version like 4.0
When running a trace in the PBX (R013x), we regularly see entries like the following: denial event 1761.
Is there a document somewhere explaining what denial event 1761 is?
dwalin,
Thanks, that did the trick. Strange though, I look after multiple PBXs and all are set to "prompting timeout: 10 secs" and only this site pauses 10 secs after a selection is made.
I have a vector that plays an announcement giving the caller 2 options. The vector collects the digits and directs the call accordingly. Everything is working fine except, there is a 10 seconds delay before the call is transferred to either options. There are no wait-time statements in the vector.
Some of my centers use the transfer connect function (*8) to transfer calls out. Some of the agents figured out that if, upon receiving a call, the quickly press *8#, the call gets immediately requeued. We have tested this and found it to be true. While one of us is logged into a test queue, I...
Has the box been upgraded lately. I have an Intuity LX that worked fine with ASA prior to an upgrade, I lost the use of ASA after the upgrade because port 23 was closed. By default, a new Intuity comes with port 23 closed. I opened a case with Avaya and at no cost to had port 23 re-opened. Works...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.