<p>Although current behavior barely passes RFC requirements (i.e. it's <strong>correct</strong>), a SIP server should try to be as permissive as possible when <em>receiving</em>, yet strictly adhere to recommended RFC behavior when <em>sending</em>. And appending unnecessary colons to URI usernames doesn't seem to be too recommended.</p>

<p>The fix looks great, since it still propagates existing empty-string passwords, if script writer <em>really</em> needs this. Many thanks, <a href="https://github.com/jarrodb" class="user-mention">@jarrodb</a> !</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br>Reply to this email directly or <a href="https://github.com/OpenSIPS/opensips/pull/598#issuecomment-130203776">view it on GitHub</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/AFOciZdiqjoG8AY4Kr-FYY5UlPBG4Bvfks5omvA0gaJpZM4Fp8rF.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/OpenSIPS/opensips/pull/598#issuecomment-130203776"></link>
  <meta itemprop="name" content="View Pull Request"></meta>
</div>
<meta itemprop="description" content="View this Pull Request on GitHub"></meta>
</div>