TTY - PMS connection not working - Nortel CS1000 Rls 7.0 4

[HollTel]

I have a CS1000 Rls 7.0 that was working up until a short time ago. We had the TTY port for the PMS connected to the QSDI card on Core 0. It stopped working and the conclusion was that the QSDI card had finally shut down. Because of the fact that we had a TTY available on the NT8D41AA in the back of the Core we programmed it with the PMS parameters and moved the connection to the appropriate DB9 connection. I am sure that all of the DIP switches are set to the appropriate settings but I am not getting anything out of the DB9. I can't help but think that there is something I'm totally missing but should have known.

I have the ability to connect a laptop up to the DB9 and PuTTy to look at the connection but don't see anything at all. Im open to any suggestions at all!!! Ha ha ha.

TTY 1 is the New one ( XSDI ) DB9 connection
TTY 5 is the Old one ( QSDI ) DB25 connection

Thanks.

REQ prt
TYPE adan

ADAN HIST
SIZE 20000
USER MTC BUG OSN
ADAN TTY 0
CTYP XSDI
DNUM 0
DES XSM
FLOW NO
USER MTC OSN
XSM YES
TTYLOG 0
BANR NO
ADAN TTY 1
CTYP XSDI
DNUM 1
DES NEWPMSPORT
FLOW NO
USER BGD PMS
CUST 00
XSM NO
ADAN TTY 2
CTYP XSDI
DNUM 2
DES PBXTTY
FLOW NO
USER MTC SCH BUG OSN
XSM NO
TTYLOG 0
BANR NO
ADAN TTY 3
CTYP XSDI
DNUM 3
DES ACDPRT
FLOW NO
USER ACD
CUST 00
SSUP NO
APRT YES
XSM NO
ADAN TTY 4
CTYP QSDI
DNUM 4
DES HOMISCO
FLOW NO
USER CTY
XSM NO
ADAN TTY 5
CTYP QSDI
DNUM 5
DES PMSPORT
FLOW NO
USER BGD PMS
CUST 00
XSM NO
ADAN TTY 6
CTYP QSDI
DNUM 6
DES UNUSED
FLOW YES
BCST NO
USER MTC SCH CTY OSN
XSM NO
TTYLOG 66
BANR NO
ADAN TTY 7
CTYP QSDI
DNUM 7
DES CoreModem
FLOW NO
USER MTC SCH OSN
XSM NO
TTYLOG 0
BANR NO
ADAN TTY 9
CTYP CPSI
DNUM 9
PORT 0
DES CoreTerminal
BPS 9600
BITL 8
STOP 1
PARY NONE
FLOW NO
USER MTC SCH BUG OSN
XSM NO
TTYLOG 0
BANR NO
ADAN TTY 10
CTYP CPSI
DNUM 10
PORT 1
DES
BPS 9600
BITL 8
STOP 1
PARY NONE
FLOW NO
USER MTC TRF SCH BUG OSN
XSM NO
TTYLOG 0
BANR YES
ADAN TTY 11
CTYP PTY
DNUM 11
PORT 11
DES hms
FLOW NO
USER BGD PMS
CUST 00
XSM NO
ADAN TTY 12
CTYP PTY
DNUM 12
PORT 1
DES IPtty2
FLOW NO
USER MTC SCH BUG OSN
XSM NO
TTYLOG 0
BANR NO
ADAN TTY 13
CTYP PTY
DNUM 13
PORT 2
DES IPTTY3
FLOW NO
USER MTC SCH BUG OSN
XSM NO
TTYLOG 0
BANR NO
ADAN DCH 20
CTYP MSDL
DNUM 8
PORT 1
DES Paytech
USR PRI
DCHL 10
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC NI2
ISDN_MCNT 300
CLID OPT0
CO_TYPE STD
SIDE USR
CNEG 1
RLS ID **
RCAP COLP
MBGA NO
OVLR NO
OVLS NO
T310 120
T200 3
T203 10
N200 3
N201 260
K 7
BSRV NO
ADAN DCH 25
CTYP DCIP
DES sip
USR ISLD
ISLM 4000
SSRC 3700
OTBF 32
NASA NO
IFC SL1
CNEG 1
RLS ID 25
RCAP
MBGA NO
H323
OVLR NO
OVLS NO

 

[HollTel]

Yes I have tried different baud rates and even different pinouts also, including just a simple null modem pinout. I was previously convinced that the issue was the cabling. But at this point I’ve spent two days trying every pinout and emulation that I can imagine.

Just as an FYI this is an option 81. CS1K Rls 7.0

I’m starting to really believe that I’ve just missed something in the programming that is shutting down the TTY with the PMS programmed on it.

I’ve even gone so far as to program the TTY for the terminal on the PMS port to see if it was a physical hardware issue and that worked just dandy.

For some reason the PMS information is just not warning as it should.

I’m at about 90% that it’s in the programming at this point. ( one can never be 100% )

 

[Firebird Scrambler]

Just a silly question, is that particular TTY showing enabled in LD 37?.

I've known them to become disabled, and it's really annoying.

With regards to the QSDI card, what is the status LED showing on it?. Has it ever been reseated?.
It now looks like you have deleted TTY 5 (Original) and TTY 6. Did TTY 6 work as a typical TTY port with e.g SCH. MTC etc?

 

[HollTel]

FS,

Thanks, all of the TTY's are enabled in load 37. Yes I deleted the original TTY-5 because I wasn't sure if it would interfere with an additional PMS TTY. TTY-6 was unused but had users ( MTC SCH CTY OSN ) on it.

when the issue originally showed its ugly head I tried everything I could to get the QSDI card to come back online but I could not get it to respond. That is when I abandon the QSDI card and started to move the information to TTY-1 for the PMS.

This is why I feel that I might have missed something in the programming due to the moving of the PMS to a different TTY.

Cheers

 

[dapster1]

I have read this post
As a try..when you connected your laptop did you change the user type to MTC so you can you can talk to pbx?
This will prove the tty port side is good.

 

[HollTel]

Yes I did change the user group and was able to log in and talk to the switch. Definitely not a physical issue. Thanks.

 

[psychotech]

read and follow the doc i sent from page 52 onwards, and complete the test process they describe ..

not sure if you are on tty 1 or tty 5 now ,
so personally i would start at the beginning from scratch
it is a fairly simple task just creating a TTY and then tweaking it to run an APP ld 17 ADAN, then PARM , nowt else to do

if you have proven that the TTY works by connecting a Laptop to it by using the ADAN tty / sch, bug ,,, you are half way there

good luck

 

[bignose21]

on the board pretty sure can you set DCE/DTE by the port may explain why one works and one doesn't as it would swap the TX/RX around.

 

[HollTel]

Yes you are correct that the board allows to pin out Terminal vs Modem (DTE/DCE). I have confirmed that this is set correctly as well as used a null modem just in case. I have also confirmed that the physical connection is working by blowing away the TTY-1 and replacing it with SCH/BUG users and it worked fine. Its only when I program BGD/PMS users to it that it will not output or input anything.

Thank you.

 

[gbtac3]

Print out your entire config in LD 22. Look under "PARM"?, (going off the top of my head), and look for PMSI. There are different settings and you may need to change those. I believe this protocol is async, so you may not be able to view it straight off the port. In LD 37 you can enl MSGI/ENL MSGO and it will display what is happening on the PMSI port defined.

 

[MossEng]

Here's a PMSI example:

PMSI
MANU PMS1
PMCR 20
PORT 1
XTMR 0
PTMR 0
NDIS 20
OCAC NO
MTRO MR
SBA_ADM_INS 000
SBA_USER 512

Is it set to Port 1 or still port 5?