|
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
|
|||||||
| Avaya Predictive Dialing Solutions Discuss predictive dialing, PDS, and proactive contact solutions. |
![]() |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
|
Hi all...have many folks been having problems with the new version? Is the Super-Patch all it's cracked up to be?
|
|
#2
|
|||
|
|||
|
What version?
4.1.0 4.1.1 4.1.2? |
|
#3
|
|||
|
|||
|
Hi Evilscooby,
We're dealing with numerous issues with 4.0.1, and trying to upgrade another box which has 4.1.0 to 4.1.2...the super-patch is supposed to fix alot of things.. Are you experiencing issues with these versions? DB |
|
#4
|
|||
|
|||
|
Yeah we saw lots of issues on 4.1.0
we found 4.1.1 with latest patches pretty stable and are yet to fully try 4.1.2 I like the idea in 4.1.2 where you can enable extra logging on core files much easier |
|
#5
|
|||
|
|||
|
We've got a strange problem: about 30-50% of all calls which are answered by our agents are dropeed straight after answering. We use CTI Dialer and VoIP trunks for outbound calls.
The made all those drops classified by agents manually with additional code so we know the problem. ![]() |
|
#6
|
|||
|
|||
|
egris, it's not a problem of a dialer. I have a lot of traces from the system. For example from MST:
14:15:40 - SETUP 14:15:58 - CONN 14:16:15 - REL COM from CSTA: 14:15:40 - Make Pred Call 14:16:04 - Established 14:16:04 - Route to agent 14:16:04 - Delivered 14:16:05 - Established 14:16:15 - ConnectionClearedEvent so as you can see PSTN send connect message at 14:15:58 and Avaya Classifier (not a Dialer, because you use CTI version) recognize it at 14:16:04 and agent pick-up headset at 14:16:05. of course, because of ~7 secs dealy most people will hang-up. What i can recommend to you: 1) switch your outboun agent to auto-answer mode it will save you up to 2-3 secs 2) insert message into system like "please wait your call is transfered to agent" while the call in queue or classified. Also, you can call me at any time ![]() Alex S. |
|
#7
|
|||
|
|||
|
evil, 4.0.1 and 4.1 was the warst releases that i've ever seen
![]() 4.1.1 was pretty good. Most problem was fixed in 4.1.2 and in february Avaya released cumulative patch 189 which will be included in 4.2 4.2. will be realesed in May. |
|
#8
|
|||
|
|||
|
Is it not jumping to 5.2 in May to match the rest of the products?
Have you played with the new logging features in 4.1.2 yet? |
|
#9
|
|||
|
|||
|
yep. i have two systems with 4.1.2. dynamic logging is very interesting feature.
|
|
#10
|
||||
|
||||
|
We have 2 dialers that are not podded together. Our primary and the one in our DR/BCP site. I want install the service pack at my DR site first and run some tests and check stability of the system. Avaya Support is tellign me that I have to do the following:
1. Upgrade to Avaya Proactive Contact 4.1.2 Dialer (Material ID: 700479025) from Avaya Proactive Contact 4.1 or Avaya Proactive Contact 4.1.1 Dialer. 2. Install Avaya Proactive Contact 4.1.2 Database (Material ID: 700479058) only if upgrading from Avaya Proactive Contact 4.1. 3. Install Avaya Proactive Contact 4.1.2 Supervisor (as applicable) (Material ID: 700479066) 4. Install Avaya Proactive Contact 4.1.2 Agent (as applicable) (Material ID: 700479033) 5. Install Avaya Proactive Contact 4.1.2 Agent API (as applicable) (Material ID: 700479041) Which translate to: Dialer Database Supervisor Agent Agent API (if appropriate) Also required Dialer patch 189, Supervisor patches 178 and 181, and Agent patch 193. Has anyone else had to follow this strategy and did you encounter any major issues? |
![]() |
| Thread Tools | |
| Display Modes | |
|
|