Enabling a PTY port

[jmcooney]

How can you enable a PTY port that was disabled by entering the incorrect password. I can not go through signaling server as TTY ports 14 and 15 (really PTY ports) show as disabled.

I accessed the PBX and attempted to enable in LD 37 with
.ENL TTY 14, but receive an error message indicating this command does not work for PTY ports.

BTW - what is the default "unlock" time for these ports?

 

[srmega41]

PTY ports are always "disabled", until they are accessed and active. I really do not know why Nortel does this, but that is the case.

As for the "unlock" part, it is the same as normal TTY ports, as defined in the PWD gateopener. Default is 3 times and 60 minutes, with an INIT to reset locked out ports set to YES.

Hope this helps,

Scott M.

 

[johnpoole]

even a physical tty, the enl tty x in 37 will not rls that locked out port. the params for the time lock out is ld 22 prt pwd and ld 17 to change. you will need pdw2 to make changes to the pwd command or even to print them

john poole
bellsouth business
columbia,sc

 

[srmega41]

Excellent point. Thanks for connecting the questions together. I sort of did a two part answer, not the best approach.

Thnaks for covering my back,

Scott M.

 

[johnpoole]

sometimes when i;m bored i just like to type, usually i see that you answered and don't even read the question...

john poole
bellsouth business
columbia,sc

 

[jmcooney]

I am not sure if this question should be asked within this thread or if I should start a new one. Please advise what you think.

After waiting for the PTY port to become available, I started paying a little more attention to what was happening. My normal way of accessing the PBX is via http to the Signalling Server. Once successfully logged into the Signalling Server, I use a pass through to the PBX (via a Virtual Terminal Session off the Tools menu). I have never experienced any trouble accessing the system when using the original username/passwords for PWD1 and PWD2. Yesterday I added an LAPW. This is when the fun began.

I have no problems using the LAPW username/password to login to the signalling server, but as soon as I try to login with the same credentials (yes, I have to log in twice), I get an ovl428. If I look at the PC connected to the SDI port, I also see an ovl400 14. Initially I tried a few times and was really locked out. Unable to login via Sig Server until the port was re-enabled. I then tried to use the LAPW credentials through the sig server and via the pass through. Although it fails to actually log in to the PBX, I am able to use the original credentials for PWD1 and PWD2 to login (so the port is not actually disabled even though I see an ovl400 14). After logging out of either (while remaining in the virtual terminal session), I am able to login with the LAPW credentials.

Any ideas why this would be the case? It doesn't help to have a LAPW if the person is unable to use it without having a successful login with credentials we are trying to limit.

 

[johnpoole]

post your pwd data, change the names and passwords but let us look at that to see if we can spot a problem,, but it sounds more like a patch issue, i usually apply the rule, if you can't program one to do that on purpose, then maybe it's a patch... has work 99 percent of the time... imo a new post (or one with stars) gets way more attention. there is no hard rule as to changing the issue in your own post. i don't like to see another user hijack a post... and welcome to the forum

john poole
bellsouth business
columbia,sc

 

[Firebird Scrambler]

What software version are you on?. Is it 4.5?. 4.5 is now case senstive. However if your system was upgraded to 4.5 from a older release, then any existing passwords will remain in either upper or lower case. This will change when a password change request is carried out to whatever "pASsWOrd" is typed in!.
Be careful!. It catches quite a few people out.

All the best

Firebird Scrambler
Meridian Programmer in the UK

http://mysite.wanadoo-members.co.uk/firebird_scrambler

 

[jmcooney]

As two people have asked the same question about which software version I am on (Firebird and a colleague of mine), this is what I pulled from the PBX.

REQ iss

VERSION 3221
RELEASE 4
ISSUE 00 T +


As per John's request, below is my "modified" PWD DATA:
>ld 22
PT2000

REQ prt
TYPE pwd
PWD2

PWD
FLTH 3
LOCK 30
AUDT NO
INIT NO
LNAME_OPTION YES
PWD1 A22456
LOGIN_NAME ADMIN1
PWD2 22456
LOGIN_NAME ADMIN2

PW01 2OLYMPICS
PWTP OVLY
LOGIN_NAME AMXWDC
OVLA 020 081 084 085 095
CUST 00 TEN
HOST NO
MAT NO
OPT PSCA CFPA LLCD PROD LOSD FORCD MOND KCCA

NOTE: although my passwords show in upper case, I regularly use lower case (I do not believe in my version the case matters).

I am not sure what it will show --- as the really strange part is the username/password combo works to get through the sig server and then again if I use it after using one of the original passwords.

I am open to any ideas

BTW - thanks for the dialog so far, I hope I can get to the bottom of this.

 

[srmega41]

Change PW01:

MAT = YES

Scott M.

 

[jmcooney]

Not sure I figured out why I should be doing this, but I did and it did not seem to change the behavior.

The parameters now look like this:

PW01 2OLYMPICS
PWTP OVLY
LOGIN_NAME AMXWDC
OVLA 020 081 084 085 095
CUST 00 TEN
HOST NO
MAT YES
MAT_READ_ONLY NO
OPT PSCA CFPA LLCD PROD LOSD FORCD MOND KCCA

My experience is still ....
I have no problems using the LAPW username/password to login to the signalling server, but as soon as I try to login to the virtual terminal session with the same credentials, I get an ovl428. However, I am able to use the original credentials for PWD2 to login (sometimes PWD1, but not always). After logging out of either (while remaining in the virtual terminal session), I am able to login with the LAPW credentials.

 

[Firebird Scrambler]

I think that you may need to change the "CUST" from 00 & TEN to "ALL". See if that improves the logging in. I find that I also have to log in twice when using the Terminal session.
I've just got used to doing it now & anyway I use the Telnet access via the Sig Server on the switch. I only have 1/2 hour time limit, but it's usually enought time for me.

All the best

Firebird Scrambler
Meridian Programmer in the UK

http://mysite.wanadoo-members.co.uk/firebird_scrambler

 

[jmcooney]

I made the change suggested by Firebird, but still a no go:

PW01 2OLYMPICS
PWTP OVLY
LOGIN_NAME AMXWDC
OVLA 020 081 084 085 095
CUST ALL
HOST NO
MAT YES
MAT_READ_ONLY NO
OPT PSCA CFPA LLCD PROD LOSD FORCD MOND KCCA

The LAPW username/password works fine to login to the signalling server via http, but as soon as I try to login to the virtual terminal session (from the Tools sub menu)with the same credentials, I get an ovl428. At this point I am able to use the original credentials for PWD2 to login. After logging out, but while remaining in the virtual terminal session, I am able to login with the LAPW credentials.

Firebird, could you clarify two things for me:
- where/how do you log in twice (is it the same as I have explained -- via http and then again after you launch the virtual terminal session once in the sig server)?
- how do you "use the Telnet access via the Sig Server on the switch"? why is it limited to 30 minutes? once the limit is reached, can you simply telnet back in?

 

[dlesap]

When logged in SS with Telnet, you can use "cslogin " command to log in CS, but that session is limited to 30 minutes, even if you are typing.

For the access to CS with "Virtual Session" in SS, i get the same problem few time and don't understand why. Problem appears in rls 4.00 and 4.5

I really suggest not to use Virtual Session in SS to connect to CS. I get 2 times a SS freezing..!! Need to restart it manually...

Rlogin session is really more safe.

 

[Firebird Scrambler]

When logged in SS with Telnet, you can use name = "admin" & password = "cslogin" for V03.00 & V04.00. For V04.50, you will need to use the Call Server's PWD1 name & password, but that session as stated above will be limited to 30 minutes only.


All the best

Firebird Scrambler
Meridian Programmer in the UK

http://mysite.wanadoo-members.co.uk/firebird_scrambler

 

[jmcooney]

I am not sur I am catching on to the method of using telnet to get to the SS. If I use a DOS telnet and go to the ip address of the SS, I am prompted for login and after typing "admin" I am prompted for password where I enter "cslogin" --- I then get Goodbye and another chance to enter a login.

If I enter the PWD1 login and password, it appears to accept this, but I get to "oam>" and have no idea what to do --- please note, when I get to this point there are a ton of system messages (mostly to do with gatekeeper).

Sorry if I am not catching on --- I really need to find a way to let someone access the PBX without giving them the PWD1 or PWD2 info --- I chose LAPW because I also want to limit their access once they authenticate.

Would my CS1000 maintenance vendor be able to help? I usually find this site a bit more help than they are.

 

[dlesap]

Entering in Telnet on SS with a dos windows is OK. Enter login and password level1 of the CS :
Login : admin1
Pass : xxxxx
Level1 pwd is a MUST when systems are synchronized.

Then oam> is displayed. Enter "cslogin" to access CS. Then standard login and pwd applies.

If you don't want to give admin1 level pwd to techs, give them a Rlogin session with PuTTy, for example. Enter additional login info : -l CPSID1000
Then LAPW pwd can applied

 

[Firebird Scrambler]

Here is part of my procomm script that I use to log in with.. I've made some changes to it!.

; 15th July 2005
; NOTE!
; This program will only work with a WINDOWS version of Procomm Plus.
; The " ; " denotes that the data on the program file line is ignored,
; when the script is run.


proc main
PAUSE 2
; waitfor "login:"
PAUSE 2
transmit "admin1^M"
; waitfor "password:"
PAUSE 4
transmit "A22456^M"
; waitfor "oam>"
PAUSE 4
transmit "cslogin^M"
; waitfor ">"
PAUSE 4
transmit "^M"
; waitfor ">"
transmit "LOGI admin1^M"
; waitfor "PASS?"
transmit "A22456^M"
endproc

All the best

Firebird Scrambler
Meridian Programmer in the UK

http://mysite.wanadoo-members.co.uk/firebird_scrambler

 

[jmcooney]

I do not have a programmer's mindset so you guys are probably giving me great advice that I somehow am not understanding.

Based on dlesap's latest comment, I tried a couple of rlogin attempts to the SS, but could not figure out what options I would need to use to provide the username/password that would allow me to get to a prompt where LAPW would be accepted (not sure if I need to script something so the PWD1 info would not be distinguishable, I tried to load firebird's sample script in, but I am no programmer :-(

At this point, maybe I should give up --- not sure it should be this difficult. I have provided NetOp access to the pc that is physically connected to one of the SDI ports so I can provide access. I was hoping I could provide access through the SS as it has been a successful method for me for over a year (I simply never tried LAPW through it before).

Thanks for your help. I welcome any further info, but if you have already given the old college try, I am ok with it.

rlogin -l ??????

 

[Firebird Scrambler]

Along with the "Putty" program, is another one called SM Telnet. As long as you have the Call Server's IP address & a "PTY" port, then you can use the RLogin protocal to access the system.
As listed on my last reply. When you have a Sig Server, you can use any Telnet program instead of a "Rlogin" one to talk to your system using the script example as listed on my last message, subject to a 30 minute time limit.

Your question was about restricting access & not using the PWD1 name / password. Have you checked your systems software version in LD 22 "ISS"?. This would help others & me in deciding what other help we can give you.

All the best

Firebird Scrambler
Meridian Programmer in the UK

http://mysite.wanadoo-members.co.uk/firebird_scrambler