<div dir="ltr"><div dir="ltr">Hi Adrian, </div><div dir="ltr"><br><div>Issue seems to be linked with large number of chunks in a transfer.<br><div>We have tested our setup with Blink client (latest version 0.8.0) and noticed that client is chunking file at around 60k bytes per chunk. at this rate there are far fewer chunks compared to our scenario where chunking is done for every 2k bytes. <br>
</div><div><br></div><div>When we configure our client to chunk at 60k its behavior is much similar to Blink; majority of file transfers are succeeding however there are still some failures similar to Blink client (on transferring 30 files [~5mb each] simultaneously between two Blink clients 2 got cancelled automatically).</div>
<div><br></div><div>To identify data corruption I have generated a file containing numbers in increasing order and transferred this file over tcp. In wireshark we can clearly see that file is sent to server successfully however at receiving end additional bytes (portion of 7 hyphens transaction id built by source client) are present. Please have a look at these wireshark captures uploaded here <a href="http://msrprelay.org/issues/2501" target="_blank">http://msrprelay.org/issues/2501</a>. </div>
</div><div><br></div><div><span style="color:rgb(72,72,72);font-family:'Lucida Grande',verdana,arial,helvetica,sans-serif;font-size:12px;background-color:rgb(255,255,221)">If you watch the tcp stream of data transfer in receivers capture note that "-----" is sent extra after number 58682. similarly after number 115492 "-------YS7dPeoD+\r" is sent extra and lastly after number 270628 "-------O" is sent extra.</span><br>
</div><div><span style="color:rgb(72,72,72);font-family:'Lucida Grande',verdana,arial,helvetica,sans-serif;font-size:12px;background-color:rgb(255,255,221)"><br></span></div><div><span style="color:rgb(72,72,72);font-family:'Lucida Grande',verdana,arial,helvetica,sans-serif;font-size:12px;background-color:rgb(255,255,221)">Thanks & Regards,</span></div>
<div><span style="color:rgb(72,72,72);font-family:'Lucida Grande',verdana,arial,helvetica,sans-serif;font-size:12px;background-color:rgb(255,255,221)">Prasun</span></div><div><span style="color:rgb(72,72,72);font-family:'Lucida Grande',verdana,arial,helvetica,sans-serif;font-size:12px;background-color:rgb(255,255,221)"><br>
</span></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 15, 2014 at 1:48 PM, <span dir="ltr"><<a href="mailto:ag@ag-projects.com" target="_blank">ag@ag-projects.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Well, MSPRelay is used for several years in production and have not heard such coruption problems. I personably transfer lot of large files with it and I never ended up with a corrupted file. Also I use it for chat and screen sharing and always works for me.<div>
<br></div><div>I use Blink as a client. Maybe it has something to do with your client.<br><div><br></div><div>Adrian</div><div><br><div><br></div><div><div><div><div><div class="h5"><div>On 15 Apr 2014, at 08:55, Prasun Bheri <<a href="mailto:prasun.bheri@gmail.com" target="_blank">prasun.bheri@gmail.com</a>> wrote:</div>
<br></div></div><blockquote type="cite"><div><div class="h5"><div dir="ltr">Hi Group,<div>I have configured msrp relay from <a href="http://msrprelay.org/" target="_blank">http://msrprelay.org</a> with plain tcp and did some file transfers.</div>
<div><br></div><div>I find it very unstable as transfer randomly gets aborted midway (relay sends reset to both clients) when doing a 2mb file transfer with small (2k) chunk size. but having a better luck when chunk size is 10k or greater as long as there is single transfer happening. when transferring multiple files one or all the transfers are getting aborted by relay sending reset to clients. </div>
<div><br></div><div>This looks like some buffer issues. </div><div><br></div><div>has anyone faced this or similar problems? if any one know a fix for this please let me know.<br></div><div><br></div><div>These are the configuration options I am using:</div>
<div>address = <a href="http://172.31.5.219:2855/" target="_blank">172.31.5.219:2855</a><br></div><div>debug_notls = yes<br></div><div>backend = memory<br></div><div><div><a href="mailto:55575@54.255.138.50" target="_blank">55575@54.255.138.50</a> = 575.55 ### using public ip </div>
<div><a href="mailto:55576@54.255.138.50" target="_blank">55576@54.255.138.50</a> = 576.55</div></div><div><br></div><div><br></div><div> <br></div><div>moreover at times, data transferred is getting corrupted. I mean received data randomly contains portion of "7 hyphens <transaction id>" sequence sent by sending client. there must be some issue with re-packetization of chunks being forwarded. I raised this as defect here <a href="http://msrprelay.org/issues/2501" target="_blank">http://msrprelay.org/issues/2501</a> </div>
<div><br></div><div>ps: does any one know any other msrp relays servers paid/free that are stable and time tested.</div><div><br></div><div>Thanks & Regards,</div><div>Prasun</div></div></div></div>
_______________________________________________<br>SIPBeyondVoIP mailing list<br><a href="mailto:SIPBeyondVoIP@lists.ag-projects.com" target="_blank">SIPBeyondVoIP@lists.ag-projects.com</a><br><a href="http://lists.ag-projects.com/mailman/listinfo/sipbeyondvoip" target="_blank">http://lists.ag-projects.com/mailman/listinfo/sipbeyondvoip</a><br>
</blockquote></div><br></div></div></div></div></div></blockquote></div><br></div>