sounds like the MWI service is not defined in the VMSC.

Has it ever worked?

Ken Means

www.tel-is.com
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

Hi:
I have setup in VMSC the MWI with the MAS and setup a port-group of 10 channels for MWI. The service MMMWI is up.I do like the manual.
I need a special extension o mailbox to signaling to CM?
Thanks

If the MWI data base is empty then the system does not think any users are able to use the service. Are you sure that the mailboxes are in a class of aervice that has MWI allowed?

Ken Means

www.tel-is.com
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

Do you only have one MAS on the system?

Ken Means

www.tel-is.com
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

yes, i have permission in cos(cos00) All mailbox have cos00.
I have one Mas Only, and all services enables.I have too a trusted served in MSS-H to MWI, name VVSTS (like avaya manual), wich password and defalut community 1. This trusted server have private Ip Addres MAS.
Thanks

Has it ever worked or is this a new install

Ken Means

www.tel-is.com
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

it´s a new install.
thanks

Its hard to say as it can be so many things. You say all of the serices are running on mas1.

What are you getting in the app log?

Ken Means

www.tel-is.com
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

Hi:
In the applications log i have gv_mwiserver startup.
I need a NCA TSC to signalig 8700 MWI?
Thanks

Have you done all of the followinf steps? and what config note are you using?

http://support.avaya.com/elmodocs2/Octel/mm_r2_0/cn88014.pdf

5.0 SWITCH CONFIGURATION FOR IP INTEGRATION
The following tasks must be completed in the following order when
programming the PBX to integrate. PBX programming is intended for
certified PBX technicians/engineers.
• Verify customer option for H.323/QSIG trunking
• Administer QSIG TSC and Extension Length
• Assign Local Node Number
• Administer C-LAN and IP Media Processor circuit packs (G3
and S8500/S8700 only)
• Assign IP node names and IP addresses to C-LAN, IP Media
Processor (G3 and S8500/S8700 only)
• Define IP interfaces (G3 and S8500/S8700 only)
• Administer IP Network Regions (Skip this step if default QOS
is used)
• Administer Codec Type (Skip this step if default QOS is used)
• Add Message Server to the node names
• Create H.323 signaling group
• Create a new trunk group
• Modify the signaling group to add trunk group
• Create Route Pattern
• Modify AAR Analysis Table
• Modify AAR Digit Conversion Table
• Modify ARS Digit Conversion Table
• Define ISDN Numbering Format
• Create Coverage Path
• Create Hunt Group (Pilot Number)

Ken Means

www.tel-is.com
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

Hi Ken:
It´s the same manual version.
Thanks

You mean you used the same config note?

If you stop the MWI service and then start it do you see anything in the app log that shows why it is stopping or does it show a number of users using MWI?

Ken Means

www.tel-is.com
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

Hi Ken:
When i stop MWI service i have this events:

Event Type:    Information
Event Source:    gv_mwiserver
Event Category:    Shutdown
Event ID:    1001
Date:        06/02/2007
Time:        8:36:39
User:        NT AUTHORITY\SYSTEM
Computer:    MYMAS1
Description:
The Message Waiting Indicator supervisor manager has shutdown.

Event Type:    Information
Event Source:    gv_mwiserver
Event Category:    Shutdown
Event ID:    1001
Date:        06/02/2007
Time:        8:36:39
User:        NT AUTHORITY\SYSTEM
Computer:    MYMAS1
Description:
The Message Waiting Indicator data manager has shutdown.

Event Type:    Information
Event Source:    gv_mwiserver
Event Category:    Shutdown
Event ID:    1001
Date:        06/02/2007
Time:        8:36:39
User:        NT AUTHORITY\SYSTEM
Computer:    MYMAS1
Description:
The Message Waiting Indicator config manager has shutdown.

Event Type:    Warning
Event Source:    gv_mwiserver
Event Category:    Configuration
Event ID:    103
Date:        06/02/2007
Time:        8:36:39
User:        NT AUTHORITY\SYSTEM
Computer:    MYMAS1
Description:
The Message Waiting Indicator service could not contact a voice server to read its configuration data.  
The service will retry every 60 seconds until the connection is re-established.
When the connection is re-established, an information event will be generated. (HR=0x80010109)

Event Type:    Information
Event Source:    gv_mwiserver
Event Category:    Shutdown
Event ID:    101
Date:        06/02/2007
Time:        8:36:39
User:        NT AUTHORITY\SYSTEM
Computer:    MYMAS1
Description:
The Message Waiting Indicator service has shutdown.



When i start MWI services:

Event Type:    Warning
Event Source:    gv_mwiserver
Event Category:    Configuration
Event ID:    164
Date:        06/02/2007
Time:        8:40:58
User:        NT AUTHORITY\SYSTEM
Computer:    MYMAS1
Description:
The Message Waiting Indicator has failed to locate an on-line voice server for service location.
All processing will be halted while continuing to search for an on-line voice server.

Event Type:    Information
Event Source:    gv_mwiserver
Event Category:    Configuration
Event ID:    173
Date:        06/02/2007
Time:        8:40:58
User:        NT AUTHORITY\SYSTEM
Computer:    MYMAS1
Description:
The Message Waiting Indicator has established a connection to the mailbox monitor server MYMAS1.

On-line mailbox monitor server(s): 1

Event Type:    Information
Event Source:    gv_mwiserver
Event Category:    Startup
Event ID:    100
Date:        06/02/2007
Time:        8:40:58
User:        NT AUTHORITY\SYSTEM
Computer:    MYMAS1
Description:
The Message Waiting Indicator service has started.

Event Type:    Information
Event Source:    gv_mwiserver
Event Category:    Startup
Event ID:    1000
Date:        06/02/2007
Time:        8:40:58
User:        NT AUTHORITY\SYSTEM
Computer:    MYMAS1
Description:
The Message Waiting Indicator supervisor manager has started.

Event Type:    Information
Event Source:    gv_mwiserver
Event Category:    Startup
Event ID:    1000
Date:        06/02/2007
Time:        8:40:58
User:        NT AUTHORITY\SYSTEM
Computer:    MYMAS1
Description:
The Message Waiting Indicator data manager has started.

Event Type:    Warning
Event Source:    gv_mwiserver
Event Category:    Configuration
Event ID:    161
Date:        06/02/2007
Time:        8:40:58
User:        NT AUTHORITY\SYSTEM
Computer:    MYMAS1
Description:
The Message Waiting Indicator could not establish a connection to the voice server MYMAS1. (HR=0x80004002)

On-line voice server(s): 0

Event Type:    Information
Event Source:    gv_mwiserver
Event Category:    General
Event ID:    1008
Date:        06/02/2007
Time:        8:40:58
User:        NT AUTHORITY\SYSTEM
Computer:    MYMAS1
Description:
The Message Waiting Indicator data manager has paused queue processing.

Event Type:    Information
Event Source:    gv_mwiserver
Event Category:    Startup
Event ID:    1000
Date:        06/02/2007
Time:        8:40:58
User:        NT AUTHORITY\SYSTEM
Computer:    MYMAS1
Description:
The Message Waiting Indicator config manager has started.

Event Type:    Information
Event Source:    MM Dump Helper
Event Category:    General
Event ID:    101
Date:        06/02/2007
Time:        8:40:58
User:        NT AUTHORITY\SYSTEM
Computer:    MYMAS1
Description:
Application: C:\Program Files\Avaya Modular Messaging\MWIServer\mwiserver.exe
Loaded system helper library: C:\Program Files\Avaya Modular Messaging\Common\dbghelp.dll

The first time i was the notes (Configurations Notes 88014-Version (09/06),last week  i obtain(configurations Notes 88014-version AB 02/07),the same you send me.

Thaks

Is the trusted server setup with the priv ip on the MSS

Ken Means

www.tel-is.com
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

Hi:
Yes i have created de trusted server like the manual:
Name : WSTS
Ip: 192.168.1.250 (private ip address MAS)
Servece name: MWI Server
Default community : 1
Special type: MWI Server

I have the same pass in all Trusted Server. In the Mas Avaya Modular Messagin Data Colletcion Tool i have the sames password.
Thanks

how many users are on the system now? and have you loaded the lic file

Ken Means

www.tel-is.com
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

Do you ever see anything in the OHV

Ken Means

www.tel-is.com
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

Hi Ken:
I have 800 mailbox licences and 2 Text-to-speech licences.
What is OHV?

Thanks

operational history viewer

Something basic must be off on the system. The MWI is not that complicated.

If you stop the MWI and then change the name of the MWI file to
MWIstate.oldmdb,then start the MWI service you should see it rebuild it. When you do what size is it?

By default it will always be 124K if it never gets any bigger then it is not pulling the info from the MSS or can't pull it from the MSS

Ken Means

www.tel-is.com
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

Also in the VMSC change the MWI to re-evaluate mailbox MWI rules for lamp state under the update schedule tab.And make sure the scheduled MWI updates is active under general tab

Ken Means

www.tel-is.com
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

Hi Ken:
The file mwistat.mdb is all time 120K.I think the mss-h can´t write in the Database. I have chek all users permissions to write to this file and are OK.
When i stop MWI service and rename mwistate to another name, and start MWI service, another file(mwistate.mdb) are created (120K).

In OHV all is ok.

Thanks.

Well i can't think of anything else at this point without looking at the system myself.  I am sure i am missing something but it is hard to say without having access to the system.  What has TAC told you?

Ken Means

www.tel-is.com
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

Hi Ken:
I have install last Paches to MM 3.0 SP 2 (MAS and MSS) and MWI is working correct.
When Avaya toll Service Pack 1 ó 2, y suppose is service pack Modular Mesaging.
How i can know what service pack are my MM?
Thank for all Ken.

you have to look at the version in the VMSC

Ken Means

www.tel-is.com
"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

maybe this helps, I have in the past confused the VVSTS for WSTS which caused me great embarrassment. Just a thought.