No incoming caller id 2

[av2246]

Avaya phone system. The 8410D handset for a particular extension will not show the incoming caller id. When the extension is moved to another handset/line the same thing happens - no caller id. A different extension on the original handset/line works fine and displays the caller ID. To my observation, the problem is in the programming of that extension somehow, and it is the only extension in the building that is having the issue. I have looked a dozen times at each and every possible setting but cannot figure out why this one extension refuses to show the incoming caller ID. It seems to work fine otherwise. Has anybody ever seen this problem or have any ideas?

 

[4merAvaya]

Remove the offending station and duplicate one that works (dup station).

Kevin

 

[av2246]

Can that be done and still keep that same extension? They don't want to lose the number they have because it's in the Sales department, and they have published it on business cards and other registrations as their phone number. I obviously don't know how, but I am working with our provider to get the issue resolved.

 

[4merAvaya]

Yes, you can remove the station and then add it back in using the same extension number. From your description it sounds like a PBX problem.

Kevin

 

[AvayaTier3]

working 8410D station xxxx
broken 8410D station yyyy
remove station yyyy
duplicate station xxxx start yyyy

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[av2246]

I gottcha. Thanks!

 

[av2246]

That indeed did do the trick. Thanks. The solution was so simple I wish I would have thought of it...

 

[Saiyan656]

What was the first digit the bad extension had what was the first digit of the good extension had? Same or different?

 

[av2246]

I'm not sure I follow what you are asking, saiyan656, but the extension with the error was 2144, and it was cloned from 1038 to corrected the problem. We didn't plan it that way, it was a matter of random choice.