Access into Option 11C via HyperTerminal 1

[rkollar]

Greetings,

A Meridian 1 Option 11C PBX was donated to my company for testing purposes. Currently it is not live. I have hooked it up to a modem, and tried using HyperTerminal to connect into it.

When powering up the PBX, with HyperTerminal running, I can see the boot routine, VM backup job scheduled, etc. However, if I try to login and/or type any commands, there is no response from the keyboard. I have tried using different PC's/laptops.

Below is an excerpt from on-line documentation I found:

How to HyperTerminal in to the PBX and VOICEMAIL Systems.
1. Launch HyperTerminal
2. Set phone number to your modem dialin number
3. Set terminal emulation to VT52
4. Dial… it should end up at a blank HyperTerminal window
5. Type the password to access the PBX modem. This will not show up on the screen when you type it. The screen should now display “Ok, You are now transparent to port 1”.
6. Type “logi” to login, then the password.
7. You should now have a > command prompt.

Is there something missing; that needs to be configured? Or another way of getting into the PBX? Thanks.

 

[zog99]

i find PROCOMM much easier to use

can you connect to TTY 0 thro a null to your PC?
then select direct conn, VT100, 8 N 1, baud maybe 2400

try that

 

[johnpoole]

the fact that you have a boot screen does seem to indicate the right baud and layer one. looks more like a open transmit lead, or even a rts lead off a pin. i would always attempt a direct connect before a dial up. put a null on port 0, set the baud rate the same as the dip switch on the ssc card .. after it boots a return should get a response. from the > prompt logi.. by dropping the modem you can better locate the weak link..

john poole
bellsouth business
columbia,sc

 

[rkollar]

Gentlemen,

I greatly appreciate both of your suggestions (Direct connect via a Null on Port 0, VT100, etc.) The DIP on the SSC was set to 2400, correspondingly the baud rate on HyperTerminal, as well.

With the settings you recommended, this time I do not see a display on boot up. Just a blank screen; still with no response from the keyboard.

Unfortunately, I do not have access to ProComm Plus. I did, however, download MerAssistant. This app provides a GUI interface, and replaces to the Maintenance Terminal. Still didn't work.

 

[zog99]

ok.. have you checked that the tty is not disabled??

 

[hawks]

When you seen the boot up where di it stop? The reason I asked is are we sure that it came all the way and initialized.

 

[srmega41]

Good question hawks. One question I have is are you using a null modem on your connection between the TTY 0 and the PC?

One other "suggestion" is to try Mark 7 & 1 instead of None 8 & 1. This sometimes works, and is an easy change to make. (This is also helpful if you do an IDU on a set and get garbage back as a response. A swap between N81 and M71 will most of the time clean this up)

Hope this helps,

Scott M.

 

[rkollar]

Folks,

Here is a capture of the output after the PBX boots up. Perhaps this could tell you something.


Meridian Small System Controller
Pre-Boot: 03 dev2.37
Flash Boot: NTDK34AA_r08 dev2.41
Reset Reason: C0, 0 - Reset due to Power Up
SRAM: 128 kBytes
DRAM: 8 MBytes, speed=60 ns
Security ID: 10000646 type: NT_STD
Backup Flash: 1572 kBytes
Program Store: 24 MBytes
Flash Drive: 8 MBytes
Expansion board #1 not installed.
Expansion board #2 not installed.
Ethernet MAC address: 00.00.75.45.F1.94
PCMCIA card not installed in drive A.
PCMCIA card not installed in drive B.

*** To invoke install setup program from PC

Executing power up self tests
Power up self test passed
DISKOS to be run.
Verifying Diskos.


*** OS RESTART ***

Meridian 1 X11 System Software
Release : x112208d
Created : Wed Sep 25 19:21:26 PDT 1996
Loaded : 3/1/96 5:17:41

Copyright(C) 1972-1994 Northern Telecom, Inc. All Rights Reserved.
VxWorks 5.1.1
Copyright(C) 1984-1994 Wind River Systems, Inc. All Rights Reserved.
Use of the above software subject to terms of a license agreement.
U.S. Government users subject to "Restricted Rights" under F

Initialize Network Interface.
Network Interface is up.
Host : PRIMARY_ENET
IP Address : 137.135.128.253
Sub-netmask : 255.255.254.0

Loading 'rpteng.db' from "c:/p/rpt/rpteng.db"
Executing startup script "c:/p/etc/startupc".
# MISC: RENAME: FOXSTARTC foxstartc =
# EDITION AB01, SL1LIB ARUNA.55 (96/02/27 15:32:50) -- CLOSED
# Empty startup file for Option 11C use in the field.
cd "c:/p/etc"
value = 0 = 0x0


Done executing startup script "c:/p/etc/startupc".





Loading retained patch from "c:/u/patch/r2cfn.p
Activating patch, handle = 0
Modifying a longword at 0x206b5d78 from 0x0 to 0x109602e2
Modifying a longword at 0x206b5ccc from 0x0 to 0x1095fc14
IN_CDNO_NUM at 0x1094f386 will be patched to jump to 0x206b5c94
Patch 0 has been activated successfully.
Loading MAT script files......
Start SNMP agent

Loading SL1 data
Processed c:/p/data/view.cfg

SYS000 000400 000000 000000 000000 CPU 0
SYSDB RLS/ISS: 2208D LOADED FROM C: DATE/TIME: 21/9/2004 01:01:20 RECS: 74 SEQNO
: 885
SYSLOAD ISSUE 22.08D
DONE
SRPT730 OS 0: Cold S
Release: x112208d
Created: Wed Sep 25 19:21:26 PDT 1996

SRPT750 INI 0: INI on side 0 due to System Cold Start

INI000 00000000 05 18 01 00000000 00000000 00000000 00000000 ? 00000000

SRPT752 INI 0: INI completed in 9 seconds

DSET000 DOWN LOAD 414 0 46 0 0 0 0 56106

INI002 00000088

INI003 0000009C 000000A0 000000AF 000000B0 000000B4 000000B8 000000CE


>
XMI002 2 DTI/PRI

XMI002 6 XDLC

XMI002 9 XDLC

XMI002 7 XDLC

XMI002 10 XMLC

XMI002 4 XUT

XMI002 5 XUT

DTA003 2

PRI000 2 5

DTA012 2

DTC0

DROL000 DAILY ROUTINE BEGIN
NWS LD30 BEGIN 05:19 3/1/1996

NWS301 -6 -7 -8

NWS401 9 : -0 -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 -11 -12 -13 -14 -15

DROL001 DAILY ROUTINE END
NWS LD30 END 05:19 3/1/1996

DROL000 DAILY ROUTINE BEGIN
TDS LD34 BEGIN 05:19 3/1/1996

DROL001 DAILY ROUTINE END
TDS LD34 END 05:20 3/1/1996

DROL000 DAILY ROUTINE BEGIN
CNF LD38 BEGIN 05:20 3/1/1996

DROL001 DAILY ROUTINE END
CNF LD38 END 05:20 3/1/1996

DROL000 DAILY ROUTINE BEGIN
AUDIT LD44 BEGIN 05:20 3/1/1996

VAS008 ADMIN VSID 9 CUST -- TIME & DATE 5:20:18 3/01/1996

AUD370 VSID 9 CUST --

AUD370 4020 VCE -- DTA -- CTN --

DROL001 DAILY ROUTINE END
AUDIT LD44 END 05:20 3/1/1996

DROL000 DAILY ROUTINE BEGIN
CCED LD135 BEGIN 05:20 3/1/1996

DROL001 DAILY ROUTINE END
CCED LD135 END 05:20 3/1/1996

VAS008 ADMIN VSID 9 CUST -- TIME & DATE 5:20:28 3/01/1996

AUD370 VSID 9 CUST --

AUD370 4020 VCE -- DTA -- CTN --

 

[techman3030]

check and make sure you have the correct com port set in hyperterminal.

 

[rkollar]

techman3030,

The correct COM port is what? I have COM1 setup.

 

[johnpoole]

if the comm was wronge, you wouldn't see the boot>>> duh

john poole
bellsouth business
columbia,sc

 

[srmega41]

Nothing looks to terrible; Release 22.08 software (rather out of date, but totally functional), it also appeears that you may have programming for cards in slots 6 and 7 with no cards(Digital Line Cards) in place. Slot 8 is a mystery, unless there is a card and no programming. Slot 9 (DLC) is a bad card, and all TN's have been disabled. (not that ANY of this is relevant)

I think your issue is simply communication mismatch between the TTY and the terminal emulation program. If you are getting this from the PBX, you should be on the right com port, unless you can set a different port for outbond communications.

My only other suggestion is to start at your dip switch setting speed and try every combination you can use for communcation to the PBX.

Anyone else have suggestions? This really should not be this hard to figure out, but I am stumpted.

Scott M.

 

[techman3030]

I agree with scott. You said you were able to see boot up with the modem connection, but not the direct. that was why I thought it might be a com port setting on the direct connect. Are you using the same port for both connections, and just trading out the cables, or are you using port 0 and 1? port o has it's baud set up on the faceplate, but port 1 is set up in ld 17 adan.

 

[johnpoole]

both post are right, now you know why we all use procomm. the comm is right, BUT i never see the >prompt and i would expect that without a transmit. i would add a breakout box to the mix to see if your sending out or not. any transmit, including a bad baud rate should get something in return.. the default is usually 8 none and 1, but that can trick you.. because you can see the boot, you seem to have everything except transmit... ini and watch that, see if after the ini the port wakes up

john poole
bellsouth business
columbia,sc