Thats a bug that needs to be resolved via software patch/bug fix. Check with Avaya for more information but I know we had similar issues when we were on release 3 of CM. The fix was a patch but It's been years since then so I don't recall what the patch information is.
A very wise and well...
If you already have redundant MedPro boards the only reason to be concerned would be if your call volume exceeds the resources on the existing board(s).
If the current MedPro boards on the other PNs will support the call volume from the users currently supported on the PN that's going away...
Is it a single processor stand alone system?
If its an ESS/LSP make sure you have the file for that processor. The file will contain the ID in the name like sxxxxxxxvyym3-110721-123456.pwd. The m3 means its MID 3 or Module ID 3.
A very wise and well respected man once told me "Shut Up!".
We use One-X Attendant and it's pretty decent. We don't have any problems with the console software itself .. but our agencies like to skimp on hardware .. so occasional w have issues with the PC build or with the headset.
At sites where they build a good PC with no software update crap like...
AvayaTier3 is on the spot. I forgot about the logs. You can check the logs for info too. Again you would be viewing logs and not real time streaming data .. but it's very close to RT.
With tail and other tools you could use the logs to piece together a picture of what you're trying to...
I agree with Mark. I would run the agent traces. This will tell you if the agents pressed the buttons or not.
Tell them to keep track of these incidents (times/dates) so you can find them in the trace logs.
They should also report these asap as those logs tend to get lengthy.
FYI .. I...
The shell commands for this type of monitoring are restricted to the "sroot" login which 99.999% of customers do not have access to.
The most common tools for live monitoring are "list trace" command run from the terminal emulator. You can also enable MST traces and then use the web interface...
Ok .. you can do this without using EC500. I have done this so I know it works. It's a bit cumbersome but if you're out of EC500 licenses this will do the trick.
Setup both number (Home/Cell) as remote coverage points.
Build a cover path for both.
The build two virtual stations with thos...
If you don' want to purchase a VAL board you could just use the auto attendant feature in audix to complete this. Then have the destination of each menu option be a meet-me VDN that puts them into the bridge.
This will work if you have a limited number of bridges. If you have more than a...
You can do both yes. You need to set them up as separate queries in your custom report.
Then add a table/chart for each query in the report designer and configure the options for each.
- Miguel
A very wise and well respected man once told me "Shut Up!".
The way we accomplish this is instead of queing to a skill (in the original Vector) we send the call to another VDN/Vector that ques the call ... then does a return step.
This works for us because the agent sees the name of the second VDN which is named appropriately for the skill it quest to...
You could use work codes ... but it would have to be configured on the station and in CMS. The agents would have to be trained to hit the work code button while still on the call.
The way it would work is when an agent recieved a call that was a warm transfer they would hit the work code...
We do not have any SIP trunks yet. All of our external trunks are ISDN/Copper T1's.
We do have echo cancellation turned n for some of them. It varies trunk to trunk. Some are one or the other and some are both in the trunk and the DS1 form.
- Miguel
A very wise and well respected man once...
well if your 8 folks are not using agent ID's ... you could setup each group in a seperate coverage answer group.
So you would need:
Cover Answer Group A (First 4 members)
Cover Path A (Point 1 uses Cover Answer Grp A)
Virtual Station A (Uses Cover Path A)
Cover Answer Group B (Second 4...
In a previous call center environment we had a similar situation with some other additional considerations.
We took a group of about 50 agents. half of them had skill 1 lvl 1 (with skill 2 as a backup - lvl 2). The other half has skill 2 lvl 1 (with skill 1 as a backup - lvl 2). They all has...
Our problems were all static and quality of voice related. This firmware has resolved both and done so very well in all locations we have deployed it.
Good luck with your issue Mj.
- Miguel
A very wise and well respected man once told me "Shut Up!".
The new firmware is the S6.2023. This is the firmware we have been testing in our environment.
It was developed specifically to resolve the voice issues and it has done so in all of our sites.
- Miguel
A very wise and well respected man once told me "Shut Up!".
Avaya has developed a set of firmware and provided it to the company I work for as a beta.
The firmware does resolve all of the audio quality and static issues we have had.
For those of you with problems .. hang in there for a few weeks and I'm sure this firmware will be GA.
- Miguel
A very...
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.