Hi Razvan!<br>
<br>
Thanks for the tip!<br>
<br>
As for the fix, I think OpenSIPS should make sure the data is correct<br>
before putting it on the DB, so that REGISTER should have been rejected.<br>
<br>
Now, data might end up bogus on the DB due to bugs, so ignoring the broken<br>
records on startup sounds like a sensible thing to do IMHO.<br>
On Dec 18, 2015 6:09 PM, "Răzvan Crainea" <notifications@github.com> wrote:<br>
<br>
> Hi Saul!<br>
><br>
> Not sure whether the problem is that opensips accepts the bogus Contact<br>
> header, or it does not start if the contact in the DB is bogus. Probably<br>
> both?<br>
> The first problem can be solved by using the sipmsg_validate() function.<br>
> Not sure if we should explicitly validate the contact before inserting it<br>
> in the database.<br>
> However, the second problem seems more serious, since OpenSIPS does not<br>
> start, no matter where that Contact header ended up in the database.<br>
><br>
> Will look into this next week.<br>
><br>
> Best regards,<br>
> Răzvan<br>
><br>
> —<br>
> Reply to this email directly or view it on GitHub<br>
> <https://github.com/OpenSIPS/opensips/issues/729#issuecomment-165842055>.<br>
><br>
<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br>Reply to this email directly or <a href="https://github.com/OpenSIPS/opensips/issues/729#issuecomment-165923461">view it on GitHub</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/AFOciRnXBlY8TkwPfJlF-akfN4Q05E-6ks5pRJVegaJpZM4G3dJy.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/issues/729#issuecomment-165923461"></link>
<meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>