Microsoft Phone System Direct Routing lets you connect a supported Session Border Controller (SBC) to Microsoft Phone System. Direct Routing allows you to decide how to provide voice to Office 365. With SIPPIO’s global reach, you can bring your own carrier or leverage our carrier services knowing you are safe, certified and secure.
Can I still use my 3rd -party system?Brandon Vargas2020-11-05T20:40:25-05:00
AudioCodes offers a fax solution for analog; however, we recommend electronic faxing if you are able to switch over because analog was not built for the internet. Our hosted solution is 100% running on AudioCodes and Microsoft. They offer gateways for various business purposes such as e-fax, elevators, door locks, etc. AudioCodes offers a series of Teams enabled and Teams native phones; these can be procured from them via standard Capex or as a device-as-a-service (DaaS) on the same monthly billing as the SIPPIO Service.
Does SIPPIO offer number porting, emergency services and toll-free support?Brandon Vargas2020-11-05T20:40:24-05:00
SIPPIO keeps it simple. We offer a flexible and economical calling plan with a vast international footprint. Our calling plans are designed to be easy and we have no upfront, carrier service or monthly commit. You simply pay for what you use.
How do I buy and pay for SIPPIO?Brandon Vargas2020-11-05T20:45:52-05:00
SIPPIO is offered by an ecosystem of IT/Telecom Agents, Telecom VARs, Systems Integrators, IT Resellers, Wholesalers and Distributors. Contact your Trusted Advisor today or drop us a line at email@example.com.
In order to enable calling services in Microsoft Teams with SIPPIO, you will need a Phone System License or have E5/A5 as part of your Microsoft 365 bundle. This can be procured from your reseller or CSP.
How does fail-over work?Cliff Cook2020-12-10T09:47:14-05:00
Our solution is built in Azure and benefits from all the availability and redundancy features that comes with it.
SIPPIO’s failover can be covered in different areas.
Geographical Presence: SIPPIO has servers in 5 different Azure regions and will grow according to business grow. All the components have direct connection with each other on the Azure backend network, which according to Microsoft has less than 15ms round trip time.
Redundancy and failover on carrier: All our SBCs are connected to several carriersallowing us to have failover and redundancy at carrierlevel. If a carrierfails, the system will automatically route the calls to the other carriers.
Redundancy and failover on routes: SIPPIO has an advanced mechanism for selecting the best and most efficient route for calls. By leveraging Audio codes ARM servers and geographically spreading them in different regions we can make sure that all the SBC have access to their closest routing manager.
Redundancy and failover on SBC: SIPPIO currently has 5 dynamic SBC in 5 Azure regions and will expand with business growth. Our AudioCodes SBCs are dynamic in a way that they expand and shrink with the traffic load. All the connections to the SBCs are based on Names and FQDN. This will allow our system to automatically connect the end points to another SBC if an entire Azure region goes down.
Redundancy and failover at Teams: By using SIPPIO, customers are connecting their tenant to an FQDN which is pointing to our SBC. In the back end we are leveraging advanced DNS features to handle the traffic and connect customers to the closest SBC. If one SBC goes down, it will automatically connect customers to other available SBCs.
Will this work with AudioCodes, Polycom, Cisco, Yealink, etc. handsets?Cliff Cook2020-08-04T16:36:07-04:00
Yes! Today’s users mix and match their communication and collaboration ‘devices’ based on where they are, what they are doing and even whom they might be talking with. Users can make and take calls however they choose.