sundance-communications.com/forum Forums TDM Business Telephone Systems Inter-Tel Telephones & Systems Axxess 8.233 CID glitch

Access 8.233, EVMC, Copper lines, one co trunk group all calls to one CRA both day night 1= Collected 2= HG 2000 4= ext 1001

Issue is any call coming in going to any destination when number is used displays:
1-(area code)-(prefix)-(first 2 of 4 of the address) in place of the last 2 digits of the address we see LL T, LL being where the last 2 digits should show up and a space then a capitol T

It's not the carrier, I changed the ring in to 1001 and display says the number as it should, I built a new CRA from scratch same issue, tested dialing the 0 to get to HG 2000 and same issue. Change to name and it is fine back to number it fails.

Oh and as soon as you answer it shows the complete correct number! Call log correct number as well you only see when it is being transferred from the VMS event built a star and same issue star with default to new CRA

That is definitely a very interesting issue. Have you tried flashing the CPC with the latest and greatest version of 8.23X?
I believe it is 8.235.

I believe the problem is coming from the voicemail, when I watch the monitor and dial the ext to transfer to I get :
" 208 ALARM: Error in e:\8.2x\netsrc\avdap\build\asai\src\layer.cpp at line #1533. Cause= Call State".
I could not find a drive e: I reloaded the avdap software and get the same response. I changed com ports, cables. Nothing works.
If I can get to the path of what ever e: is that would get me moving..

Straight from the Edge:

208 ALARM: Error in file at line #line_num. Cause = cause.
FIELDS: <file> The name of the file the error occurred in <line_num> The line number where the error occurred <cause> The cause of the error
CAUSE(S): There was an unexpected event in the ASAI protocol. The AVDAP and Database Programming could be out of synch or there may be some loose and/or defective cabling between the two PCs.
ACTION: None, if the AVDAP continues to operate correctly. Otherwise, reset the AVDAP PC. Make sure the AVDAP software and the Database Programming software are both up to date.

I would try flashing the CPC with the latest and greatest .bin file - 8.235. Pull down the database, clean and restore.
I would then reload the latest and greatest version on the EVMC card. 8.236 is the latest for Linux and 8.234 is the latest for OS/2.

Admittedly, this would be grasping at straws but it's definitely worth a shot to be going with the most current release.

You could also run a scandisk and defrag on the voice mail hard drive.

Yea this thing is a Butt kicker, everything is at the latest , I have already done the scandisk and defrag.
If I knew how to get to the E: drive where the error is coming from I would have a better chance at fixing the problem. I have already changed the cables, com ports, crazy amount of resets.
Is there a way that via the avdap commands to get to the e:file?.

Is the vmail Linux or OS/2?

the one and only OS/2,,, which is half my problem..

having the same issue with the caller ID showing LL T, the LL is in place of the last 2 digits of the phone number. T-1 PRI, software 11.010 and Win2k voice mail.