Modem Issue 1

[MERIDIAN11C]

hello

I can connect to the Modem but just only have access to PDT
and when i type SL1Input its frezze and then go back to PDT and i can type anything

any idea ?

the only way that i have is reboot in PDT and wait, and then have access to the PBX but made a reboot everytime
is wrong

thanks

 

[phonz1]

can you "exit" from pdt?

 

[MERIDIAN11C]

thanks phonz1

yes i can exit but i cant access to PBX

 

[MagnaRGP]

Are you certain that the TTY that the modem is connected to has SCH MTC and BUG in the user type?

Try physically reconnecting the modem to TTY 0 and see what happens.

 

[MERIDIAN11C]

pretty sure

i dont know why i have to reboot everytime that i connect to the PBX

once i reboot i get access the system

and hang up and redial and the screen is freeze (reboot again)

 

[ginao]

I have an Meridian option 11c, Release 23.35..

My customer wanted to switch over to another carrier for international calls only. Everything in the route data block is built correctly. The carrier is stating the when they trace the call coming in when I'm call from a local phone (in the switchroom) the carrier states the call party is taging the call as an international call instead of a network call. I know there are several patches which the optional 11C, needs. Is there anything else you can think of instead of getting these patches?? Nortel states they do not support this release anymore. I even traced teh trunk going out when I made an international call and the ISDN PRA CALL is seeing the ANI?? Right now, they are using At&t for International and it's working fine, but the customer does not want to use them anymore, they want this company called Broadwing?? Any suggestions??

 

[MagnaRGP]

ginao:

my first suggestion would be to start your own thread and not hijack someone elses.

 

[MERIDIAN11C]

Thanks MagnaRPG

 

[acewarlock]

You only need SCH MTC and BUG to receive these type messages automatically from the system, you don't need them to talk to the system.

What port are you connecting the modem to? I'm Assuming fron from your handle it's an Option 11C. Can you access the system from another port and do a STAT in LD 37?

Also verify the Dip switch settings on the SSC if your usung Port 0 and the CFN if your using any other Port.

Why change the engine if all you need is to change the spark plugs.

 

[MERIDIAN11C]

Thanks acewarlock

yes i handle the OP11 and the big problem is that all the port are blocked
so i cannot see in LD 37 the status
the only way is vis modem and reboot to have access
but the system seems to be fine i dont have any other problem
the trunks y sets are working fine

 

[geirendre]

A MAN INIT normaly frees up stuck TTY's.
Have your PC connected to Port 0 if you do the MAN INIT.
You should se the "Warm-restart"-messages there.

 

[MERIDIAN11C]

This Op11 is a remote system
the only way is via modem
question ?

the MAN INIT is the same if i reboot via PDT ?

 

[johnpoole]

1. There are (8) dip switches on the rear of the modem. Set switches S1, S3, S7, & S8 in the down position, the rest in the up position.

2. Connect the modem to a terminal or personal computer using a 25 pin RS232 cable.

3. Set the terminal or personal computer serial port to 9,600 baud (8 data bits / no parity / 1 stop bit ).

4. Turn the power ON to the modem.

5. Using the terminal or the terminal portion of the personal computer communications package, issue the following AT command. AT&B1&W&W1

6. Turn the power OFF to the modem, and disconnect it from the terminal or personal computer.

7. Set the (8) dip switches on the rear of the modem as follows. Set switches S1, & S4 in the down
position the rest in the up position.

8. Connect the modem to the Meridian 1 system as instructed in the NTPs

that one works for me everytime.. maybe he can take the time to add that as a faq..

john poole
bellsouth business
columbia,sc

 

[MagnaRGP]

Meridian11C:

I just had this same problem on a CS1k MG running 4.5. I couldn't login to any local TTYs nor via telent to the SS. Only one port worked (modem) and DIS ing and ENL ing one of my local TTY's cleared up the issue.

However after fixing this issue, I came across this solution in KNOVA. I think it might apply to your situation. Here is the full text for you:

Unable to log into Call Server via any TTY (SDI or PTY)

--------------------------------------------------------------------------------

Problem Description
Problem Description:
==============
Unable to login via the QSDI paddle board, CPSI ports or via PTY
After entering LOGI and user name the PASS? does not come up.

TTY 03 SCH MTC TRF BUG 15:23
OVL111 IDLE 0
>logi admin1
TTY 03 SCH MTC TRF BUG 15:23
OVL111 IDLE 0
>logi
TTY 03 SCH MTC TRF BUG 15:23
OVL111 IDLE 0

This problem has happened twice before and the Call Server has been INIed to fix it.
The problem was initially reported on 03.00 but it has reoccurred since
the site was upgraded to 04.50W.

Site Setup:
=======

CS1000M MG / 04.50W / CPP2
Two signaling servers 04.05.88

SETUP AND ACTIONS PERFORMED TO CAUSE THE PROBLEM:
- The customer tries to log into the Call Server overlay area, enters "logi admin1" expecting the "pass" option to come up.
No "pass" option comes up.
- Customer tries again using the same login name, same problem
- Customer connects to different TTY port and tries to log in, same problem, unable to log in.
- Customer connects to CPSI ports, same problem.
Customer is able to log into pdt from all TTY/PTY ports.

EXPECTED RESULTS:
Should be able to log into the overlay area everytime.

ACTUAL RESULTS:
Unable to log into the PBX via any TTY(QSDI-NT8D41BB) or PTY(SS) ports. The system would not respond to "logi" it would just ignore it.
The system would not respond to a "logi" prompt with "user id" or "pass?".
The system would allow PDT login. The system would have to be INIed to resolve the issue, but the problem would return
after some time.
- Call Server does not show any errors when problem occurs

IMPACT OF PROBLEMS:
Site tech / Customer unable to communicate with the Call Server to perform admin/maintenance work

Problem Resolution
WORKAROUND:

1. Log into the Call Server using uppercase letters "LOGI ADMIN1" the system will respond. Enter the password as configured. Do not use upper-case letters for the password. After logging in using upper-case LOII and ADMIN1 you should be able to log into the system with lower case logi and admin1.

2. Install patch MPLR22198

Affected Products
Succession CS1000M MG
Meridian Core Option 81C - CPP
Meridian Core Option 81C - CP4
Meridian Core Option 81C - CP3

 

[acewarlock]

When you do get logged in, do a STAT in LD 37 and post here.

Why change the engine if all you need is to change the spark plugs.

 

[geirendre]

And LD 22
PRT ADAN TTY

 

[MERIDIAN11C]

CONNECT 9600
0000 admin1 ( i hit enter and nothing happen)

PDT: login on /sio/1
Password:
PDT in Progress. Please Wait....

Done!

pdt>
pdt>
pdt>
pdt>

this is the problem
when i try to logi in i hit enter and the port do not respond nither the local port TTY 0
the modem port is TTY1

 

[MERIDIAN11C]

And logically when i reboot the system the TTY port are
ENABLE

 

[MERIDIAN11C]

the modem should respond with this

TTY 03 SCH MTC TRF BUG 15:23
OVL111 IDLE 0
>logi admin1
TTY 03 SCH MTC TRF BUG 15:23
OVL111 IDLE 0
>logi
TTY 03 SCH MTC TRF BUG 15:23
OVL111 IDLE 0


but nothing happen i just have access to PDT and I dont know why in PDT I CAN DO anything

 

[MERIDIAN11C]

CONNECT 9600
0000 admin1

PDT: login on /sio/1
Password:
PDT in Progress. Please Wait....

Done!

pdt>
pdt>
pdt>
pdt>
pdt> help
Available commands:


devs echo enlPPP exit
h help hosts i
lkup mem pppBegin pppEnd
rdaccess rx slipBegin slipEnd
ti version vx

adr crg csm csn
dcp dnt drp dsm
dsn fgn ini ipr
mon net nwk osn
p pld ple plp
pua sl1input sl1load sl1listen
sl1run sl1Version ssm ssn
tnt trp tsm w
wua zap @ %
ivd clm ivm xmi
msg

cat cd chkdsk cp
copy del pcmciaformat label
ll ls mkdir mv
pwd ren rename rm
rmdir tree type

b bd bdall bm
br bs c cret
debug l s so
tt loc

d dbgprt pins plis
pload pnew poos pout
prp pstat cpins cplis
cpload cpoos cpout cpstat
reboot remotereboot su symload
td tdb
pdt>


as you can see I can do anything