The new age of All-IP networking has arrived. Now that session initiation protocol (SIP)-based telephony is well established, enabling broad adoption of unified communications (UC), the traditional Public Switched Telephone Network (PSTN) seems a bit clunky and old-fashioned. Yet that old PSTN was—and still is—highly reliable. As carrier-providers—and their subscribers—plunge head-first in to the sea of IP Telephony, the good old PSTN remains good solid ground—a trustworthy plan B—for those inevitable times when your subscriber’s Internet connection fails… for whatever reason.
Another way (in addition to PSTN backup) to solve the uptime problem with Internet-based phone systems is for the subscriber maintain dual access links with separate Internet service providers (ISPs)—ideally over different physical cabling plants with varied networking providers (fiber-optic Ethernet, coaxial cable-modem, copper DSL). This multi-provider approach is highly resilient. In addition to providing a backup plan for the broken WAN access link, it covers potential hardware or software failures in the service-provider cloud. As another layer of redundancy for added resilience, a second Internet Telephony Service Provider (ITSP) may be added to the mix.
​

The Crux of the Problem
Whether your subscriber is operating a business, hotel, school, church or hospital, the problem is the same.
​How are you going to keep your customer’s phone system working—no matter what?

Cloud PBX
In this age where the PBX is often in the cloud, the unfortunate reality is that a loss of connection to the cloud service, for any reason, breaks station-tostation calls within the enterprise, kills 911 emergency services and wipes out inbound and outbound call capability.

SIP Trunks
In SIP trunking implementations, where the IP-PBX resides on-premise, a broken Internet access link kills inbound and outbound calling. However the PBX can still support station-to-station calls between SIP terminals within the local area network).

​Patton offers a flexible solution for enterprise-telephony survivability and business continuity that employs an intelligent enterprise session border controller (eSBC)—equipped with the necessary features and functions—installed on the subscriber premise.

The latest 3CX iOS BETA client is now available with a number of improvements to the user experience. As well as OPUS codec support, there is also faster launch and reconnect and a smoother, more speedy experience in the recents display. Support for the upcoming V15.5 SP6 PUSH will allow for multiple devices to be registered for PUSH on the same extension so stay tuned for Update 6!
Other features and improvements include:

• Added Apple’s UI refresh control in Recents (by swiping-holding down the list)
• Fixed wrong call start/connect duration in Recents
• Fixed New Contact button in Contacts not being shown sometimes when account reconnects or is changed
• Fixed status custom message being wrongly cleared when status updates
• Fixed Presence/Contacts search bar remaining “hidden” sometimes
• Minor fix in color themes
• Added OPUS codec
• Support for upcoming V15.5 SP6 PUSH
• Faster launch and reconnect
• Faster and smoother Recents display

Want to test out 3CX’s iOS client BETA releases? Click here to join 3CX TestFlight

The BETA release of the latest 3CX client for Android was very well received. 3CX development team worked hard on making massive improvements to the app, adding new features and also making some interface changes – all to make the user’s experience more seamless.
Some of the features worth highlighting are less battery and memory usage, the PUSH functionality has come leaps and bounds, QR scanner improvements, OPUS codec support and the ability to have multiple devices registered for PUSH on the same extension – this will however require V15.5, Update 6 which is not released yet, so wait for it!


More features and improvements:

• Improvements in PUSH reliability – made more robust and reliable.
• Ability to have multiple mobile devices registered for PUSH for the same extension (will require an V15.5, Update 6).
• Less battery and memory usage for devices with many contacts.
• Added TLS 1.2 support for Android devices using Android 5.0 and below.
• Added partial match ability when dialing numbers. Typing an incomplete number will now be matched and completed with the first available contact match in your phone book.
• Improved the QR scanner – it no longer requires specific Android OS version & Google Store Updates. It also includes targeting scanner & haptic feedback when a QR code has been scanned.
• Several visual improvements.
• Added an “Exit Confirmation” notification when pressing the “Back” button on any Android device.
• Added support for the OPUS codec.

Patton has been making analog trunking gateways for decades. The recently announced menu of on-premise FXO VoIP devices offers ideal solutions for SMBs that need up to 8 FXO trunks to connect with a SIP PBX (a.k.a. IP PBX).
These new Patton gateways, eSBCs, and eSBC-Routers are perfect for delivering…

• First-Line analog POTS connectivity
• BRI/S0 connectivity
• PSTN/ISDN fallback and survivability

…for any on-premise all-IP enterprise telephony system. Including 3CX, Avaya, Asterisk, RingCentral, Mitel, Panasonic, and many others.

Press Release: New Analog Trunking Gateway morphs from FXO to SIP when you go All-IP
For people that need a digital-analog hybrid solution, the Smartnode 5550 offers a great deal of flexibility on your interface options.

You can order this little sweetheart from a menu of choices. . .

• 2, 4 or 8 FXO
• 4 FXS + 4 FXO
• 2 BRI + 2 FXS
• 4 BRI + 4 FXS
• 2 BRI + 2FXS + 2 FXO
• 4 BRI + 4 FXS + 4 FXO

​SmartNode Configuration Wizard

All the new FXO SmartNode solutions work with Patton’s WebWizard—a powerful, time-saving configuration tool for carriers,
​ installers, and end-customers. Go to www.patton.com/wizard/