Issue with Aastra 9133i and caller display.

[Slamby]

Had a search and can't seem to find anyone else with this issue.

Basically, when someone calls in, the phone number is supposed to show on both lines of the display:

01352781812
01352781812

Assuming no caller ID lookup is in place. Now, it does this most of the time, but occasionally it seems to get a little confused, and shows the calling number on the first line, and the previous call's inbound number on the second.

For example, if ext.103 has called me previously, a call from 01352781812 will be displayed as:

01352781812
103

The same behaviour occurs if I use Asteridex as a callerID lookup source. It'll show the correct name on the top line, but the number below will be the previous caller's number.

As I say, it doesn't happen all the time, but enough times to be confusing and annoying.

Any ideas?


Edit: Shows the wrong number in the Callers List too, although it's only calls I've answered that show any discrepancy, and it's not every answered call either. I'll post a pic or two of what I mean.

 

[Slamby]

Here's an example of an OK call:



And here's the next call from a co-worker's mobile phone:



It's got the caller name right, but it's showing the number from the previous answered call, and not Chris's mobile phone number.

Chris Mob is in Asteridex, but for some reason the phone is overriding the CLI. iSymphony and Asterisk info shows the right name and number, so it's the phone that's doign something funny.

Without CallerID lookup, you'll get the right number on the top line, and the wrong one on the 2nd. With CallerID lookup, we'll get in even more of a mess because we'll get the right identification of the caller, but can't trust that the number will be right, which makes my current implementation of CallerID lookup pretty much pointless.

No replies yet, so are we saying no-one else has seen this behaviour on 9133is?

I'll disable the Directory and Callers List, and see if that makes a difference, though we find the Callers List pretty handy.

 

[kenn10]

I don't have this issue with my 9133i's but I don't use Astridex either. I'm also running the most recent 9133i firmware (SIP Generic 1.4.3). I've seen this behavior only once when the CLID lookup returned nulls or bizarre HTML code instead of blanks or a number.