I have a new D40 phone. I have installed Certified Asterisk (1.8.11) and the matching res_digium_phone. I have configured res_digium_phone.conf and the phone is working properly, but the applications are not. If I try to open Contacts, I just get the spinning wheel and “Loading contact list”, and the contacts never appear. The contacts do appear to be loaded, because CLID names appear when dialling or receiving calls.
I have done a SIP debug during the loading of contacts and I can see messages being exchanged between the phone and Asterisk, and there are no error messages, until the end when I get the message “Auto fallthrough, channel ‘Message/ast_msg_queue’ status is ‘UNKNOWN’”
The full message sequence is:
-- 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.3.114:5060") in new stack
-- Executing [proxy@dpma_message_context:3] MessageSend("Message/ast_msg_queue", "digium_phone:blah") in new stack
-- Auto fallthrough, channel 'Message/ast_msg_queue' status is 'UNKNOWN'
-- 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.3.114:5060") in new stack
-- Executing [digium_phone_module@dpma_message_context:3] Set("Message/ast_msg_queue", "MESSAGE_DATA(X-Digium-AppServer-Response-URI)=") in new stack
-- Executing [digium_phone_module@dpma_message_context:4] MessageSend("Message/ast_msg_queue", "sip:192.168.3.114:5060,proxy") in new stack
-- Auto fallthrough, channel 'Message/ast_msg_queue' status is 'UNKNOWN'
Visual voicemail, which also generates these messages, works, but there I get no sound. This might be a codec issue, as it works on everything else. I am sure that the sound worked earlier.
Are these issues all related to the ast_msg_queue messages, or are the separate issues?