1 / 10

IETF SPIRITS WG

IETF SPIRITS WG. 56 th IETF, San Francisco, CA Early implementation of the SPIRITS protocol < draft-gurbani-spirits-implementation-00.txt > Presented by: Vijay Gurbani. Services Implemented. 2 Services have been implemented using SPIRITS: Presence for phone lines

sawyer-thompson
Download Presentation

IETF SPIRITS WG

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IETF SPIRITS WG 56th IETF, San Francisco, CA Early implementation of the SPIRITS protocol <draft-gurbani-spirits-implementation-00.txt> Presented by: Vijay Gurbani

  2. Services Implemented • 2 Services have been implemented using SPIRITS: • Presence for phone lines • Instant Messaging from PSTN -> Internet

  3. Presence • Four DPs needed to consider presence for phone lines: • OAA (Origination Attempt Authorized) • TA (Termination Answer) • OD (Origination Disconnect) • TD (Termination Disconnect)

  4. Presence SUBSCRIBE sip:192.168.1.2:9001 SIP/2.0 Event: spirits-INDPs Allow: SUBSCRIBE, NOTIFY Accept: application/spirits-event, application/cpim-pidf+xml Content-Type: application/spirits-event Content-Length: 462 … <?xml version="1.0"?> <spirits-event> <DP INDPs="TA" Mode="N"> <CalledPartySubaddress>5552207722</CalledPartySubaddress> </DP> <DP INDPs="OAA" Mode="N"> <CallingPartySubaddress>5552207722</CallingPartySubaddress> </DP> <DP INDPs="OD" Mode="N"> <CalledPartySubaddress>5552207722</CalledPartySubaddress> </DP> <DP INDPs="TD" Mode="N"> <CalledPartySubaddress>5552207722</CalledPartySubaddress> </DP> </spirits-event>

  5. Presence • When any of the events occurred, 2 NOTIFY requests were sent to the SPIRITS UA: • One contained the DP that was triggered • The other one contained a PIDF (Presence Information Data Format) document corresponding to the presence state of the device.

  6. Presence NOTIFY sip:192.168.1.1:9090 SIP/2.0 Content-Type: application/cpim-pidf+xml … Subscription-State: active Content-Length: 416 <?xml version="1.0"?> <presence xlmns="urn:ietf:params:xml:ns:cpim-pidf" xlmns:local="urn:lucent-com:pidf-category" entity="pres:5552207722@lucent.com"> <tuple id="910ss1"> <status> <basic>CLOSED</basic> <local:category> In a call since Thu Feb 20 14:56:54 2003 </local:category> </status> <contact>sip:5552207722@lucent.com</contact> </tuple> </presence>

  7. Presence

  8. Instant Messaging • SPIRITS UA subscribes to a TAA on a line. • When the event occurs, the PSTN sends two requests to the SPIRITS UA: • The NOTIFY request • A SIP MESSAGE request

  9. Instant Messaging SUBSCRIBE sip:192.168.1.2:9001 SIP/2.0 Allow: SUBSCRIBE, NOTIFY, MESSAGE Accept: application/spirits-event, text/plain Content-Type: application/spirits-event ... Content-Length: 154 <?xml version="1.0"?> <spirits-event> <DP INDPs="TAA" Mode="N"> <CalledPartySubaddress>5552202040</CalledPartySubaddress> </DP> </spirits-event>

  10. Instant Messaging

More Related