Inbound Caller ID in voicemail issue

[JayNEC]

Just upgraded a site from 1.3 to 2.1(27) as well as VM Pro to 2.1.14

Inbound callerID on the analog trunks (5 of them)

Calls coming into voicemail do not read the caller ID to the listener, they used to.
Extension to Extensions calls do state "call from extension X" but calls from the outside say "call from extension (pause) at blah blah time etc."

 

[JayNEC]

Anyone out there with ICLID on analog trunks - do you have caller ID announcement in your voicemail?

 

[Ragnorak]

I know it reads of the callerID received on incoming PRI trunks.

I believe by default on the Analog Tab for your POTS lines the trunk type defaults to Loop Start. It needs to be Loop Start ICLID for Caller ID info to be received.

Also try checking the Long CLI Line box at the bottom of the same Analog Tab and see if that solves the problem.

 

[JayNEC]

CallerID IS being received. It is showing on the display of the station, and even shows in the notification email subject line.

BUT, when one is listening to that same VM it no longer reads the CallerID off.

Before the VM and IPO upgrade it worked.

 

[IPGuru]

is your CLI being presented with a "-" between the STD & the main number? ythis format causes trouble with alpha taging on the IPO & may posibly be related

 

[JayNEC]

Hmm, what's an STD? Is there a way to fix this if it is the case? It didn't used to cause a problem. They've been running since the version 1.1 days.

 

[IPGuru]

STD = Dialing code.
I dont see why it should affect VM but who can tell with Avaya?
It does not affect incomming call routes.
|ALpha tagging does not work _it willnot match a directory entry for display.

Avaya have been looking into this problem & hopefully it will make its way into V3.0

 

[Morrack]

I can confirm that this feature works correctly on at least 1 403 I know of running 2.1.27, VMPro .14, and analog trunks with callerID.

When you upgraded from 1.3, did you make all the stops along the way (1.4, then 1.99 if a 403, then 2.0, then 2.1) or just go straight to 2.1?

Peter

 

[JayNEC]

I went from 1.3 to 1.99 then to 2.1

 

[Morrack]

Probably your issue right there. Best practice is to upgrade through all the major revisions. Especially 1.4, they changed a lot with that one. Do you still have a copy of the config from before the upgrade? If so you can simply redo the process. Otherwise you may be looking at a manual re-entry of the config, starting from a defaulted 2.1.27

Peter