Recent content by technomojo

  1. V20 Can't login to web console of T48Us (3) or W70B

    Hi John, Thanks for your reply. No SBC, just the router phones. I think we got to the bottom of the issue. With the help of the tech team at my local SIP provider, we were able to reset the web console password of each of the phones and login to take a look at the configuration. It seems that...

  2. V20 Can't login to web console of T48Us (3) or W70B

    New install of V20 on Amazon LightSail in September. All rigorously tested and working fine after installation. 3 x T48Us, all set as router phones and one W70B with one handset. At some stage in the 2 months since the initial setup, the W70B stopped registering. Not sure when this happened...

  3. Solved Yealink W60B Extensions Not Registering

    Yeah, doesn't happen in Chrome :rolleyes:

  4. Solved Yealink W60B Extensions Not Registering

    Maybe a combination of the field type and Firefox? I don't even need to highlight the field.

  5. Solved Yealink W60B Extensions Not Registering

    Solved. I imagine the IGMP issue was the problem initially but at some stage the config of the W60B in 3CX was modified: Apparently the number changes if you scroll while hovering over the field. I must have done this at some point. Thanks for the assistance. A little bit of feedback: that...

  6. Solved Yealink W60B Extensions Not Registering

    OK, I've tested connecting a Yealink T46S at that site and initially it didn't show up in the 3CX Phones list. After a closer look at the router settings, I found that IGMP blocking was enabled (to some degree) either by the router manufacturer or their ISP. The router's description: After...

  7. Solved Yealink W60B Extensions Not Registering

    I also set a static DNS on the W60B pointing to the local router as per @cobaltit 's suggestion on this thread but no luck there either.

  8. Solved Yealink W60B Extensions Not Registering

    SBC is registering, no problem there. It's also on the same LAN as the W60B. SIP ALG is disabled on the client's Netcomm NF18ACV router. I don't believe there are any other NAT or firewall-related issues that could be getting in the way. Funny regarding the firmware, 77.85.0.20 was the latest...

  9. Solved Yealink W60B Extensions Not Registering

    SBC Version is 16.2.24. These are the only handsets on this site (the rest use soft clients), I could take a tester out if need be. This is the first time I've used a Pi for an SBC, I've been through the guides a few times to hopefully ensure I hadn't missed any details. I guess I thought that...

  10. Solved Yealink W60B Extensions Not Registering

    No, provisioning was pretty straightforward. I'd reset and reprovisioned before but tried again and still no registration. I've also tried enabling the 'Local Log' of the W60B but the 185KB zip file it downloads is invalid... Edit: I tried opening the zip with 7zip and it opened :rolleyes...

  11. Solved Yealink W60B Extensions Not Registering

    That's right, for each extension/account, the W60B's SIP Server 1 is set to the 3CX server's FQDN and the Outbound Proxy Server 1 is set to the SBC's local IP and the extension authentication is correct (Account > Register).

  12. Solved Yealink W60B Extensions Not Registering

    Good point! Thank you. I've updated the thread title accordingly. Reassuring that the issue is nothing to do with the handsets. Any idea why auto provisioned extensions won't register? I've been through the guides again, triple checked my settings, reprovisioned and everything looks as it...

  13. Solved Yealink W60B Extensions Not Registering

    I have 2 W59Rs (FW 115.85.0.20) paired with a W60B base station (FW 77.85.0.20), connected to a self-hosted cloud install (3CX 16.0.1078 on Amazon Lightsail) via an SBC running on a Raspberry Pi. Edit: I've managed to get the W60B (not the W59Rs) to auto provision but the extensions won't...

  14. Solved FQDN Issue? Registration Failed: Destination Is Not Reachable

    That was it! I changed it to 'Any' and it registered straight away. Much appreciated. Thanks again!

  15. Solved FQDN Issue? Registration Failed: Destination Is Not Reachable

    Yes, they seem to complete as expected from both locations, ending with the SIP address.
See more
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom