Meet Me Conference Bridge - Out of Whack following a VM PRO Rebuild 2

[x11dude]

Howdy all -

After our vendor rebuilt our VM Pro (v8) following a RAID failure, the system has "forgotten" the welcome message we once used to introduce callers to the bridge. Most (if not all) wav's, and system settings, were on backups and were restored to the new system.

Now it just greets users with a beep. Not very friendly; confuses everyone. (Previously, it said "press 2 and state your name at the beep"...yadda yadda)

VM\Greetings\Bridge_1.wav still plays the old greeting - it's just not associated with the bridge.

External callers are going to the bridge's voicemail instead of being placed into conference.

Any ideas? Thanks in advance!

 

[amriddle01]

Modules will ony look into the WAVS folder for prompts by default, so you probably need to copy the Bridge_1.wav file there and make sure it's still added/listed as a prompt in the callflow


Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)

 

[amriddle01]

Or if you want to be fancy, you could add the prompt using the filepath ..\Greetings\Bridge_1.wav


Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)

 

[x11dude]

Thanks Amriddle....I've been going through the settings and finding others hosed as well. May take some time to get it all sorted out.

I don't see any call flow for the Conference Bridges. Not sure if it's cause it's not there, or I'm just not smart enough to find it

Thanks again, other ideas welcome as well!

 

[amriddle01]

I hope you haven't been using Remote Desktop, that corrupts the callflows and that can show itself as missing/invisible modules etc


Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)

 

[Westi]

oh no not remote desktop

I have had a few customers that used RDP for years without problems and I had one that screwed up the entire call flow. Took me 8 hours to go into all that was still there and redo from scratch.
but
that was in R4.2 or so not in the latest R8 or R8.1 and I hope that since there is only 1 session being able to be open at the same time it will no longer be an issue.
But

Spoiler

We know that Avaya sometimes throws us curveballs

Joe W.

FHandw, ACSS (SME), ACIS (SME)

http://convergednetworks.ca

Give a tech a solution and he will be back tomorrow to ask you the next question, teach a tech how to read the manual and he will be able to solve the problems for a life time.

 

[x11dude]

Aaaaarrgh, guilty as charged. Was using RDP.... aaaaaaack! I need to do some more digging. I do know that it only allows one RDP session at a time; hopefully it isn't too bollixed up.

Thanks for replying, I very much appreciate it!

 

[Westi]

I meant actually the VM Pro client session not the RDP.
In older releases you could have simultaneous sessions of VmPro client running and that caused the problems as the open client did not get the changes of another client making changes and then caused these changes to be hidden and would never show up again after the second session was closed.
Hopefully you have a good backup of the .mdb file

Good luck and thanks for the star

Joe W.

FHandw, ACSS (SME), ACIS (SME)

http://convergednetworks.ca

Give a tech a solution and he will be back tomorrow to ask you the next question, teach a tech how to read the manual and he will be able to solve the problems for a life time.

 

[x11dude]

Hi Westi, Aha, thanks for the clarification; glad to know I didn't hose myself even worse than usual

Regarding call flow, there is none for the bridges - (only the auto attendants). I think I'm just getting more and more confused...

And you're more than welcome for the star. I'm grateful for the help, believe you me!

Thanks!