Problem printing FFC list

[elturko]

I'm trying to print the FFC list in LD 57, but I get an error as it's listing the codes. Here's what I'm doing:

>ld 57
REQ prt
TYPE ffc
CUST 0
CODE all

It starts printing the codes...
CUST 00
FFCT YES
ASRC *40
AUTH
AWUA ........

but as it gets going, it does this:

PUDN
PUGR *71
SCH0600
CODE SCH0600
CODE

And it leaves me at the CODE prompt. I looked up SCH0600 and it shows "Illegal input character." I'm not typing anything as it's printing the list, and it sometimes happens at different points in the list. (Just ran it again, and it got past PUGR, down to RDLN when it quit.)

Any suggestions?

Thanks,
Matt

 

[acewarlock]

What Baud rate is your terminal running, is it a printer or a VDU?

 

[elturko]

It's a Wyse dumb terminal (and I hate it). I can check the baud rate later... what would you suggest it be set at?

 

[johnpoole]

prt
ffc
0
all

john poole
bellsouth business
columbia,sc

 

[acewarlock]

at least 9600 or higher

 

[johnpoole]

are you on an opt 11? is so slow the port down to 1200, dip setting on the ssc card.. then set the wise to match.. i needed to read slower, my bad. older dumb terms filled the buffer up and started to corrupt on longer prints.. and do not try and print at the same time.. i haven't used a dumb term back in the late 70's

john poole
bellsouth business
columbia,sc

 

[elturko]

Probably a topic for a new thread, but.... how are you guys connecting? We got the shaft from our vendor, so I know we're not set up in the most efficient manner.

Basically, we've got the Wyse terminal for programming, and are capturing CDR through the COM port of (what used to be) our OTM server. OTM never did work right for simple traffic capture (we never even tried to do programming with it), and we couldn't get any support from the vendor, so we basically gave up on it. Now, I'm just using a utility called ComCap to capture the raw CDR data, then have a script that I wrote to parse through it and dump into an Access database. That's our fancy call logging solution!

Anyway, I'd love to use ProComm or something, but the PC only has one COM port. I've thought about getting an add-in card for an extra port, and might still do that. What would be even better would be accessing the Opt11 directly over the network, like through telnet or something. I've heard bad things about plugging it directly onto the LAN, but I've also thought about a serial device server as an intermediary.

Now that I got that all out of the way, how are you guys connecting to your systems for programming?

Always glad to get anyone's thoughts...

 

[acewarlock]

I have a PC with OTM on it , but I don't use it except for the passthough to the Switch as it was there before I came here. I use CLI, it's what I learnd on back in 1979 and I've been using it since.

 

[johnpoole]

in the 70's it took me a week to do what i can do in a day now.. i spent all weekend building a nul modem cable just to get a vt-100 to work, then went to ld 20 did a print, nothing would print i got a code at cust 0, after unpacking books for an hour i found out that the code was trying to tell me there was no cust 0 built.. then it took another week to look up every command in ld 15 and about every sch code in the book.. as soon as laptops came out i grabbed a 286 black and white, i even used a tandy 80 with a term emulation package for a while.. MOST of our smaller switches have a dumb term in the switchroom, if i am going to be on site longer then a few minutes, i drag the laptop in.. (not the same one)... for an on site i would find someone that is upgrading and use the old pc add procomm and save time... i never use otm.. we started about the same time, i remember techs telling me that 300 baud was to fast, you can't read that fast anyway... in the corp we had machines that ran at 33 baud, but i didn't stay at that speed very long...

for longer prints on a dumb term, slow it back down.. 1200 or even 300 if your printing.. or grab the book and print the codes one at a time

john poole
bellsouth business
columbia,sc

 

[elturko]

Thanks guys. I was able to stop logging CDR temporarily and login through the PC to capture all the FFCs. Will probably look in to getting one of those serial-to-Ethernet devices so I can have the CLI right at my desk!