Presence Examples¶

Publish¶

Subscribe¶

SENDING: Packet 10348, +13:04:47.968704
2013-03-15 08:43:21.066174: 192.168.1.57:54336 -(SIP over tls)-> 85.17.186.7:5061
SUBSCRIBE sip:ag+presence@sip2sip.info SIP/2.0
Via: SIP/2.0/tls 192.168.1.57:54336;rport;branch=z9hG4bKPjxzWxyHoyQE1B14kzh2e5HzQ1fe9YCxAS
Max-Forwards: 70
From: "Adrian Georgescu" <sip:ag@sip2sip.info>;tag=Nk9vYs7jSrxoFxJlHhpGqp5ratba8.fZ
To: <sip:ag+presence@sip2sip.info>
Contact: <sip:18692507@192.168.1.57:62448;transport=tls>
Call-ID: LxLofW8im8tXeSeqtFD9eLx.Qww7dgZv
CSeq: 4102 SUBSCRIBE
Event: presence
Expires: 300
Accept: multipart/related, application/rlmi+xml, application/pidf+xml
Allow-Events: conference, message-summary, dialog, presence, presence.winfo, xcap-diff, dialog.winfo, refer
Supported: eventlist
User-Agent: Blink Pro 2.1.0 (MacOSX)
Proxy-Authorization: Digest username="ag", realm="sip2sip.info", nonce="5142d136c3cd3c566c348c811f3e61d73901e538", uri="sip:ag+presence@sip2sip.info", response="141b2c3c3b0d5a06bc0276a60f350f85" 
Content-Length:  0

RECEIVED: Packet 10349, +13:04:47.972002
2013-03-15 08:43:21.069472: 85.17.186.7:5061 -(SIP over tls)-> 192.168.1.57:54336
SIP/2.0 200 OK
Record-Route: <sip:85.17.186.7;transport=tcp;r2=on;lr;ftag=sQgfZ4lW3hmwYxKzERR3aGzVsiz8gP9S>
Record-Route: <sip:85.17.186.7:5061;transport=tls;r2=on;lr;ftag=sQgfZ4lW3hmwYxKzERR3aGzVsiz8gP9S>
Via: SIP/2.0/tls 192.168.1.57:54336;received=82.161.39.123;rport=54336;branch=z9hG4bKPjONne8WosnfVUF.pr4FIZILX9BlPbwzjz
From: "Adrian Georgescu" <sip:ag@sip2sip.info>;tag=sQgfZ4lW3hmwYxKzERR3aGzVsiz8gP9S
To: <sip:ag@sip2sip.info>;tag=104fb72fe3a4f8dc6b8eaad6b52e574f-3e38
Call-ID: jBS0ToEV8.ieDf8yBhQ-rIaQ7kc9ITA3
CSeq: 10974 SUBSCRIBE
Expires: 300
Contact: <sip:presence@81.23.228.129;transport=tcp>
Server: SIP Thor on OpenSIPS XS 1.9.0
Content-Length: 0

Notify¶

RECEIVED: Packet 10355, +13:04:48.004262
2013-03-15 08:43:21.101732: 85.17.186.7:5061 -(SIP over tls)-> 192.168.1.57:54336
NOTIFY sip:18692507@82.161.39.123:54336;transport=tls SIP/2.0
Record-Route: <sip:85.17.186.7:5061;transport=tls;r2=on;lr;ftag=104fb72fe3a4f8dc6b8eaad6b52e574f-9b73>
Record-Route: <sip:85.17.186.7;transport=tcp;r2=on;lr;ftag=104fb72fe3a4f8dc6b8eaad6b52e574f-9b73>
Via: SIP/2.0/TLS 85.17.186.7:5061;branch=z9hG4bK39f1.17cb9ca3.0;i=dfb06
Via: SIP/2.0/TCP 81.23.228.129:5060;rport=33450;received=81.23.228.129;branch=z9hG4bK39f1.ff127ab1.0
To: <sip:ag@sip2sip.info>;tag=Nk9vYs7jSrxoFxJlHhpGqp5ratba8.fZ
From: <sip:ag+presence@sip2sip.info>;tag=104fb72fe3a4f8dc6b8eaad6b52e574f-9b73
CSeq: 1 NOTIFY
Call-ID: LxLofW8im8tXeSeqtFD9eLx.Qww7dgZv
Max-Forwards: 69
Content-Length: 2737
User-Agent: SIP Thor on OpenSIPS XS 1.9.0
Event: presence
Contact: <sip:rls@81.23.228.129:33450;transport=tcp>
Subscription-State: active;expires=300
Require: eventlist
Content-Type: multipart/related;type="application/rlmi+xml";start="<1363333400.sip:ag+presence@sip2sip.info.41798616>";boundary="De4MDAaTbj3SuLeANRB15T2r" 

--De4MDAaTbj3SuLeANRB15T2r
Content-Transfer-Encoding: binary
Content-ID: <1363333400.sip:ag+presence@sip2sip.info.41798616>
Content-Type: application/rlmi+xml;charset="UTF-8" 

<?xml version="1.0"?>
<list uri="sip:ag+presence
...