<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">Nice !</div><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">Thankx</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><br></div><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 Tue, Sep 22, 2015 at 3:08 PM, Daniel Grotti <span dir="ltr"><<a href="mailto:dgrotti@sipwise.com" target="_blank">dgrotti@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>
we already have it on our roadmap (internal ticket MT#0009327)<br>
I already noticed that not-fully-compliant point to rfc.<br>
We will provide a solution for that in the future, cannot say why though.<br>
<span class=""><br>
<br>
--<br>
Daniel Grotti<br>
VoIP Engineer<br>
<br>
<br>
Sipwise GmbH<br>
Europaring F15 | 2345 Brunn am Gebirge, Austria | <a href="http://www.sipwise.com" rel="noreferrer" target="_blank">www.sipwise.com</a><br>
<br>
</span><span class="">On 09/22/2015 04:04 PM, Marco Teixeira wrote:<br>
> Hi Daniel,<br>
><br>
> Thank you for your reply.<br>
> Please consider getting it onto your roadmap to keep your amazing<br>
> product RFC compliant.<br>
><br>
> For clarity here is the link i forgot to past (i guess)<br>
> <a href="https://support.software.dell.com/kb/sw10958" rel="noreferrer" target="_blank">https://support.software.dell.com/kb/sw10958</a><br>
><br>
> ---<br>
> Best regards<br>
> Marco<br>
><br>
><br>
> On Tue, Sep 22, 2015 at 2:57 PM, Daniel Grotti <<a href="mailto:dgrotti@sipwise.com">dgrotti@sipwise.com</a><br>
</span><span class="">> <mailto:<a href="mailto:dgrotti@sipwise.com">dgrotti@sipwise.com</a>>> wrote:<br>
><br>
> Hi Marco,<br>
> SPCE does not fallback in TCP unfortunately.<br>
> you should reduce the MTU by removing headers or you should be able to<br>
> rebuild your fragmented packets at the final destination.<br>
><br>
> --<br>
> Daniel Grotti<br>
> VoIP Engineer<br>
><br>
><br>
> Sipwise GmbH<br>
> Europaring F15 | 2345 Brunn am Gebirge, Austria | <a href="http://www.sipwise.com" rel="noreferrer" target="_blank">www.sipwise.com</a><br>
</span>> <<a href="http://www.sipwise.com" rel="noreferrer" target="_blank">http://www.sipwise.com</a>><br>
<div><div class="h5">><br>
> On 09/21/2015 11:27 PM, Marco Teixeira wrote:<br>
> > Hi there,<br>
> ><br>
> > I might have stumbled upon the issue described here (but without<br>
> any ALG<br>
> > in the middle, just for example, as i can't pass any sensitive<br>
> info here)<br>
> ><br>
> > I'm seeing fragmented SIP packets when the final gateway sends OPTION<br>
> > back over 2 NGCP CE and over to a final farm of SIP servers...<br>
> ><br>
> > The call is established correctly and only when the OPTIONs don't get<br>
> > ACK, the call drops within 10 seconds (always).<br>
> ><br>
> > So, according to the test on that link, trancript below:<br>
> > (..) If a request is within 200 bytes of the path MTU, or if it is<br>
> larger<br>
> > than 1300 bytes and the path MTU is unknown, the request MUST<br>
> be sent<br>
> > using an RFC 2914 [43] congestion controlled transport<br>
> protocol, such<br>
> > as TCP. (...)<br>
> ><br>
> > Shouldn't SIPWISE activate TCP or whatever to avoid this ?<br>
> > How did you guys solve this ?<br>
> > (no, TCP on all calls is really asking for trouble on the call volume<br>
> > i'm aimming for)<br>
> ><br>
> ><br>
> > Best regards<br>
> > Marco<br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > Spce-user mailing list<br>
</div></div>> > <a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a> <mailto:<a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a>><br>
<span class="">> > <a href="https://lists.sipwise.com/listinfo/spce-user" rel="noreferrer" target="_blank">https://lists.sipwise.com/listinfo/spce-user</a><br>
> ><br>
> _______________________________________________<br>
> Spce-user mailing list<br>
</span>> <a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a> <mailto:<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/listinfo/spce-user</a><br>
><br>
><br>
</blockquote></div><br></div></div>