Tech

Presence in, Presence out

Published on:

November 19, 2012

In PBX terms, presence typically indicates if someone is on the phone or unavailable. With snom ONE version 5.0.2, we’ve enhanced presence functionality by adding the ability for the PBX to show when a user is on the phone, even if they are using an external device like a mobile phone. This is achieved through an HTTP request to the PBX from the mobile service provider, updating the presence status without needing complex SIP configurations. The system can track call duration and reset the status after a call ends. Additionally, the PBX can relay presence updates to connected platforms like Microsoft Lync.

In PBX terms, presence is a glorified term for “someone is on the phone”, and possibly “someone does not want to get disturbed”. We already talked about how snom ONE publishes the presence state changes to Microsoft Lync when that someone is on the phone.

Now with the 5.0.2 version, we started adding the other direction: When someone talks on the phone without using the PBX, the PBX can still show the other office users that this person is on the phone. For example, when someone is on his or her mobile phone, either the phone or the phone provider can send that status information to the PBX. I have learned that in Scandinavian countries, some mobile phone providers support this kind of updating the presence information.

Instead of going a complicated SIP route, we just added that feature into the HTTP part of the PBX. All the service provider needs to do is to open a HTTP request to a predefined URI that looks like this:

https://pbx/call_state.htm?domain=abc.com&user=123&password=secret&number=12345678

Then the PBX will assume that the user is busy talking to 12345678. When the call is over the service provider is supposed to make another request:

https://pbx/call_state.htm?domain=abc.com&user=123&password=secret

The absence of the number parameter tells the PBX, that there is no phone call going on. Right now, the PBX does not populate the number to anybody else, like it does not populate the internal numbers as well. The URI may contain a parameter “expires” that tells the PBX for how long the extension is in a call, unless it clears the state explicitly with the empty number. The default value for this parameter is the maximum call duration on the system, usually two hours. This makes sure that the status of the extensions gets cleared eventually, even if the service provider should miss the clear update.

Now this works from the cell phone service provider, but it would also work from a cell phone directly. For example, if someone has an Android app that is watching the call state of the phone, it could easily update the PBX call state with this little application.

The other interesting note is that the PBX can also combine incoming presence updates with outgoing presence updates. For example, if the cell phone provider sends the information to the PBX, the PBX could then relay the information to the connected Microsoft Lync account.

This is the beginning of the journey. We have to see what other services support presence information. For example, I can think about IBM sametime or the Google plus and Facebook networks. Hopefully they just use some simple HTTP-based API; that would make it a lot easier for us to get this done in one of the next releases.

If one of you out there has a wish what presence network we should address next, let us know. Feedback is always welcome.

Derniers articles

Voir tous

Integrating OpenAI's Realtime API with Vodia PBX: Webinar Recording Now Available

In our recent webinar, "Integrate OpenAI’s Realtime API with Vodia PBX," we explored how integrating AI with your communication systems can revolutionize the way your business operates. From automating repetitive tasks to improving workflow efficiency, the webinar covered how the collaboration between Vodia PBX and OpenAI’s Realtime API can streamline operations, enhance collaboration - especially for Microsoft Teams users - and provide intelligent automation to stay ahead in a competitive landscape. If you missed the live session or want to revisit the insights, the recording is now available for you to access.

December 18, 2024

Unlock the Power of OpenAI’s Realtime API with Vodia PBX: Join Our Exclusive Webinar!

Join our exclusive webinar to explore how Vodia PBX seamlessly integrates with OpenAI’s Realtime API, unlocking powerful new capabilities for your communication systems. This session will showcase how AI-driven features can streamline workflows, improve operational efficiency and elevate the PBX experience for both general users and those on Microsoft Teams. Whether you’re looking to stay ahead of the competition or leverage the latest AI trends, this webinar offers practical knowledge and actionable strategies. Register now to secure your spot and take the first step toward transforming your telecom infrastructure with AI innovation!

December 4, 2024

Connecting to OpenAI Realtime API

This document details the beta version of the Vodia PBX that connects to the OpenAI realtime API, enabling users to interact with a chatbot via telephone. The backend JavaScript code facilitates the connection, handling audio input and output, and the WebSocket connection to the OpenAI API. The setup requires a Vodia PBX version 69.5.3 or higher, an API key, and a license with an IVR node. The demo can be accessed by editing the ivrnode.js template and creating an IVR node in the tenant. The system supports various VoIP devices and offers good voice quality. Future improvements include voice activity detection and the ability to take actions based on OpenAI responses.

November 26, 2024