VMPro Conference Facility

[tidypants]

Hi all,

Scenario:

Conference call - Extension Conf - A call comes in hits the VM pro asks the user for Pin and then their name, they will be put on hold till the moderator comes into the conference bridge, the moderator then gets all the callers names and has the ability to press 1 to accept or any other digit to decline.

Problem:

Is their a way for the moderator to only accept one caller at a time rather than accepting all if more than one caller is waiting?

System Details:

IPO: IP500V2 - 8.1
VM: VMPRO - 8.1

 

[tidypants]

Anyone know of anything relating to the above, any words of wisdom are welcome.

Cheers

 

[amriddle01]

It works how it works and can't be changed, but why invite people they don't want to accept?

 

[tidypants]

Good question and one we are still trying to understand however their argument is they get rogued conference participants who enter the conference and by pressing one to accept all they may slip into the conference unknown.

They do not want to go down the route of apps nor manually entering new passcodes to stop this, in fact they want this to work on a polycom so have no visibility.

 

[hairlessupportmonkey]

This is why Avaya bought a conferencing company because the IPO facilities are pretty limited. (in an end user configuration way)

ACSS - SME
General Geek

 

[amriddle01]

their argument is they get rogued conference participants

No they don't, unless it's programmed badly/specifically to allow this or they are doing something stupid and transferring people who don't belong to those conferences

 

[tidypants]

They say internal users enter the conference with previous credentials and listen into the conference not sure how true this is however they have 6 sites worldwide so could potentially be true what they are trying to get us to do is stop the human from entering or even manage their staff correctly!!

 

[IPGuru]

I can think of 2 steps to help with this issue.

1) configure the conference so that the PIN can be changed regularly (validate PIN against user Variables)
2) issue P45's (or local equivalent) to staff members who attempt to access Conferences they should not.

Step 2 will be the most effective against internal eavesdroppers, it is amazing how fast word will spread after the 1st time it is implemented
Step 1 is required to prevent external abuse.


A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[amriddle01]

You can make shortcodes alphanumeric, that way people internally cannot simply dial them.
For example if a customer want to transfer call directly offsite I make a shortcode: ANDYMOBILE - Dial - 1234556 then in ICR I enter ANDYMOBILE as destination, then I can see who/where it goes and not just a number and user can't dial ANDYMOBILE even if they wanted to, the same logic can be applied to any shortcode even conferences