Mitel Forums > Mitel MiVoice Business/MCD/3300

Can't Answer Call Issue!! (3300, Residential App)

<< < (2/3) > >>

thinkrick:
Got some more details about this issue... still no resolve, but I did another test and here's some additional info to add to my intiial post:

1. When a successful call comes in, normally I see the caller ID at the top LCD of the phone (5340) and the lower right of the LCD replacing the extension #.  I notice for a second after phone rings, the lower right has the voicemail port # first, then it switches over quickly to the actual phone # of the caller.  In addition, the caller's phone # pops up on my desktop computer (mitel desktop).

2. When the freeze call occurs (again, only happening from a few companies with certain phone service), the caller ID shows at the top of the LCD correctly , BUT... the lower right of the LCD shows the voicemail port # instead (which is like 2501 for us) and never switches to the actual phone # of the caller.  In addition, my desktop also shows that voicemail port # in the caller ID rather than the phone #.

Still no clue how to fix it, but I thought this might help the guru's who are following this thread.  Thanks again for any feedback to this issue.

ralph:
Can you PM me with a printout of each of the following classes of service?
Phone
Trunks
Voicemail  (also be sure all vm ports have same COS)

Ralph

Chakara:
  There is a COS option that displays the caller ID info on the ringing line button - or call appearance.  Also it is a newer option so more likely to be a bit buggy.  As that is the time when the crash appears to occur you might disable that option.  It's called "Display Caller ID on Multicall/keylines" and disable it to see if it helps.

I would do so on the trunks as well as the sets COS.

-Chak

thinkrick:

--- Quote from: ralph on September 16, 2008, 04:23:14 PM ---Can you PM me with a printout of each of the following classes of service?
Phone
Trunks
Voicemail  (also be sure all vm ports have same COS)

Ralph


--- End quote ---

Hi Ralph,  thanks for the reply!!

I've sent you a PM.

thinkrick:

--- Quote from: Chakara on September 16, 2008, 11:40:36 PM ---  There is a COS option that displays the caller ID info on the ringing line button - or call appearance.  Also it is a newer option so more likely to be a bit buggy.  As that is the time when the crash appears to occur you might disable that option.  It's called "Display Caller ID on Multicall/keylines" and disable it to see if it helps.

I would do so on the trunks as well as the sets COS.

-Chak

--- End quote ---

Hi Chak,

I tried that and it looks like it prevents caller ID from showing on all phones except for the extension.  I could test this and see if that at least would resolve the issue and better help us debug.  It's not easy to test since I have to get my guard shack to call my phone system to test (it's awkward everytime bothering them and explaining why I want them to call a strange phone #).  Problem is, this wouldn't be a end all solution since disabling caller ID on nearly every phone would be far worse than the actual bug.  I'd much rather have Caller ID on all phones and deal with the bug (which happens to only a few callers). lol

I will test it though tomorrow and have the guard shack call me with that option disabled.

Thanks, Rick

Navigation

[0] Message Index

[#] Next page

[*] Previous page