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.

Latest Articles

View All

Webinar | Real-Time Media Streaming in Vodia PBX: AI, Call Transcription, and Security in V69.5.6

Join Vodia Networks on April 8 for a live, in-depth webinar on how real-time media streaming is powering the future of voice communication. Discover how Vodia PBX version 69.5.6 enables seamless AI integration, live call transcription using the Whisper API, and secure voice data handling. Hosted by Sales Engineer Eric Altman and VoIP Engineer Hamlet Collado, this session will walk you through real-world use cases, including OpenAI and Google Speech-to-Text integrations, MS Teams support, and new security features. You’ll also get a first look at Vodia’s AI roadmap and have the opportunity to ask your questions during a live Q&A.

March 28, 2025

The Vodia PBX On-Premise Whisper AI Deployment​

Whisper, OpenAI’s Automatic Speech Recognition system, delivers multilingual, noise-tolerant, and technical-language-ready transcription through a streamlined encoder-decoder architecture. With Vodia PBX’s integration, organizations can choose between using OpenAI’s service or hosting Whisper AI locally for complete data sovereignty and control. This on-premise option ensures that sensitive call data stays within your infrastructure while still benefiting from powerful transcription capabilities. To explore deployment options, see our Whisper AI on-premise setup documentation, review a self-hosted integration example, or follow our cloud-based call transcription guide.

March 27, 2025

Vodia at Enterprise Connect 2025: Embracing AI and Advancing Communications

Vodia Sales Engineer Eric Altman attended Enterprise Connect 2025 on March 18 and 19, where he connected with partners and gained insight into the future of enterprise communications. AI was the clear focus of the event, with discussions centered on agentic systems, chatbots, and generative technologies. “It was certainly the main element in the atmosphere,” Eric noted. He also shared his excitement about Vodia PBX version 69.5.6, which includes real-time AI integration with OpenAI and call transcription using the Whisper API. The event confirmed that AI is rapidly becoming a core component of modern communication platforms—and Vodia is well-positioned to lead the way.

March 26, 2025