Hi Razvan!
Thanks for the tip!
As for the fix, I think OpenSIPS should make sure the data is correct
before putting it on the DB, so that REGISTER should have been rejected.
Now, data might end up bogus on the DB due to bugs, so ignoring the broken
records on startup sounds like a sensible thing
the caching entries are parsed and stored directly in shared memory
fix delimiters default initialisation, now done before script parsing
You can view, comment on, or merge this pull request online at:
https://github.com/OpenSIPS/opensips/pull/731
-- Commit Summary --
* sql_caher: remove pkg
Hi Saul!
Not sure whether the problem is that opensips accepts the bogus Contact header,
or it does not start if the contact in the DB is bogus. Probably both?
The first problem can be solved by using the `sipmsg_validate()` function. Not
sure if we should explicitly validate the contact before
Updated issue name and improved its content. Trevor also configured the OS so
that future corefiles will not overwrite each other. Waiting for a proper
backtrace.
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/730#issuecomment-165839117
Please close this ticket if there are no other issues.
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/712#issuecomment-165811894___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/
Branch: refs/heads/master
Home: https://github.com/OpenSIPS/opensips
Commit: d60503270b887715a473c71092c8109468a64b9b
https://github.com/OpenSIPS/opensips/commit/d60503270b887715a473c71092c8109468a64b9b
Author: ionutrazvanionita
Date: 2015-12-18 (Fri, 18 Dec 2015)
Changed p
