Help: 3CX Phones Not Provisioning After Unexpected Shutdown

[Plains_JosephW]

On Monday we came into the office to find our own 3CX server here at the office had lost power. After turning the server back on the Queue Manager, IVR, and Management Console Services, were not running and I was unable to restart them using the RestartSrv.exe so I uninstalled the 3CX Phone System from the server, reinstalled 3CXPhoneSystem155 (a version I downloaded on 3/14/18). I restored the system to the backup from the previous night and the system seemed to be working great.

Yesterday I attempted to provision 2 - Yealink T21P E2 using STUN, received the RPS request for Yealink T21P E2 IP Phone of **** ******* (29**) delivered successfully, however neither phone would provision. I pulled a Yealink T41S to try next and the same process occured with no provisioning. Last night I installed all updates for phone templates, clients, and the 3CX system updates, and still could not provision.

I came in this morning, power cycled my server and tried to provision 1 of each model using the Local LAN provisioning and still am not able to provision the phones.

- 'Disallow use of extension outside the LAN' is not selected.

 

[craigreilly]

You say tried local lan provisioning - then mention 'disallow use of extension outside of lan'.
provisioning for local lan is when phone and pbx are on same lan... the 'disallow' checkbox doesn't affect that, except for softphones roaming on cellular or other wifi networks.

Reading thru all this - you are Local Lan for Server. So, the 'Disallow' wouldn't matter.

Is there anything in the log files?

Perhaps run a capture from the ACTIVITY log, plug in the phone for provisioning, then STOP the capture. Then open it in Wireshark. (or send to me via Dropbox/Onedrive link in Private Conversation).

 

[Plains_JosephW]

You say tried local lan provisioning - then mention 'disallow use of extension outside of lan'.
provisioning for local lan is when phone and pbx are on same lan... the 'disallow' checkbox doesn't affect that, except for softphones roaming on cellular or other wifi networks.

Reading thru all this - you are Local Lan for Server. So, the 'Disallow' wouldn't matter.

Is there anything in the log files?

Perhaps run a capture from the ACTIVITY log, plug in the phone for provisioning, then STOP the capture. Then open it in Wireshark. (or send to me via Dropbox/Onedrive link in Private Conversation).

craigreilly,

Thanks for your reply and help, you are correct that the 'disallow' checkbox does not matter. My original intent was to provision two T21P's for use in remote locations. I attempted to provision them locally just to confirm that neither method was working.

I have been continuously seeing this on the log today but seems unrelated:

05/02/2018 1:56:46 PM - [CM503003]: Call(C:198): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5488
05/02/2018 1:56:46 PM - [CM503003]: Call(C:198): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 192.168.205.209:51546
05/02/2018 1:54:57 PM - [CM503003]: Call(C:196): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5488
05/02/2018 1:54:57 PM - [CM503003]: Call(C:196): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Cancelled/INVITE from 192.168.205.49:5060
05/02/2018 1:51:11 PM - [CM503003]: Call(C:194): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5488

I will send you a onedrive link to the capture if/when you have time to assist me.

Thank you!

 

[craigreilly]

is any of the IP's shown or extension numbers accurate?
192.168.205.49
or 2252, 7311, 2905

 

[Plains_JosephW]

2905 is the extension I am trying to provision a second phone for use in her home.
As you probably know 192.168.205.49 is the ip address for the phone using ext 7311, no issues reported.
and 2252, my call center manager, also no issues reported.