search for: sip_resolve_invoke_user_callback

...9;_sip._tcp.iptel.org' res_pjsip/pjsip_resolver.c:349 sip_resolve_callback: [0x7f4e740564e8] SRV record received on target '_sip._udp.iptel.org' res_pjsip/pjsip_resolver.c:419 sip_resolve_callback: [0x7f4e740564e8] Resolution completed - 0 viable targets res_pjsip/pjsip_resolver.c:207 sip_resolve_invoke_user_callback: [0x7f4e740564e8] Invoking user callback with '0' addresses testA: res_pjsip/pjsip_resolver.c:477 sip_resolve: Performing SIP DNS resolution of target 'sip.linphone.org' res_pjsip/pjsip_resolver.c:504 sip_resolve: Transport type for target 'sip.linphone.org' is 'Uns...

...try=0x7f773c633ac8, sent=<optimized out>, sent at entry=-70002) at ../src/pjsip/sip_util.c:1276 #11 0x00007f777bc71b3a in stateless_send_resolver_callback (status=<optimized out>, token=0x7f773c635950, addr=<optimized out>) at ../src/pjsip/sip_util.c:1377 #12 0x00007f77380c3398 in sip_resolve_invoke_user_callback (data=0x7f773c4563c8) at res_pjsip/pjsip_resolver.c:206 #13 0x000055e7c0a6f0e3 in ast_taskprocessor_execute (tps=tps at entry=0x7f775416ebc0) at taskprocessor.c:1302 #14 0x000055e7c0a76d28 in execute_tasks (data=0x7f775416ebc0) at threadpool.c:1352 #15 0x000055e7c0a6f0e3 in ast_taskprocessor_execut...

...quot;Unable to cancel schedule ID" in dtls_srtp_check_pending (Reported by Dade Brandon) * ASTERISK-25168 - Random Core Dumps on Asterisk 13.4 PJSIP, in ast_channel_name at channel_internal_api.c (Reported by Carl Fortin) * ASTERISK-25115 - Crash related to func sip_resolve_invoke_user_callback of res_pjsip/pjsip_resolver.c (Reported by John Bigelow) * ASTERISK-25226 - chan_sip: Channel leak in branch 13 on early replaces call pickup (Reported by Walter Doekes) * ASTERISK-25220 - [patch]Closing of fd -1 in chan_mgcp.c (Reported by Walter Doekes) * ASTERISK-25219 - [pa...

On Wed, Aug 9, 2023 at 3:20 PM Dan Cropp <dcropp at amtelco.com> wrote: > I have a customer who just encountered a crash while running Asterisk > 18.17.1 version. > > > > I’m trying to adapt to the changes so not sure where best to look or how > to possibly report this. > > > > I started by going through >

...quot;Unable to cancel schedule ID" in dtls_srtp_check_pending (Reported by Dade Brandon) * ASTERISK-25168 - Random Core Dumps on Asterisk 13.4 PJSIP, in ast_channel_name at channel_internal_api.c (Reported by Carl Fortin) * ASTERISK-25115 - Crash related to func sip_resolve_invoke_user_callback of res_pjsip/pjsip_resolver.c (Reported by John Bigelow) * ASTERISK-25226 - chan_sip: Channel leak in branch 13 on early replaces call pickup (Reported by Walter Doekes) * ASTERISK-25220 - [patch]Closing of fd -1 in chan_mgcp.c (Reported by Walter Doekes) * ASTERISK-25219 - [pa...

...londe transfer does not result in connected line updates (Reported by Joshua Colp) * ASTERISK-25087 - Asterisk segfault when using Directory application with alias option and specific mailbox configuration (Reported by Chet Stevens) * ASTERISK-25115 - Crash related to func sip_resolve_invoke_user_callback of res_pjsip/pjsip_resolver.c (Reported by John Bigelow) * ASTERISK-25096 - [patch]Segfault when registering over websockets with PJSIP (in ast_sockaddr_isnull at /include/asterisk/netsock2.h) (Reported by Josh Kitchens) * ASTERISK-24963 - ASAN: heap-use-after-free with PJSIP an...

...issues.asterisk.org/jira/browse/ASTERISK-25087>] - Asterisk segfault when using Directory application with alias option and specific mailbox configuration (Reported by Chet Stevens) - [ASTERISK-25115 <https://issues.asterisk.org/jira/browse/ASTERISK-25115>] - Crash related to func sip_resolve_invoke_user_callback of res_pjsip/pjsip_resolver.c (Reported by John Bigelow) - [ASTERISK-25096 <https://issues.asterisk.org/jira/browse/ASTERISK-25096>] - [patch]Segfault when registering over websockets with PJSIP (in ast_sockaddr_isnull at /include/asterisk/netsock2.h) (Reported by Josh Kitchens) -...