Is there a way of suppressing the digium_phone_module messages on the console. The console fills up with them, and I cannot find a verbose level that hides them:
Which messages?
DIalplan messages aren’t suppressed because it’s actually executing things out of the dpma_message_context. Asterisk has no capability to not log a particular context of dialplan to the console.
I think I have the same question, I have loads of DPMA messages on my console and it makes troubleshooting almost impossible from the Asterisk CLI because of the amount of DPMA messages.
For example, I log on to the Asterisk CLI to look into a problem only to be bombarded with DPMA messages which makes it next to impossible to troubleshoot any other problems.
Is there are way to suppress DPMA messages so that the Asterisk CLI is useful again? I’m running 11.4. Below is a cut and paste of 3 seconds of the CLI
-- Executing [proxy@dpma_message_context:1] Set("Message/ast_msg_queue", "MESSAGE(custom_data)=mark_all_outbound") in new stack
-- Executing [proxy@dpma_message_context:2] Set("Message/ast_msg_queue", "MESSAGE_DATA(X-Digium-AppServer-Response-URI)=sip:192.168.245.33:5060") in new stack
-- Executing [proxy@dpma_message_context:3] Set("Message/ast_msg_queue", "MESSAGE_DATA(X-Digium-AppServer-Response-FullContact)=sip:192.168.245.33:5060;ob") in new stack
-- Executing [proxy@dpma_message_context:4] MessageSend("Message/ast_msg_queue", "digium_phone:blah") in new stack
-- Executing [proxy@dpma_message_context:5] Hangup("Message/ast_msg_queue", "") in new stack
[Nov 13 15:50:29] WARNING[2335][C-00000000]: channel.c:1332 __ast_queue_frame: Unable to write to alert pipe on Message/ast_msg_queue (qlen = 124): Resource temporarily unavailable!
== Spawn extension (dpma_message_context, proxy, 5) exited non-zero on ‘Message/ast_msg_queue’
– Executing [digium_phone_module@dpma_message_context:1] Set(“Message/ast_msg_queue”, “MESSAGE(custom_data)=mark_all_outbound”) in new stack
– Executing [digium_phone_module@dpma_message_context:2] Set(“Message/ast_msg_queue”, “TMP_RESPONSE_URI=sip:192.168.245.33:5060”) in new stack
– Executing [digium_phone_module@dpma_message_context:3] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(Request-URI)=sip:192.168.245.33:5060;ob”) in new stack
– Executing [digium_phone_module@dpma_message_context:4] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-URI)=”) in new stack
– Executing [digium_phone_module@dpma_message_context:5] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-FullContact)=”) in new stack
– Executing [digium_phone_module@dpma_message_context:6] MessageSend(“Message/ast_msg_queue”, “sip:192.168.245.33:5060,proxy”) in new stack
– Executing [digium_phone_module@dpma_message_context:7] Hangup(“Message/ast_msg_queue”, “”) in new stack
[Nov 13 15:50:29] WARNING[2335][C-00000000]: channel.c:1332 __ast_queue_frame: Unable to write to alert pipe on Message/ast_msg_queue (qlen = 125): Resource temporarily unavailable!
== Spawn extension (dpma_message_context, digium_phone_module, 7) exited non-zero on ‘Message/ast_msg_queue’
== Extension Changed auto_hint_4774[internal] new state Idle for Notify User 4774
== Extension Changed auto_hint_4718[internal] new state Idle for Notify User 4718
– Executing [proxy@dpma_message_context:1] Set(“Message/ast_msg_queue”, “MESSAGE(custom_data)=mark_all_outbound”) in new stack
– Executing [proxy@dpma_message_context:2] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-URI)=sip:192.168.245.49:5060”) in new stack
– Executing [proxy@dpma_message_context:3] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-FullContact)=sip:192.168.245.49:5060;ob”) in new stack
– Executing [proxy@dpma_message_context:4] MessageSend(“Message/ast_msg_queue”, “digium_phone:blah”) in new stack
– Executing [proxy@dpma_message_context:5] Hangup(“Message/ast_msg_queue”, “”) in new stack
[Nov 13 15:50:34] WARNING[2335][C-00000000]: channel.c:1332 __ast_queue_frame: Unable to write to alert pipe on Message/ast_msg_queue (qlen = 126): Resource temporarily unavailable!
== Spawn extension (dpma_message_context, proxy, 5) exited non-zero on ‘Message/ast_msg_queue’
== Parsing ‘/var/spool/asterisk/voicemail/default/4537/Old/msg0000.txt’: Found
== Parsing ‘/var/spool/asterisk/voicemail/default/4537/Old/msg0001.txt’: Found
== Parsing ‘/var/spool/asterisk/voicemail/default/4537/Old/msg0002.txt’: Found
== Parsing ‘/var/spool/asterisk/voicemail/default/4537/Old/msg0003.txt’: Found
== Parsing ‘/var/spool/asterisk/voicemail/default/4537/Old/msg0004.txt’: Found
== Parsing ‘/var/spool/asterisk/voicemail/default/4537/Old/msg0005.txt’: Found
== Parsing ‘/var/spool/asterisk/voicemail/default/4537/Old/msg0006.txt’: Found
== Parsing ‘/var/spool/asterisk/voicemail/default/4537/Old/msg0007.txt’: Found
== Parsing ‘/var/spool/asterisk/voicemail/default/4537/Old/msg0008.txt’: Found
– Executing [digium_phone_module@dpma_message_context:1] Set(“Message/ast_msg_queue”, “MESSAGE(custom_data)=mark_all_outbound”) in new stack
– Executing [digium_phone_module@dpma_message_context:2] Set(“Message/ast_msg_queue”, “TMP_RESPONSE_URI=sip:192.168.245.49:5060”) in new stack
– Executing [digium_phone_module@dpma_message_context:3] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(Request-URI)=sip:192.168.245.49:5060;ob”) in new stack
– Executing [digium_phone_module@dpma_message_context:4] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-URI)=”) in new stack
– Executing [digium_phone_module@dpma_message_context:5] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-FullContact)=”) in new stack
– Executing [digium_phone_module@dpma_message_context:6] MessageSend(“Message/ast_msg_queue”, “sip:192.168.245.49:5060,proxy”) in new stack
– Executing [digium_phone_module@dpma_message_context:7] Hangup(“Message/ast_msg_queue”, “”) in new stack
[Nov 13 15:50:34] WARNING[2335][C-00000000]: channel.c:1332 __ast_queue_frame: Unable to write to alert pipe on Message/ast_msg_queue (qlen = 127): Resource temporarily unavailable!
== Spawn extension (dpma_message_context, digium_phone_module, 7) exited non-zero on ‘Message/ast_msg_queue’
– Executing [digium_phone_module@dpma_message_context:1] Set(“Message/ast_msg_queue”, “MESSAGE(custom_data)=mark_all_outbound”) in new stack
– Executing [digium_phone_module@dpma_message_context:2] Set(“Message/ast_msg_queue”, “TMP_RESPONSE_URI=sip:192.168.245.49:5060”) in new stack
– Executing [digium_phone_module@dpma_message_context:3] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(Request-URI)=sip:192.168.245.49:5060;ob”) in new stack
– Executing [digium_phone_module@dpma_message_context:4] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-URI)=”) in new stack
– Executing [digium_phone_module@dpma_message_context:5] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-FullContact)=”) in new stack
– Executing [digium_phone_module@dpma_message_context:6] MessageSend(“Message/ast_msg_queue”, “sip:192.168.245.49:5060,proxy”) in new stack
– Executing [digium_phone_module@dpma_message_context:7] Hangup(“Message/ast_msg_queue”, “”) in new stack
[Nov 13 15:50:34] WARNING[2335][C-00000000]: channel.c:1304 __ast_queue_frame: Exceptionally long queue length queuing to Message/ast_msg_queue
[Nov 13 15:50:34] WARNING[2335][C-00000000]: channel.c:1332 __ast_queue_frame: Unable to write to alert pipe on Message/ast_msg_queue (qlen = 128): Resource temporarily unavailable!
== Spawn extension (dpma_message_context, digium_phone_module, 7) exited non-zero on ‘Message/ast_msg_queue’
– Executing [digium_phone_module@dpma_message_context:1] Set(“Message/ast_msg_queue”, “MESSAGE(custom_data)=mark_all_outbound”) in new stack
– Executing [digium_phone_module@dpma_message_context:2] Set(“Message/ast_msg_queue”, “TMP_RESPONSE_URI=sip:192.168.245.49:5060”) in new stack
– Executing [digium_phone_module@dpma_message_context:3] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(Request-URI)=sip:192.168.245.49:5060;ob”) in new stack
– Executing [digium_phone_module@dpma_message_context:4] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-URI)=”) in new stack
– Executing [digium_phone_module@dpma_message_context:5] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-FullContact)=”) in new stack
– Executing [digium_phone_module@dpma_message_context:6] MessageSend(“Message/ast_msg_queue”, “sip:192.168.245.49:5060,proxy”) in new stack
– Executing [digium_phone_module@dpma_message_context:7] Hangup(“Message/ast_msg_queue”, “”) in new stack
[Nov 13 15:50:34] WARNING[2335][C-00000000]: channel.c:1332 __ast_queue_frame: Unable to write to alert pipe on Message/ast_msg_queue (qlen = 65): Resource temporarily unavailable!
== Spawn extension (dpma_message_context, digium_phone_module, 7) exited non-zero on ‘Message/ast_msg_queue’
– Executing [proxy@dpma_message_context:1] Set(“Message/ast_msg_queue”, “MESSAGE(custom_data)=mark_all_outbound”) in new stack
– Executing [proxy@dpma_message_context:2] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-URI)=sip:192.168.245.20:5060”) in new stack
– Executing [proxy@dpma_message_context:3] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-FullContact)=sip:192.168.245.20:5060;ob”) in new stack
– Executing [proxy@dpma_message_context:4] MessageSend(“Message/ast_msg_queue”, “digium_phone:blah”) in new stack
– Executing [proxy@dpma_message_context:5] Hangup(“Message/ast_msg_queue”, “”) in new stack
[Nov 13 15:50:34] WARNING[2335][C-00000000]: channel.c:1332 __ast_queue_frame: Unable to write to alert pipe on Message/ast_msg_queue (qlen = 66): Resource temporarily unavailable!
== Spawn extension (dpma_message_context, proxy, 5) exited non-zero on ‘Message/ast_msg_queue’
– Executing [digium_phone_module@dpma_message_context:1] Set(“Message/ast_msg_queue”, “MESSAGE(custom_data)=mark_all_outbound”) in new stack
– Executing [digium_phone_module@dpma_message_context:2] Set(“Message/ast_msg_queue”, “TMP_RESPONSE_URI=sip:192.168.245.20:5060”) in new stack
– Executing [digium_phone_module@dpma_message_context:3] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(Request-URI)=sip:192.168.245.20:5060;ob”) in new stack
– Executing [digium_phone_module@dpma_message_context:4] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-URI)=”) in new stack
– Executing [digium_phone_module@dpma_message_context:5] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-FullContact)=”) in new stack
– Executing [digium_phone_module@dpma_message_context:6] MessageSend(“Message/ast_msg_queue”, “sip:192.168.245.20:5060,proxy”) in new stack
– Executing [digium_phone_module@dpma_message_context:7] Hangup(“Message/ast_msg_queue”, “”) in new stack
[Nov 13 15:50:34] WARNING[2335][C-00000000]: channel.c:1332 __ast_queue_frame: Unable to write to alert pipe on Message/ast_msg_queue (qlen = 67): Resource temporarily unavailable!
== Spawn extension (dpma_message_context, digium_phone_module, 7) exited non-zero on ‘Message/ast_msg_queue’
In my opinion the best way to debug a server with high load of calls/messages is using the full log combined with the grep utility.
For example if you are looking for an incoming call based on the CID 2222222 you can execute:
That command will give every otuput containing the cid 22222 then you can use the number in the brackets after the word VERBOSE and grep that number, it will output all the call leg.
I add always to my pbx 3 functions to my bashrc:
sf1 () { cat /var/log/asterisk/full | grep "$1"; }
sf2 () { cat /var/log/asterisk/full | grep "$1" | grep "$2"; }
sf3 () { cat /var/log/asterisk/full | grep "$1" | grep "$2" | grep "$3"; }
That allow me to search based on cid or verbose id, id and date or id, date and cid.
Thanks, that’s pretty much what I have to do and I also send logs to logstash.
however, I was just wondering if there was a way to suppress all the DPMA message because I never read them and it just make my CLI scroll. On servers which I haven’t rolled out DPMA, I I still use the CLI and for some issues it’s quick and easy to use.
Thanks for you input though.
I agree. I just implemented some D70’s into my environment and I LOVE the features they bring over my old Cisco 7960’s but the already busy CLI has become unusable with only 3 test phones in the environment. I can’t imagine adding 40 or so…
The messages are much less verbose if you set verbosity to 2 but that removes much of what I look at during troubleshooting. If the whole deal could be moved up one verbosity level that would make it perfect. That way if for some reason I needed to see them I could set verbosity to 4 instead of 3.