CDR TTY port oddity

[NortelGuy1979]

Hi All, hope everyone's holidays were good! Happy New Year too!
I have a question about CDR on a TTY port. We recently upgraded to Succesion 3.0 from r25.40B, and also at the same time upgraded from OTM 1.2.x to 2.10.56. The OTM is connected via ethernet to both switches for DBA, and then is physically close enough to one of the switches to use Call Tracking on a CDR TTY port. The user of that port had been previously only CTY. Now, it will not work unless I add MTC and SCH to the port. Even looking at the port in ProComm or HyperTerminal, it gives only garbage unless I add other users on the TTY. Anyone have any idea why? I fought with it for weeks, changing cables, outing / rebuilding the TTY, verifying port settings, baud, etc - I just stumbled across it todya. Anyone seen this before? TIA! -Matt

Matt H.
TMC - KCMO, USA

 

[janaya]

thread798-969798

Check this thread to see if it is the same issue.

John

 

[NortelGuy1979]

Doesn't appear to be, no. We do have the patch mentioned in that thread in our system. It's working OK, I'm just curious as to why. It was one of those things i worked on in my spare time for quite a while, and it confuses me Thanks! -Matt

Matt H.
TMC - KCMO, USA

 

[johnpoole]

did the same upgrade and after the upgrade and patch i had to out the cdr data and re-enter the data, came up clean, the upgrade blew away about half of my internal cdr from some loops so i had to add it back to class for a few hundred sets

john poole
bellsouth business
columbia,sc