Welcome to the SIPERB Beta Program
Thank you for your interest in the SIPERB beta Program! We’re excited to have you on board and look forward to your valuable feedback.
Siperb Softphone documentation for IT admins and business users — connecting to your PBX across Web, Desktop, and Mobile.
Thank you for your interest in the SIPERB beta Program! We’re excited to have you on board and look forward to your valuable feedback.
At Siperb we allow you to control your data.
When setting up a New Account, you will be asked if this is for a New Domain, or to Join and Existing Domain. The concept of domains plays a crucial role.
SIPERB’s platform utilizes a flexible concept known as “Devices” to enhance user experience and accessibility. This feature allows you to manage multiple devices under one account, ensuring you never miss important calls, regardless of your location or the device you are using.
Connections are a fundamental component of SIPERB, acting as the link between your PBX or ISP and your SIPERB account.
Outbound Trunks function similarly to Outbound Registration but do not send a REGISTER message, meaning there’s no registration status available. They are commonly used when connecting to endpoints with a static or fixed IP address since the primary purpose of registration is to retrieve an IP address.
Outbound Registration involves entering SIP details from your PBX or ISP into SIPERB systems to maintain a registration loop through REGISTER messages.
Inbound Registration is when the SIP details, are automatically generated on our side. Once created, it is up to you, to REGISTER with us, just like a typical UAC to UAS scenario.
SIPERB provides robust WebRTC client formats to meet diverse communication needs across various devices. Our solutions include clients tailored for web, tablet, and mobile interfaces, each designed to optimize your communication experience regardless of your device type.
Transcoding is a crucial function within the SIPERB platform, especially when dealing with legacy PBX systems that do not natively support WebRTC’s modern codecs and protocols.