I have a customer with an OS7200 that is slowly migrating to an new install Avaya IP Office. I have the two systems linked via peer SIP trunks and with some creative routing have 4 digit dialing between systems. Currently outgoing calls go out on SIP trunks registered in the Samsung KSU. Outgoing calls placed on Avaya handsets route out thru the Samsung with no issue. The biggest problem is with incoming calls and Caller ID. It's sort of like the two systems don't quite speak the same lingo. Different accents, so to speak.

Incoming calls are answered by the Samsung SVMi 20 voicemail card. Calls transferred to Avaya extensions transfer to the extension, but Caller ID says 'Anonymous', while the proper CID shows on Samsung extensions as you would expect.

Extension to extension calls show the Avaya 'Full Name' as the calling party on a Samsung extension. while Avaya displays only the extension number from a Samsung extension.

These two systems are linked almost the same way two Samsung systems would be linked over SPNet, but not quite. I've had SPNet systems I've service in the past with total transparency as far as CID issues. There must be some setting that I've missed or some box that needs to be checked/unchecked to make Caller ID a little more accurate. I'm sure it has something to do with the way my peer tie trunk is configured. Any help or ideas would be appreciated.

Sometimes the thoughts in my head get so bored, they go for a stroll through my mouth. This is rarely a good thing.