Voice Mail Server

[MWeise]

Hi gang,
I am switching out a voice mail server to a system with some higher specs, here is what I got:

Avaya IP Office Unit IP403
Old System:
Manager 3.2 (53)
VM Pro 3.1 (18)

New System
Manager 3.2 (53)
VM Pro 3.2 (28)

What has me preplexed is that everything works perfect on the Old system. On the new system, the AA won't pick up when calling in? What am I missing? It obviously sounds like something with VMPro 3.2 (28), but I can't figure it out. I plug the old one into the network everythings good to go. I plug the new one in with the same config, AA tec. and NADA. is there something different in VM Pro (28) that needs to be changed? And yes, chnaged all the IP address etc.

Thanks for the help,
Mike

 

[flashover]

CHECK TO MAKE SURE THAT THE SELECT MODE OPTION IS SET FOR OLINE. THATS UNDER VM PRO. FILE , SELECT MODE.

 

[disturbedone]

When you dial *17 does it answer? Or is it just DDI calls to the AA that don't work?

If *17 doesn't work, then your IPO doesn't know the VMPro is there. In VMPro enable the service to interact with the desktop and view what's happening - does it contact the IPO?

On the new computer, is it XP SP2 with the firewall on? Could be just that the firewall is blocking them from talking.

Did you export the config file & msgs from the old VMPro and import into the new or set it up from scratch?

 

[1043]

Make sure the service is running.

 

[MWeise]

Hey guys,

Ok, here ya go:


1. YES, it is setup for "Online" mode
2. It is WIN XP Pro, on both systems.
3. NO you do NOT get the AA when dialing the short code (*90) from a phone internally and no DDI calls.
4. Firewalls are all tunred off.
5 Imported the old config files and VM Pro. Like i sadi, they work with the other system, just not the new server.

It seesm like short code or start point issue in the New VM Pro? But it works with the old VM Pro.

Mike

 

[disturbedone]

Use the service in 'Interact with the desktop' mode to see what is happening. Or use the app DubugView (if you have it). You need to see what is going on.

 

[jml2665]

IP address setup correctly on the IPOffice?
Can you ping the new VM machine?
VMPro services running?

Get voicemail running in a default mode then re-import your mdb file and wav files

 

[MWeise]

Yes, I can ping the IP unit and the VM Server. And yes, tme VMPro services are running and yes, the licnse key is good and active. Where do i get Debug View? No got.

Thanks !!

Mike

 

[1043]

Was it running as a service or a program on the old system . The VMpro 3.2 server will only work as a service on Windows XP cpu's.

 

[disturbedone]

DebugView can be obtained from your distributor (if they're any good). It's just a little app that looks like the VMLite window (but gives a little more info). You can see the same stuff by putting the service into Interact with the Desktop mode.

I haven't got a copy of it anymore but could get it but will take some time. Just put it in Interactive mode, it takes 30secs and you'll see what's going on.

 

[MWeise]

As a program on the old system and a service on the new system

 

[1043]

Set the service logon to work as a local account.

 

[MWeise]

Service is/was set to work as a local acount, still nada. I still think it's a short code issue...just can't figure out how or why

 

[disturbedone]

Dose *17 work? You've mentioned your *90 but we can't even look that far unless it's not working at all.

 

[MWeise]

In regard to the *17, yes it works, as a matter of fact if I set the incoming call routes to a *90 AND voice mail collect and call into the Ip Unit, you gte the voice mail attendant BUT if I set the incoming call routes to *90, Attendant, Voice Mail Node, I get nada

 

[disturbedone]

Right, progress. So it is working. It's just your AA that isn't. We can scrub a whole lot off the ideas list now.

Short code should be
S/C *90
T/N #AutoAttendant
Feat VoicemailNode

Where is your AA in VMPro - Start Points or Modules?

What exactly do you have?
What do you get when dialling *90 now? Silence? Busy? Something else?

 

[disturbedone]

It is also now more important to put the service in Interact mode or use DebugView to see exactly what's going on.

 

[MWeise]

My Short code is:

*90
VoiceMail Node
Attendant (Yes, it's spelled correctly

Attendant is located in "Start Points" "Short Codes" in VMPRO Client. Don't have it under "Modules" or any where else. Works on the old system not on the new. I imported the config into the new system and haven't changed anything?

In the new system it should be:

*90
VoiceMail Node
#AutoAttendant

???

 

[jml2665]

Attendant or AutoAttendant ??
no need for a # in the SC either

 

[tlpeter]

so probebly you need to change the shortcode in the IPO