"You have [N] new messages" plays during calls 2

[AlexPQI]

I recently upgraded to IPO 8 and VMPRO 8. Since then people in my office have been noticing something weird. When every they are connected to a call, the "You have [N] new messages" plays at the beginning of the call.

It only happens something and eventually stops doing it.

Has anyone else heard of this?

Thank you.

 

[amriddle01]

It has been mentioned a couple of times, must be a new and interesting R8 bug

 

[shardian]

I had the same issue on our system.

From what I could tell, it only happened to extensions that had call recording enabled. I disabled recordings for all extensions and then when I was able, rebooted the voicemail machine. After that, all seemed to work fine.

I guess instead of recording the calls, the system is conferencing each extension's mailbox.

 

[AlexPQI]

Shardian,

That seams to be my assessment as well. Only the extensions that have auto recording on have this problem.

Did you re-enable call recording after VM reboot or do you have another solution for recording calls?

Thanks.

 

[amriddle01]

I guess instead of recording the calls, the system is conferencing each extension's mailbox

That's exactly how the system records calls, it is supposed to not play the greeting though

 

[shardian]

After the reboot I've turned recording on again - no problems since. It was really weird. We have 2 systems in an SCN setup and both had the same problem. Reboot seemed to fix it all up.

 

[TomMills]

Had the same here. Rebooting the VM server also cleared it and touch wood, it hasn't come back since january.

http://www.twitter.com/tem1985

APSS/ACIS/ACSS-SME
not arrogant, just succinct.

 

[tlpeter]

We have had it too although i only restart the VMPro service.
We also do call recording.
It was worse in the trials for 8.0 but it seems to be still there once in a while.
It happens most of the times while i am configuring VMPro.

BAZINGA!

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

 

[dagz]

We set up a system last week with a lot of call recording extensions and had the same problem right after we went into production. A reboot of the VM server did the trick for us, too.

 

[AlexPQI]

So restarting it does stop it, but I have notice that it will come back when I am in the Voicemail Pro client.

I guess if I need to change something in the client, I will have to do it when the office is closed. Hopefully Avaya will come out with a fix for that.

Thanks everyone!

 

[tlpeter]

Indeed only when you make changes.


BAZINGA!

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

 

[dagz]

Just made a few changes on mine today and as soon as I did save/make live, we had the problem again. The problem only appears on extensions that are recorded.

I rebooted the VM server and the problem was gone again. I'm going to try just restarting the service next time.

 

[elly10]

Had the same issue, problem was fine after reboot. However if a change was made to any module was made the problem came back.

 

[PhoneMan777]

Same problem here as well. As soon as I hit save and make live I will immediately open services and restart contact store and vmpro and it clears the issue. I am not certain you have to restart contact store but I know that doing both will fix it.

 

[tlpeter]

I had it yesterday too.
I logged in with the VMPro client and there it was.
I think i am going to raise an issue on this one.


BAZINGA!

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

 

[sq12345]

Same issue.

Disable the record will solve crosstalk.

But we need record.

 

[tlpeter]

You need to raise a case with Avaya.


BAZINGA!

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

 

[Lodde]

FYI

This is what I have discovered:
You will have the problem if you make a change to the config while there is an ongoing recorded call in the system.

But you will not have the problem if you are using VM Pro on Windows and using the VM Pro Client on the same PC as the VM Server (Local).
This also means that you will always have this problem if you are using Application Server, because your Client is never Local.

Workaround for every Windows installation is to always be Local with your Client. Workaround for App Server can be to make sure that all VM Pro ports are free when saving. But I have not confirmed that. Or as said in previous posts, restart Service after each change in config.

This is reported to Avaya

/ Lodde

 

[sq12345]

Lodde,

We have Windows Server 2008 installed Release 8 VMPRo and Contact Store.

When we made the changes by using the VM Pro Client one the same PV as VM pro server (local), this problem still happened.



Sq

 

[Lodde]

sq12345 - interesting, because I could not reproduce the problem when I was local. So there might be more scenarios that triggers the problem.

/ Lodde