I currently have several asterisk servers up at various locations (several old and scheduled to be replaced.) We are getting this error daily on a new rollout and I am wondering if anyone else has come across it and if there is a suggested fix to correct it.
It ends up taking the place of the ast_msg_queue message traffic and is cleared by doing a core restart when convenient. We also tend to see the Unable to write to alert pipe on Message/ast_msg_queue error come up before it eventually becomes the “tps is NULL!”
(Example of what we don’t see anymore after the error arrives)
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:10.87.1.178:5060”) in new stack
– Executing [digium_phone_module@dpma_message_context:3] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(Request-URI)=sip:10.87.1.178: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:10.87.1.178:5060,proxy”) in new stack
Asterisk 12.4.0 loaded from Asterisk’s rpm
DPMA
About 100 Digium D40, D70, and D50 phones using LLDP with firmware version=1_4_2_0_63880
Linux 2.6.32-431.23.3.el6.x86_64 #1 SMP Thu Jul 31 17:20:51 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ((Centos 6.5))