Digium DPMA stops working after FreePBX 13 -> 14 upgrade

After upgrading FreePBX from 13 -> 14 our digium phones no longer can retrieve their configuration from DPMA. The phone hangs at:

Contacting sip:proxy@asterisk.cora.nwra.com:5060;transport=udp

asterisk log shows:

[2019-10-20 18:40:27] VERBOSE[2249][C-00000000] pbx.c: Executing [proxy@dpma_message_context:1] Set("Message/ast_msg_queue", "MESSAGE(custom_data)=mark_all_outbound") in new stack
[2019-10-20 18:40:27] VERBOSE[2249][C-00000000] pbx.c: Executing [proxy@dpma_message_context:2] Set("Message/ast_msg_queue", "MESSAGE_DATA(X-Digium-AppServer-Response-URI)=sip:10.11.8.108:5060") in new stack
[2019-10-20 18:40:27] VERBOSE[2249][C-00000000] pbx.c: Executing [proxy@dpma_message_context:3] Set("Message/ast_msg_queue", "MESSAGE_DATA(X-Digium-AppServer-Response-FullContact)=") in new stack
[2019-10-20 18:40:27] VERBOSE[2249][C-00000000] pbx.c: Executing [proxy@dpma_message_context:4] MessageSend("Message/ast_msg_queue", "digium_phone:blah") in new stack
[2019-10-20 18:40:27] VERBOSE[2249][C-00000000] pbx.c: Executing [proxy@dpma_message_context:5] Hangup("Message/ast_msg_queue", "") in new stack
[2019-10-20 18:40:27] VERBOSE[2249][C-00000000] pbx.c: Spawn extension (dpma_message_context, proxy, 5) exited non-zero on 'Message/ast_msg_queue'
[2019-10-20 18:40:27] VERBOSE[2249][C-00000000] pbx.c: Executing [proxy@dpma_message_context:1] Set("Message/ast_msg_queue", "MESSAGE(custom_data)=mark_all_outbound") in new stack
[2019-10-20 18:40:27] VERBOSE[2249][C-00000000] pbx.c: Executing [proxy@dpma_message_context:2] Set("Message/ast_msg_queue", "MESSAGE_DATA(X-Digium-AppServer-Response-URI)=sip:10.11.8.108:5060") in new stack
[2019-10-20 18:40:27] VERBOSE[2249][C-00000000] pbx.c: Executing [proxy@dpma_message_context:3] Set("Message/ast_msg_queue", "MESSAGE_DATA(X-Digium-AppServer-Response-FullContact)=") in new stack
[2019-10-20 18:40:27] VERBOSE[2249][C-00000000] pbx.c: Executing [proxy@dpma_message_context:4] MessageSend("Message/ast_msg_queue", "digium_phone:blah") in new stack
[2019-10-20 18:40:27] VERBOSE[2249][C-00000000] pbx.c: Executing [proxy@dpma_message_context:5] Hangup("Message/ast_msg_queue", "") in new stack
[2019-10-20 18:40:27] VERBOSE[2249][C-00000000] pbx.c: Spawn extension (dpma_message_context, proxy, 5) exited non-zero on 'Message/ast_msg_queue'
[2019-10-20 18:40:27] VERBOSE[2249][C-00000000] pbx.c: Executing [digium_phone_module@dpma_message_context:1] Set("Message/ast_msg_queue", "MESSAGE(custom_data)=mark_all_outbound") in new stack
[2019-10-20 18:40:27] VERBOSE[2249][C-00000000] pbx.c: Executing [digium_phone_module@dpma_message_context:2] Set("Message/ast_msg_queue", "TMP_RESPONSE_URI=sip:10.11.8.108:5060") in new stack
[2019-10-20 18:40:27] VERBOSE[2249][C-00000000] pbx.c: Executing [digium_phone_module@dpma_message_context:3] Set("Message/ast_msg_queue", "MESSAGE_DATA(Request-URI)=") in new stack
[2019-10-20 18:40:27] VERBOSE[2249][C-00000000] pbx.c: Executing [digium_phone_module@dpma_message_context:4] Set("Message/ast_msg_queue", "MESSAGE_DATA(X-Digium-AppServer-Response-URI)=") in new stack
[2019-10-20 18:40:27] VERBOSE[2249][C-00000000] pbx.c: Executing [digium_phone_module@dpma_message_context:5] Set("Message/ast_msg_queue", "MESSAGE_DATA(X-Digium-AppServer-Response-FullContact)=") in new stack
[2019-10-20 18:40:27] VERBOSE[2249][C-00000000] pbx.c: Executing [digium_phone_module@dpma_message_context:6] MessageSend("Message/ast_msg_queue", "sip:10.11.8.108:5060,proxy") in new stack
[2019-10-20 18:40:27] VERBOSE[2249][C-00000000] pbx.c: Executing [digium_phone_module@dpma_message_context:7] Hangup("Message/ast_msg_queue", "") in new stack
[2019-10-20 18:40:27] VERBOSE[2249][C-00000000] pbx.c: Spawn extension (dpma_message_context, digium_phone_module, 7) exited non-zero on 'Message/ast_msg_queue'

Any ideas?

I don’t know the answer, but these questions might help you get this resolved:

  • Do you need chan_pjsip now instead of chan_sip for latest DPMA binary ? This is a major change in the underlying SIP infrastructure in newer versions of Asterisk.
  • Is your local PBX firewall blocking LAN traffic ? Check logs, fail2ban, iptables, etc.
  • Did you try searching on the FreePBX forums ? This is the more generic Asterisk forum.
  • Can you work around the configuration step on the phones, thereby letting them default/revert to their previous saved-in-phone-flash-memory configuration files ? At least this might let you register existing phones while you work on a solution for MACDs in the future.
  • If you manually configure a phone via its web interface, then does it register to your new FreePBX 14 ?
  • How quick can you spin up a backup from your previous FreePBX 13 install ? Most phones let you register to multiple PBXes at the same time, so a new beta 14 could be the secondary registration point while you keep 13 as your primary during your testing phase.