Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

BCM400 Distribute Timers 1

Status
Not open for further replies.

BrokenIT

IS-IT--Management
Jan 24, 2005
6
GB
Hi,

I've just bought a BCM400 (ooooh) and it is poorly (aaaaah) in as much as it doesn't do what the programming for groups says it should.

The system is setup to ring an agent's phone for 4 rings.
Problem: the customer hears 4 rings but the agent hears 3 rings. Where is my 4th ring - the callback delay timer is set to 3, is this overriding the other parameter?

The call distribute timer won't work below 12 seconds and is tempremental below 15. With 2-3 agents in the system it rings on distribution for approx 24 seconds. So what gives with the extra 9 seconds (cpu time ?)

Nortel released a patch to us for this which was applied by my phone man and although this seems to stop the system looping back from the 1st dist timer to the welcome greeting it still doesn't correct the dist timer's inability to count.

Can anyone confirm the following concerns:
1. The dist timer is actually related to the number of rings per group instead of time and should be a simple value rather than a time presentation.
2. The dist timer has a minimum setting at which it works but the Nortel software allows the user to lower it below safe tolerances so that it conflicts with the main setup values.
3. The BCM400 is a pile of donkey droppings and I've been hoodwinked.

Mine blew it's ISDN30 trunk card straight out of the box and then 4 days later fried its primary 32port card on it's first day in production service. After 9 days of trying to configure it cleanly (using a well known telecomms service company) Nortel agreed that there was a bugfix.
What else don't I know about this product and should I send it back as unfit for purpose?

Try this sequence with 3 agents
Greeting 1, forced, no transfer
Dist=00:12
Greeting 2, normal, no transfer
Dist=00:12
Greeting 3, normal, no transfer
Mailbox xxx

We set the overflow at 55 seconds but it isn't necessary for this test.

Run it with 2 agents logged in but ignoring the phone.
Run it again with 2 free agents ignoring the phone but set the dist to 00:15. Any difference?
Run it again with dist =00:15 but with 3 agents logged in but ignoring the phone. What do you make the time delay between greetings 1 and 2?
OK, so we shouldn't be ignoring the phone in a call centre environment but it happens and what is worse is that the system apparently can't handle it.
 
Have your vendor come back out to tweak the programming.

A ring cycle is aprroximately 6 seconds. Ringing from the customers telco is usually false. There are almost always delays from telco ring cycles to Phone System cycles. There is almost always a delay from a customer hanging up but still rings once on a phone system.

Steve
tele-dataservices.com
 
I agree with Sphoneman. Contact your vendor so that they can work directly with Nortel on this. Allthough I have many complaints myself with the new CC, I have to say that I have had great response directly from the Nortel support group on the problems that I have encountered...one piece of advice though....don't refer to the BCM as a "pile of donkey droppings" when contacting Nortel for technical support...it may slow your response time greatly...

Teleplop
 
Sphoneman and Teleplop - thanks for the feedback - much appreciated. I have been verbalising with the vendor Sales Rep today.
The answer for the distribute timers is to put them so far in the future that they drop over the edge of the planet - out of sight and out of mind. Hmmmm.

More verbalising to be had I fear.
 
you may want to contact nortel to complain about the vendor...

ski season has started
 
BrokenIT,

All of the previous replies are valid, but there is one issue that hasn't been addressed regarding "agents logged in but ignoring the phone." This is the source of the seeming time discrepancy. If an agent is available, (whether they are actually there to answer the phone or not) the call will be delivered to the agent's phone without starting the distribute timer. If that agent doesn't answer, the agent will be logged out or set to unavailable automatically (depending on system programming). The call will then go to the next agent. If both of your agents are busy (on ACD calls) when a new call comes in, I think you will find that the greetings will be heard after 12 or 15 seconds as programmed (I have customers with dist times set to as little as 6 seconds). The system is doing exactly what it is supposed to do (get a call to a phone where there is supposed to be a person to answer it). If your agents are away from their desks they should make themselves unavailable. Its the way all ACD software works.

I hope this helps. Let me know if anything needs to be explained further. I just found this board yesterday. But, I intend to check the topics on a fairly regular basis.

BCMguy.com


www.BCMguy.com
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top