Category:HowTo:Presence

From Snom User Wiki

(Difference between revisions)
Jump to: navigation, search
(Contact List)
m (Contact List)
 
(8 intermediate revisions not shown)
Line 1: Line 1:
-
== Introduction==
 
-
 
-
This feature consists of the following two methods:
 
-
# '''Presence State Publishing''': the phone user (extension) may publish its presence state, e.g. ''Online'', ''Offline (default)'', ''Invisible'', ''Busy'' in order to indicate its current communication status, i.e. availability and willingness to communicate, to other phone users or contacts.
 
-
# '''Contact List''': the phone user (extension) may receive updates about the communication status of other phone users (extensions), i.e. their availability and willingness to communicate.
 
-
 
== Configuration==
== Configuration==
Line 22: Line 16:
or use any free programmable key to call up the “Presence State” list
or use any free programmable key to call up the “Presence State” list
-
  [[Settings/fkey/presence|Free Programmable Function Keys P1-Px <Presence>]]
+
  [[Settings/F_PRESENCE|Free Programmable Function Keys P1-Px <Presence>]]
=== Contact List===
=== Contact List===
Line 31: Line 25:
For snom 320 / 360 / 370 only: Configure one context-sensitive key S1…S4 to call up the “Contacts“ list:
For snom 320 / 360 / 370 only: Configure one context-sensitive key S1…S4 to call up the “Contacts“ list:
-
  [[Settings/gui_fkey|Context-Sensitive Function Keys: Sx <Contacts>]]
+
  [[Settings/F_CONTACTS|Context-Sensitive Function Keys: Sx <Contacts>]]
== Usage ==
== Usage ==
Line 69: Line 63:
=== Contact List===
=== Contact List===
-
Do be able to build a contact list on your snom ühone, your server must support Resource Lists as defined in RFC 4662 (http://www.ietf.org/rfc/rfc4662.txt)
+
Io be able to build a contact list on your snom phone, your server must support Resource Lists as defined in RFC 4662 (http://www.ietf.org/rfc/rfc4662.txt)
Here is an example on how you can build a contact list of 3 contacts.
Here is an example on how you can build a contact list of 3 contacts.
-
First you set:
+
First we set:
* [[Settings/user_presence_subscription|Contact List]] to 'on'  
* [[Settings/user_presence_subscription|Contact List]] to 'on'  
* [[Settings/user_presence_buddy_list_uri|Contact List URI]] to '100@10.10.12.190'
* [[Settings/user_presence_buddy_list_uri|Contact List URI]] to '100@10.10.12.190'
Line 103: Line 97:
  Call-ID: 3c2780313513-bs5wfyu7fifh
  Call-ID: 3c2780313513-bs5wfyu7fifh
  CSeq: 1 SUBSCRIBE
  CSeq: 1 SUBSCRIBE
-
  Expires: 7200
+
  Expires: 3600
-
Require: eventlist
+
  Content-Length :0
  Content-Length :0
   
   
 +
 +
Next, the server sends a NOTIFY contaning the contact list and the states for each contact:
 +
  Received from udp:10.10.12.190:5060 at 8/3/2011 09:31:43:328 (2072 bytes):
  Received from udp:10.10.12.190:5060 at 8/3/2011 09:31:43:328 (2072 bytes):
   
   
Line 188: Line 184:
  Content-Length: 0
  Content-Length: 0
 +
Now if you set one of the Sx key to open the Contacts list, the list will look something like this:
-
Also see the instructions given in the [[Documentation/User_Manual|User Manual, page 86]]
+
:[[File:screenContacts.jpg]]
-
== SIP Flow ==
+
Also see the instructions given in the [[Documentation/User_Manual|User Manual, page 86]]
[[Category:HowTo]][[Category:Presence]]
[[Category:HowTo]][[Category:Presence]]

Latest revision as of 11:30, 25 August 2011

Contents

Configuration

Follow the instructions given in the User Manual, page 84:

Note: Your VoIP PBX must support this functionality. This feature is only available from firmware release 7 onwards. The following settings must have been configured in advance:

Presence State Publishing

Publish Presence:ON

For snom 320 / 360 / 370 only: Configure one context-sensitive key S1…S4 to call up the “Presence State” list and another one to call up the “Contacts“ list:

Context-Sensitive Function Keys: Sx <Presence>

or use any free programmable key to call up the “Presence State” list

Free Programmable Function Keys P1-Px <Presence>

Contact List

Contact List:ON
Contact List URI:<SIP URI>

For snom 320 / 360 / 370 only: Configure one context-sensitive key S1…S4 to call up the “Contacts“ list:

Context-Sensitive Function Keys: Sx <Contacts>

Usage

Presence State Publishing

Follow the instructions given in the User Manual, page 85

SIP Package: when you change your presence state to "Lunch", your phone will send the server a SIP package similar to:

PUBLISH sip:431@192.168.10.59 SIP/2.0
Via: SIP/2.0/UDP 10.10.12.136:2051;branch=z9hG4bK-i9mwzvn9bqv7;rport
From: "431" <sip:431@192.168.10.59>;tag=31xhncbjm9
To: "431" <sip:431@192.168.10.59>
Call-ID: 3c2698992729-frk2yiv6im5g
CSeq: 1 PUBLISH
Max-Forwards: 70
Event: presence
Expires: 3600
Content-Type: application/pidf+xml
Content-Length: 414 

<?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:im="urn:ietf:params:xml:ns:pidf:im"
entity="pres:431@192.168.10.59">
<tuple id="snom320-0004132495C2">
<status>
<basic>open</basic>
<im:im>Lunch</im:im>
</status>
<contact priority="1.00">sip:431@192.168.10.59</contact>
<note xml:lang="en">Lunch</note>
</tuple>
</presence>

Contact List

Io be able to build a contact list on your snom phone, your server must support Resource Lists as defined in RFC 4662 (http://www.ietf.org/rfc/rfc4662.txt)

Here is an example on how you can build a contact list of 3 contacts.

First we set:

Sent to udp:10.10.12.190:5060 at 8/3/2011 09:31:43:249 (542 bytes):

SUBSCRIBE sip:100@10.10.12.190;user=phone SIP/2.0 
Via: SIP/2.0/UDP 10.10.12.130:1027;branch=z9hG4bK-omtesyzy6kev;rport 
From: <sip:100@10.10.12.60>;tag=tj169z062h
To: <sip:100@10.10.12.190;user=phone>
Call-ID: 3c2780313513-bs5wfyu7fifh
CSeq: 1 SUBSCRIBE
Max-Forwards: 70
Contact: <sip:100@10.10.12.130:1027>;reg-id=1
Event: presence
Accept: application/pidf+xml, application/rlmi+xml, multipart/related
Supported: eventlist
User-Agent: snom370/8.4.18
Proxy-Require: com.nortelnetworks.firewall
Expires: 3600
Content-Length: 0

Received from udp:10.10.12.190:5060 at 8/3/2011 09:31:43:319 (292 bytes):

SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.10.12.130:1026;branch=z9hG4bK-omtesyzy6kev;rport=1026
From: <sip:100@10.10.12.60>;tag=tj169z062h
To: <sip:100@10.10.12.190;user=phone>;tag=1
Call-ID: 3c2780313513-bs5wfyu7fifh
CSeq: 1 SUBSCRIBE
Expires: 3600
Content-Length :0

Next, the server sends a NOTIFY contaning the contact list and the states for each contact:

Received from udp:10.10.12.190:5060 at 8/3/2011 09:31:43:328 (2072 bytes):

NOTIFY sip:100@10.10.12.130;user=phone SIP/2.0
Via: SIP/2.0/UDP 10.10.12.190:5060;branch=z9hG4bK-3c2780313513-bs5wfyu7fifh1;rport
From: <sip:100@10.10.12.130>;tag=1
To: <sip:100@10.10.12.130;user=phone>
Call-ID: 3c2780313513-bs5wfyu7fifh
CSeq: 997935770 NOTIFY
Contact: <sip:pres.vancouver.example.com>
Event: presence
Subscription-State: active;expires=7200
Require: eventlist
Content-Type: multipart/related;type="application/rlmi+xml";boundary="50UBfW7LSCVLtggUPe5z"
Content-Length: 1566

--50UBfW7LSCVLtggUPe5z
Content-Type: application/rlmi+xml;;charset="UTF-8"

<?xml version="1.0" encoding="UTF-8"?>
<list xmlns="urn:ietf:params:xml:ns:rlmi"
uri="sip:adam-friends@stockholm.example.org" version="1"
fullState="true">
<name xml:lang="en">Buddy List at COM</name>
<name xml:lang="de">Liste der Freunde an COM</name>
<resource uri="sip:joe@stockholm.example.org">
<name>Joe Thomas</name>
<instance id="1" state=StrUtils::kActive
cid="joe@stockholm.example.org"/>
</resource>
<resource uri="sip:106@10.10.12.60">
<name>Mark Edwards</name>
<instance id="1" state=StrUtils::kActive
cid="mark@stockholm.example.org"/>
</resource>
<resource uri="sip:101@10.10.12.60">
<name>Marie Edwards</name>
<instance id="1" state=StrUtils::kActive
cid="mariem@stockholm.example.org"/>
</resource>
</list>

--50UBfW7LSCVLtggUPe5z
Content-Type: application/pidf+xml;charset="UTF-8"

<?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf"
entity="sip:joe@stockholm.example.org">
<tuple id="sg89ae">
<status>
<basic>open</basic>
</status>
<contact priority="1.0">sip:joe@stockholm.example.org</contact>
</tuple>
</presence>

--50UBfW7LSCVLtggUPe5z
Content-Type: application/pidf+xml;charset="UTF-8"

<?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf"
entity="sip:101@10.10.12.60">
<tuple id="sg89ar">
<status>
<basic>closed</basic>
</status>
<contact priority="1.0">sip:mariem@stockholm.example.org</contact>
</tuple>
</presence>

--50UBfW7LSCVLtggUPe5z--

Sent to udp:10.10.12.190:5060 at 8/3/2011 09:31:43:675 (261 bytes):

SIP/2.0 200 Ok
Via: SIP/2.0/UDP 10.10.12.190:5060;branch=z9hG4bK-3c2780313513-bs5wfyu7fifh1;rport=5060
From: <sip:100@10.10.12.130>;tag=1
To: <sip:100@10.10.12.130;user=phone>
Call-ID: 3c2780313513-bs5wfyu7fifh
CSeq: 997935770 NOTIFY
Content-Length: 0

Now if you set one of the Sx key to open the Contacts list, the list will look something like this:

File:screenContacts.jpg

Also see the instructions given in the User Manual, page 86

This category currently contains no pages or media.

Personal tools
Interoperability