<br><br><div class="gmail_quote">On Wed, Mar 23, 2011 at 6:39 AM, Gustavo Espeche <span dir="ltr"><<a href="mailto:gustavo.espeche@easyipcall.com">gustavo.espeche@easyipcall.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
i'm attaching a tcpdump capture.<br>
Thanks.<br></blockquote><div>Did you actually look at the capture? :D </div><div>You have a ton of these:</div><div><font class="Apple-style-span" face="'courier new', monospace">SIP/2.0 400 Bad To Header</font></div>
<div><br></div><div>So, this has nothing to do with a Diversion Header, it has to do with the fact that you have a '#' in your To Header, which is a no-no. Whoever is sending this invite needs to URL-encode it or remove the # sign. The offending header is this:</div>
<div><br></div><div><div><font class="Apple-style-span" face="'courier new', monospace">To: 548#254722577500 <sip:548#<a href="mailto:254722577500@38.108.107.228">254722577500@38.108.107.228</a>></font></div>
</div><div><br></div><div>Brian West is wondering if this is from a Nextone device? Just curious. Anyway, have them fix the To header and you should be okay. (Note: the Diversion header also needs to have the # URL endcoded.)</div>
<div><br></div><div>-MC</div><div><br></div><div>P.S. - If they get their knickers in a twist over the URL encoding then throw the RFC at them:</div><div><a href="http://www.ietf.org/rfc/rfc1738.txt">http://www.ietf.org/rfc/rfc1738.txt</a></div>
<div><br></div><div>Specifically, page 2 under "Unsafe:" you have this sentence:</div><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><pre>The character "#" is unsafe and should always be encoded because it is used in World Wide Web and in other systems to delimit a URL from a fragment/anchor identifier that might follow it.</pre>
</div></div>