Whether you’re working with:
I’m curious to know what challenges you’re currently facing.
Let’s discuss solutions, share experiences, and help each other.
We are currently facing an issue where some calls appear to remain stuck at a Set() application in the dialplan.
The dialplan instruction is:
same => n,Set(CDR(userfield)=none)
We are not seeing any database connection errors. The CDR connection is configured through cdr_pgsql.conf.
The following messages appear in the Asterisk logs:
[Jul 22 17:46:08] ERROR[2149159][C-00000e86] res_pjsip_header_funcs.c: This function requires a header name.
[Jul 23 06:30:58] ERROR[3335921] manager.c: Unable to process manager action 'Ping'. Asterisk is shutting down.
[Jul 23 06:32:02] Asterisk 22.9.0 built by root @ plantila-voice-to-voice-full on a x86_64 running Linux on 2026-04-23 17:17:59 UTC
The applications connected to Asterisk through AMI do not have any task, command, or automation configured to shut down or restart Asterisk.
Has anyone experienced a similar issue where calls appear to stop at Set(CDR(userfield)=...)? Could the AMI Ping error or the PJSIP header error be related, or should we investigate another part of the dialplan or CDR configuration?
This means you aren’t setting a header name when using PJSIP_HEADER. Without seeing actual dialplan, don’t what the real issue is.
It’s not responding to the Ping because Asterisk was in the process of shutting down. You need to figure out why Asterisk was shutting down.
So far you haven’t shown anything related to the Set() issue. Of course it might not be Set()ing something if it’s in the middle of a shutdown process.