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 making it so the PBX shows when a user is on the phone, even if the user is on an external device like a mobile phone. This is achieved via an HTTP request to the PBX from the mobile service provider, which updates presence status without the necessity of 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 doesn't want to be disturbed”. We already talked about how snom ONE publishes the presence state changes to Microsoft Lync when that person is on the phone.

With the 5.0.2 version, we started adding in the other direction: When someone talks on the phone without using the PBX, the PBX can still show the other users in the office users 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 update of 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 an HTTP request to a predefined URI that looks like this:

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

The PBX will assume 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 there is no phone call going on. Right now, the PBX doesn't populate the number to anybody else, nor does it poplulate the internal numbers. The URI may contain a parameter, “expires”, that tells the PBX for how long the extension is in a call, unless it explicitly clears the state with the empty number. The default value for this parameter is the maximum call duration on the system, which is usually two hours. This makes sure the status of the extensions gets cleared eventually, even if the service provider misses the clear update.

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

The other interesting note is 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. This would make it a lot easier for us to get this done in one of the next releases.

If someone out there has a wish as to what presence network we should address next, let us know. Feedback is always welcome.

Latest Articles

View All

Announcing the Vodia Prepaid Offer on AWS Marketplace

Vodia has launched a new prepaid PBX offering on AWS Marketplace, enabling businesses of all sizes to quickly and easily deploy a secure, feature-rich phone system in the cloud. Building on the success of our prepaid solutions for Microsoft Azure and DigitalOcean, this new AWS package offers a cost-effective, scalable, and reliable way to integrate enterprise-grade telephony into your existing infrastructure. Whether you're connecting SIP devices with Microsoft Teams via our certified SBC or establishing a standalone PBX, the deployment process is streamlined, flexible, and built for growth.

June 30, 2025

Mastering Vodia PBX Installation on Linux: A Complete Guide for System Administrators

Installing Vodia PBX on Linux offers system administrators a powerful, enterprise-grade communication solution with built-in monitoring, automated backups, and disaster recovery features. This guide walks through supported Linux distributions, pre-installation requirements, and step-by-step instructions using a universal install script. With options for service monitoring, backup scheduling, and cloud deployment, it ensures a scalable and secure setup. Post-installation, standard Linux tools manage service status, updates, and logs, making ongoing maintenance simple.

June 26, 2025

Vodia Now Integrates with Microsoft Dynamics 365

Vodia now integrates its industry-leading PBX with Microsoft Dynamics 365, enabling automatic synchronization of call data with the CRM to enhance customer interaction tracking and streamline communications. This integration offers features such as automatic contact creation for unknown numbers, comprehensive call activity logging including direction, duration, and outcomes, and seamless user matching for accurate call attribution. Designed to empower businesses, this connection supports more efficient and scalable communication workflows within the Microsoft ecosystem.

June 24, 2025