<html 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" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
/* 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;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
..MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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 link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Do you have a ‘fixup protocol sip’ option in the SLB (where you
are Nating)?<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <b>On
Behalf Of </b>Andy Saykao<br>
<b>Sent:</b> Friday, February 08, 2008 1:49 AM<br>
<b>To:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> [cisco-voip] Is there a way to rewrite SIP headers?<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Traffic
Flow:</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:10.0pt;font-family:"Arial","sans-serif"'>External
Calls -> PortaBilling / SIP Gateway (203.10.x.x) -> Cisco SLB Load
Balancer (210.15.x.x) -> Either CCM1 (172.16.55.5) OR CCM2 (172.16.55.6)
-> User Agent</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:10.0pt;font-family:"Arial","sans-serif"'>What
we are finding is that the Cisco SLB (load balancing) is working ok and
the packet reaches one of the CCM's - but the CCM's are discarding the packet
because inside the SIP header, the TO: address does not contain the IP address
of the CCM (see packet capture below taken from the CCM end). </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:10.0pt;font-family:"Arial","sans-serif"'>>
INVITE sip:613xxxxxxxx@210.15.x.x:5060 SIP/2.0<br>
> Via: SIP/2.0/UDP<br>
> 203.10.x.x<br>
> :5061;branch=z9hG4bK4a2139daf022d80af26275540f1b5722;rport<br>
> Max-Forwards: 70<br>
> From:<br>
> <sip:0404xxxxxx@203.10.x.x>;tag=171a2a27c0d677b4b142551fa092f0f0<br>
> To: <sip:613xxxxxxxx@210.15.x.x><br>
> Call-ID: <a href="mailto:1C6F6260-D46511DC-84E280E4-D0AAFDDC@203.10.x.x">1C6F6260-D46511DC-84E280E4-D0AAFDDC@203.10.x.x</a><br>
> CSeq: 200 INVITE<br>
> Contact: Anonymous <sip:203.10.x.x:5061><br>
> Expires: 300<br>
> User-Agent: Sippy</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:10.0pt;font-family:"Arial","sans-serif"'>You
can see that once the packet reaches the CCM, it STILL contains the address of
the SLB virtual IP (210.15.x.x) in the SIP header. Is there a way to change the
sip header information in the To: field. We need 210.15.x.x. rewritten to point
to our Cisco Call Manager (172.16.55.5 or 172.16.55.6) so that the packet
won't be discarded and call setup can continue.</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:10.0pt;font-family:"Arial","sans-serif"'>This
is our SLB config:</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:10.0pt;font-family:"Arial","sans-serif"'>ip
slb serverfarm CCM-REAL<br>
nat server<br>
predictor leastconns<br>
real 172.16.55.5<br>
inservice<br>
real 172.16.55.6<br>
inservice<br>
!<br>
ip slb vserver CCM-VIRT-TCP<br>
virtual 210.15.x.x tcp 0<br>
serverfarm CCM-REAL<br>
inservice<br>
!<br>
ip slb vserver CCM-VIRT-UDP<br>
virtual 210.15.x.x udp 0<br>
serverfarm CCM-REAL<br>
inservice</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:10.0pt;font-family:"Arial","sans-serif"'><br>
Thanks.</span><o:p></o:p></p>
</div>
<p><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>This email
and any files transmitted with it are confidential and intended solely for the
use of the individual or entity to whom they are addressed. Please notify the
sender immediately by email if you have received this email by mistake and
delete this email from your system. Please note that any views or opinions
presented in this email are solely those of the author and do not necessarily
represent those of the organisation. Finally, the recipient should check this
email and any attachments for the presence of viruses. The organisation accepts
no liability for any damage caused by any virus transmitted by this email.</span><o:p></o:p></p>
</div>
</body>
</html>
<HTML><BODY><P><hr size=1></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></BODY></HTML>