Recent content by NTB Inc

  1. v15.5 Working Great - Thanks 3cx!

    Just wanted to post a comment, did our upgrade last night from v15 to v15.5, have to say what a smooth process. We clicked install update and less than 10 mins later all was upgraded and working. Moved through phone firmware as well quickly and all is working great. Coming from the legacy PBX...
  2. 3cx to Toshiba SIP....possible?

    I'm not intimately familiar with Toshiba but having done other integrations with legacy PBXs in the past I have a few thoughts to share: - Be "OK" with possibly having features missing and/or not working as how they used to, especially on the legacy side, items like MWI lights being lit can...
  3. cloud 3cx + old handsets

    Not to insult 3cx but the current 3cx SBC is not a true enterprise SBC. If you are a service provider you really should be using an enterprise SBC, it will help address a number of deployment scenarios, NAT transversal issues and eliminate customer side complexity like VPNs or customer-side...
  4. What SIP Provider do you use?

    Yeah this is the best case. Sometimes even if the provider themselves doesn't offer SIP trunking they will have another provider that is "on-net" that can. Our current colo provider has some large peering in major markets that allows us to hop on and hop off with other SIP providers easily but...
  5. What SIP Provider do you use?

    In my experience the bigger names like AT&T treat SIP trunks as a delivery method not a cost savings one. We do a lot with AT&T IP Flex and their enterprise voice services and the costs are usually similar whether the service is delivered via SIP or PRI from the router. We tend to find we have...
  6. Implemented Intelligent phone template override system

    If the goal is to eliminate custom templates, these are the items we typically configure on our Yealinks, these were taken from a T23G template....... remote_phonebook.data.1.name We like to be able to customize phonebook name instead of 3cx Phonebook call it the company name or something else...
  7. Redundant SBC's / SBC reliability issue

    I would highly recommend actually getting an enterprise grade SBC to use especially if you are doing these with multiple customers across internet. The 3cx SBC is just another single point of failure. A true enterprise SBC will have redundancy features and solve a lot of the common NAT issues...
  8. Broadvoice SIP Trunk goes to 1 way audio

    This sounds like a firewall/router issue, knowing the make/model would help as many of these units have varying configuration needs. Depending on the router/firewall you should be able to do packet captures or view traffic logs to see the TCP/UDP connections coming in/out which should help...
  9. Site survivability

    Yes works very well, some good reading.... Yealink Redundancy: http://download.support.yealink.com/download?path=upload/attachment/2015-3-10/3/2497e56d-76cd-4b6f-b14a-09effb6c7c1f/Using Server Redundancy on Yealink IP Phones.pdf We use the T23G phones and it works well. In your 3cx...
  10. Site survivability

    There are a few different ways to achieve this. This is what we have done..... Assuming your IP Phones support PBX redundancy or failover (each manufacturer uses a different term slightly) basically allowing you to define 2 PBXs the phone will register to, you can modify your 3cx provisioning...
  11. Switchboard shows stuck calls / doesn't update

    Ok great, we have a scheduled task to stop/start it so hasn't been a huge deal. Are there any timeframes of when 15.5 will be a GA release and available to update via Update option in GUI?
  12. Switchboard shows stuck calls / doesn't update

    One scenario we have reviewed is if the TCP/UDP timeouts across our VPN are contributing but we have these set to high values and also wasn't a problem in v14. We are running PBX version 15.0.62928.5 and 3cx client 15.0.60903.0
  13. Switchboard shows stuck calls / doesn't update

    Yes, since upgrading to v15 from v14 we have seen this issue, we are running latest build of the clients and sometimes 1-2x per day will need to close/start 3cx client to get it to update. In v14 we rarely if ever had to restart. We have not opened case with support as we are eagerly awaiting...