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

 

[Firebird Scrambler]

Go into LD 37 and key in STAT TTY to see all the status of them.

Go into LD 22 and key in

REQ. PRT
TYPE CFN

To print out all the Configuration

 

[HollTel]

Thank you, here is what I'm seeing.... I don't see anything wrong though?

>ld 37
IOD000
.stat tty

TTY 0 : ENBL DES: XSM
TTY 1 : ENBL DES: NEWPMSPORT
TTY 2 : ENBL DES: PBXTTY
TTY 3 : ENBL DES: ACDPRT
TTY 4 : ENBL DES: HOMISCO
TTY 5 : ENBL DES: PMSPORT
TTY 6 : ENBL DES: UNUSED
TTY 7 : ENBL DES: CoreModem
TTY 9 : ENBL DES: CoreTerminal
TTY 10 : ENBL
TTY 11 : ENBL DES: hms
TTY 12 : DSBL DES: IPtty2
TTY 13 : DSBL DES: IPTTY3


REQ prt
TYPE cfn

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 PBXHOLLTEL
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
PARM
LPIB 96
HPIB 100
500B 160
NCR 500
MGCR NULL
NCPU 2
CFWS NO
PCML MU
ALRM YES
ERRM ERR XBUG AUD
DTRB 100
TMRK 128
FCDR OLD
PCDR YES
TPO NO
TSO NO
CLID NO
DUR5 NO
MLDN YES
MARP YES
IPIE NO
FRPT NEFR
DCUS NULL
MSCL 30
PMSI
MANU PMS1
PMCR 100
PORT 5
XTMR 0
PTMR 0
NDIS 20
OCAC NO
MTRO MR
SBA_ADM_INS 002
SBA_USER 050
BCAP SPEECH
IDLE_SET_DISPLAY Hotel
ICON YES
MSEC OFF
DLAC YES
CEQU
SUPL 004 N100 V144 V156
SUPC
SUPF
XCT 000 016
CONF * 001 * 017

DLOP NUM DCH FRM TMDI LCMT YALM TRSH
TRK 011 24 ESF NO B8S FDL 00
018 24 ESF NO B8S FDL 00
PRI 010 24 ESF NO B8S FDL 00
MISP
EXT0 3PE
CNI 009 000 000
EXT1 3PE
CNI 009 000 000
MCFN 509 MB
OVLY
SID 27
BKGD 044
FR44 1
PBXH 04
TODR 03
DROL 034 036 037 038 060 135 137
MID_SCPU NO
MULTI_USER ON
ATRN
CODE 0
SOLR 12
ROLR +45.00
AOLR +45.00
TOLR -45.00
AGCD NO
VOLR NO
HRLR +42.00
HTLR -44.00
ESA
LIS NONE
DYNAMIC_ELIN_TIMEOUT 180
DYNAMIC_ELIN_REUSE YES

 

[Firebird Scrambler]

Thanks for the quick response today.
The PTY terminals will always show as disabled.

You have in LD 37, 13 TTY ports. You also have two D Channels configured.

That makes 15 ports in use. Add the History ADAN and that makes 16.

I recall many years ago getting issues with a TTY failing to work. After much grief, I stumbled across that I also had 16 ADAN's configured.

To confirm my thoughts, I deleted the History ADAN and the "faulty" TTY started working.

The History ADAN can easily be put back in and the size set to the maximum of 65535 (I think?)

The ADAN maximum number of 16 allowed is very historic from the days of very old software.

 

[gbtac3]

In CFN, PMSI is still set to 5.

PMSI
MANU PMS1
PMCR 100
PORT 5
XTMR 0
PTMR 0
NDIS 20

 

[psychotech]

as firebird says , you have excess ADAN ports allowed in config
as TTY 6 is shown as unused try deleting that ..

or the new one you have created may be on a duff qsdi port
delete that one and reuse tty 6 as pms

k

 

[HollTel]

Thank you all... I'm going to try deleting TTY 5 and TTY 6 since one is UNUSED and 5 is the OLD PMS.

Just curious will that bump PSMI to change in the CFN file or do I need to do that manually?

Or should I just delete "all" the PMS TTY's and build one from scratch after they are all removed to update the PSMI to show on TTY 1

 

[HollTel]

In CFN, PMSI is still set to 5.

PMSI
MANU PMS1
PMCR 100
PORT 5
XTMR 0
PTMR 0
NDIS 20

Is there a simple way to update this to PORT 1... Thank you.

 

[Firebird Scrambler]

I would just delete TTY 13 as that is the second PTY on port 2.

 

[HollTel]

I would just delete TTY 13 as that is the second PTY on port 2.

FS,

You're going to have to forgive me perhaps I'm not understanding this the way that I should. I would like the PMS to reside on TTY 1 which has a DB9 (RS232) connection off the back of a NT8D41AA card.

I have deleted the TTY 5 and TTY 6 so that I have less programmed TTY's in the system so that should clear up the TTY 1 to start working again? ( I believe )

I think that the only issue that I may have left is the one that "GBTAC3" pointed out which is that in the printout of the CFN the PMS was listed under PSMI as PORT 5. My thought was that PORT 5 was because the PMS used to reside on TTY 5, but that may be just a happy coincidence.

So I believe that the only thing that I still need to do is change the PORT on the PMSI to "port 1" ??? ( Sorry if I've misinterpreted all this )

Unfortunately I don't know how to make the change to the PSMI. I looked for several CHG options in LD17 but didn't see any that I thought appropriate.

I appreciate your patience and help.

 

[gbtac3]

Ld 17
REQ: CHG
TYYPE: PARM
...
PMSI: Yes
...
PORT 1 (enter the port number here)

then enter through until you get the UDATA/PDATA.

LD 22
PRT
PARM (to check)

 

[Firebird Scrambler]

In LD 17, try..

REQ. CHG
TYPE PARM
Press enter until you get to PMSI
Key in YES and when you see "port" to enter in "1"
Press enter until you get to REQ.

I've done the above from memory, it might be slightly wrong.

 

[psychotech]

hiya
this doc should be a good guide for you

 

[HollTel]

hiya
this doc should be a good guide for you

Thank you this is a great document to keep for my records!

 

[HollTel]

Thank you to GBTAC3 and FS for the information. Those commands worked like a charm. I will be onsite today and able to test the physical connection to see if all is good. I will let you know.

 

[HollTel]

I hope everyone had a great weekend! So I went to the site and looked at everything and I'm defiantly missing something. Here is what I found, (Then you get to tell me how much I've forgotten over the years.)

I worked with the engineer at the company that provides the PMS to the hotel. He indicated that he was seeing the information come back to him as a loopback. I verified that his connection was sound and also placed a serial cable from my PC to the PBX and found the same state. In then removed the serial cable from the PBX and crossed pins 2 and 3 and found that it acted just like when connected to the PBX ( loopback )

I spent the weekend looking through all the documentation that I could find and could not determine why the PBX is showing loopback on the TTY-1 port.

any ideas? ( I do sincerely appreciate it )

Just so you can see where we are Ive added the PRT / CFN information again.

My original wish was to allow the PMS to connect to the DB9 (TTY-1) on the back of the CS1000 and transfer information back and forth

>ld 22

REQ prt
TYPE cfn

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 PMSPORT
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 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
PARM
LPIB 96
HPIB 100
500B 160
NCR 500
MGCR NULL
NCPU 2
CFWS NO
PCML MU
ALRM YES
ERRM ERR XBUG AUD
DTRB 100
TMRK 128
FCDR OLD
PCDR YES
TPO NO
TSO NO
CLID NO
DUR5 NO
MLDN YES
MARP YES
IPIE NO
FRPT NEFR
DCUS NULL
MSCL 30
PMSI
MANU PMS1
PMCR 100
PORT 1
XTMR 0
PTMR 0
NDIS 20
OCAC NO
MTRO MR
SBA_ADM_INS 002
SBA_USER 050
BCAP SPEECH
IDLE_SET_DISPLAY Sheraton Hotel
ICON YES
MSEC OFF
DLAC YES
CEQU
SUPL 004 N100 V144 V156
SUPC
SUPF
XCT 000 016
CONF * 001 * 017

DLOP NUM DCH FRM TMDI LCMT YALM TRSH
TRK 011 24 ESF NO B8S FDL 00
018 24 ESF NO B8S FDL 00
PRI 010 24 ESF NO B8S FDL 00
MISP
EXT0 3PE
CNI 009 000 000
EXT1 3PE
CNI 009 000 000
MCFN 509 MB
OVLY
SID 27
BKGD 044
FR44 1
PBXH 04
TODR 03
DROL 034 036 037 038 060 135 137
MID_SCPU NO
MULTI_USER ON
ATRN
CODE 0
SOLR 12
ROLR +45.00
AOLR +45.00
TOLR -45.00
AGCD NO
VOLR NO
HRLR +42.00
HTLR -44.00
ESA
LIS NONE
DYNAMIC_ELIN_TIMEOUT 180
DYNAMIC_ELIN_REUSE YES

 

[Firebird Scrambler]

I've usually found that a null modem adapter was often needed when connecting TTY applications.

Have you checked the RS232 pin outs on the TTY you are using against the original TTY that was used.

I've known that some RS232 ports had more pins in use than others.

 

[HollTel]

So I connected my serial cable on my laptop to the back of the PBX on the TTY I usually use to talk to the PBX (TTY-2) and it DID NOT WORK...

Then I connected the serial cable on my laptop to the cable that is used by the onsite PBX and it worked like a charm. The cable that is being used is a (NT8D93AW) - Don't know the wiring for this particular cable yet.

This seems to tell me that the pinout coming out of the TTY on the PBX is not normal. Im looking for what that pinout would be but have not found it as of this writing. The board that Im using is ( NT8D41AA Dual Port SDI Paddle Board ) https://pbxbook.com/meridian/hardware/NT8D41AA.html

If I find it I will post the results back here. If you having anything by all means post.

 

[HollTel]

So I did some more testing and connected the onsite PC with the correct cable to the TTY-2 port, this is the usual port I access the PBX through and it works just as expected.

I then took that same cable and connected it to the TTY-1 port that the PMS is supposed to be on and I could not get anything to come out of it. I of course made sure that I was at the right settings on PuTTy (8N1) @ 9600. ( These are all set on the paddle board not in the software. )

Im defiantly missing something in the programming of the PMS TTY it's just not responding to anything that Im doing.

Any thoughts on the programming side of this?

 

[Firebird Scrambler]

Although you have checked the paddle board settings, have you tried a different baud rate?.
I'm aware that the Option 11c SDI cards had a tendency to default to 1200 baud.

The only other thing I would try is a null modem adapter that sits between the PBX TTY port and the cable going to the PMS equipment as this swaps over pins 2 and 3 as was previously mentioned.

I still have my old "clever" cable that allows me to toggle the pinouts.

I also use a useful tool called ZOC. I prefer it to PuTTY as its more versatile and works fine in evaluation mode.