<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Dec 17, 2010, at 1:19 PM, Juha Heinanen wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>i reported a month or so back that blink adds transport protocol<br>to request uri based on what it uses for its outbound proxy. for<br>example it sends this kind of request uri when i try to place call<br>tosip:<a href="mailto:3333@sip2sip.info">3333@sip2sip.info</a>: <br><br>INVITE <a href="sip:3333@sip2sip.info;transport=tcp">sip:3333@sip2sip.info;transport=tcp</a> SIP/2.0<br><br>the reply that i got was that it is a bug in pjsip library. when i<br>checked pjsip pages, i noticed that blink is using a pretty old version<br>of that library. perhaps the bug is fixed in later versions?<br><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" color="#144FAE"><br></font></font></div></blockquote><div><br></div><div><div>We cannot 1.2.3. update to a newer pjsip version because we have 40 patches agains the PJSIP library version we use (that is 1.0 branch). Many of them address multi-threading, audio and other core issues that are unlikely to be merged with the public trunk as there will be endless debates about them.</div><div><br></div><div>If there is something relevant to fix like this problem we have to back port if the fix exists somewhere in some later version or fix it ourselves with a new patch.</div><div><br></div><div>If you know which pjsip version or patch addresses this issue please update this ticket:</div><div><br></div><div><a href="http://sipsimpleclient.com/ticket/132">http://sipsimpleclient.com/ticket/132</a></div><div><br></div></div><div>Regards,</div><div>Adrian</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></div></body></html>