Terranova is dropping me off before connection

[phonesaz]

I am working on an old Guestworks. I followed the crossconnects back from the last pair on the 1st board, used my butt set to ID the phone number, and called the number from the site to verify modem tone. So far so good.
Went back to the office, opened my Terranova, built a file, it called the site, rang once, modem tone, then almost immediately disconnected me. I have compared the settings to 3 or 4 others I have that work fine, so am a little stumped. I checked the list history on site, and Avaya has been in within the last couple of weeks, so I don't think it is the modem. My Terranova settings (line options) are: Hayes modem, COM3 (which I know is right because I connect to other sites) Unix, full, 8,1,19600 both speeds, 0 50, control is xon xoff, which translates to dc1 Q and dc3 S (I just listed these in the order they appear.) Any suggestions on what may be wrong? Is Guestworks different from Definity? The system is a GWSi.03.1.640.04. Thanks as always - D

 

[jfh9219]

Haven't used Terranova in years (though I met him earlier this year at INAAU) and this might not have anything to do with it but I would try with the modem set at 2400. If that didn't work I would then leave the speed set at 2400 and try different control settings. If they didn't work I would go back to the site with my laptop and a crossover cable and directly plug in eliminating the modems to verify you can still get in.

 

[jfh9219]

Just had another thought. Make sure that your modem is not doing data compression. Most new modems do it by default, and most old modems don't do it at all.

 

[phonesaz]

Two ?? re above - first, would the settings change that much from system to system? I regularly log into 2 other Definity systems with the setup that I have currently; they are both G6, so old but not as old as this one. Second, w/ laptop and crossover cable, how is that different from using the on-site terminal (which I can do successfully.) Thanks - Diana

 

[phonesaz]

My modem had data compression, which I disabled. Still having the same problem; ring, connection, about 5 seconds of noise and then the dreaded "line connection lost" message. Is there a chance that I have ID'd the wrong number? It is the last port on the first card, which is the aux board. You literally can't get behind the system to look closely at the 110 blocks due to the tight fit, so I just followed cross connect wires from that point back to the 66 block. Is there another way to verify the INADS number? These people have a maintenance contract but haven't talked to Avaya for years because the system doesn't give them any problems.

 

[jfh9219]

If you can't get to the wiring, on the System-Parameters Maintenance form you could change the OSS Endpoint from Avaya to a number you control with Caller-ID capabilities, cause an alarm and then see which number called you. Change the OSS Endpoint back! Seems unlikely that you would pick a wrong number and happen to get modem tone however.

You could also verify on that form that Customer Access to INADS Port is set to "Y".

Page three will also tell you your (limited) modem settings.

 

[phonesaz]

Great suggestions - I am going out there next week and will try these. I am pretty sure the modem is enabled because the history shows the routine inads/init stuff that Avaya does, but these are a couple of great things to check. I am tring to think of an easy way to create an alarm - would pulling cross connects from a CO line do it? I am a little rusty on Definity - pretty much stopped working on anything new several years ago, and haven't done a lot of marc work in the last year - before that it was a daily thing, but mostly end-user changes, clearing simple alarms, things of that nature. Very rarely at the switch level.

 

[jfh9219]

On the login administration frame there is also a field:
"Access to INADS port?". You will probably want to check that for your login.

As far as creating an alarm, I don't have a good suggestion. I would try things on my PBX that I would never suggest someone else do because I know the downside in my environment. Look at your alarm history and see if anything gives you an idea.