Hi all. It’s Carolin from Quobis. Today we are going to talk about the new release of Sippo with our product manager Santiago Troncoso. Hi, Santi, we have a new release, the version 3.0, what can you tell us about this new release?
Hi Carolin, yes, the new release was launched some months ago, it’s a great jump in terms of stability and use case implementations.
What are the main objectives of this release?
We did a big internal refactor, that’s the reason to change from 2.x to 3.x. We know that the change in name could make somebody scary, but don’t worry, our SippoJS and APIs are still there, but we have to do more internal documentation...
No, seriously, we have great improvements. Onboarding use case leads us to a solid rock engine, in fact, “solid rock” was the internal codename of the version… We worked quite hard on it, even with the HA-Scaling architecture, improved on a significative way. But in addition we increased the API features and review some details on the frontend.
Could you specify some new API services?
Well, we did interesting integrations with proprietary software that help us to improve the hook mechanisms for authentication. Do “anti-fraud mechanisms” (double check of a customer ID) are possible and easier now. We also included all SAPI commands under the OAuth authentication, increasing security, and also the reporting is better exposed now.
What can you tell us about the news on the WebRTC Application Controller?
Included on the new features we have now the SMS backend, a new way to notify about the meetings and also a great service to use with future services, like alarms, or last-call notifications. As said before, improves on security means improvements on the token system for authentication, using the gateway capabilities or any customer service adapted to it.
The MCU recording and integration is improved, and also we started to work on the docker containers.
So you are exploring Docker to have the service on the cloud based on it?
Well it is a possibility... we don’t have a definitive answer about it, we offer the Sippo family as a service and, of course docker is a way to reach the cloud, but nowadays our service is based on virtual machines, not container. It’s too early to say something about this right now. But yes, Sippo WAC Docker is a reality that we are using internally for lab and testing
What news can we expect about the SippoJS applications?
About the Web Collaborator we have improvements, the AngularJS interface allow us to play more with the components so we are moving things and adopting, step by step a simpler interface always with the mobile applications on mind.
We also modified SippoJS to include chat options for groups, an internal change that will allow the chat on the meetings. And the auto-login feature, a nice idea to integrate the Web Collaborator as it is on your web suite of applications.
Something new on the Click To Call?
Yes, captcha is a typical protection of these open services, now it’s available. And also a dialpad, legacy, but useful when dialing voice IVRs on existing services.
And a great one: select the camera to start the video conference, allowing more use cases. These use cases are known as “context evaluation”, like on an accident, or on a video of your environment. On these cases, is more important to the agent to use the rear camera than the front camera of a mobile. Now that’s configurable, and soon it will be dynamic.
Many thanks for your time Santi. Check more uses cases on our website.
We invite our partners and customers to evaluate this new version or request access to this version on the online demo lab. Remember that the upgrade is included by default in your maintenance support contract.