Hi All,

This is my first post so be gentle!
I have a client with an IPO 500 V2 7.0 running latest sw etc.
They use VMPro to route incoming calls.
When night service kicks in they want the option for the caller to leave a VM in the night service group mailbox but they DONT want the caller to press # when they have finished recording, sounds simple but it wont work without pressing #.
If i dial the night service group internally i get the standard mailbox greeting and can leave a message and hang up, no # required.
If i try and do it via a voice question and put the recording in the mailbox i have to press # otherwise it doesnt save it.
If i do a transfer to the extension i have the same issue with the requirement for #.
So it seems that whichever way i do it, going through the VMPro server forces the need for a # which the customer REALLY doents want.
Any suggestions would be welcome.

Is this analogue trunks ?

I have had this issue using a prem cell on our dem kit , and am trying to also resolve.

APSS (SME)
ACSS (SME)

This is a known issue, a fix will come when Avaya pull their finger out

Which version of 7.0 are you running?
It should be fixed in 7.0.31.
They fixed in 8.0.42 for sure.
 

BAZINGA!

I'm not insane, my mother had me tested!

IPO Manager is V9.0 (27)
VoiceMail Pro is 7.0 (32)

This is on a system using ISDN30 Trunks.
Unless i get the IPO to direct the calls to the night services i have to use #.
Direct via the IPO removes VMPro from the equation but the audio quality on the personalised announcement isnt as good as the studio recorded Wav file they have, hence the need for going through VMPro.

Such a simple thing, such huge frustration!!

Then upgrade to 7.0.31.
This issue is one where i have hunt down Avaya on in the trials.
We use the  voice question a lot so i was really focused on that one.
Let me know if it fixed it for you.
I still need to test it on 7.0
 

BAZINGA!

I'm not insane, my mother had me tested!

Hi tlpeter,

How do i upgrade to 7.0.31 when it is already 7.0.32 which is the 2012 Q1 release.
I upgraded everything to the 2012 Q1 release in the hope that this would resolve the issues but it hasn't.

Your IPO is not on 7.0.31
Try that first.
Your VMPro is the latest one.
 

BAZINGA!

I'm not insane, my mother had me tested!

Got you, my bad!!
Late in the week and brain fried lol!!

i know the feeling.
I am not sure if they fixed this issue on the Windows VMPro.
I have ony VMPro on Linux running.
So it could still be possible that it does not work on the Windows but you have to try that.
 

BAZINGA!

I'm not insane, my mother had me tested!

Ok so getting a little further on but not quite perfect enough for the customer.
If i use Voice Question i still have the same issue with the # being required, however i can now txfr the call to the mailbox or the extension, however, it now rings for the length of the set "no answer" time and then for another 1 second before switching to VM.
Is there any way i can make it go immediately to VM without the ringing?
If i use the Leave Voicemail module option in VMPro i have the same issue.

*Bump*

Does anyone have any other way to achieve this or a solution?

Thanks

So it does not work on 7.0.31 ???
I would try to put in a Linux apps and see what happens then.
Or you should raise a bug because this is basic stuff and needs to be fixed.
Or request an upgrade license but then i still do not know if it is fixed in the Windows version.
 

BAZINGA!

I'm not insane, my mother had me tested!

Nope still doesnt work.
As mentioned in previous post it does "kind" of work in a very loose sense of the word, but not as i think it should!

Did you try a deinstall off VMPro and then a clean install of VMPro?
 

BAZINGA!

I'm not insane, my mother had me tested!

Hi tlpeter, do you have the CQ number of the supposed fix?
I am being told if i can have this i can get Avaya to look into it as it clearly isnt fixed on my build.

I will look for you later,I can't at the moment.
Although keep in mind this was on the fields trials.
 

BAZINGA!

I'm not insane, my mother had me tested!

I have no CQ number.
All i know is that i raised it as a bug on the 8.0 Q1 trials.
I raised it as bug 7 with NPI.
Maybe Avaya can use this info.
 

BAZINGA!

I'm not insane, my mother had me tested!

I have found that when they don't assign a CQ during NPI trials it doesn't get fixed/looked at, I had 3 or 4 fixed and they all had CQ's assigned, I had 2 not fixed and they were never assigned CQ's and one is still present in all current releases

It probably did get one but i don't have it.
It did get fixed but apparently only for Linux.
I did not raise it for Windows.
 

BAZINGA!

I'm not insane, my mother had me tested!