similar to: [asterisk 13.9] pjsip: Extensions always lost after short period of time

Good day. Asterisk 13.7.2, res_pjsip. There is a problem of loss of registration of several devices. This happens not on all devices, but problem devices a lot. Below is the log of registration of a contact of one device. Is suspect two things: 1. delete a contact after the contact is added. But, like, it's a feature of code that may already be fixed. 2. deleting a contact much earlier

Hello! I occasionally can see warnings like these during *idle* times in asterisk log (asterisk 13.7.2): [2016-06-05 06:11:51] WARNING[27817] pjsip: sip_transactio Unable to register REGISTER transaction (key xists) [2016-06-05 06:11:51] WARNING[27817] pjsip: sip_transactio Unable to register REGISTER transaction (key exists) Nothing more. The third REGISTER package works as expected.

The Asterisk Development Team would like to announce the release of asterisk-18.21.0. The release artifacts are available for immediate download at https://github.com/asterisk/asterisk/releases/tag/18.21.0 and https://downloads.asterisk.org/pub/telephony/asterisk This release resolves issues reported by the community and would have not been possible without your participation. Thank You!

The Asterisk Development Team would like to announce the release of asterisk-18.21.0. The release artifacts are available for immediate download at https://github.com/asterisk/asterisk/releases/tag/18.21.0 and https://downloads.asterisk.org/pub/telephony/asterisk This release resolves issues reported by the community and would have not been possible without your participation. Thank You!

Hello everyone. I allow myself to submit a problem that I can not solve with my VOIP provider Orange in France [2023-06-08 13:19:03] ERROR[185091]: res_pjsip/pjsip_configuration.c:1044 from_user_handler: Error configuring endpoint 'Biv_Sortie' - 'from_user' field contains invalid character '@' [2023-06-08 13:19:03] ERROR[185091]: config_options.c:798 aco_process_var:

The Asterisk Development Team would like to announce the release of asterisk-20.6.0. The release artifacts are available for immediate download at https://github.com/asterisk/asterisk/releases/tag/20.6.0 and https://downloads.asterisk.org/pub/telephony/asterisk This release resolves issues reported by the community and would have not been possible without your participation. Thank You!

The Asterisk Development Team would like to announce the release of asterisk-20.6.0. The release artifacts are available for immediate download at https://github.com/asterisk/asterisk/releases/tag/20.6.0 and https://downloads.asterisk.org/pub/telephony/asterisk This release resolves issues reported by the community and would have not been possible without your participation. Thank You!

The Asterisk Development Team would like to announce the release of asterisk-21.1.0. The release artifacts are available for immediate download at https://github.com/asterisk/asterisk/releases/tag/21.1.0 and https://downloads.asterisk.org/pub/telephony/asterisk This release resolves issues reported by the community and would have not been possible without your participation. Thank You!

The Asterisk Development Team would like to announce the release of asterisk-21.1.0. The release artifacts are available for immediate download at https://github.com/asterisk/asterisk/releases/tag/21.1.0 and https://downloads.asterisk.org/pub/telephony/asterisk This release resolves issues reported by the community and would have not been possible without your participation. Thank You!

On 06/11/2017 at 06:51 PM Joshua Colp wrote: > On Sun, Jun 11, 2017, at 01:47 PM, Joshua Colp wrote: >> The distributor is in res/res_pjsip/pjsip_distributor.c, the distributor >> function being the entry point. That function returning PJ_TRUE >> indicates to PJSIP that it has been handled and no subsequent modules >> should be called by that running thread. The

Hello! unchanged asterisk crashes during udptl / t.38 negotiation with telekom - they do not support t.38 / udptl. In detail: fax client -> asterisk -> telekom -> easybell -> asterisk -> fax server Fax server sends t.38 reinvite via asterisk to easybell. Session Description Protocol Version (v): 0 Owner/Creator, Session Id (o): - 2447581897 4 IN IP4 46.17.15.23

On Sun, Jun 11, 2017, at 01:31 PM, Michael Maier wrote: > On 06/11/2017 at 04:39 PM Joshua Colp wrote: > > On Sun, Jun 11, 2017, at 11:34 AM, Michael Maier wrote: > > > > <snip> > > > >>> > >>> PJSIP uses a dispatch model. The request is queued up, acted on, and > >>> then that's it. The act of acting on it removes it from

On 06/14/2017 at 10:17 PM, Joshua Colp wrote: > On Wed, Jun 14, 2017, at 05:09 PM, Michael Maier wrote: > > <snip> > >> >> I can now say, that asterisk / pjsip seams to work *mostly* as expected. >> Just one exception - and that's the package in question, which can't be >> seen in tcpdump. >> >> I extended the above patch by adding

asterisk-16.13.0-rc2. Fedora 32 pjsip won't load because of undefined symbols: [Sep 4 14:19:25] ERROR[141137]: loader.c:2396 load_modules: Error loading module 'func_pjsip_aor.so': /usr/lib64/asterisk/modules/func_pjsip_aor.so: undefined symbol: ast_sip_location_retrieve_aor_contacts [Sep 4 14:19:25] ERROR[141137]: loader.c:2396 load_modules: Error loading module

On 06/14/2017 at 05:53 PM Joshua Colp wrote: > On Wed, Jun 14, 2017, at 12:47 PM, Michael Maier wrote: > > <snip> > >> >> I added this patch to see, if really all packages are are freed after >> they have been processed: >> >> --- b/res/res_pjsip/pjsip_distributor.c 2017-05-30 19:44:16.000000000 >> +0200 >> +++

On Mon, Jun 5, 2017, at 04:26 PM, Michael Maier wrote: > On 06/05/2017 at 06:29 PM, Joshua Colp wrote: > > On Mon, Jun 5, 2017, at 01:22 PM, Michael Maier wrote: > >> > >> Do you have any idea where to start to look at? Adding additional output > >> in the source code? Which functions could be interesting? I may add own > >> debug code to see why things

The Asterisk Development Team has announced the release of Asterisk 13.10.0. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk The release of Asterisk 13.10.0 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following are the issues resolved in this release:

The Asterisk Development Team has announced the release of Asterisk 13.10.0. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/asterisk The release of Asterisk 13.10.0 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following are the issues resolved in this release:

The Asterisk Development Team would like to announce the release of Certified Asterisk 13.18-cert1. This release is available for immediate download at http://downloads.asterisk.org/pub/telephony/certified-asterisk The release of Certified Asterisk 13.18-cert1 resolves several issues reported by the community and would have not been possible without your participation. Thank you! The following

On Sun, Jun 11, 2017, at 11:34 AM, Michael Maier wrote: <snip> > > > > PJSIP uses a dispatch model. The request is queued up, acted on, and > > then that's it. The act of acting on it removes it from the queue. > > That's the *expected* behavior ... . I rechecked again and again. All > existing tcpdumps. The "resent" package isn't part of