Older IVX system. Had to replace one A12 card and an expansion cabinet. Since that repair, the Caller ID operation has changed. On a 48 key phone, it only displays the Caller ID name. The CID digits are not displayed until the call is answered. I have made sure that the COs are not named. This happens on all the pilots as well as the DID numbers. ESI tech support says this is normal operation, but it was not doing this before the expansion cabinet and card replacement.

I have compared programming from before and after the service, and can find no differences in programming that is related to COs or CID.

This happens on the pilot numbers that are set to ring to the auto attendant as well as the ones that are set to ring a department, and also the DID numbers.

What is an IVX 256? I have no idea what that may be.

IF you actually have an IVX 128, what release is it?

The A12 module is a single line 12 port station module. It has nothing to do with the PRI programming. Unless something changed, program wise, everything should remain the same as before the module replacement.

If you can provide more information, such as software load and the actual system and rev, then we can help you.

Rcaman

256 = (2) 128 X cabinets with an expansion cable between .
Not sure what is going on with the callerID though...

I remember that swapping cards out would create issues with CO's, like messing up the line groups, but don't remember anything affected with caller ID.

I know you said you made sure the CO's are not named, but I would go into each CO and make sure there are no spaces inserted in the name. I think that happened to me once.

It is, in fact an expanded 128. So it ends up showing as a 256X FSIII in ESI Access. The software version is 72.109.16. Swapping out the A12 and the expansion cabinet did change the line groups of the COs, which has been corrected already. Regarding the CO names, I went onsite and cleared out all the names of all the COs with a phone connected to the system, not with ESI Access. I did this by filling all the character spaces, then deleting the characters so I feel certain there are no spaces in the names of any of the COs.

@rcaman: YOu'd think that programming wouldn't change as a result of changing an A12 card and an expansion cabinet, but for whatever reason it did. CO line groups changed, and something else must have changed because now I have this CID problem.

Have you checked the CID with another device?

I have not. All the info is coming through, so I never checked it with by butt set. I assume since the digits pop on the second line after the call is answered, that the information is being sent from the CO.
Another thing to mention: if I name one of the DIDs, the only thing that shows on the display is the DID name. No other info is displayed.

I think the Caller ID data is being sent. The ESI is just not handling it properly. So, now I guess the question is What was the original setup, cabinet and module and how was it changed.

If the trunk groups got scrambled, that's a good place for ESI to "poke and peek" to see why the caller ID got messed. I would start with the card config and verify that all the modules are properly listed in the config. Next, you need to look at all the channels in ESI-Access to see if there is ANY artifacts left in the labels, like a stray weird character. Then, how about checking to see what the PRI is defined as. Did the protocol change? Most systems are NI-2, but some older systems are NI-1 or DMS or AT&T. Make sure that didn't get messed.

If all checks out, you need to get Scott at ESI to look into it. He seems to know more about digging into the code than anyone else there.

Rcaman

The system is set up as it was originally. The only changes that were made: Replaced the expansion cabinet and the A12 card in slot 1 of the expansion cabinet. The PRI card is in slot 1 of the main cabinet.
Compared before and after programming, PRI is configured as NI-2 in both.
I see no stray characters in any CO line names or channel names. I guess it's time for some more time on the phone with ESI....

could be a coincidence, Maybe,,, the callerid buffer is Full, when that happens You won't see any callerid until it is Cleared ( a master Tech can clear it ) so can ESI

I'm seeing caller ID info.
One more time:

On a 48 key phone with a multi-line display Only the CID name shows on the top line of the display until the call is answered at which point the digits display on the second line of the display.
If i name the CO or DID, ONLY that name shows on the display. No other info appears.

What I'm used to seeing on a multiline display phone: CID name appears on the top line, CID digits appear on the second line, and the third line displays the CO name or department the CO is programmed to ring.

ok, sorry, didn't see that You are getting the callerid,

Did you try, wiping out the programming in the Pilot table, and reentering it?( as far as the software you are running, I do Not recognize that version, it almost looks like a Demo version, I have 2 sites still running a 256X and they are both at 10.8.6

Do you have remote access via NSP ? ( You could PM me the IP ) ( I could take a quick look

That software version is weird. There was a software load for the X that was like that but not exactly the same, so I'm at a loss. Your best bet is to have ESI get in and deal with it.

Rcaman

I wonder How he made out? I tried PM...no response

I have a feeling this either was a corruption in the software load, or something else happened to the system that the OP has not written about. Caller ID is tagged to the CO programming but shares memory space with system wide data.

Rcaman

I have no idea what it is. ESI says it's normal. (I don't think so, but...)It's very possible that whatever killed the expansion cabinet and the card broke something else as well. Being that the phone system is very old, we're leaving it alone for now. Every time it's power cycled something strange happens. It's also at a county agency, so system downtime is not very convenient for the customer. Sorry I didn't come through with a fix.

OK, thanks for getting back, I do have a request...does it have NSP access? I would just like to See for myself( free of charge ) if so, please PM me the IP

The company owner will not allow this information to be shared with others. Thanks for the offer though.

OK, NP.