<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">Thankx Andreas,</div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">Question is, this was working before on 3.8.7 and simptoms started aftrer upgrading to 3.8.9.</div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">Like i said, on the forum there is at least one finding witch stated a smaller base64 hash...</div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">Did this hash increase in size between the two versions?<br></div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small"><br></div><div class="gmail_extra"><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">=Marco</div><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><span style="background-color:rgb(255,255,255)"><font face="tahoma, sans-serif"><br></font></span></div></div></div></div>
<br><div class="gmail_quote">On Fri, Mar 24, 2017 at 1:27 PM, Andreas Granig <span dir="ltr"><<a href="mailto:agranig@sipwise.com" target="_blank">agranig@sipwise.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
There is no limit in the SIP RFC (unless I overlooked something), and<br>
different vendors handle it differently. E.g. the Dialogic SBC has a<br>
limit at 1024, see<br>
<a href="https://www.dialogic.com/webhelp/BorderNet2020/2.1.0/WebHelp/sip_message_header_restrict.htm" rel="noreferrer" target="_blank">https://www.dialogic.com/<wbr>webhelp/BorderNet2020/2.1.0/<wbr>WebHelp/sip_message_header_<wbr>restrict.htm</a>.<br>
<br>
Actually not much you can do here. The ngcpct is there to work around<br>
issues for other user-agents, which don't handle a Contact of 127.0.0.1<br>
very well, which we used to send in certain scenarios (which is also<br>
totally fine in theory, but in practice breaks some clients). Therefore<br>
we put the IP of the kamailio-lb there and store the original one in<br>
masked form in the ngcpct param and reconstruct it in other scenarios.<br>
<br>
Andreas<br>
<span class=""><br>
On 03/23/2017 07:47 PM, Marco Teixeira wrote:<br>
> So... searching around the mailing list archives, I can see that in the<br>
> ngcpct parameter was 22 chars shorter back in 2014...<br>
> <a href="https://lists.sipwise.com/pipermail/spce-user/2014-January/005675.html" rel="noreferrer" target="_blank">https://lists.sipwise.com/<wbr>pipermail/spce-user/2014-<wbr>January/005675.html</a><br>
><br>
> is this something I can manipulate? the length of ngcpct?<br>
><br>
> =Marco<br>
><br>
><br>
> On Thu, Mar 23, 2017 at 6:20 PM, Marco Teixeira <<a href="mailto:admin@marcoteixeira.com">admin@marcoteixeira.com</a><br>
</span><span class="">> <mailto:<a href="mailto:admin@marcoteixeira.com">admin@marcoteixeira.<wbr>com</a>>> wrote:<br>
><br>
> Forgot to mention, the peer is a Metaswitch Perimeta SBC.<br>
><br>
> =Marco<br>
><br>
><br>
> On Thu, Mar 23, 2017 at 6:04 PM, Marco Teixeira<br>
</span><span class="">> <<a href="mailto:admin@marcoteixeira.com">admin@marcoteixeira.com</a> <mailto:<a href="mailto:admin@marcoteixeira.com">admin@marcoteixeira.<wbr>com</a>>> wrote:<br>
><br>
> Hi list,<br>
><br>
> Trying to figure out a problem where calls incoming from peer<br>
> get dropped around 900 secs.<br>
> Peer vendor claiming the issue is, and I quote:<br>
><br>
> "(...) because the request-uri is >160 bytes. (...) The reason<br>
> the Request-URI is so long is due to the long contact header<br>
> coming from 1.2.3.4 -<br>
> Contact: <<a href="http://sip:ngcp-lb@1.2.3.4:5060" rel="noreferrer" target="_blank">sip:ngcp-lb@1.2.3.4:5060</a><br>
</span>> <<a href="http://sip:ngcp-lb@1.2.3.4:5060" rel="noreferrer" target="_blank">http://sip:ngcp-lb@1.2.3.4:<wbr>5060</a>>;ngcpct=<wbr>7369703a3332372e302e302e313a35<wbr>3338303b707278726f7574653d33>"<br>
<span class="">> Please ask the customer to reduce the length of the ngcpct<br>
> parameter coming from their SIP server."<br>
><br>
> Has anyone ever came across this issue?<br>
> Is 160 bytes limits even on the SIP RFC?<br>
> How can i shorten or stop using ngcpct parameter in contact?<br>
><br>
> Apreciate your help,<br>
> Marco<br>
><br>
><br>
><br>
><br>
><br>
</span>> ______________________________<wbr>_________________<br>
> Spce-user mailing list<br>
> <a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a><br>
> <a href="https://lists.sipwise.com/listinfo/spce-user" rel="noreferrer" target="_blank">https://lists.sipwise.com/<wbr>listinfo/spce-user</a><br>
><br>
______________________________<wbr>_________________<br>
Spce-user mailing list<br>
<a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a><br>
<a href="https://lists.sipwise.com/listinfo/spce-user" rel="noreferrer" target="_blank">https://lists.sipwise.com/<wbr>listinfo/spce-user</a><br>
</blockquote></div><br></div></div>