MAT Configuration

[mjpearson]

After my vendor left, I lost connectivity using MAT. I think I've narrowed the problem down to a security problem. I think the vendor may have wiped out the MAT passwords/settings on the 11c.

I used LD 22 print the settings but I'm very confused about the security stuff. My LD 22 looks something like this:

**********
PWD
FLTH 3
LOCK 30
AUDT NO
INIT NO
PWD1 ____
PWD2 ____

PW00 _________
PWTP OVLY
OVLA 002 - 0048
CUST ALL
HOST NO
MAT NO
OPT PSCD CFPD LLCD PROD LOSD FORCD MOND
**********

Is it a matter of changing MAT to YES -or- do I need to setup some sort of LAPW? Assuming I have to setup LAPW, is there a good reference as the 11c book is very confusing about this subject. Assuming I don't have to use LAPW, do I set my MAT password to the PW00 password?


mike

 

[thetinman]

you need to have a user name and passsword set up for mat
look in admin book ld 17, it will show you how to set up user name and password

 

[Billy]

default is id: admin pw: admin

 

[mjpearson]

At one time, the MAT system worked and I didn't need to use account names for PW1 nor PW2. In my present configuration, is the PW00 the account for MAT? Is it just a matter of changing the password; enabling the MAT and the HOST attrributes?

Or do I have to enable a brand new name and password for MAT?

mike

 

[Reusser]

it may work without a new name and password but it may create problems. Recommendation is a LAPW just for MAT

LD 17
REQ: chg
Type: PWD
LAPW: --> enter the LAPW number 1-99
PW: --> enter the password to use for MAT
Login_Name: --> enter the login name to use for Mat
OVLA: all
Cust: all
MAT: Yes
MAT_Read_Only: No

Now enter the login name and password under the Customer Tab and give it a try.

 

[mjpearson]

Thanks,

I'm still a little confused but some of it is starting to make sense. Each time I read the book, I get more confused.

I was under the impression that once you setup LAPW, ALL accounts had to have a LOGIN_NAME. Thus, I'd have to setup a LOGIN_NAME for PW1 and PW2 as well as the MAT account.

So, a quick double check.....you're telling that PW1 and PW2 can remain as-is (without LOGIN_NAME) and I can set up an indepedendent MAT account with a LOGIN_NAME. Correct?


mike

 

[Reusser]

You can have lapw without login name but you should turn it on first

Ld 17
Req: chg
Type: pwd
LName_Option: YES

this will set your pw1 name to admin1 and your pw2 name to admin2. You can then go in and change them if you like.

 

[acewarlock]

What do you mean (lost connectivity)?

Is it a direct connect or a dialup?

How did you lose it, did you reboot the PC or LOGO of MAT?

You should be able to get a responce from the PBX when you hit the enter key.

 

[mjpearson]

The original Nortel installation was ugly. The vendor just didn't have their "stuff" together. Subsequent "fixes" tended to make things worse but at least MAT worked via with dial-up and I could clean up some things. Not the most ideal situation but it gave me something to use while I learned about the command line stuff.

After about 6 months, I didn't using dial-up so, I decided to setup the Ethernet. With a lot of help from documents and postings on the net, I figured out how to do it and to my amazement, it worked.

Then about 6 months later, the vendor arrived to do some PM work and install the latest versions and upgrades. About a week later, I tried to use it and it didn't work. MAT tried very hard but the switch just wouldn't let me in to the system now matter what I tried. The vendor has been playing dumb (or at least I think they're playing). I finally figure out that iw as related to the security stuff. Thus all my questions.

I'm not excited about MAT but I need to continue to use it for two basic reasons.....it is the only way to refresh the CORPORATE DIRECTORY and I need to recover my investment. There is no way I can go to my management and ask them for money to upgrade to Optivity.



mike

 

[Reusser]

Make sure you have at lease one recommend two PTY ports

ld 22
prt
adan

 

[unkalary]

Reusser is correct about the PTY ports. Print the ADAN in LD 22 and look for type as PTY. If none is found then add a new tty in LD 17 and put type as PTY with port 0 and user as SCH MTC.

 

[mjpearson]

That is one of the more interesting parts to the puzzle. I TTY 13 set as PTY. Before I saw the security problems, I would change the port from SCH to MTC/SCH/BUG. I'd attempt to use MAT without success and then I'd go back to the 11c and find that the port had reverted back to SCH only.

This Nortel stuff is very strange. Given it's population, maturity and how cheap memory and tools available, you'd think that Nortel would have developed a more user friendly interface to the the system. The basic command line stuff stinks and MAT is a poor substitute. Too bad the system is closed to the outside world. Look at the Unix world; It's open and people are advancing it every day.



mike

 

[Avaya911PLM]

There were instances where a patch was required because MAT did not drop the PTY session cleanly.

--
Fletch

http://PBXTech.Net

 

[vztech]

Stupid ? but you should be able to ping the PBX. if that's ok look under site info (customers) then properties window and make sure the password is the same as PBX.

good luck

 

[davebopp]

Not exactly a "fix" - drop MAT (its being phased out anyway)and go with PhoneMaster by PhoneWare. Its much cheaper and far easier to use - its all GUI.

Good luck with MAT!

 

[mjpearson]

A million things since original posting and all too pressing to ignore and on top of that, the PBX continues to work despite no MAT software.

Over the holiday, I took the plung (I also finally got up enough courage to make the changes - this pbx stuff scares me). Anyway, I'm up and running again.

I used the

- LD 17 to reconfigure PW00
- I enabled MAT and now I can use it again however, I've become accustomed to using the command line at the dumb terminal.

Well with MAT now I can update my Corporate Directory.

Some day we'll get enough budget money to consider replacing MAT until then, it's the only thing I've got.


Thanks to all

mike