[cisco-voip] meetme - use specific conference resource

[Wes Sisk]

I'm not aware of anything inside CUCM that allows the same device to differentiate MRGL for adhoc vs. meet me.

I have worked with a few patterns who wanted this in the past. We sent them down the route of a custom application. Something like a UCCX custom application. Use a telephony trigger that invokes a script that remote controls a dedicated phone and initiates the conference.

-wes

On Apr 1, 2013, at 1:34 PM, Erick Wellnitz <ewellnitzvoip at gmail.com> wrote:

I think that would work but we have to be able to initiate from the phone of any IT person. 
 
My ideal outcome is:
From any phone go off hook, press meetme, dial conference number - conference uses software CFB.
From any phone initiate an ad-hoc conference - conference uses hardware CFB.
I haven't found a way to do this but it was an idea that I thought I should investigate.
 
 I can always set the maximum conference-participants on the IOS CFB higher but that would also allow an ad-hoc conference to have more participants.
 
 


On Mon, Apr 1, 2013 at 12:19 PM, Wes Sisk <wsisk at cisco.com> wrote:
For some reason I thought this was possible by initiating the meet me from a dedicated device (phone/cipc) that uses a specific MRGL?

This is quite fuzzy to me so I am more than willing to be wrong. Just sharing an idea.

-wes

On Apr 1, 2013, at 1:14 PM, Erick Wellnitz <ewellnitzvoip at gmail.com> wrote:

Hello all!

I have a situation where i need to make my meet-me numbers use a specific CFB resource, specifically a software CFB.  My problem arises because I want ad-hoc conferences to keep using the hardware CFB so changing the order of MRG in the MRGL assigned to phones is out.

Any ideas are greatly appreciated.

Thanks in advance!

Erick
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130401/0d2f52ca/attachment.html>