<!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:m =
"http://schemas.microsoft.com/office/2004/12/omml"><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; COLOR: black; FONT-FAMILY: "Times New Roman","serif"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; COLOR: black; FONT-FAMILY: "Times New Roman","serif"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; COLOR: black; 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
}
PRE {
FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; COLOR: black; FONT-FAMILY: "Courier New"; mso-style-priority: 99; mso-style-link: "HTML Preformatted Char"
}
SPAN.HTMLPreformattedChar {
COLOR: black; FONT-FAMILY: Consolas; mso-style-priority: 99; mso-style-link: "HTML Preformatted"; mso-style-name: "HTML Preformatted Char"
}
SPAN.EmailStyle19 {
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 bgColor=white>
<DIV dir=ltr align=left><SPAN class=709250919-07052009><FONT face=Arial
color=#0000ff size=2>Does the corp directory work?</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> Matt Slaga (US)
[mailto:Matt.Slaga@us.didata.com] <BR><B>Sent:</B> Thursday, May 07, 2009 3:07
PM<BR><B>To:</B> Wes Sisk; Jason Burns<BR><B>Cc:</B> Cisco VOIP; Matthew
Loraditch; Miller, Steve<BR><B>Subject:</B> RE: [cisco-voip] 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'">I’m
assuming the ASA is going to run PhoneProxy. At home, I have a 7960
plugged into a Linksys WRT54 that works just fine. No DMZ or port
forwarding is configured. We’ve been running the phoneproxy since it was
Metreos with mixed results. Been really solid though on the
ASA.<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>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><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>
<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; COLOR: windowtext; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; COLOR: windowtext; FONT-FAMILY: 'Tahoma','sans-serif'">
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net]
<B>On Behalf Of </B>Wes Sisk<BR><B>Sent:</B> Thursday, May 07, 2009 2:56
PM<BR><B>To:</B> Jason Burns<BR><B>Cc:</B> Cisco VOIP; Matthew Loraditch;
Miller, Steve<BR><B>Subject:</B> Re: [cisco-voip] Deploying 7961 Phones Remotely
with ASA5500?<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Hmm, I'm going to need a little more convincing on this
one.<BR><BR>phone1----------homerouter-----------ASA--(typical enterprise with
cm)--phone2<BR>10.10.11.2 10.10.11.1 10.10.10.76
<BR>*homerouter doubles as a firewall as is common<BR><BR>In the ORCAck that
leaves phone1 offers to receive audio on 10.10.11.2 port 33333.<BR>homerouter is
blissfully unaware of SCCP so passes the IP datagram along after rewriting IP
headers for the 10.10.10.76 network<BR>this gets through ASA with any
translation it does, then on to CM, then on to phone2.<BR><BR>phone2 begins to
transmit audio. Audio goes to the IP:Port fixed up by ASA. ASA
rewrites IP and UDP and passes along back toward home router.<BR><BR>Now comes
the challenge. homerouter never knew it should listen on port 33333.
It would have to be SCCP aware to do that. It would have to be SCCP aware
to rewrite that to any other port number.<BR><BR>So the audio via RTP/UDP/IP is
back to the "outside" interface of homerouter, but how does it get through to
phone1?<BR><BR>/Wes<BR><BR><BR>On Thursday, May 07, 2009 10:47:36 AM, Jason
Burns <A href="mailto:burns.jason@gmail.com"><burns.jason@gmail.com></A>
wrote:<BR><BR><o:p></o:p></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt">Ryan,<BR><BR>Even though the IP
Phone would be embedding it's own private IP address inside of SCCP ORCAck
messages, the ASA Phone Proxy feature would know the message was really sourced
from the public IP. The Phone Proxy would handle that, so that the Linksys
doesn't have to worry about SCCP fixup.<BR><BR>One important caveat is that with
PAT, not al homel routers support a TFTP Client connection like the phone tries
to do to the ASA Phone Proxy.<BR><BR>TFTP is destined to UDP port 69 for the
initial Read Request, then a new connection on an ephemeral port is negotiated,
and not all home routers know to look for this to open the new UDP
Port.<BR><BR>If you run into TFTP problems you will have to configure the IP
Phone's IP to be in the DMZ so that all ports get forwarded to the IP
Phone.<BR><BR>So, the short answer is that just about any home router should
work with the ASA Phone Proxy. Provided you're on the very latest ASA code (as
PhoneProxy is still a very new product).<o:p></o:p></P>
<DIV>
<P class=MsoNormal>On Thu, May 7, 2009 at 10:29 AM, Ryan Ratliff <<A
href="mailto:rratliff@cisco.com">rratliff@cisco.com</A>>
wrote:<o:p></o:p></P>
<P class=MsoNormal>Your Linksys router is going to be doing NAT/PAT and I'm
pretty confident they don't support SCCP fixup. You will need the phone to
either be in the DMZ or have a vpn tunnel behind the Linksys.<BR><BR>-Ryan
<o:p></o:p></P>
<DIV>
<DIV>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><BR><BR>On May 7, 2009, at 10:12
AM, Miller, Steve wrote:<BR><BR>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!<BR><BR>Steve Miller<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"
target=_blank>MillerS@dicksteinshapiro.com</A><BR><BR><BR><BR>From: Matthew
Loraditch [mailto:<A href="mailto:MLoraditch@heliontechnologies.com"
target=_blank>MLoraditch@heliontechnologies.com</A>]<BR>Sent: Thursday, May 07,
2009 10:08 AM<BR>To: Miller, Steve; Cisco VOIP<BR>Subject: RE: Deploying 7961
Phones Remotely with ASA5500?<BR><BR>What do you mean by necessary? If you can
get your Linksys to setup a vpn tunnel then yes<BR><BR><BR><BR><BR><BR>Matthew
Loraditch<BR>1965 Greenspring Drive<BR><BR>Timonium, MD 21093<BR><A
href="mailto:support@heliontechnologies.com"
target=_blank>support@heliontechnologies.com</A><BR>(p) (410) 252-8830<BR>(F)
(443) 541-1593<BR><BR>Visit us at <A href="http://www.heliontechnologies.com"
target=_blank>www.heliontechnologies.com</A><BR>Support Issue? Email <A
href="mailto:support@heliontechnologies.com"
target=_blank>support@heliontechnologies.com</A> for fast
assistance!<BR><BR><BR><BR>From: Miller, Steve [mailto:<A
href="mailto:MillerS@DicksteinShapiro.COM"
target=_blank>MillerS@DicksteinShapiro.COM</A>]<BR>Sent: Thursday, May 07, 2009
10:05 AM<BR>To: Matthew Loraditch<BR>Subject: Re: Deploying 7961 Phones Remotely
with ASA5500?<BR><BR><BR><BR>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><A href="mailto:millers@dicksteinshapiro.com"
target=_blank>millers@dicksteinshapiro.com</A><BR><BR>From: Matthew
Loraditch<BR>To: Miller, Steve; Cisco VOIP<BR>Sent: Thu May 07 09:45:41
2009<BR>Subject: RE: Deploying 7961 Phones Remotely with ASA5500?<BR><BR>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.<BR><BR>You could
use an ASA5505 and that does poe and the vpn tunnel all in
one<BR><BR><BR><BR><BR><BR>Matthew Loraditch<BR>1965 Greenspring
Drive<BR><BR>Timonium, MD 21093<BR><A
href="mailto:support@heliontechnologies.com"
target=_blank>support@heliontechnologies.com</A><BR>(p) (410) 252-8830<BR>(F)
(443) 541-1593<BR><BR>Visit us at <A href="http://www.heliontechnologies.com"
target=_blank>www.heliontechnologies.com</A><BR>Support Issue? Email <A
href="mailto:support@heliontechnologies.com"
target=_blank>support@heliontechnologies.com</A> for fast
assistance!<BR><BR><BR><BR>From: <A
href="mailto:cisco-voip-bounces@puck.nether.net"
target=_blank>cisco-voip-bounces@puck.nether.net</A> [mailto:<A
href="mailto:cisco-voip-" target=_blank>cisco-voip-</A><A
href="mailto:bounces@puck.nether.net" target=_blank>bounces@puck.nether.net</A>]
On Behalf Of Miller, Steve<BR>Sent: Thursday, May 07, 2009 9:34 AM<BR>To: Cisco
VOIP<BR>Subject: [cisco-voip] Deploying 7961 Phones Remotely with
ASA5500?<BR><BR><BR><BR>Simple question:<BR><BR><BR><BR>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!<BR><BR><BR><BR>Steve Miller<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"
target=_blank>MillerS@dicksteinshapiro.com</A><BR><BR><BR><o:p></o:p></P></DIV></DIV>
<P class=MsoNormal>--------------------------------------------------------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
confidentialcommunication 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 <A
href="mailto:postmaster@dicksteinshapiro.com"
target=_blank>postmaster@dicksteinshapiro.com</A> Dickstein Shapiro LLPhttp://<A
href="http://www.DicksteinShapiro.com"
target=_blank>www.DicksteinShapiro.com</A>
==============================================================================--------------------------------------------------------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
confidentialcommunication 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 <A
href="mailto:postmaster@dicksteinshapiro.com"
target=_blank>postmaster@dicksteinshapiro.com</A> Dickstein Shapiro LLPhttp://<A
href="http://www.DicksteinShapiro.com"
target=_blank>www.DicksteinShapiro.com</A>
==============================================================================
<o:p></o:p></P>
<DIV>
<P class=MsoNormal
style="MARGIN-BOTTOM: 12pt"><BR><BR>--------------------------------------------------------
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 <A
href="mailto:postmaster@dicksteinshapiro.com"
target=_blank>postmaster@dicksteinshapiro.com</A> Dickstein Shapiro LLP <A
href="http://">http://</A><A href="http://www.DicksteinShapiro.com"
target=_blank>www.DicksteinShapiro.com</A>
==============================================================================<o:p></o:p></P></DIV>
<P class=MsoNormal>_______________________________________________<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>_______________________________________________<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><o:p></o:p></P></DIV>
<P class=MsoNormal><BR><BR><o:p></o:p></P><PRE><o:p> </o:p></PRE><PRE style="TEXT-ALIGN: center">
<HR align=center width="90%" SIZE=4>
</PRE><PRE><o:p> </o:p></PRE><PRE>_______________________________________________<o:p></o:p></PRE><PRE>cisco-voip mailing list<o:p></o:p></PRE><PRE><A href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><o:p></o:p></PRE><PRE><A href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><o:p></o:p></PRE><PRE> <o:p></o:p></PRE>
<P class=MsoNormal><o:p> </o:p></P></DIV>
<P>
<HR SIZE=1>
<P></P>
<P><STRONG>Disclaimer: This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the designated
addressee(s) named above only. If you are not the intended addressee, you are
hereby notified that you have received this communication in error and that any
use or reproduction of this email or its contents is strictly prohibited and may
be unlawful. If you have received this communication in error, please notify us
immediately by replying to this message and deleting it from your computer.
Thank you. </STRONG></P>
<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>