paul bennett

release 9 has been out since last year

aggro

Yes i got wind of this and i believe version 10 is out so i asked my maintainer for an update but apparently none of these fix the problem.

paul bennett

bobcheese will know.

if not ask mitel to do a design request / bug fix.

also if your sites are clusterd then all may need upgrading at the same time

bobcheese

Hi, we run MCD 4.0 (release 10) and I have call history on my set which always has the correct number.

Aggro, when you recieve a call does the CLI that displays on your set as the call is ringing also display this '0' in the middle?

Can't say I have ever heard of this as a known product issue to be honest. Even so for it to exist in R8 and not be fixed by R10 for what would be considered a major issue (as so many people use this feature) sound a bit fishy. If you dont mind me asking who is your maintainer?

mitel100

I think that your maintainer does not know what they are doing. If they are saying that there is not fix for this even in the latest release, there would be up roar, as Call History is a key feature.

I have never come across this fault myself, but would upgrade first before anything else.

Can you confirm what release of 8.0 your are running?

bobcheese

I would agree with Mitel 100 about your maintainer but i'm just abit to polite to say

acejavelin

OK, I am all for a good upgrade. Release 8 is a little old, going on 3+ years, so upgrading is probably a good idea, but at the same time release 8 was very stable and, for the most part, free of major bugs and issues. Also, remember that going from Rls 8 to 10.0 or higher requires a memory upgrade in the controller from 256MB to 512MB.

But why are we assuming the issue here is just because they have older software? No troubleshooting at all? That is not like most users in this forum and only bobcheese asked an actual question to try to figure out if its a real problem or just a configuration issue.

So, I will ask a few questions:

1) Does the caller ID display normally on the phone's display, then show incorrectly in the call logs? <bobcheese's question again, just rephrased a little>
2) Is this a clustered system? Sharing trunking?
3) Are the logged calls that are incorrect coming in/out on local trunks, or remote trunks.
4) If you monitor SMDR are the call records incorrect as well? How do they compare to the phone display and log?
5) What is the specific version of 8 you are running?

BTW... if your maintainer thought this was a software issue, they should have called tech support and reported it as an issue as soon as it was realized that it was happening. I am not normally one to cut on another technician because everyone has bad days, but IMHO a maintainter that just says "its a software problem" and doesn't follow up on a incorrectly functioning feature that is clearly documented, supported, and has a history of functioning properly is probably not that much of maintainer, but take that as my opinion only and make your own judgements...

__________________
Telephony users cannot gain anything without first giving something in return. To obtain a useful feature, a feature of equal value must be lost.

This is Telephony’s First Law of Equivalent Exchange.

aggro

Hi all
1) Always displays correctly when recieving a call,
2) ? all my sites are independent.
3)? Local
4) I have forgot the answer to this one, can you remind me how to monitor smdr?
5) 8.0 UR5

I would like to say that we have many sites running the 3300 on the same software release but only two have this problem.

bobcheese

and this happens on all sets that use call history on these two sites on every missed call? And its always adds the digit in the same place, 3rd digit after the STD code eg 01234 12(0)3456?