<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>Thanks Scott. I figured I could do something with Connection only as a front end where it's a supervised transfer and asks for the user's name and then asks the called party to accept the call or not. We'll see if it pans out.<br><br>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>"Bad grammar makes me [sic]" - Tshirt<br><br><br>----- Original Message -----<br>From: "Scott Voll" <svoll.voip@gmail.com><br>To: "Lelio Fulgenzi" <lelio@uoguelph.ca><br>Cc: "cisco-voip voyp list" <cisco-voip@puck.nether.net><br>Sent: Tuesday, September 8, 2009 5:27:49 PM GMT -05:00 US/Canada Eastern<br>Subject: Re: [cisco-voip] MeetMe conferencing questions<br><br><link href="/zimbra/css/msgview.css?v=081117021119" rel="stylesheet">meetme uses your MRL and can in fact use HW. <div><br></div><div>meetme stinks because you still have to start it from an IP phone.</div><div><br></div><div>for security reasons I run my through a script on UCCx / Unity to get there conference number and name to be broadcasted to the audio conference members. Helps with the security piece.</div>
<div><br></div><div>Scott<br><br><div class="gmail_quote">On Tue, Sep 8, 2009 at 12:11 PM, Lelio Fulgenzi <span dir="ltr"><<a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div style="font-family: Verdana; font-size: 10pt; color: rgb(0, 0, 0);">Sorry, forgot to ask whether or not the MeetMe initiator has controls over the conference list like in an AdHoc.<div class="im"><br><br>---<br>Lelio Fulgenzi, B.A.<br>
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>"Bad grammar makes me [sic]" - Tshirt<br>
<br><br></div><div><div></div><div class="h5">----- Original Message -----<br>From: "Lelio Fulgenzi" <<a href="mailto:lelio@uoguelph.ca" target="_blank">lelio@uoguelph.ca</a>><br>To: "cisco-voip voyp list" <<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>><br>
Sent: Tuesday, September 8, 2009 3:04:19 PM GMT -05:00 US/Canada Eastern<br>Subject: MeetMe conferencing questions<br><br><div style="font-family: Verdana; font-size: 10pt; color: rgb(0, 0, 0);">I've been asked to look at MeetMe conferencing as a potential solution to save some dollars. I will be doing some reading, but thought the list could help out on a few things:<br>
<ul><li>Can MeetMe conferences use hardware conferencing just like AdHoc based on the media resource list assigned to the device(pool)? The service parameter says something to this affect, I'm just wanting to make sure it can.</li>
<li>If so above, can MeetMe and AdHoc conferences happen on the same hardware bridge?</li></ul>Are there any gotchas to worry about?<br><br>Thanks, Lelio<br><br>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>"Bad grammar makes me [sic]" - Tshirt<br><br></div></div></div></div></div><br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>
</div></body></html>