From 360d2ec0e0795b2281acd2b049ca3f913c8ebc1a Mon Sep 17 00:00:00 2001 From: Devon-White Date: Tue, 8 Sep 2026 11:04:03 -0400 Subject: [PATCH 1/2] docs(sip): state that SIP presence and PIDF-LO are not supported Adds a 'Presence and location support' section to the SIP overview so the docs (and the Sigmond retriever) answer the 'PIDF-LO / SIP presence' question directly instead of falling through to unrelated pages. Closes signalwire/cloud-product#20822 Co-Authored-By: Claude Fable 5.1 --- .../platform/pages/calling/voice/SIP/index.mdx | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/fern/products/platform/pages/calling/voice/SIP/index.mdx b/fern/products/platform/pages/calling/voice/SIP/index.mdx index 8124826d60..2182c7678d 100644 --- a/fern/products/platform/pages/calling/voice/SIP/index.mdx +++ b/fern/products/platform/pages/calling/voice/SIP/index.mdx @@ -18,6 +18,8 @@ SIP is fundamental to modern Voice over IP (VoIP) communications and enables fea - Presence information - Multimedia distribution +These are capabilities of the protocol in general. See [Presence and location support](#presence-and-location-support) for which of them SignalWire supports. + Getting started with SIP involves understanding a few key components: - SIP endpoints (phones, softphones, or applications) - SIP servers (proxies, registrars) @@ -82,6 +84,16 @@ SIP calling consolidates your entire communication network into a handful of dev Most SIP providers offer wideband audio or HD voice with a higher sample rate of telephone audio, giving your phone higher fidelity audio than other systems. +## Presence and location support + +Two SIP features that other providers sometimes bundle with a SIP trunk aren't supported on SignalWire: SIP presence and PIDF-LO location objects. + +**SIP presence** is the SUBSCRIBE/NOTIFY event package that lets one SIP device watch another's status, with state carried in PIDF (Presence Information Data Format) bodies. Busy lamp field (BLF) keys and online/offline indicators in desk phones and softphones depend on it. SignalWire doesn't accept presence subscriptions, so devices registered with SIP Credentials can't watch each other's status. The Dashboard shows whether a SIP Credential is currently registered, but there is no API or webhook for registration state. + +**PIDF-LO** (Presence Information Data Format Location Object, RFC 4119 and RFC 5491) attaches a caller's location to an INVITE through a `Geolocation` header, so a 911 call can carry a per-call location. SignalWire doesn't read PIDF-LO from inbound INVITEs or add it to emergency calls. The location the dispatcher sees comes from the emergency address you register and assign to the phone number. See [E911](/docs/platform/e911) to set one up, and update the assigned address when a device moves. + +If you need either capability, contact [SignalWire support](https://support.signalwire.com) so the request is on record. + ## Using a softphone with SignalWire [#softphone-configuration] Any SIP-compatible softphone (such as Zoiper, Bria, Linphone, MicroSIP, or 3CX) can be used with a SignalWire SIP Credential. From 650df08812ab6aeb624913f58780d7108caaeb6f Mon Sep 17 00:00:00 2001 From: Devon-White Date: Thu, 10 Sep 2026 12:35:36 -0400 Subject: [PATCH 2/2] docs(sip): address review feedback on presence and location section - Dashboard shows last-registered time, not live registration state - Drop bold labels from paragraph openers - Point the Benefits list at the support section too - Frame emergency location around the registered E911 address --- .../platform/pages/calling/voice/SIP/index.mdx | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/fern/products/platform/pages/calling/voice/SIP/index.mdx b/fern/products/platform/pages/calling/voice/SIP/index.mdx index 2182c7678d..a0dbee95f2 100644 --- a/fern/products/platform/pages/calling/voice/SIP/index.mdx +++ b/fern/products/platform/pages/calling/voice/SIP/index.mdx @@ -64,6 +64,8 @@ SIP phone systems enable you to perform a wide range of functions that a traditi - Enabling instant messaging, multimedia conferences, user presence information, and E911 calls for emergencies. - Bridging different sets of equipment and software by negotiating common capabilities before the calls start, akin to two people who speak different languages finding a way to communicate. SIP has the benefit of working with diverse vendors and setups as long as they share even a fraction of similar capabilities. +These are functions of the protocol, and support for them varies by provider. See [Presence and location support](#presence-and-location-support) for the location, availability, and presence items on this list. + #### Affordability As we alluded to earlier, a big benefit of alternating to a SIP trunk is price-oriented. We had mentioned how you save on long-range calls and international calls due to every call being viewed as a local call through SIP. However, there are other areas that a SIP trunk saves money in, including: @@ -86,13 +88,13 @@ Most SIP providers offer wideband audio or HD voice with a higher sample rate of ## Presence and location support -Two SIP features that other providers sometimes bundle with a SIP trunk aren't supported on SignalWire: SIP presence and PIDF-LO location objects. +SIP presence and PIDF-LO location objects are two SIP features that other providers sometimes bundle with a SIP trunk. SignalWire handles both differently: presence isn't supported, and emergency location comes from an address you register rather than from the call. -**SIP presence** is the SUBSCRIBE/NOTIFY event package that lets one SIP device watch another's status, with state carried in PIDF (Presence Information Data Format) bodies. Busy lamp field (BLF) keys and online/offline indicators in desk phones and softphones depend on it. SignalWire doesn't accept presence subscriptions, so devices registered with SIP Credentials can't watch each other's status. The Dashboard shows whether a SIP Credential is currently registered, but there is no API or webhook for registration state. +SIP presence is the SUBSCRIBE/NOTIFY event package that lets one SIP device watch another's status, with state carried in PIDF (Presence Information Data Format) bodies. Busy lamp field (BLF) keys and online/offline indicators in desk phones and softphones depend on it. SignalWire doesn't accept presence subscriptions, so devices registered with SIP Credentials can't watch each other's status. The Dashboard shows when a SIP Credential last registered, but there is no API or webhook for registration state. -**PIDF-LO** (Presence Information Data Format Location Object, RFC 4119 and RFC 5491) attaches a caller's location to an INVITE through a `Geolocation` header, so a 911 call can carry a per-call location. SignalWire doesn't read PIDF-LO from inbound INVITEs or add it to emergency calls. The location the dispatcher sees comes from the emergency address you register and assign to the phone number. See [E911](/docs/platform/e911) to set one up, and update the assigned address when a device moves. +PIDF-LO (Presence Information Data Format Location Object, RFC 4119 and RFC 5491) is how some networks attach a per-call location to a 911 call, carried on the INVITE through a `Geolocation` header. On SignalWire, the location a dispatcher receives comes from the emergency address you register and assign to the phone number. See [E911](/docs/platform/e911) to set one up, and update the assigned address when a device moves. -If you need either capability, contact [SignalWire support](https://support.signalwire.com) so the request is on record. +To request either capability, contact [SignalWire support](https://support.signalwire.com). ## Using a softphone with SignalWire [#softphone-configuration]