datadump

are you using TTY's(serial) or PTY's (IP)??

John_In_Dakota

Check the user name and password that you use to login. Look at your TTY that you have connected when OTM tries to login. If the login and or password is incorrect you will get an "OVL428". That is telling you the user name/password is incorrect.

__________________
We need change in this country...

M1tech

If you are running PBX Software under Relase 4.5 and have applied a SU to OTM SU3 or SU4 then you will have an issue logging in.

Below is how to correct this issue depending on what your are using for combination of OTM and PBX Software.

OTM 2.20.78 +SU3 causes login issues for releases less than 4.5

ANALYSIS
A new password complexity feature was introduced in CS 1000 Release 4.5. SU3 in OTM 2.2 has a fix that supports this new feature. Prior to Release 4.5, all the above mentioned applications of OTM/TM when connect to the PBX, automatically turned login name and password to upper case. This automation was removed as part of password complexity feature support introduced in SU3. Now, if the above mentioned applications of OTM/TM need to connect to the CS 1000 in releases prior to 4.5 (eg. release 4.0, 3.0, 25.40 etc), then the user has to enter the login name and password in upper case so that the connectivity can be established. If the login name and password are not in upper case connectivity to PBX fails. When the connection fails, the user will see a screen like this indicating an incorrect login/password:

RECOMMENDATIONS
The user needs to manually enter the login name and password in upper case if they need to use the applications listed below to be able to connect to the CS 1000 in Releases 4.0 and earlier.

For CS 1000 Release 4.5 and above, the password must be entered exactly as it was set in the PBX.

1. System Terminal.
2. DBA.
3. Inventory.
4. Maintenance Windows (Core Equipment) and Web Maintenance Pages.

The information in this bulletin is applicable to OTM 2.2 + SU 3/4, TM 3.0

rajblr1

I logged in with the UPPER case and it gives the same login failed (session failed)message.

with the same user name and password i am able to login in to the 81c system in the tty 2 port.

whenever i try to login to OTM ,In the Tty port 2 screen it gives like

''message MAT 003 User ,the user name and the IP''

MAT003 error meassge is actually it says the login is denied too many sessions. But i cannot see any other session is running i am first login user ,no other session is established.

the tty port which OTM is using is tty 15 (which is the pty port)

Panchanka

I believe the OTM NTPs specify that you must have 2 PTYs. Do you have 2 TTYs programmed as PTYs or just one?
Also, enter into LD 22
REQ: prt
TYPE: PWD
PWD2:
and make sure your login has
MAT: YES
Read Only: NO

Keep in mind that blank usernames are not supported, make sure you have a name after LOGI. Also, you may require the multi login package.

Post back on what you have in your patch viewer. SU4a and SU4b are the most current for OTM 2.2.
One more thing, close down everything except the OTM Navigator, right click the PBX for the site that you are trying to connect to ->properties -> customer -> properties. Make sure the right username and password is in there (try with and without caps).

If still not working, close that OTM Navigator -> Security ->User Groups -> Open whatever group you are in (probably administrators) -> Sites -> select site -> click on the system (PBX) Make sure the right username and password is in there too (try with and without caps).

Did any of this help?

rajblr1

IN LD 22 it is same as below that is

MAT yes
read only No

I given the same use name and passw0rd in the site ,customer,properties

and in the security also (it is administrator) in the site option i have given the same user name and password

i have attched the scrennshot of the latest patch

we have created one tty as pty (that is tty 15)


and in ld 37
stat tty

it shows tty 15 disabled

and it is not taking enable command on pseudo tty (pty ) port

Attached Files

otmpatch.doc (55.0 KB, 16 views)