Re: [OpenSIPS-Devel] [opensips] Opensips 1.10 segfault (#113)
sorry you cannot access at server because its in private lan however i can send all file you need Michele N. Il 15/12/13 21:02, Bogdan Andrei IANCU ha scritto: Any chances to get access to the corefile on the machine were it was generated ? — Reply to this email directly or view it on GitHub https://github.com/OpenSIPS/opensips/issues/113#issuecomment-30618788. --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/issues/113#issuecomment-30653893___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] [opensips] pua_dialoginfo: failed calls triggers sending PUBLISH errors (#142)
Hi Bogdan, The main reason why I added that setting in the first place was to workaround the SIP PUBLISH problem in OpenSIPS. We wanted to minimize the number of PUBLISH being sent. For example, when you call a device that is BUSY, you will be notified through a PUBLISH that there was a call attempt, then that the call was finished, instantly. With the unordered PUBLISH problems, the BLF was most of the time stuck in a wrong state. In general, even if that specific problem has been fixed, I think that it is preferable to minimize state changes on servers with many users, and many BLFs, It is probably best to be notified as soon as the call is ringing state, but not before to prevent such rapid state changes. I would keep the option, but I would apply Ovidiu's suggesting : when the publish_on_trying parameter is disabled, we should not try publishing the terminated state. Moreover, the RFC 4235 states: 3.10. Rate of Notifications For reasons of congestion control, it is important that the rate of notifications not be excessive. It is RECOMMENDED that the server not generate notifications for a single subscriber faster than once every 1 second. So I think that trying - terminated instant transitions should be prevented, and that is what the publish_on-trying option is trying to do. --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/issues/142#issuecomment-30655605___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] [opensips] pua_dialoginfo: failed calls triggers sending PUBLISH errors (#142)
Hello Damien, Please update the documentation with what you described here. I suggest to set the default value of the parameter to '1' and let the admin to choose not to signal/publish the 'trying' state. Can you also take a look and fix the issue that was introduced by this new parameter: the bogus error probe? Thanks, Ovidiu --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/issues/142#issuecomment-30669079___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] [opensips] pua_dialoginfo: failed calls triggers sending PUBLISH errors (#142)
Hi Ovidiu, I can change the default value, and adapt the documentation. Please note that the trying state corresponds to dialoginfo_set being called in the dialplan. Not to the remote peer answering with a 100 Trying. However, fixing the bogus error probe seems difficult. I can't see a way in pua_dialoginfo to prevent publishing the terminated state if there was no previous publication (ie if we did not reach the trying state when publish_on_trying is set to 0). There is actually no way to determine the state before the callback is triggered. Do you, or Bogdan, have an implementation suggestion ? --- Reply to this email directly or view it on GitHub: https://github.com/OpenSIPS/opensips/issues/142#issuecomment-30681836___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [OpenSIPS/opensips] 9d25d0: opensipsctl: new command 'trap'
Branch: refs/heads/master Home: https://github.com/OpenSIPS/opensips Commit: 9d25d0c7cf4391ca85bb25a23e2e933e6878a48a https://github.com/OpenSIPS/opensips/commit/9d25d0c7cf4391ca85bb25a23e2e933e6878a48a Author: Ovidiu Sas o...@voipembedded.com Date: 2013-12-16 (Mon, 16 Dec 2013) Changed paths: M scripts/opensipsctl M scripts/opensipsctl.base M scripts/opensipsctlrc Log Message: --- opensipsctl: new command 'trap' - useful to get a full bt dump of all opensips processes - handy in dead-lock investigatigations ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [OpenSIPS/opensips] 55bde1: Makefile.conf.template: add newline at end of file
Branch: refs/heads/master Home: https://github.com/OpenSIPS/opensips Commit: 55bde1d8e2d3d387a796e2a9ed8fcbd6876185d3 https://github.com/OpenSIPS/opensips/commit/55bde1d8e2d3d387a796e2a9ed8fcbd6876185d3 Author: Ovidiu Sas o...@voipembedded.com Date: 2013-12-16 (Mon, 16 Dec 2013) Changed paths: M Makefile.conf.template Log Message: --- Makefile.conf.template: add newline at end of file ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] [OpenSIPS/opensips] f2d32e: Makefile.conf.template: add newline at end of file
Branch: refs/heads/1.10 Home: https://github.com/OpenSIPS/opensips Commit: f2d32ec4e5f20e412a2353372b90c8710cd59900 https://github.com/OpenSIPS/opensips/commit/f2d32ec4e5f20e412a2353372b90c8710cd59900 Author: Ovidiu Sas o...@voipembedded.com Date: 2013-12-16 (Mon, 16 Dec 2013) Changed paths: M Makefile.conf Log Message: --- Makefile.conf.template: add newline at end of file (cherry picked from commit 55bde1d8e2d3d387a796e2a9ed8fcbd6876185d3) ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
