Meet-Me-VDN help 1

[skill1]

Meet-Me-VDN will not release when the conference call has ended so the next call is denied, caller here's the full to capacity announcement.Why is this happing?

Thanks
Randy

 

[adminman3]

Could you paste a copy of your 2-page VDN used for Meet-Me?

 

[skill1]

This how I have them setup.

VECTOR DIRECTORY NUMBER

Extension: 8311
Name: Corp 1
Vector Number: 492
Meet-Me Conferencing? y

COR: 1
TN: 1
MEE-ME CONFERENCE PARAMETERS:
Conference Access Code: xxxx
Conference Controller: 2323

Thanks
Randy

 

[MERIDIAN11C]

could you posted the vector 492?

 

[skill1]

CALL VECTOR
Number: 492 Name: Corp1
Multimedia: n Attendant Vectoring? n Meet-Me Conf: y Lock:n
Basic: y EAS: Y G3V4 Enhanced: y ANI/II-Digits: y
ASAI Routing: n Prompting: y LAI: N G3V4 Adv Route: y
CINFO: Y BSR: Y Holidays: y

01 goto step 2 if unconditionally
02 goto step 6 if digits = meet-me-access
03 collect 6 digits after announcement 3476
04 goto step 6 if digits = meet-me-access
05 disconect after announcement 3478
06 goto step 11 if meet-me-idle
07 goto step 14 if meet-me-full
08 announcement 3480
09 route-to meet-me
10 stop
11 announcement 3681
12 route-to meet-me
13 stop
14 disconnect after announcement 3479
15 stop

 

[marcell55]

What is step 2 for?

 

[NX01]

It happens all the time for me. I have to do a "reset meet-me-vdn XXXX" (XXXX=DID extention)

In the future everything will work...

 

[tsturg]

Does anyone know if there is a solution for this problem? I am facing the same issue - having to reset the meet-me VDN after every conference call.

 

[phonesrus]

This is how I have a MMC configured, and it has been in operation for a year with no reported reset requests on a CM 2.0 with PRI Trunks and DID. Build a new vector as a test using this config. If you still have an issue with it then there is a possible trunk problem. What type of trunks are you using to access the MMC??

display vector 83 Page 1 of 3 SPE A
CALL VECTOR

Number: 83 Name: MMC-3
Attendant Vectoring? n Meet-me Conf? y Lock? y
Basic? n EAS? n G3V4 Enhanced? n ANI/II-Digits? n ASAI Routing? n
Prompting? y LAI? n G3V4 Adv Route? n CINFO? n BSR? n Holidays? y
Variables? n
01 collect 6 digits after announcement 3140
02 goto step 6 if digits = meet-me-access
03 collect 6 digits after announcement 3141
04 goto step 6 if digits = meet-me-access
05 disconnect after announcement 3142
06 goto step 11 if meet-me-idle
07 goto step 14 if meet-me-full
08 announcement 3143
09 route-to meetme
10 stop
11 announcement 3144

display vector 83 Page 2 of 3 SPE A
CALL VECTOR


12 route-to meetme
13 stop
14 disconnect after announcement 3145
15 stop

 

[tsturg]

I have a Multivantage S8700 running R1.3.2. This is my MMC set-up. We mainly use this for internal conferencing so I don't think it is anything to do with the trunks, but if there is anything I should look at on the trunks please let me know, because on some of the MMC vdn's, I need to reset them everyday.

CALL VECTOR

Number: 950 Name: Meet-me vector
Multimedia? n Attendant Vectoring? n Meet-me Conf? y Lock? y
Basic? y EAS? y G3V4 Enhanced? y ANI/II-Digits? y ASAI Routing? n
Prompting? y LAI? y G3V4 Adv Route? y CINFO? y BSR? y Holidays? y

01 wait-time 3 secs hearing ringback
02 collect 6 digits after announcement 602405
03 goto step 8 if digits = meet-me-access
04 collect 6 digits after announcement 602409
05 goto step 8 if digits = meet-me-access
06 disconnect after announcement 602406
07 stop
08 goto step 13 if meet-me-idle
09 goto step 16 if meet-me-full
10 announcement 602408
11 route-to meetme
12 stop
13 announcement 602410
14 route-to meetme
15 stop
16 disconnect after announcement 602407
17 stop
18

 

[phonesrus]

Could be an issue where the conference controller hangs up before the other parties causing the switch to think the conference is still in progress. Switches sometimes get funny ideas in their "chips".
There is a known issue with PRI calls getting busy's to MMC's with no members logged in to the conference. It might be worth a call to AVAYA.
Follow this link;

http://support.avaya.com/elmodocs2/PSN/PSN262u.pdf

Not sure if internal calls to a MMC would relate, assuming no trunking at all is involved in the conf. There would seem to be some issue involved if you have to constantly reset the VDN.