Jump to content



Recommended Posts

any plans to support this:


PUBLISH sip:204@demo.com SIP/2.0

Via: SIP/2.0/UDP;rport;branch=z9hG4bKPjDs7OJ5FzkCTwuLDu2fGTzY0EnOVptA0s

Max-Forwards: 70

From: "204" <sip:204@demo.com>;tag=Xyic-H.r4wwRlxf2TDYBmhKsQgh0B2GG

To: "204" <sip:204@demo.com>

Call-ID: 9Z9yh2fCNON-3Wyq-xwk6j1JR6yDEyHO

CSeq: 26503 PUBLISH

Event: presence

Expires: 900

User-Agent: Bria iOS 2.3.4

Content-Type: application/pidf+xml

Content-Length: 282


<?xml version="1.0" encoding="UTF-8"?>

<presence entity="sip:204@demo.com" xmlns="urn:ietf:params:xml:ns:pidf">

<tuple id="cpodI8oEQm6EOWf8gTBoacDyzirEemmloQ">







Link to comment
Share on other sites

Supporting that is easy on the surface, and I think the PBX did and does that for many years. If someone subscribes for the presence state the PBX happily relays the messages. However the true problem is that you have to merge device state and PBX state. If it great if that soft phone feels that it is available, but what if there is a call recording a voice message of that extension because the DND has been set? Our answer was so far to leave the SIP presence state alone and use a PBX extension state in parallel. The PBX extension state is set only by the PBX, regardless of what device is registered. This way others can see when the extension is on a cell phone or on a ATA, without having to worry about those devices capability to generate PUBLISH messages.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...