Extensions with multiple phones assigned not ringing when called

[JosephV]

I have 3cx setup with a call queue that rings out to multiple extensions. All the extensions have both a deskphone Yealink T41S, and a cordless Yealink W56H which are configured to ring together.
Suddenly one of the extensions will only ring on the deskphone and skip the cordless phone all together. In the logs i keep getting Call to <sip:[email protected]:0> has failed; Cause: 486 Busy Here/INVITE from 127.0.0.1:5080.
I have reset both cordless phone and the deskphone to factory defaults and I have even tried deleting the extension completely from the 3cx system and replacing it with a completely new extension number and the problem just replicates itself.

Any ideas on what I can do to solve this as I am completely lost

 

[JosephV]

Further logging information:

07/14/2021 1:09:58 PM - L:36.14[Extn:107] got Terminated Recv 486/INVITE from 127.0.0.1:5080 tid=f9184143e244db01 Call-ID=Jny0gNpp3NWPydXZflIK4A..: SIP/2.0 486 Busy Here Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-524287-1---f9184143e244db01;rport=5060 Record-Route: <sip:[email protected]:5080;user=proxy;uri=sbc.fb0c8aba> To: <sip:[email protected]>;tag=2870128082 From: "0418928263:Queue new" <sip:[email protected]:5060;nf=q>;tag=6e21a06f Call-ID: Jny0gNpp3NWPydXZflIK4A.. CSeq: 1 INVITE Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE User-Agent: Yealink W60B 77.83.0.65 805ec0aaa8dd Allow-Events: talk, hold, conference, refer, check-sync Content-Length: 0

07/14/2021 1:09:58 PM - Terminated from <sip:[email protected]>;tag=2870128082 to "0418928263:Queue new" <sip:[email protected]:5060;nf=q>;tag=6e21a06f; reason: Error

07/14/2021 1:09:58 PM - L:36.14[Extn:107] got Failure: Failure Recv 486/INVITE from 127.0.0.1:5080 tid=f9184143e244db01 Call-ID=Jny0gNpp3NWPydXZflIK4A..: SIP/2.0 486 Busy Here Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-524287-1---f9184143e244db01;rport=5060 Record-Route: <sip:[email protected]:5080;user=proxy;uri=sbc.fb0c8aba> To: <sip:[email protected]>;tag=2870128082 From: "0418928263:Queue new" <sip:[email protected]:5060;nf=q>;tag=6e21a06f Call-ID: Jny0gNpp3NWPydXZflIK4A.. CSeq: 1 INVITE Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE User-Agent: Yealink W60B 77.83.0.65 805ec0aaa8dd Allow-Events: talk, hold, conference, refer, check-sync Content-Length: 0

07/14/2021 1:09:58 PM - [CM503003]: Call(C:36): Call to <sip:[email protected]:0> has failed; Cause: 486 Busy Here/INVITE from 127.0.0.1:5080

07/14/2021 1:09:58 PM - Failure from <sip:[email protected]>;tag=2870128082 to "0418928263:Queue new" <sip:[email protected]:5060;nf=q>;tag=6e21a06f

07/14/2021 1:09:58 PM - L:36.14[Extn:107] got Provisional Recv 180/INVITE from 127.0.0.1:5080 tid=f9184143e244db01 Call-ID=Jny0gNpp3NWPydXZflIK4A..: SIP/2.0 180 Ringing Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-524287-1---f9184143e244db01;rport=5060 Record-Route: <sip:[email protected]:5080;user=proxy;uri=sbc.fb0c8aba> Contact: <sip:[email protected]:5060> To: <sip:[email protected]>;tag=2870128082 From: "0418928263:Queue new" <sip:[email protected]:5060;nf=q>;tag=6e21a06f Call-ID: Jny0gNpp3NWPydXZflIK4A.. CSeq: 1 INVITE Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE User-Agent: Yealink W60B 77.83.0.65 805ec0aaa8dd Allow-Events: talk, hold, conference, refer, check-sync Content-Length: 0

 

[JohnS_3CX]

Hi Joseph,

Please start by reading this post and providing us with some information so we can better understand your deployment: https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

 

[JosephV]

• 3CX Version, Professional Annual 16.0.9
  
• Server OS Debbian 9
• Is the 3CX Server Hosted and where? ( Our own data center )
• IP Phone Make/Model/Firmware SIP-T41S 66.86.05 , SIP-W60B 77.83.0.65
• Provisioning Method: SBC - Raspberry Pi
• Trunk Provider or Gateway Make/Model - Maxotel
• Has the Firewall Checker passed: YES
• Are custom Phone Templates being used: NO

 

[JohnS_3CX]

As can also be seen from the provided logs, the W60B firmware is out of date.

Please follow out guide to upgrade it, then factory reset and reprovision it from the beginning.
https://www.3cx.com/sip-phones/yealink-dect-w52p/

Following that, try to repeat your test and see if it works as intended.




PS: While your at it, check your SIP trunks page, and confirm the Pi SBC version too. Should be on 16.2.24