Cisco SPA504g always busy or not available

[Mike MSTG]

I'm not sure if this is a problem with how the phones have gotten provisioned or some other setting we are missing however we have every phone in our office giving the same response in the logs:
8-Jan-2014 16:13:19.844 Leg L:27.3[Extn] is terminated: Cause: 486 Busy Here/INVITE from .....
08-Jan-2014 16:13:19.844 L:27.1[Line:89999<<...] failed to reach Extn:2025, reason Busy

On the phone side of things, the phone does happen to ring but only once and its more of a half-ring that lasts less than a second.

And if that failed, this happens:
08-Jan-2014 16:13:27.658 L:28.1[Extn] failed to reach Line:89999>>1723420300, reason Server Failure
08-Jan-2014 16:13:27.658 Call to T:Line:89999>>1723420300@[Dev:sip:9999999999@xxxx:5060] from L:28.1[Extn] failed, cause: Cause: 503 Service Unavailable/INVITE from xxxxx:5060
08-Jan-2014 16:13:27.658 [CM503003]: Call(C:28): Call to <sip:999999@xxxxx:5060> has failed; Cause: 503 Service Unavailable/INVITE from xxxxxx:5060

Phones do not have DND set. We have upgraded the firmware to the latest version of 7.5.5 on the phones as well as up to date on the PBX v12 SP3 as well as the provisioning rules. We have restarted all services several times and outgoing calls are not a problem. Does anyone know what the cause of this may be?

 

[leejor]

Did you ever try a manual config on one of the sets?
If not, do a "factory" reset on one phone. Use the menus (GUI or on the set if possible) and figure just the basics (just to get dialtone) manually. If that works then compare the working settings (not all the extra bells and whistles), with an auto configured set, that isn't working. Finding some differences should give some clues as to what is happening in the auto provision file that prevents the set from working properly...or it might point to something else, if it doesn't work at all.

 

[Mike MSTG]

Did you ever try a manual config on one of the sets?
If not, do a "factory" reset on one phone. Use the menus (GUI or on the set if possible) and figure just the basics (just to get dialtone) manually. If that works then compare the working settings (not all the extra bells and whistles), with an auto configured set, that isn't working. Finding some differences should give some clues as to what is happening in the auto provision file that prevents the set from working properly...or it might point to something else, if it doesn't work at all.

Same...

Its funny because it did the exact same thing from extension to extension (set I just did a factory reset, manual provision):
13-Jan-2014 17:14:46.443 Leg L:98.3[EndCall] is terminated: Cause: BYE from PBX
13-Jan-2014 17:14:46.443 [CM503008]: Call(C:98): Call is terminated
13-Jan-2014 17:14:46.443 Leg L:98.1[Extn] is terminated: Cause: BYE from 192.168.1.31:5060
13-Jan-2014 17:14:42.817 [CM503007]: Call(C:98): EndCall:EndCall has joined, contact <sip:[email protected]:40600>
13-Jan-2014 17:14:42.816 [CM503007]: Call(C:98): Extn:2045 has joined, contact <sip:[email protected]:5060>
13-Jan-2014 17:14:42.815 L:98.3[EndCall] has joined to L:98.1[Extn]
13-Jan-2014 17:14:42.667 [CM503025]: Call(C:98): Calling T:EndCall:EndCall@[Dev:sip:[email protected]:40600;rinstance=81a07b4dcd482e92] for L:98.1[Extn]
13-Jan-2014 17:14:42.663 Leg L:98.2[Extn] is terminated: Cause: 503 No matching transport found/INVITE from local
13-Jan-2014 17:14:42.663 L:98.1[Extn] failed to reach Extn:2015, reason Server Failure
13-Jan-2014 17:14:42.663 Call to T:Extn:2015@[Dev:sip:[email protected]:5060] from L:98.1[Extn] failed, cause: Cause: 503 No matching transport found/INVITE from local
13-Jan-2014 17:14:42.663 [CM503003]: Call(C:98): Call to <sip:[email protected]:5060> has failed; Cause: 503 No matching transport found/INVITE from local
13-Jan-2014 17:14:42.563 [CM503025]: Call(C:98): Calling T:Extn:2015@[Dev:sip:[email protected]:5060] for L:98.1[Extn]
13-Jan-2014 17:14:42.514 [CM503027]: Call(C:98): From: Extn:2045 ("abc" <sip:[email protected]:5060>) to T:Extn:2015@[Dev:sip:[email protected]:5060]
13-Jan-2014 17:14:42.514 [CM503004]: Call(C:98): Route 1: from L:98.1[Extn] to T:Extn:2015@[Dev:sip:[email protected]:5060]
13-Jan-2014 17:14:42.513 [CM503001]: Call(C:98): Incoming call from Extn:2045 to <sip:[email protected]:5060>

 

[Mike MSTG]

I just performed a clean install of the 3cx software and I still received the message above. This is very frustrating in that it makes me not want to spend money to actually get this software if it can't handle something as entering an extension from the main digital receptionist.