Branch: refs/heads/master
Home: https://github.com/OpenSIPS/opensips
Commit: 5722f36e38c3e3824d9dee086200d5a1fd9dc411
https://github.com/OpenSIPS/opensips/commit/5722f36e38c3e3824d9dee086200d5a1fd9dc411
Author: Ovidiu Sas
Date: 2016-03-24 (Thu, 24 Mar
@bogdan-iancu The fix seems to work fine for us. The error is gone now.
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Thanks for the fix, I will try out and update you.
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/829#issuecomment-200498948___
Devel
@santhosh-kumar , many thanks for your help in troubleshooting this - I
prepared a fix for this. Please remove the previous patches and apply
(backport) this 2503bc4. Let me know if it fixes your problem.
---
You are receiving this because you are subscribed to this thread.
Reply to this email
Branch: refs/heads/master
Home: https://github.com/OpenSIPS/opensips
Commit: 2503bc4929c86f4601b131c84d664f471e046798
https://github.com/OpenSIPS/opensips/commit/2503bc4929c86f4601b131c84d664f471e046798
Author: Bogdan-Andrei Iancu
Date: 2016-03-23 (Wed,
I've tried your patch and it works!!
Thank you
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/797#issuecomment-200481725___
Devel
@petekelly , could you please test this via commit ea1eb62 ? If it does the
trick for you, I can do a backport.
Thanks, Bogdan
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Branch: refs/heads/master
Home: https://github.com/OpenSIPS/opensips
Commit: ea1eb625acfc2211d3c8c6997c8b8db7e53ccab4
https://github.com/OpenSIPS/opensips/commit/ea1eb625acfc2211d3c8c6997c8b8db7e53ccab4
Author: Bogdan-Andrei Iancu
Date: 2016-03-23 (Wed,
Try this:
https://www.dropbox.com/sh/93j7gdfwk2h5lnq/AACGTMrj6zKaXHjw_YBQBm84a?dl=0
I wasn't able to reproduce the successful case this time. It's failing all the
time.
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Unfortunately, we do not support 1.8 anymore. 1.11 includes so many
fixes and improvements, you really should consider an update!
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com
On 23.03.2016 18:17, surya wrote:
Hi Liviu,
Thanks for responding.
I should have mentioned the
Well, with your initial patch, it would return `0`, while hiding the error. I
consider this to be the correct approach from a scripting perspective,
especially since transformation errors are quite cumbersome.
Input errors can be caught beforehand, if needed, through the use of the regex
Hi Liviu,
Thanks for responding.
I should have mentioned the version I am using is 1.8.4
And this is just for 1 call. I get a coredump of the failure but couldn't
extract much info from it. (Not expert in C and gdb)
Thanks,
Surya
--
View this message in context:
It makes no sense to run with `DBG_MALLOC` in order to troubleshoot a crash,
while enabling compiler optimizations (`-O9`) just to make your life harder. In
this case, OpenSIPS should be compiled with `-O0`.
---
You are receiving this because you are subscribed to this thread.
Reply to this
Branch: refs/heads/master
Home: https://github.com/OpenSIPS/opensips
Commit: b7bd2d7ac839d6eaee6eec18651e0cfcce20ce7d
https://github.com/OpenSIPS/opensips/commit/b7bd2d7ac839d6eaee6eec18651e0cfcce20ce7d
Author: ionutrazvanionita
Date: 2016-03-23
Hi surya,
In the world of multi-threaded programming, the logging level can have a
big impact on program behaviour, so the short answer is: "yes, although
it sounds crazy, it is totally possible!"
To debug your "fail" (crash, error, deadlock), "gdb" and "LM_DBG" logs
are your best friends.
Branch: refs/heads/master
Home: https://github.com/OpenSIPS/opensips
Commit: 06cec362a5cf99309bc47f77e89d217a10349b60
https://github.com/OpenSIPS/opensips/commit/06cec362a5cf99309bc47f77e89d217a10349b60
Author: ionutrazvanionita
Date: 2016-03-23
@santhosh-kumar , there was an issue in the prev patch, please revert it and
use this new one:
https://gist.github.com/bogdan-iancu/fa596f4c99cda796e90a
Also, looking for logs :)
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on
hep_store_no_script parameter now changed into hep_route. Using
this parameter one can either do sip_capture() without going
through the script or define a route where messages can be
forwarded using hep_relay() function and modified if hep version
3 is used, withot parsing the sip message, or go
18 matches
Mail list logo