|
Joined: Mar 2002
Posts: 411
Member
|
Member
Joined: Mar 2002
Posts: 411 |
I've got a client with an IPO 500 that is having problems with incoming calls when caller ID is enabled. The inbound calls are set to ring the receptionist, overflow to two other people, and then hit VM. When CID is enabled the receptionist can pick up the phone and it stops ringing but the caller isn't there. When they hang up the phone it starts ringing again. Depending on how long it takes them it generally overflows to the two other people and they can generally retrieve the ringing call.
Version is 4.2.14, lines coming in on analog, all digital stations.
|
|
|
|
Joined: May 2004
Posts: 1,669 Likes: 4
Moderator-Avaya
|
Moderator-Avaya
Joined: May 2004
Posts: 1,669 Likes: 4 |
Was this system on a previous version? Did they just go up to 4.2.14?
I have had a few systems do some weird crap on that new release. I would take them down to 4.2.11 and see what happens.
|
|
|
|
Joined: Mar 2002
Posts: 411
Member
|
Member
Joined: Mar 2002
Posts: 411 |
They have had a variety of versions as I tried to find the problem. I'll have to check and see what the previous one was.
|
|
|
|
Joined: Jan 2009
Posts: 854 Likes: 1
Member
|
Member
Joined: Jan 2009
Posts: 854 Likes: 1 |
The only problem I have had with Caller ID w/ analog lines on an IPO 500 (all versions...currently 4.2.14) is the amount of time it takes for the ID to appear on the phone. When a customer calls in to the location, by the time the Caller ID displays on the receptionist phone, the customer has heard approx 4 rings, wheras it has only rang twice on the reception phone. I wish they could find a way that by the 2nd ring the customer hears, it would be the 2nd ring on the phone system as well.....
|
|
|
|
Joined: Jul 2001
Posts: 3,347 Likes: 10
Moderator-Avaya-Lucent, Antique Tele
|
Moderator-Avaya-Lucent, Antique Tele
Joined: Jul 2001
Posts: 3,347 Likes: 10 |
CID comes between the 1st and 2nd ring. IPO waits until it either captures the CID, or received a 2nd ring without CID before presenting the call to its destination (be it an extension or hunt group). Without this operation, the phone would ring, and then the CID info would appear.
You might want to test with a butt set to see what the caller hears, and how many rings come in at the MPOE, and when the IPO starts ringing.
|
|
|
|
Joined: Jan 2009
Posts: 854 Likes: 1
Member
|
Member
Joined: Jan 2009
Posts: 854 Likes: 1 |
I have simulated with a butt set, and it is as the customer reports. They hear anywhere from 3-4 rings before IPO is ringing. I understand that the IPO is waiting for the CID, but on Nortel CICS/MICS (for example) the lines ring right away and will present CID on the 2nd ring. Just wish IPO could behave the same way.
|
|
|
|
Joined: May 2004
Posts: 1,669 Likes: 4
Moderator-Avaya
|
Moderator-Avaya
Joined: May 2004
Posts: 1,669 Likes: 4 |
I would also clamp a butt set on the trunk and make a call in on it. Monitor and see what happens. You should hear the tones when CID is transferred, then what????
Does this happen on all ATM4 ports?
|
|
|
|
Joined: Jan 2009
Posts: 79
Member
|
Member
Joined: Jan 2009
Posts: 79 |
You can eliminate 2 ring delay by going to trunk type and changing it to Loop start. No caller id will be delivered though.
|
|
|
|
Joined: Jan 2009
Posts: 854 Likes: 1
Member
|
Member
Joined: Jan 2009
Posts: 854 Likes: 1 |
That's how I have it set now. Just loop start. They do not use CID now, but may in the future. It does happen on all ATM4 ports.
|
|
|
|
Joined: Mar 2002
Posts: 411
Member
|
Member
Joined: Mar 2002
Posts: 411 |
Just for an update, we went through Catalyst support and are at Avaya Tier 3 support. It's programmed correctly but not acting correctly.
|
|
|
Forums84
Topics94,534
Posts640,048
Members49,854
|
Most Online5,661 May 23rd, 2018
|
|
0 members (),
322
guests, and
36
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|