koulioumbis
IS-IT--Management
Hello team.
can someone confirm if VMPRO7_0_35 is compatible with MS Server 2016?
thanks
Nikos
can someone confirm if VMPRO7_0_35 is compatible with MS Server 2016?
thanks
Nikos
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
VMPRO7_0_35 on windows 2016 server 3
- Thread starter koulioumbis
- Start date
- Status
holdmusic34
Vendor
Well it's not supported. you could try running it in compatibility mode...
remembering Intrigrant 2019
remembering Intrigrant 2019
- Thread starter
- #3
koulioumbis
IS-IT--Management
I selected compatibility mode for windows 7, service starts OK I imported database and wavs but when connected to IPO I do not get audio prompt played.
I cannot troubleshoot it now as I am on a live system.
.NET 3.5 is installed and service runs.
Maybe 2012R2 is compatible?
Thanks
Nikos
I cannot troubleshoot it now as I am on a live system.
.NET 3.5 is installed and service runs.
Maybe 2012R2 is compatible?
Thanks
Nikos
-
3
- #4
holdmusic34
Vendor
You better troubleshoot it or you'll live in interesting times.
No audio being played doesn't sound like a production system to me.
Record a wav file through a handset on a generic box in a new start point named "Test".
Save and make live.
Write a short code of *61/voicemail collect "Test"
Dial *61. See if it doesn't work.
If it doesn't, check your recording are actually there.
Check what's happening in monitor when the call is targeting... you know.. technician stuff.
To be honest, if i were you i would throw the Windows server out the window (ha! get it?) and deploy IP Office Application Server 7.0.16.12 Software on a virtual host
I'm not giving flippant advice here- i redeployed an IP Office SE with kernel panic yesterday. After importing the recordings back in they wouldn't work.
Turns out the voicemail password was mismatched between VMPro client>Preferences and the IP Office's security settings.
But i worked this out by checking system status, looking for available VMBs against users. Didn't see any there. Didn't see any users in the VMPro client.
Saw errors in targeting.
Hmm. Dialled *17 and bingo, no voicemail. that's why my IVR is not playing my custom treatments.
Gonna have to start at the beginning and fault fix from there mate. let us know how you go.
remembering Intrigrant 2019
No audio being played doesn't sound like a production system to me.
Record a wav file through a handset on a generic box in a new start point named "Test".
Save and make live.
Write a short code of *61/voicemail collect "Test"
Dial *61. See if it doesn't work.
If it doesn't, check your recording are actually there.
Check what's happening in monitor when the call is targeting... you know.. technician stuff.
To be honest, if i were you i would throw the Windows server out the window (ha! get it?) and deploy IP Office Application Server 7.0.16.12 Software on a virtual host
I'm not giving flippant advice here- i redeployed an IP Office SE with kernel panic yesterday. After importing the recordings back in they wouldn't work.
Turns out the voicemail password was mismatched between VMPro client>Preferences and the IP Office's security settings.
But i worked this out by checking system status, looking for available VMBs against users. Didn't see any there. Didn't see any users in the VMPro client.
Saw errors in targeting.
Hmm. Dialled *17 and bingo, no voicemail. that's why my IVR is not playing my custom treatments.
Gonna have to start at the beginning and fault fix from there mate. let us know how you go.
remembering Intrigrant 2019
- Status
Similar threads
- Locked
- Question
- Question