Presence-Anca Vamanu-Von SAN JOSE 2008

8/8/2019 Presence-Anca Vamanu-Von SAN JOSE 2008

1/27

Presence with OpenSER

Anca-Maria Vamanu

Senior Developer at Voice System

Presence designer for OpenSER Project


2/27

O

March 17 OpenSER Summit VoN 2008 San Jose, US

Outline

Presence Server

Centralized presence info exchange

XCAP based watcher permission rules

Pidf manipulation possibility

Presence extensions Implemented as presence user agents Get presence status from Register

Gateway to xmpp presence

Publish info from non SIP devices

Bridge Line Appearance (BLA)

Resource List Server (RLS) List subscriptions with an XCAP server


3/27

O


PRESENCESERVER


4/27

O


Old End-to-End Presence

A client receives requests from all other devices thatwant to see its status

SIP server

Wanttosee

test'sstatus

Want to see

test's' status

Wantto

see

test's'stat

us

W1

W2

W3

w1 request

w2 request

w3 request


5/27

O


Old End-to-End Presence

When availability status changes the client has tosend one notification for each watcher

I'm busytest is busy

testisbusy

testi

sbus

y

SIP server

I'm busy

I'm busy

I'm busy

W1

W2

W3


6/27

O


Presence with a Central Server

If central presence server is used, all presencerequests are handled by the presence server (PS)

Requesttest's

presence

Request test's

presence

Requestte

st's

presen

ce

SIP server

with

Presence Server

W1

W2

W3


7/27

O


Presence with a Central Server

When a status change occurs the client need tosend only one notification to the server and the

server deals with distributing the information

test is busy

testisbusy

testisbu

sy

I'm busySIP server

with

Presence Server

W1

W2

W3


8/27

O


Presence Server vs. End-to-end Presence

Presence with a central Server better than old end-to-end presence

Fewer SIP messages

Less processing overhead at the client

Possibility to manipulate presence information ( likepublish miscellaneous information from virtual user agents)

Get basic presence status from client registration status

Gateway to other presence protocols

Centralized storage (buddy list, presence-rules) that allows

service configuration sharing between devices ( using the

same account)


9/27

O


Features of OpenSER Presence Server

Can be integrated with end to end presence

Privacy/permission rules (define who can see thepresence status)

Based on XCAP server OpenXCAP integrated with OpenSER high speed

communication

OpenXCAPserverpresence-

rulesDatabase

OpenSER

Presence Server

watcherstatus


10/27

O



Independent entity, can be used in any siparchitecture

SIP Proxy

OpenSER

Presence Server

other SIP services

SUBSCRIBE/

PUBLISH

other customservices

Local domain


11/27

O



Scalability possibility Use more presence servers

Infinite number of usersOpenSER

Presence Server

1

OpenSER

Presence Server

N

SIP Proxy

Database


12/27

O



Pidf manipulation possibility (RFC 4827) Setting of permanent presence state that is independent of

activeness of any particular device

Use cases:

Publishing presence state for periods when there are no activedevices capable of publishing available;

Ex: traveling, vacations.

Advertising services that are open for communication;

Ex: e-mail, MMS and SMS

Setting the default state of any person, service, or device

The communication is through an XCAP server

OpenXCAP has support for pidf manipulation


13/27

O


Extensibility possibility

The current modules architecture:

presence

moduleSip entity

SUBSCRIBE/

PUBLISH

NOTIFY

presence_xml

module

presence_mwi

module

'presence', 'presence.winfo'

'dialog;sla'

event specific processing

'message-summary'

specific processing

other event

specific processing


14/27

O


Extensibility possibility

The implementation

General event independent core 'presence' module

'Client' modules that define events

At this time: presence_xml and presence_mwi (Event:message-summary)

New events can be easily added


15/27

O


PRESENCE

EXTENSIONS


16/27

O


Registration status to presence status

Publish'online'

Presence Server

Publish 'offline'

OpenSER registrar

with pua_usrloc

Register

unRegister


17/27

O


Registration status to presence status

Features Get presence information from Register

Publish presence status in behalf of clients with no

presence support

Limited to online/offline presence status Implemented in pua_usrloc module (used with pua module)


18/27

O


Presence Extensions in OpenSER

Publish information from non SIP devices Useful for monitoring or advertising

Uses Management Interface to push presence information

Implemented in pua_mi module (uses pua module)

Ex: a store publishing news through the presence of a virtual user


19/27

O


Gateway to XMPP presence

Presence gateway to XMPP (jabber) Possibility to see from SIP side the status(presence) of jabber

buddies and vice versa


20/27

O


Gateway to XMPP presence

Features Translates sub-status also

Transparent for users

The contacts from the other domain must be transformed to

as shown bellow:

At the SIP client:

sip:usernamejabber_server@gateway_domain

At the jabber client:

sip_usernameopenser_domain@xmpp_domain

defaults to '*'

Implemented in pua_xmpp modules (uses pua and xmpp

modules)


21/27

O


Presence Extensions in OpenSER

Bridge Line Appearance (BLA) Shared line with exclusive use only one inbound oroutbound call at a time

Notification mechanisms

Standard implemented in OpenSER : draft anil sipping bla

03 txt; Event:dialogl;sla

Known to work with Polycom and Snom phones

Implemented in pua_bla module (uses pua module)


22/27

O


RESOURCE LIST

SERVER


23/27

O


Resource List Server (RLS)

In a presence server architecture, a client has to send

presence requests for all the buddies in its contact list

Subscribe to ben

Presence ServerSubscribe to nicole

Subscribe to sam

Notify about ben

Notify about nicole

Notify about sam


24/27

O


Resource List Server (RLS)

A Resource List Server reduces the presence requests sent bythe client and notifies received to only one

OpenSER

RLS

XCAP

server

my buddy list

test's

buddy listSubscribe

to my listPRESENCE

SERVER

Notify

about your list

Subscribe

Notify


25/27

O


Resource List Server(RLS)Features

Independent can be used in any sip architecturewith any SIP presence server

Uses an external XCAP server

Integrated with OpenXCAP high speed

Still under testing Not many clients that have support for RLS


26/27

O


FUTURE

PLANS


27/27

O


Future

RLS testing and integration with clients

Optimize rules handling change the storing method: one rule per line

easier access and manipulation

'validity' feature real time efficient

XCAP-DIFF feature method to synchronize clients registered for the same account

with a SIP event notification mechanism

in collaboration with OpenXCAP

Presence-Anca Vamanu-Von SAN JOSE 2008

Documents

Transcript of Presence-Anca Vamanu-Von SAN JOSE 2008