Appendix D-Ad Hoc Conferencing and External Database Authentication

Entry Queue Level - Conference Initiation Validation with an External Database Application

Starting a new conference with external database application validation entails the following steps:

IP Endpoint

 

 

 

MCU

 

9

 

 

 

 

2

 

 

 

 

5

 

 

 

 

1

 

 

 

 

0

 

 

 

 

0

 

 

 

 

0

MCU Prefix in

 

IP Endpoint

 

Gatekeeper - 925

 

 

 

 

 

925DefaultEQ

Network

1001

 

1200

 

 

 

 

 

 

 

 

1300

 

0

 

 

 

 

0

 

 

 

 

0

 

 

 

 

1

 

 

 

 

5

 

 

 

 

2

 

 

 

 

9

 

 

Name: DefaultEQ

 

 

 

 

 

 

 

 

Numeric ID: 1000

IP Endpoint

 

 

 

 

On Going

Conference with this ID?

New Conference

ID: 1300

Figure D-2Conference Initiation Validation with External Database Application

1The participant dials in to an Ad Hoc-enabled Entry Queue.

2The participant is requested to enter the Conference ID.

3The participant enters the conference ID via his/her endpoint remote control using DTMF codes. If there is an ongoing conference with this Conference ID, the participant is moved to that conference where another authentication process can occur, depending on the IVR Service configuration.

4If there is no ongoing conference with that Conference ID, the MCU verifies the Conference ID with the database application that compares it against its database. If the database application finds a match, the external database application sends a response back to the MCU, granting the participant the right to start a new ongoing conference.

D-4

Page 717
Image 717
Polycom 2000/4000 manual Network