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!

 

[AACon]

Usually the conference bridge codes are user defined variables, and don't change unless someone goes in and changes them...they don't really...expire. Is someone maybe changing them and not telling you?

-Austin
ACE: Implement IP Office

 

[jyang12]

Not really, I notice this problem before even announcing this feature... It seems like as long as people keep using them, then it will delay the expiry but I don't have solid proof. Yes the password is user defined variables. Your explanation is exactly what I would have expected but unfortunately that's not the case.

 

[AACon]

Then perhaps another module is affecting it...or someone is calling in and doing it maliciously?

-Austin
ACE: Implement IP Office

 

[jyang12]

I don't see other modules sharing the same variables - is that how it works? Those are unique variables added just for this feature...

 

[AACon]

It was just a thought. Typically the variables are unique to a function, but ya never know. If you want to post your conf module, I could take a look at it...

-Austin
ACE: Implement IP Office

 

[jyang12]

It just happened again! I set the password earlier in the morning but 2 hours later when a conference is ready they told me the code is not valid again...

How do I post the conf module here?

 

[AACon]

export the module, and upload it to a hosting site.

-Austin
ACE: Implement IP Office

 

[jyang12]

Here it is and thanks!

 

[AACon]

I noticed there is no pin set on the menuSetConfPassword module...so anyone that just randomly dialed a *5 could get in there and change codes.

-Austin
ACE: Implement IP Office

 

[jyang12]

Right, I should set that up, but do you think it's related to this issue?

 

[AACon]

Are you using vm to email at all? You could be sneaky and put an email action in the setconfpass flow and have it email you the Caller ID of the person who enters the bridge. Maybe stick it after the set varconf, before your module return. Have it send the $CID and maybe the $KEY or something.

Unless of course you just have a corrupted DB that is getting messed up by AV or something.

-Austin
ACE: Implement IP Office

 

[AACon]

I don't know. user defined variables don't expire. They don't change unless someone changes them. Either is a buggy software (possibly), or someone is doing it (just as possible).

-Austin
ACE: Implement IP Office

 

[jyang12]

So you don't see anything configuration related right? for the email action, do you mean I add an eMail action right before the "password set"? Thanks

 

[AACon]

No. the configuration looks fine for what it is (there are a few better ways to do it, but this works). Though, because you only sent modules, the user defined variables don't come across. You might want to check the set and get for each user defined var and make sure it is going to the right one. It's possible one is overwriting another one. As for the email action, yeah stick it between the set function, and before the password set return function.

-Austin
ACE: Implement IP Office

 

[amriddle01]

I haven't looked at the config, but if you have used the same user variable for several people this will happen, when changing a variable it's system wide, it isn't a just localised to that user, to do this each user should be setting/checking a unique variable


Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)

 

[jyang12]

OK I double checked all get and set and added the email option. Let's see what is the real cause(hopefully). Thanks again for your help.

 

[jyang12]

Oh one more question: is there some sort of "house-keeping" feature that VM Pro would do that might wipe out the user defined variables?

 

[AACon]

nope

-Austin
ACE: Implement IP Office

 

[jyang12]

Hi amriddle01, can you elaborate what do you mean by "the same user variable for several people"? The passcode is user defined variable for the whole VM Pro system but all people participate in the call need to use it - is that a problem at all? Thanks