VM Pro conference password keeps expiring

[jyang12]

Hi all,

By following some posts here I managed to set up conference bridge using our VM Pro 7.0 with IPO 500 V2 7.0. However we find that the password we set for the conferences keeps expiring every few days, that I have to dial in and set them up again and again. Is there anywhere I can set a longer expiry period, or better yet, set it permanently? Thanks for your help!

 

[amriddle01]

Say for example 2 people regularly hold conferences and have their own module built for this purpose, if I create a variable that I set called "ConfPass" and set it to 1234 then when people call in I test to see the pin they enter is the same as "ConfPass" works great, but if I use that same "ConfPass" variable in the other module (for a seperate conference) and I set it to 5678 then that variable will also be set to 5678 in the first module, so anyone joining that conference with 1234 will not get in


Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)

 

[jyang12]

Oh yes I see what you're saying, but our conferences don't share the variables - we have unique variable for each conference. I think AACon proof read that as well

 

[jyang12]

It's still doing it! I receive no email on password being changed and I can confirm the email alert is working. This is really brutal. Is there any way to "hardcode" the password into each conference ID from VM Pro client? I'm not taking any chance to use user variables if there is another way out. Thanks for all your input.

 

[jyang12]

Can I instead of pointing to a menu, point the conference ID selected to a generic box, with pin hardcoded, and then point to the conference bridge? Would this work? Thanks

 

[AACon]

Sure, point the primary menu with the bridge ID to another menu. In that menu have the pin code as a touch tone, and an invalid option. Link the pin code to the conference transfer, and the invalid to maybe the receptionist, or back to the beginning, or have it loop through a counter to try again.

-Austin
ACE: Implement IP Office

 

[jyang12]

The way I'm trying to set it up, is to point the primary menu to a generic block, in which I've set the PIN up, with the next hop to the conference transfer. Would this work? Understanding that the invalid passcode will keep sending it back to the prompt for PIN. Thanks

 

[AACon]

sure why not.

-Austin
ACE: Implement IP Office

 

[amriddle01]

Any action in VM Pro can be PIN protected, a menu is better as you can control the amount of retries and handle accordingly once that limit is reached


Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)

 

[jyang12]

just to make sure, I've exported the module again, would you mind taking a look for me:

https://www.dropbox.com/s/26s3v0t1qfax709/modules2.mod

See there is a "To 5812" added and I point 18 to 5812 in the way I described. Let me know if this will work. Thanks for all your help!

 

[AACon]

module dosen't have what you described...

-Austin
ACE: Implement IP Office

 

[AACon]

but yes...it'll work. it won't be the best way to do it, but it'll work. take your pick option from the primary menu (say 18), point it to a generic action with a pin code, and then a transfer after that to your bridge shortcode. easy. not elegant though. I would pony up for the advanced edition and stick a sql db in the backend with web management for the bridges, but that's me.

-Austin
ACE: Implement IP Office

 

[jyang12]

Hehehe, if I knew what I'm doing...

I'll save it and try to upload again...

 

[jyang12]

Sorry guys, let's try again:

https://www.dropbox.com/s/26s3v0t1qfax709/modules2.mod

I'm doing it the menu way, however, I have problem getting the call transferred to 5812 even after PIN is entered correctly. It's not going anywhere without a #, but if I hit # after the PIN, it keeps telling me "invalid entry". Can you help me out? Thanks

 

[AACon]

Well, it's wrong.

You would not use a menu in the pin selector. use a generic action, with a pin on it in the general tab. The reason they are only going after the #, is because the # is...invalid.
You need to either make it a generic action, or take out that pin code, and make it a MENU TOUCH TONE (the pin) on that menu...and have THAT transfer to the shortcode. It says INVALID ENTRY, because there is a prompt on your invalid touch tone...with 3 retries. put the pin code as a touch tone on that menu, and take the pin out of the general tab.

-Austin
ACE: Implement IP Office

 

[jyang12]

OK you mean like this right?

https://www.dropbox.com/s/26s3v0t1qfax709/modules2.mod

I still like the idea of having a menu to control how many retry and give proper prompt. Please let me know if you think I need to add anything else. Really appreciate your help!

 

[AACon]

well you need to connect the invalid to some place, maybe the receptionist...but yeah..its okay...i guess.

-Austin
ACE: Implement IP Office

 

[jyang12]

I find that invalid just loop back to the "please enter your pin" prompt, so I guess we're good then?

 

[AACon]

well it's going to want to go somewhere after the retry amount...

-Austin
ACE: Implement IP Office

 

[jyang12]

it just drops the call - would that corrupt anything? Thanks

 

[AACon]

it would only corrupt the users view of how the system was programmed. Like I said, send it somewhere. No one likes a dropped call. seriously.

-Austin
ACE: Implement IP Office