Re: [OpenSIPS-Devel] [opensips] Invalid Insert Query to missed calls (#703)

I've attached a small patch which fixed this for me. [acc.txt](https://github.com/OpenSIPS/opensips/files/117573/acc.txt) @razvancrainea could you take a look and see if it is sane? --- Reply to this email directly or view it on GitHub:

Re: [OpenSIPS-Devel] [opensips] topology_hiding + 302 response (#656)

Hi, is this something that might be considered soon? --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/issues/656#issuecomment-172813067___ Devel mailing list Devel@lists.opensips.org

Re: [OpenSIPS-Devel] [opensips] topology_hiding + 302 response (#656)

Hi @bogdan-iancu! - Yes, and multiple Contact headers too if multiple are sent --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/issues/656#issuecomment-172817036___ Devel mailing list Devel@lists.opensips.org

Re: [OpenSIPS-Devel] [opensips] Possible bug in 2.1 implementation of force_send_socket (#690)

Hi Razvan, I have emailed the logs. Hope they make sense :) Pete --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/issues/690#issuecomment-154014859___ Devel mailing list Devel@lists.opensips.org

Re: [OpenSIPS-Devel] [opensips] Possible bug in 2.1 implementation of force_send_socket (#690)

Not sure if this is related, but if OpenSIPS receives an INVITE as a TLS UAS then the bug also occurs in the Contact generated by OpenSIPS: ~ Contact: #should be 5061 ~ --- Reply to this email directly or view it on GitHub:

[OpenSIPS-Devel] [opensips] Possible bug in 2.1 implementation of force_send_socket (#690)

I am trying to relay a SUBSCRIBE message onwards to another proxy using the force_send_socket() function to force the use of TLS. The relay is working as expected, however OpenSIPS is not populating the Record-Route headers correctly on relay. Instead of using the TLS port it is putting the

Re: [OpenSIPS-Devel] [opensips] memset all connection memory to 0 to avoid unwanted values (ad8011a)

@ionutrazvanionita Thank you, it looks like that has done the trick. --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/commit/ad8011a02116456a5d111664246aaf6d5b8674d2#commitcomment-13585778___ Devel mailing list

[OpenSIPS-Devel] [opensips] dialplan causes crash on startup (#655)

I am running OpenSIPS 2.1 latest from git, and seeing a strange issue with dialplan module in conjunction with postgresql. Basically opensips will not start, even with an empty dialplan table and is terminated with a SIGBUS. The problem still happens with some rows in dialplan table, but

[OpenSIPS-Devel] [opensips] topology_hiding + 302 response (#656)

if you are using topology hiding and the UAS sends a 302, the data (new $ru) in the Contact header is not persisted to the UAC, meaning topology hiding is not valid in a scenario where a 302 may be found. It would be useful (even if it was a per module setting or per transaction flag) to allow

Re: [OpenSIPS-Devel] [opensips] Opensips crash on CANCEL on unanswerd call. (2.1-rc2) (#484)

Some further info @vladpaiu - this seems very connected to failure route. If there is a failure route defined (even one that does only a simple xlog) then opensips will crash on failure response. I feel sure it must be related to script somehow too as I have other 2.1 scripts which exhibit no

Re: [OpenSIPS-Devel] [opensips] Intermittent segmentation fault in flat_db_insert when acc db_missed_flag param is set [2.1] (#559)

@razvancrainea I was still seeing this bug yesterday on a vanilla 2.1 install, did it get backported to 2.1? I admit I did not hugely investigate the cause, however it was very reproducible within some SIPP scripts, and when I stopped setting the missed_call flag the bug stopped - in this

Re: [OpenSIPS-Devel] [opensips] Opensips crash on CANCEL on unanswerd call. (2.1-rc2) (#484)

Managed to get a core dump for this: Core was generated by `/usr/local/opensips/sbin/opensips -P /var/run/opensips/opensips.pid -m 64 -M 64'. Program terminated with signal SIGABRT, Aborted. #0 0x7f86d7b2a107 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56

Re: [OpenSIPS-Devel] [opensips] Opensips crash on CANCEL on unanswerd call. (2.1-rc2) (#484)

I am also seeing this problem in a certain scenario, the output from opensips in logs is: Jun 30 15:54:52 lab-pett-opensips2 scp1a[13568]: CRITICAL:tm:free_faked_req: pkg_free() on shm ptr 0x7fd12f2aeb30 - aborting! It seems you have hit a programming bug. --- Reply to this email directly or