<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:x =
"urn:schemas-microsoft-com:office:excel" xmlns:p =
"urn:schemas-microsoft-com:office:powerpoint" xmlns:a =
"urn:schemas-microsoft-com:office:access" xmlns:dt =
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s =
"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs =
"urn:schemas-microsoft-com:rowset" xmlns:z = "#RowsetSchema" xmlns:b =
"urn:schemas-microsoft-com:office:publisher" xmlns:ss =
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:c =
"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc =
"urn:schemas-microsoft-com:office:odc" xmlns:oa =
"urn:schemas-microsoft-com:office:activation" xmlns:html =
"http://www.w3.org/TR/REC-html40" xmlns:q =
"http://schemas.xmlsoap.org/soap/envelope/" XMLNS:D = "DAV:" xmlns:mt =
"http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2 =
"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois =
"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir =
"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds =
"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp =
"http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc =
"http://schemas.microsoft.com/data/udc" xmlns:xsd =
"http://www.w3.org/2001/XMLSchema" xmlns:sub =
"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec =
"http://www.w3.org/2001/04/xmlenc#" xmlns:sp =
"http://schemas.microsoft.com/sharepoint/" xmlns:sps =
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi =
"http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs =
"http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf =
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p =
"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf =
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss =
"http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi =
"http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi =
"http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver =
"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels =
"http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp =
"http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t =
"http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m =
"http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl =
"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl =
"http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService"
XMLNS:Z = "urn:schemas-microsoft-com:" xmlns:st = ""><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3527" name=GENERATOR><!--[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-face {
        font-family: Cambria Math;
}
@font-face {
        font-family: Calibri;
}
@font-face {
        font-family: Tahoma;
}
@font-face {
        font-family: Consolas;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
LI.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
DIV.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"
}
A:link {
        COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
        COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
        COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
        COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P {
        FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman","serif"; mso-style-priority: 99; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
PRE {
        FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Courier New"; mso-style-priority: 99; mso-style-link: "HTML Preformatted Char"
}
P.MsoAcetate {
        FONT-SIZE: 8pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
LI.MsoAcetate {
        FONT-SIZE: 8pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
DIV.MsoAcetate {
        FONT-SIZE: 8pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link: "Balloon Text Char"
}
SPAN.HTMLPreformattedChar {
        FONT-FAMILY: Consolas; mso-style-priority: 99; mso-style-link: "HTML Preformatted"; mso-style-name: "HTML Preformatted Char"
}
SPAN.BalloonTextChar {
        FONT-FAMILY: "Tahoma","sans-serif"; mso-style-priority: 99; mso-style-link: "Balloon Text"; mso-style-name: "Balloon Text Char"
}
SPAN.EmailStyle22 {
        COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal
}
SPAN.EmailStyle24 {
        COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal-reply
}
.MsoChpDefault {
        FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.Section1 {
        page: Section1
}
</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]--></HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=089361014-07052009><FONT face=Arial
color=#0000ff size=2>Yes. I am just trying to make sure that there is nothing
other than generic router (Linksys or whatever someone would normally have in
their home) and the phone which are necessary to work with the the ASA55XX back
at the network site. We have been using VPN3002 boxes which are expensive
and sometimes problematic to set up/program. Thank you for your
feedback!</FONT></SPAN></DIV>
<DIV> </DIV><!-- Converted from text/rtf format -->
<P align=left><STRONG>Steve Miller</STRONG><BR>Telecom Engineer<BR>Dickstein
Shapiro LLP<BR>1825 Eye Street NW | Washington, DC 20006<BR>Tel (202) 420-3370|
Fax (202) 330-5607<BR><A
href="mailto:MillerS@dicksteinshapiro.com">MillerS@dicksteinshapiro.com</A><FONT
face=Arial> </FONT></P>
<DIV> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Matthew Loraditch
[mailto:MLoraditch@heliontechnologies.com] <BR><B>Sent:</B> Thursday, May 07,
2009 10:08 AM<BR><B>To:</B> Miller, Steve; Cisco VOIP<BR><B>Subject:</B> RE:
Deploying 7961 Phones Remotely with ASA5500?<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">What
do you mean by necessary? If you can get your Linksys to setup a vpn tunnel then
yes<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Arial','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'">Matthew
Loraditch</SPAN></B><SPAN
style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'"><BR>1965
Greenspring Drive<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'">Timonium,
MD 21093 <BR><A href="mailto:support@heliontechnologies.com"><SPAN
style="COLOR: black">support@heliontechnologies.com</SPAN></A><BR>(p) (410)
252-8830<BR>(F) (443) 541-1593<BR><BR>Visit us at <A
href="http://www.heliontechnologies.com"><SPAN
style="COLOR: black">www.heliontechnologies.com</SPAN></A> <BR>Support Issue?
Email <A href="mailto:support@heliontechnologies.com"><SPAN
style="COLOR: black">support@heliontechnologies.com</SPAN></A> for fast
assistance!</SPAN><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P></DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<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'"> Miller, Steve
[mailto:MillerS@DicksteinShapiro.COM] <BR><B>Sent:</B> Thursday, May 07, 2009
10:05 AM<BR><B>To:</B> Matthew Loraditch<BR><B>Subject:</B> Re: Deploying 7961
Phones Remotely with ASA5500?<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: 'Arial','sans-serif'">Thanks.
Only the phone is necessary, correct?<BR><BR><BR>Steve Miller <BR>Telecom
Engineer <BR>Dickstein Shapiro LLP <BR>1825 Eye Street NW <BR>Washington, DC
20006 <BR>Tel (202) 420-3370 <BR>Fax (202)-330-5607
<BR>millers@dicksteinshapiro.com </SPAN><o:p></o:p></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center>
<HR align=center width="100%" SIZE=2>
</DIV>
<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'">: Matthew Loraditch
<BR><B>To</B>: Miller, Steve; Cisco VOIP <BR><B>Sent</B>: Thu May 07 09:45:41
2009<BR><B>Subject</B>: RE: Deploying 7961 Phones Remotely with ASA5500?
</SPAN><o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Only
the hardware needed to establish connectivity back to the cluster (VPN or direct
via a t-1 or other circuit), and provide power for the
phone.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">You
could use an ASA5505 and that does poe and the vpn tunnel all in
one<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; COLOR: #1f497d; FONT-FAMILY: 'Arial','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><B><SPAN
style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'">Matthew
Loraditch</SPAN></B><SPAN
style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'"><BR>1965
Greenspring Drive<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: 'Calibri','sans-serif'">Timonium,
MD 21093 <BR><A href="mailto:support@heliontechnologies.com"><SPAN
style="COLOR: black">support@heliontechnologies.com</SPAN></A><BR>(p) (410)
252-8830<BR>(F) (443) 541-1593<BR><BR>Visit us at <A
href="http://www.heliontechnologies.com"><SPAN
style="COLOR: black">www.heliontechnologies.com</SPAN></A> <BR>Support Issue?
Email <A href="mailto:support@heliontechnologies.com"><SPAN
style="COLOR: black">support@heliontechnologies.com</SPAN></A> for fast
assistance!</SPAN><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p></o:p></SPAN></P></DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<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'">
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net]
<B>On Behalf Of </B>Miller, Steve<BR><B>Sent:</B> Thursday, May 07, 2009 9:34
AM<BR><B>To:</B> Cisco VOIP<BR><B>Subject:</B> [cisco-voip] Deploying 7961
Phones Remotely with ASA5500?<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Simple
question:</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">What hardware is
required (if any) at the remote location to allow a Cisco phone to work?
My understanding was that hardware was unnecessary....that the phone could just
hang off a regular Linksys router at a person's home. Please advise. Thank
you!</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<P><STRONG>Steve Miller</STRONG><BR>Telecom Engineer<BR>Dickstein Shapiro
LLP<BR>1825 Eye Street NW | Washington, DC 20006<BR>Tel (202) 420-3370| Fax
(202) 330-5607<BR><A
href="mailto:MillerS@dicksteinshapiro.com">MillerS@dicksteinshapiro.com</A><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'"> </SPAN><o:p></o:p></P>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV><PRE>--------------------------------------------------------<o:p></o:p></PRE><PRE>This e-mail message and any attached files are confidential and are intended solely for the use of the addressee(s)<o:p></o:p></PRE><PRE>named above. This communication may contain material protected by attorney-client, work product, or other <o:p></o:p></PRE><PRE>privileges. If you are not the intended recipient or person responsible for delivering this confidential<o:p></o:p></PRE><PRE>communication to the intended recipient, you have received this communication in error, and any review, use, <o:p></o:p></PRE><PRE>dissemination, forwarding, printing, copying, or other distribution of this e-mail message and any attached files <o:p></o:p></PRE><PRE>is strictly prohibited. Dickstein Shapiro reserves the right to monitor any communication that is created, <o:p></o:p></PRE><PRE>received, or sent on its network. If you have received this confidential communication in error, please notify the <o:p></o:p></PRE><PRE>sender immediately by reply e-mail message and permanently delete the original message. <o:p></o:p></PRE><PRE><o:p> </o:p></PRE><PRE>To reply to our email administrator directly, send an email to postmaster@dicksteinshapiro.com<o:p></o:p></PRE><PRE><o:p> </o:p></PRE><PRE>Dickstein Shapiro LLP<o:p></o:p></PRE><PRE>http://www.DicksteinShapiro.com<o:p></o:p></PRE><PRE><o:p> </o:p></PRE><PRE>==============================================================================<o:p></o:p></PRE><PRE>--------------------------------------------------------<o:p></o:p></PRE><PRE>This e-mail message and any attached files are confidential and are intended solely for the use of the addressee(s)<o:p></o:p></PRE><PRE>named above. This communication may contain material protected by attorney-client, work product, or other <o:p></o:p></PRE><PRE>privileges. If you are not the intended recipient or person responsible for delivering this confidential<o:p></o:p></PRE><PRE>communication to the intended recipient, you have received this communication in error, and any review, use, <o:p></o:p></PRE><PRE>dissemination, forwarding, printing, copying, or other distribution of this e-mail message and any attached files <o:p></o:p></PRE><PRE>is strictly prohibited. Dickstein Shapiro reserves the right to monitor any communication that is created, <o:p></o:p></PRE><PRE>received, or sent on its network. If you have received this confidential communication in error, please notify the <o:p></o:p></PRE><PRE>sender immediately by reply e-mail message and permanently delete the original message. <o:p></o:p></PRE><PRE><o:p> </o:p></PRE><PRE>To reply to our email administrator directly, send an email to postmaster@dicksteinshapiro.com<o:p></o:p></PRE><PRE><o:p> </o:p></PRE><PRE>Dickstein Shapiro LLP<o:p></o:p></PRE><PRE>http://www.DicksteinShapiro.com<o:p></o:p></PRE><PRE><o:p> </o:p></PRE><PRE>==============================================================================<o:p></o:p></PRE></DIV>
<P><pre wrap>--------------------------------------------------------
This e-mail message and any attached files are confidential and are intended solely for the use of the addressee(s)
named above. This communication may contain material protected by attorney-client, work product, or other
privileges. If you are not the intended recipient or person responsible for delivering this confidential
communication to the intended recipient, you have received this communication in error, and any review, use,
dissemination, forwarding, printing, copying, or other distribution of this e-mail message and any attached files
is strictly prohibited. Dickstein Shapiro reserves the right to monitor any communication that is created,
received, or sent on its network. If you have received this confidential communication in error, please notify the
sender immediately by reply e-mail message and permanently delete the original message.
To reply to our email administrator directly, send an email to postmaster@dicksteinshapiro.com
Dickstein Shapiro LLP
http://www.DicksteinShapiro.com
==============================================================================
</pre></P></BODY></HTML>