Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

cm8 bridged appearances

Status
Not open for further replies.

wpetilli

Technical User
May 17, 2011
1,877
0
36
US
Hi all- What is the max amount of people that can hop on a bridged appearance in cm8? Need to find a way to get 20 or so people simultaneously on the same call.
 
Up to six parties can be off-hook and involved in a conversation on a bridged appearance of an
extension.

Found this in the Feature Impelemntation and discription manual
 
If you have a media server you can enable 12-party conference. You may also want to look at blast conference. Otherwise 6 should be max.
 
That's not what bridged appearances are for!

You want a conference bridge, right?
 
These folks want to simulate turrets. They want a general line that a bunch of them can just go off hook and get on. Conferencing is too many hoops to jump through.
 
They deal with external parties and aren’t using any sort of ARD lines.
 
Sounds like a trading floor, if so I doubt if Avaya will ever meet their requirements.
 
I got it! Fair warning - I'm not responsible for your G450 catching fire.

So you turn on blast conferencing. It's a kind of meet-me VDN.

You can't have a meet-me VDN be the destination.

But you can loopty-loop trunk it through SM.

So let's say you've got VDNs
0000020 - the blast VDN
0000021 - the first bridge of 6
0000022 - the second bridge of 6
0000023 - the third bridge of 6
0000024 - the fourth bridge of 6
0000025 - the fifth bridge of 6

Let's say the AAR code is 8.
Make the blast destinations 80000021, 80000022, etc
In AAR make them pick a sig/trunk on a different domain - like conf.yourcompany.com
In SM, make 000002x from that domain go to CM
Now the blast calls loop thru SM and terminate on the bridges.
But, because you're a wise guy and bridged conference bridges to conference bridges, they both think there's 2 parties on the call and it never drops. Which really isn't a huge deal for you if you design your logic just right.

In the meet-me vector you can have logic like checking if it's idle or full. That's intended to make people wait on hold until a moderator shows up or reject them if the bridge is full, but we can make them be basic logic checks for our little Rube Goldberg machine. The caveat there is that you can only have the vector check the meet-me VDN you're in. You can't check other meet-me VDNs. So we hop along through many VDNs to check.

Let's say it's vector 20 for this for VDN 0000020 and vector 21 for 0000021-25

Vector 21:
step 1 - wait 0 seconds hearing silence
step 2 - route-to meet-me

Vector 20
1- wait 0 secounds hearing silence
2- go to step 10 if meet-me-idle
3- route to 0000021
4- route to 0000022
5- route to 0000023
6- route to 0000024
7- route to 0000025
10 - route to meet-me

Vector processing continues if a route-to fails. So, the first person to dial in brings up the bridge, the next 20 each try the bridges in sequence.

You could have vectors 21,22,23,24,25 instead. I don't think you'd need to go this far though.
vector 21:
wait 0 sec silence
go to step 10 if meet-me-full
route to meet-me
10 - route to 0000022

Either way, it'll only drop if CM does a reset 4, so vector 20 will only ever need to setup the blast conference once to get it up.
You can "stat meet-me 0000020" and busy the ports one by one if you need to bring it down, but you shouldn't have to.
 
It works, but it's weird. I can get 10 people in the first bridge, which I shouldn't be able to, and the 11th goes in the second bridge but bumps off the blast user so I'm all alone on 000-0022...

Oh well. Something to play with :)

status meet-me-vdn 0000020
GENERAL STATUS
Service State: active

Extension: 000-0020

Conferee Ports
T028576 T001472 T001471 T004452 T001470 T004453

status meet-me-vdn 0000021
GENERAL STATUS
Service State: active

Extension: 000-0021

Conferee Ports
T007885 T028545 T028514 T028483 T028452 T028421
T028390 T028359 T028328 T028297 T028266

 
OK... This should be better.

Everyone calls 0000020 that goes to vector 20 which IS a meet-me vector
The first guy fires up the blast bridge


01 wait-time 0 secs hearing silence
02 goto step 5 if meet-me-idle
03 route-to number 0000030 cov n if unconditionally
04
05 route-to meet-me

The second caller calls 0000020 thru vector 20 that then sends him to 0000030 that goes to vector 30 which is NOT a meet-me vector.
Go in your variables and set something. I picked R and S. R is a type "collect" of scope Global length 1, start 1, assignment 1. S is a type value, global, length 1, assignment 1.

Vector 30 will round robin each caller to a new meet me bridge so no one bridge fills up first. If R=1, hit 0000021, if it's 2, go 0000022. Now you don't fill up any one bridge.
It says it's not tested with SIP and I don't have 12 party conferencing turned on, but my first try got 10+ people on the same meet-me bridge, so this should hopefully avoid that.


01 wait-time 0 secs hearing silence
02
03 goto step 10 if R = 1
04 goto step 20 if R = 2
05 goto step 30 if R = 3
06 goto step 40 if R = 4
07 goto step 50 if R = 5
08 goto step 9 if R = 6
09 set R = S ADD 0
10 set R = R ADD 1
11 route-to number 0000021 cov n if unconditionally
20 set R = R ADD 1
21 route-to number 0000022 cov n if unconditionally
30 set R = R ADD 1
31 route-to number 0000023 cov n if unconditionally
40 set R = R ADD 1
41 route-to number 0000024 cov n if unconditionally
50 set R = R ADD 1
51 route-to number 0000025 cov n if unconditionally


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top