<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
A mobile destination is just a phone number. Who said it had to be
a cell phone?<br>
<br>
On 8/15/2011 11:50 AM, Wellnitz, Erick A. wrote:
<blockquote
cite="mid:873B0893A34B904C8FD444B6293D937D40DEE39B@CHI-US-MAIL-1C.us.kmz.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);">You can set up access lists for remote
destinations but I’ve not seen a way to use it for a
non-mobility device. Now Lelio has me interested in this
type of feature/functionality. It would be extremely useful
for some of our directors.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri","sans-serif"; color: rgb(31,
73, 125);"><o:p> </o:p></span></p>
<div>
<div style="border-right: medium none; border-width: 1pt
medium medium; border-style: solid none none; border-color:
rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color;
padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span style="font-size: 10pt;
font-family:
"Tahoma","sans-serif";">From:</span></b><span
style="font-size: 10pt; font-family:
"Tahoma","sans-serif";">
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>
[<a class="moz-txt-link-freetext" href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>]
<b>On Behalf Of </b>Lelio Fulgenzi<br>
<b>Sent:</b> Monday, August 15, 2011 10:36 AM<br>
<b>To:</b> Wes Sisk<br>
<b>Cc:</b> cisco-voip (<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>)<br>
<b>Subject:</b> Re: [cisco-voip] migration options for
Cisco Personal Assistant<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom: 12pt;"><span
style="font-size: 10pt; font-family:
"Verdana","sans-serif"; color: black;">even
more specific, call screening...<br>
<br>
<a moz-do-not-send="true"
href="http://www.cisco.com/en/US/docs/voice_ip_comm/personal_assistant/user/guide/paurules.html#wp1030185">http://www.cisco.com/en/US/docs/voice_ip_comm/personal_assistant/user/guide/paurules.html#wp1030185</a><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>
Cooking with unix is easy. You just sed it and forget it.
<br>
- LFJ (with apologies to Mr.
Popeil)<br>
<br>
<o:p></o:p></span></p>
<div class="MsoNormal" style="text-align: center;"
align="center"><span style="font-size: 10pt; font-family:
"Verdana","sans-serif"; color: black;">
<hr id="zwchr" width="100%" align="center" size="2">
</span></div>
<p class="MsoNormal" style="margin-bottom: 12pt;"><b><span
style="font-size: 10pt; font-family:
"Verdana","sans-serif"; color:
black;">From:
</span></b><span style="font-size: 10pt; font-family:
"Verdana","sans-serif"; color: black;">"Lelio
Fulgenzi" <a class="moz-txt-link-rfc2396E" href="mailto:lelio@uoguelph.ca"><lelio@uoguelph.ca></a><br>
<b>To: </b>"Wes Sisk" <a class="moz-txt-link-rfc2396E" href="mailto:wsisk@cisco.com"><wsisk@cisco.com></a><br>
<b>Cc: </b>"cisco-voip (<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>)"
<a class="moz-txt-link-rfc2396E" href="mailto:cisco-voip@puck.nether.net"><cisco-voip@puck.nether.net></a><br>
<b>Sent: </b>Monday, August 15, 2011 11:27:15 AM<br>
<b>Subject: </b>Re: [cisco-voip] migration options for
Cisco Personal Assistant<o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="margin-bottom: 12pt;"><span
style="font-size: 10pt; font-family:
"Verdana","sans-serif"; color:
black;">this is the feature I was talking about...<br>
<br>
<a moz-do-not-send="true"
href="http://www.cisco.com/en/US/docs/voice_ip_comm/personal_assistant/user/guide/paurules.html">http://www.cisco.com/en/US/docs/voice_ip_comm/personal_assistant/user/guide/paurules.html</a><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>
Cooking with unix is easy. You just sed it and forget
it. <br>
- LFJ (with apologies to
Mr. Popeil)<br>
<br>
<o:p></o:p></span></p>
<div class="MsoNormal" style="text-align: center;"
align="center"><span style="font-size: 10pt; font-family:
"Verdana","sans-serif"; color:
black;">
<hr id="zwchr" width="100%" align="center" size="2">
</span></div>
<p class="MsoNormal" style="margin-bottom: 12pt;"><b><span
style="font-size: 10pt; font-family:
"Verdana","sans-serif"; color:
black;">From:
</span></b><span style="font-size: 10pt; font-family:
"Verdana","sans-serif"; color:
black;">"Lelio Fulgenzi" <a class="moz-txt-link-rfc2396E" href="mailto:lelio@uoguelph.ca"><lelio@uoguelph.ca></a><br>
<b>To: </b>"Wes Sisk" <a class="moz-txt-link-rfc2396E" href="mailto:wsisk@cisco.com"><wsisk@cisco.com></a><br>
<b>Cc: </b>"cisco-voip (<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>)"
<a class="moz-txt-link-rfc2396E" href="mailto:cisco-voip@puck.nether.net"><cisco-voip@puck.nether.net></a><br>
<b>Sent: </b>Monday, August 15, 2011 11:23:00 AM<br>
<b>Subject: </b>Re: [cisco-voip] migration options for
Cisco Personal Assistant<o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="margin-bottom: 12pt;"><span
style="font-size: 10pt; font-family:
"Verdana","sans-serif"; color:
black;">I think the biggest feature they wanted was
management of calls. As far as I can tell, PA was able
to handle calls based on schedules and routing rules.
I know Unity/Connection can do this, but I can't see
how to handle calls extension-to-extension and/or to a
DID.<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>
Cooking with unix is easy. You just sed it and forget
it. <br>
- LFJ (with apologies to
Mr. Popeil)<br>
<br>
<o:p></o:p></span></p>
<div class="MsoNormal" style="text-align: center;"
align="center"><span style="font-size: 10pt;
font-family:
"Verdana","sans-serif"; color:
black;">
<hr id="zwchr" width="100%" align="center" size="2">
</span></div>
<p class="MsoNormal"><b><span style="font-size: 10pt;
font-family:
"Verdana","sans-serif"; color:
black;">From:
</span></b><span style="font-size: 10pt; font-family:
"Verdana","sans-serif"; color:
black;">"Wes Sisk" <a class="moz-txt-link-rfc2396E" href="mailto:wsisk@cisco.com"><wsisk@cisco.com></a><br>
<b>To: </b>"Lelio Fulgenzi" <a class="moz-txt-link-rfc2396E" href="mailto:lelio@uoguelph.ca"><lelio@uoguelph.ca></a><br>
<b>Cc: </b>"cisco-voip (<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>)"
<a class="moz-txt-link-rfc2396E" href="mailto:cisco-voip@puck.nether.net"><cisco-voip@puck.nether.net></a><br>
<b>Sent: </b>Monday, August 15, 2011 10:38:55 AM<br>
<b>Subject: </b>Re: [cisco-voip] migration options
for Cisco Personal Assistant<br>
<br>
PA did alot of things. No single product replaced it
but the features are available with a combination of
other products. What features were(are?) you using?<br>
<br>
Regards,<br>
Wes<br>
<br>
On 8/15/2011 9:14 AM, Lelio Fulgenzi wrote: <o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="margin-bottom: 12pt;"><span
style="font-size: 10pt; font-family:
"Verdana","sans-serif"; color:
black;"><br>
Just wondering what the migration options are for
Cisco Personal Assistant users. Well, someone is
interested in deploying it after visiting the Cisco
website and there are no migration options. The
compatibility matrix simply says it is not
compatible with CCM v5.0 and later but provides no
other details.<br>
<br>
Any thoughts?<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>
Cooking with unix is easy. You just sed it and
forget it. <br>
- LFJ (with apologies
to Mr. Popeil)<br>
<br>
<o:p></o:p></span></p>
</div>
<pre><span style="color: black;"><o:p> </o:p></span></pre>
<pre><span style="color: black;">_______________________________________________<o:p></o:p></span></pre>
<pre><span style="color: black;">cisco-voip mailing list<o:p></o:p></span></pre>
<pre><span style="color: black;"><a moz-do-not-send="true" href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><o:p></o:p></span></pre>
<pre><span style="color: black;"><a moz-do-not-send="true" href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></span></pre>
</div>
</div>
</div>
</div>
<table>
<tbody>
<tr>
<td bgcolor="#ffffff"><font color="#000000">
<pre>===========================================================
CIRCULAR 230 DISCLOSURE: Pursuant to Regulations Governing Practice Before the Internal Revenue
Service, any tax advice contained herein is not intended or written to be used and cannot be used
by a taxpayer for the purpose of avoiding tax penalties that may be imposed on the taxpayer.
===========================================================
CONFIDENTIALITY NOTICE:
This electronic mail message and any attached files contain information intended for the exclusive
use of the individual or entity to whom it is addressed and may contain information that is
proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you
are not the intended recipient, you are hereby notified that any viewing, copying, disclosure or
distribution of this information may be subject to legal restriction or sanction. Please notify
the sender, by electronic mail or telephone, of any unintended recipients and delete the original
message without making any copies.
===========================================================
NOTIFICATION: Katten Muchin Rosenman LLP is an Illinois limited liability partnership that has
elected to be governed by the Illinois Uniform Partnership Act (1997).
===========================================================</pre>
</font></td>
</tr>
</tbody>
</table>
</blockquote>
</body>
</html>