Call Data Recording

[RadissonIT]

We have a dot matrix Printer that prints call data reports (SCB?) and is connected to TTY 2 on our switch. It has been working now for about 4 months. Suddenly it quit printing like it had 4 months ago when the Sprint tech that installed our switch had to come out and get it printing again. he indicated that it was a bad TTY port. Now I suspect that the current port has gone bad as well. Does anyone have any suggestions as to what might be going on? Also, what programming needs to be done to move this thing to a good port. Please excuse my ignorance!

 

[RadissonIT]

I found a few posts that will be helpful to me. If anyone has an answer to my first question though it would be much appreciated.
Thanks

 

[telsan]

Check in LD 37 and make sure the TTY port is enabled.

 

[johnpoole]

ld 37
stat tty

ld 22
prt
adan tty 2

ld 37
tty 2

will send a test msg to that port.. what is your switch type? may be other places to check

john poole
bellsouth business
columbia,sc

 

[DocVic]

Reset the TTY ports or SDI card itself. DIS TTY xx (in LD 37) on all ports on the card, disable the switch, and remove it from the backplane. Re-seat the card. enable the switch, and ENL TTY xx on all ports. Put your laptop on the port and see if you're getting data. (TTY xx, then END in LD 37) If not, and your under contract with Sprint, have them replace the SDI card. Good luck.

 

[RadissonIT]

I think it is a bad TTY. I get nothing from it when I test it. I have been through this once before and we moved to a different TTY to resolve the issue. After losing some programming the we no longer get reports. How do you tell which TTY ports refer to what when looking at the digi boards in the cabinets?
Thanks

 

[RadissonIT]

I found a good TTY, made it ACD user, changed SCB PRIO to 1 (The good TTY), outed bad TTY. All is well.