View Single Post
Old October 29th, 2009   #8 (permalink)
acejavelin
Moderator
 
acejavelin's Avatar
acejavelin is a high-tech, heavy metal redneck!

Activity Longevity
11/20 4/20
Today Posts
0/0 ssssss619
Location: North Dakota
Rep Power: 2acejavelin is on a distinguished road
Gender:
Country:
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.

Last edited by acejavelin; October 29th, 2009 at 10:16 PM.
acejavelin is offline   sendpm.gif Reply With Quote