Voicemail, Call Parking, New Phone Registration Suddenly Fails

configuration
Tags: #<Tag:0x00007f24c5784a38>

#1

Nothing has changed on my network. Nothing was changed on the FreePbx unit. However, today I was made aware pulling voicemails on our Digium 50 phones and trying to view the parked calls on the phones does not work. It looks like this type of function uses many of the same operations as the registration when setting up new phones as it pulls data from the server. This is failing as I tried to reconfigure my phone after a factory reset to try and correct the issues. I have no idea what is going on. This is an older setup, details below.

FreePBX 12.0.76.6
CentOs centos-release-6-5.el6.centos.11.2.x86_64

Everything has worked great for a long time, no changes or additions in long time as well. I have tried multiple things.

Nat settings confirmed. Local networks added to Local Networks, External Network shows my public IP address as I have a remote unit and others are on local networks connected via VPN connections through firewalls. Nothing has changed with firewall settings anywhere. I have rebooted all network equipment. I have tried registering a phone from the local network that the PBX is on and it fails. It’s almost like the unit isn’t responding to 5060 requests or something. I have turned on and off ip tables on the centos machine. I have cleared the ip tables, added allow all configuration, no luck with anything I try.

I have tried to restore from multiple backups, 3 weeks ago and 2 weeks ago prior to the issues. Nothing has worked. I’m really struggling to understand what is happening and or what happened. Any help would be amazing.

I found this in the logs (Message dropped because of lacking session id), looked like it might be an issue. Same thing shows up when I try and register a new phone and or use a phone with an old config and try and pull up the voicemail visual display or look at the parked calls on the phone display. I can simply dial in the voicemail or dial the parked call to pick it up, if I know the extension without issues. But displaying these things fails. The message says error communicating with server or something similar.

Log with full details and asterisk -r sip set debug off.

[2021-06-02 00:00:51] VERBOSE[6974] chan_sip.c: Scheduling destruction of SIP dialog ‘-KdXi8DcuTPUphdMPSmmF4cNh-dW28c4’ in 32000 ms (Method: REGISTER)
[2021-06-02 00:00:51] VERBOSE[6974] chan_sip.c: Really destroying SIP dialog ‘CL29Yqmjjj-rQkQgActLNB7ajb8M.oQj’ Method: MESSAGE
[2021-06-02 00:00:51] VERBOSE[6974] chan_sip.c: Really destroying SIP dialog ‘W9l2.1BBUykvUvt4ED.6bZOWhmEwzudd’ Method: REGISTER
[2021-06-02 00:00:53] VERBOSE[6974] chan_sip.c: Really destroying SIP dialog ‘Z3e-9YXlCAgLE.Bj8nIIST42jLW6FgWQ’ Method: REGISTER
[2021-06-02 00:00:57] VERBOSE[26363] asterisk.c: – Remote UNIX connection disconnected
[2021-06-02 00:01:05] NOTICE[6974] chan_sip.c: Received SIP subscribe for peer without mailbox: 1401
[2021-06-02 00:01:10] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:1] Set(“Message/ast_msg_queue”, “MESSAGE(custom_data)=mark_all_outbound”) in new stack
[2021-06-02 00:01:10] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:2] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-URI)=sip:192.168.255.105:5060”) in new stack
[2021-06-02 00:01:10] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:3] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-FullContact)=sip:192.168.255.105:5060;ob”) in new stack
[2021-06-02 00:01:10] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:4] MessageSend(“Message/ast_msg_queue”, “digium_phone:blah”) in new stack
[2021-06-02 00:01:10] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:5] Hangup(“Message/ast_msg_queue”, “”) in new stack
[2021-06-02 00:01:10] VERBOSE[6957][C-00000000] pbx.c: == Spawn extension (dpma_message_context, proxy, 5) exited non-zero on ‘Message/ast_msg_queue’
[2021-06-02 00:01:10] WARNING[6995] phone_message.c: Session could not be created due to invalid credentials
[2021-06-02 00:01:17] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:1] Set(“Message/ast_msg_queue”, “MESSAGE(custom_data)=mark_all_outbound”) in new stack
[2021-06-02 00:01:17] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:2] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-URI)=sip:192.168.255.119:5060”) in new stack
[2021-06-02 00:01:17] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:3] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-FullContact)=sip:192.168.255.119:5060;ob”) in new stack
[2021-06-02 00:01:17] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:4] MessageSend(“Message/ast_msg_queue”, “digium_phone:blah”) in new stack
[2021-06-02 00:01:17] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:5] Hangup(“Message/ast_msg_queue”, “”) in new stack
[2021-06-02 00:01:17] VERBOSE[6957][C-00000000] pbx.c: == Spawn extension (dpma_message_context, proxy, 5) exited non-zero on ‘Message/ast_msg_queue’
[2021-06-02 00:01:17] WARNING[6995] phone_message.c: Message dropped because of lacking session id
[2021-06-02 00:01:20] NOTICE[6974] chan_sip.c: Received SIP subscribe for peer without mailbox: 1403
[2021-06-02 00:01:25] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:1] Set(“Message/ast_msg_queue”, “MESSAGE(custom_data)=mark_all_outbound”) in new stack
[2021-06-02 00:01:25] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:2] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-URI)=sip:192.168.255.119:5060”) in new stack
[2021-06-02 00:01:25] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:3] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-FullContact)=sip:192.168.255.119:5060;ob”) in new stack
[2021-06-02 00:01:25] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:4] MessageSend(“Message/ast_msg_queue”, “digium_phone:blah”) in new stack
[2021-06-02 00:01:25] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:5] Hangup(“Message/ast_msg_queue”, “”) in new stack
[2021-06-02 00:01:25] VERBOSE[6957][C-00000000] pbx.c: == Spawn extension (dpma_message_context, proxy, 5) exited non-zero on ‘Message/ast_msg_queue’
[2021-06-02 00:01:25] WARNING[6995] phone_message.c: Message dropped because of lacking session id
[2021-06-02 00:01:26] NOTICE[6974] chan_sip.c: Received SIP subscribe for peer without mailbox: 1311
[2021-06-02 00:01:26] NOTICE[6974] chan_sip.c: Peer ‘1209’ is now UNREACHABLE! Last qualify: 1006
[2021-06-02 00:01:26] VERBOSE[6962] chan_sip.c: == Extension Changed auto_hint_1209[from-internal] new state Unavailable for Notify User 1209 (queued)
[2021-06-02 00:01:26] VERBOSE[6962] chan_sip.c: == Extension Changed auto_hint_1209[from-internal] new state Unavailable for Notify User 1209 (queued)
[2021-06-02 00:01:26] VERBOSE[6962] chan_sip.c: == Extension Changed auto_hint_1209[from-internal] new state Unavailable for Notify User 1209 (queued)
[2021-06-02 00:01:26] VERBOSE[6962] chan_sip.c: == Extension Changed auto_hint_1209[from-internal] new state Unavailable for Notify User 1204
[2021-06-02 00:01:26] VERBOSE[6962] chan_sip.c: == Extension Changed auto_hint_1209[from-internal] new state Unavailable for Notify User 1210
[2021-06-02 00:01:26] VERBOSE[6962] chan_sip.c: == Extension Changed auto_hint_1209[from-internal] new state Unavailable for Notify User 1220
[2021-06-02 00:01:26] VERBOSE[6962] chan_sip.c: == Extension Changed auto_hint_1209[from-internal] new state Unavailable for Notify User 1202
[2021-06-02 00:01:26] VERBOSE[6962] chan_sip.c: == Extension Changed auto_hint_1209[from-internal] new state Unavailable for Notify User 1203
[2021-06-02 00:01:26] VERBOSE[6962] chan_sip.c: == Extension Changed auto_hint_1209[from-internal] new state Unavailable for Notify User 1207
[2021-06-02 00:01:26] VERBOSE[6962] chan_sip.c: == Extension Changed auto_hint_1209[from-internal] new state Unavailable for Notify User 1201
[2021-06-02 00:01:26] VERBOSE[6962] chan_sip.c: == Extension Changed auto_hint_1209[from-internal] new state Unavailable for Notify User 1200
[2021-06-02 00:01:26] VERBOSE[6962] chan_sip.c: == Extension Changed auto_hint_1209[from-internal] new state Unavailable for Notify User 1208
[2021-06-02 00:01:27] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:1] Set(“Message/ast_msg_queue”, “MESSAGE(custom_data)=mark_all_outbound”) in new stack
[2021-06-02 00:01:27] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:2] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-URI)=sip:192.168.255.102:5060”) in new stack
[2021-06-02 00:01:27] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:3] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-FullContact)=sip:192.168.255.102:5060;ob”) in new stack
[2021-06-02 00:01:27] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:4] MessageSend(“Message/ast_msg_queue”, “digium_phone:blah”) in new stack
[2021-06-02 00:01:27] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:5] Hangup(“Message/ast_msg_queue”, “”) in new stack
[2021-06-02 00:01:27] VERBOSE[6957][C-00000000] pbx.c: == Spawn extension (dpma_message_context, proxy, 5) exited non-zero on ‘Message/ast_msg_queue’
[2021-06-02 00:01:27] WARNING[6995] phone_message.c: Message dropped because of lacking session id
[2021-06-02 00:01:28] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:1] Set(“Message/ast_msg_queue”, “MESSAGE(custom_data)=mark_all_outbound”) in new stack
[2021-06-02 00:01:28] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:2] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-URI)=sip:192.168.255.119:5060”) in new stack
[2021-06-02 00:01:28] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:3] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-FullContact)=sip:192.168.255.119:5060;ob”) in new stack
[2021-06-02 00:01:28] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:4] MessageSend(“Message/ast_msg_queue”, “digium_phone:blah”) in new stack
[2021-06-02 00:01:28] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:5] Hangup(“Message/ast_msg_queue”, “”) in new stack
[2021-06-02 00:01:28] VERBOSE[6957][C-00000000] pbx.c: == Spawn extension (dpma_message_context, proxy, 5) exited non-zero on ‘Message/ast_msg_queue’
[2021-06-02 00:01:28] WARNING[6995] phone_message.c: Message dropped because of lacking session id
[2021-06-02 00:01:32] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:1] Set(“Message/ast_msg_queue”, “MESSAGE(custom_data)=mark_all_outbound”) in new stack
[2021-06-02 00:01:32] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:2] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-URI)=sip:192.168.255.119:5060”) in new stack
[2021-06-02 00:01:32] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:3] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-FullContact)=sip:192.168.255.119:5060;ob”) in new stack
[2021-06-02 00:01:32] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:4] MessageSend(“Message/ast_msg_queue”, “digium_phone:blah”) in new stack
[2021-06-02 00:01:32] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:5] Hangup(“Message/ast_msg_queue”, “”) in new stack
[2021-06-02 00:01:32] VERBOSE[6957][C-00000000] pbx.c: == Spawn extension (dpma_message_context, proxy, 5) exited non-zero on ‘Message/ast_msg_queue’
[2021-06-02 00:01:32] WARNING[6995] phone_message.c: Message dropped because of lacking session id

Log with full details and asterisk -r sip set debug on.

ÿ<------------->
[2021-06-01 23:49:29] VERBOSE[6974] chan_sip.c: — (12 headers 0 lines) —
[2021-06-01 23:49:29] VERBOSE[6974] chan_sip.c: Sending to 192.168.255.104:5060 (no NAT)
[2021-06-01 23:49:29] VERBOSE[6974] chan_sip.c:
ÿ<— Transmitting (no NAT) to 192.168.255.104:5060 —>
ÿSIP/2.0 401 Unauthorized
ÿVia: SIP/2.0/UDP 192.168.255.104:5060;branch=z9hG4bKPjLLGUBQDr-oj2atQ88J4wCMv8.a2T7Fga;received=192.168.255.104;rport=5060
ÿFrom: “Lindsey S <1209>” <sip:1209@192.168.255.1>;tag=BbLiOY3V4SpruXyy0VgrbbYTMnsrcEQ0
ÿTo: “Lindsey S <1209>” <sip:1209@192.168.255.1>;tag=as1ced9978
ÿCall-ID: vaD5WfA-d4JGZWP1Y.N34f9AliwhdZ98
ÿCSeq: 37779 REGISTER
ÿServer: FPBX-12.0.76.6(11.12.0)
ÿAllow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
ÿSupported: replaces, timer
ÿWWW-Authenticate: Digest algorithm=MD5, realm=“asterisk”, nonce=“401cdf47”
ÿContent-Length: 0
ÿ
ÿ
ÿ<------------>
[2021-06-01 23:49:29] VERBOSE[6974] chan_sip.c: Scheduling destruction of SIP dialog ‘vaD5WfA-d4JGZWP1Y.N34f9AliwhdZ98’ in 32000 ms (Method: REGISTER)
[2021-06-01 23:49:30] VERBOSE[6974] chan_sip.c:
ÿ<— SIP read from UDP:192.168.255.119:5060 —>
ÿMESSAGE sip:proxy@192.168.255.1:5060 SIP/2.0
ÿVia: SIP/2.0/UDP 192.168.255.119:5060;rport;branch=z9hG4bKPjJtFL-jmrbOlsRiNPBcVlkO-I2BM514Ko
ÿMax-Forwards: 70
ÿFrom: <sip:192.168.255.119>;tag=l0V2hKDwEfpZdPhrFJ2xC.uGZgvP2ZFC
ÿTo: <sip:proxy@192.168.255.1>
ÿCall-ID: CFGi9dXFiFaQXiibCc8daLm4elrI0-2A
ÿCSeq: 45098 MESSAGE
ÿAccept: text/plain, application/im-iscomposing+xml
ÿContact: <sip:192.168.255.119:5060;ob>
ÿUser-Agent: Digium D50 1_4_2_1_73372
ÿX-Digium-User-Agent: Digium D50 1_4_2_1_73372
ÿX-Digium-AppServer-ID: aeprox572964212
ÿX-Digium-AppServer-MACAddress: 000FD309D0C3
ÿX-Digium-AppServer-RequestType: AsteriskRequest
ÿContent-Type: text/plain
ÿContent-Length: 388
ÿ
ÿAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
ÿ<------------->
[2021-06-01 23:49:30] VERBOSE[6974] chan_sip.c: — (16 headers 1 lines) —
[2021-06-01 23:49:30] VERBOSE[6974] chan_sip.c: Sending to 192.168.255.119:5060 (NAT)
[2021-06-01 23:49:30] VERBOSE[6974] chan_sip.c: Receiving message!
[2021-06-01 23:49:30] VERBOSE[6974] chan_sip.c: Looking for proxy in dpma_message_context (domain 192.168.255.1)
[2021-06-01 23:49:30] VERBOSE[6974] chan_sip.c:
ÿ<— Transmitting (NAT) to 192.168.255.119:5060 —>
ÿSIP/2.0 202 Accepted
ÿVia: SIP/2.0/UDP 192.168.255.119:5060;branch=z9hG4bKPjJtFL-jmrbOlsRiNPBcVlkO-I2BM514Ko;received=192.168.255.119;rport=5060
ÿFrom: <sip:192.168.255.119>;tag=l0V2hKDwEfpZdPhrFJ2xC.uGZgvP2ZFC
ÿTo: <sip:proxy@192.168.255.1>;tag=as4da990ba
ÿCall-ID: CFGi9dXFiFaQXiibCc8daLm4elrI0-2A
ÿCSeq: 45098 MESSAGE
ÿServer: FPBX-12.0.76.6(11.12.0)
ÿAllow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
ÿSupported: replaces, timer
ÿContent-Length: 0
ÿ
ÿ
ÿ<------------>
[2021-06-01 23:49:30] VERBOSE[6974] chan_sip.c: Scheduling destruction of SIP dialog ‘CFGi9dXFiFaQXiibCc8daLm4elrI0-2A’ in 32000 ms (Method: MESSAGE)
[2021-06-01 23:49:30] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:1] Set(“Message/ast_msg_queue”, “MESSAGE(custom_data)=mark_all_outbound”) in new stack
[2021-06-01 23:49:30] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:2] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-URI)=sip:192.168.255.119:5060”) in new stack
[2021-06-01 23:49:30] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:3] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-FullContact)=sip:192.168.255.119:5060;ob”) in new stack
[2021-06-01 23:49:30] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:4] MessageSend(“Message/ast_msg_queue”, “digium_phone:blah”) in new stack
[2021-06-01 23:49:30] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:5] Hangup(“Message/ast_msg_queue”, “”) in new stack
[2021-06-01 23:49:30] VERBOSE[6957][C-00000000] pbx.c: == Spawn extension (dpma_message_context, proxy, 5) exited non-zero on ‘Message/ast_msg_queue’
[2021-06-01 23:49:30] WARNING[6995] phone_message.c: Message dropped because of lacking session id
[2021-06-01 23:49:30] VERBOSE[6974] chan_sip.c:

ÿ<------------->
[2021-06-01 23:30:07] VERBOSE[6974] chan_sip.c: — (10 headers 0 lines) —
[2021-06-01 23:30:08] VERBOSE[6974] chan_sip.c:
ÿ<— SIP read from UDP:192.168.255.105:5060 —>
ÿMESSAGE sip:proxy@192.168.255.1:5060 SIP/2.0
ÿVia: SIP/2.0/UDP 192.168.255.105:5060;rport;branch=z9hG4bKPjFeMEjtR.fkzcHRrDSBYUNw.OpoZDWAcj
ÿMax-Forwards: 70
ÿFrom: <sip:192.168.255.105>;tag=WH8pi.M-Cl7C927TLHoD8luLDx4uhcC2
ÿTo: <sip:proxy@192.168.255.1>
ÿCall-ID: ge2ARxxon-qy.AKFo-UNwVmFLNIjtDlt
ÿCSeq: 45638 MESSAGE
ÿAccept: text/plain, application/im-iscomposing+xml
ÿContact: <sip:192.168.255.105:5060;ob>
ÿUser-Agent: Digium D50 1_4_2_1_73372
ÿX-Digium-User-Agent: Digium D50 1_4_2_1_73372
ÿX-Digium-AppServer-RequestType: Handshake
ÿX-Digium-AppServer-MACAddress: 000FD30683D8
ÿX-Digium-Software-Version: 1_4_2_1_73372
ÿX-Digium-AppServer-ID: bootc_170611
ÿContent-Type: text/plain
ÿContent-Length: 875
ÿ
ÿ-----BEGIN CERTIFICATE-----
ÿMIICWTCCAcKgAwIBAgIBVTANBgkqhkiG9w0BAQUFADBgMQswCQYDVQQGEwJVUzEL
ÿMAkGA1UECBMCQ0ExEjAQBgNVBAcTCVNhbiBEaWVnbzEVMBMGA1UEChMMRGlnaXVt
ÿLCBJbmMuMRkwFwYDVQQDExBEaWdpdW0gQXBwc2VydmVyMB4XDTcwMDEwMTAwMDAw
ÿMFoXDTM4MDEwMTAwMDAwMFowTDELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAkNBMRUw
ÿEwYDVQQKEwxEaWdpdW0sIEluYy4xGTAXBgNVBAMTEERpZ2l1bSBBcHBzZXJ2ZXIw
ÿXDANBgkqhkiG9w0BAQEFAANLADBIAkEA2J9o2p9eltMYCR43tvGDyOyhDwio5NGT
ÿJqH20AL2rMpDzGTbTlDlGASeSOT/YSo1sCrE52z/ZLZjxeCH0MActQIDAQABo3sw
ÿeTAJBgNVHRMEAjAAMCwGCWCGSAGG+EIBDQQfFh1PcGVuU1NMIEdlbmVyYXRlZCBD
ÿZXJ0aWZpY2F0ZTAdBgNVHQ4EFgQUcHhB8gihAT9BHx6n5ZMtL9yvLpQwHwYDVR0j
ÿBBgwFoAUQ4XMqehyfmlcYNQhgohxNy8y3/UwDQYJKoZIhvcNAQEFBQADgYEAIz5E
ÿc18JOKRYwr5ryk3ybubeiBHXBCFgxs/8rYcZRTpWYgPK2eN2rEISsD5KjMuuJpC6
ÿbXpxbmfQt6gWVOwxXbgv7PBt44wVp1/tWmldpRVVkh7zFe/B5jUNrGsbDOv4lIhQ
ÿ7WDHrFN/DgCIobzXAvk5hTCQxcpMQr5dGYEZCE4=
ÿ-----END CERTIFICATE-----
ÿ<------------->
[2021-06-01 23:30:08] VERBOSE[6974] chan_sip.c: — (17 headers 15 lines) —
[2021-06-01 23:30:08] VERBOSE[6974] chan_sip.c: Sending to 192.168.255.105:5060 (NAT)
[2021-06-01 23:30:08] VERBOSE[6974] chan_sip.c: Receiving message!
[2021-06-01 23:30:08] VERBOSE[6974] chan_sip.c: Looking for proxy in dpma_message_context (domain 192.168.255.1)
[2021-06-01 23:30:08] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:1] Set(“Message/ast_msg_queue”, “MESSAGE(custom_data)=mark_all_outbound”) in new stack
[2021-06-01 23:30:08] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:2] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-URI)=sip:192.168.255.105:5060”) in new stack
[2021-06-01 23:30:08] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:3] Set(“Message/ast_msg_queue”, “MESSAGE_DATA(X-Digium-AppServer-Response-FullContact)=sip:192.168.255.105:5060;ob”) in new stack
[2021-06-01 23:30:08] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:4] MessageSend(“Message/ast_msg_queue”, “digium_phone:blah”) in new stack
[2021-06-01 23:30:08] VERBOSE[6957][C-00000000] pbx.c: – Executing [proxy@dpma_message_context:5] Hangup(“Message/ast_msg_queue”, “”) in new stack
[2021-06-01 23:30:08] VERBOSE[6957][C-00000000] pbx.c: == Spawn extension (dpma_message_context, proxy, 5) exited non-zero on ‘Message/ast_msg_queue’
[2021-06-01 23:30:08] WARNING[6995] phone_message.c: Session could not be created due to invalid credentials
[2021-06-01 23:30:08] VERBOSE[6974] chan_sip.c:
ÿ<— Transmitting (NAT) to 192.168.255.105:5060 —>
ÿSIP/2.0 202 Accepted
ÿVia: SIP/2.0/UDP 192.168.255.105:5060;branch=z9hG4bKPjFeMEjtR.fkzcHRrDSBYUNw.OpoZDWAcj;received=192.168.255.105;rport=5060
ÿFrom: <sip:192.168.255.105>;tag=WH8pi.M-Cl7C927TLHoD8luLDx4uhcC2
ÿTo: <sip:proxy@192.168.255.1>;tag=as713cfed2
ÿCall-ID: ge2ARxxon-qy.AKFo-UNwVmFLNIjtDlt
ÿCSeq: 45638 MESSAGE
ÿServer: FPBX-12.0.76.6(11.12.0)
ÿAllow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
ÿSupported: replaces, timer
ÿContent-Length: 0
ÿ
ÿ
ÿ<------------>


(TheJames) #2

I would say the user or password is wrong


#3

When registering a new phone what credentials are used? I have the following settings that I believe would apply only to phones pulling the user list and applying them to their phone.

Connectivity > Digium Phones > General Settings
Easy Mode: Disabled
Global Pin: 4444
Require Global PIN for user list?: No
Phone Authentication Method: Global Pin

However, I’m never asked for the password as the user list is never displayed. It errors out while trying to start the connection from what I can see. It says contacting the server… then fails. It used to pull the user list then when I selected the user I would have to enter the Global Pin.

However, this also doesn’t explain why the voicemail and parked calls on the phones can not be displayed while trying to connect to the freepbx unit.

Some people seem to have the registration issue and find out that there are bad or corrupt extensions in the system or they usually have a NAT issue. I haven’t changed any network settings in some time, so I would think that the NAT setup wouldn’t all of a sudden change and or be wrong. Digium Phone Provisioning Hangs at fetching user list

I’m also seeing this in the logs quite a bit… what is going on with this!

[2021-06-02 00:38:33] WARNING[6974] chan_sip.c: Retransmission timeout reached on transmission ggvhMtlBv4uQ27BnDcVRnAZtSQ-Sedq6 for seqno 102 (Critical Request) – See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions


(Joshua C. Colp) #4

Did you update DPMA? Critical Information for all DPMA users


#5

I have not ran any updates in some time as the modules are all the last release for that version of FreePbx.

The phones run on firmware version 1.4.2.1 which is pretty old as well. Just suprised to see something kill the functionality if nothing was upgraded or installed.

Do you believe this is my issue?


(Lorne Gaetz) #6

Linked thread has a description of the issue and the resolution. If you are using DPMA, you must upgrade to current.


#7

I’m assuming I would be better off starting with a fresh install on FreePbx 15?


(Lorne Gaetz) #8

What version are you running now? Are you using the FreePBX Distro?


#9

Freepbx on centos box.

FreePBX 12.0.76.6
CentOs centos-release-6-5.el6.centos.11.2.x86_64


(Lorne Gaetz) #10

FreePBX 12 is EOL and has been for years. You should be able to restore a backup from 12 on a new 15 system. Best to spin one up in a temporary location to confirm.


(system) closed #11

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.