Search in book...
Toggle Font Controls
Create new playlist

Name your new playlist

Playlist description (optional)
Sign In

Email address

Password

Forgot Password?

or

Continue with Facebook

Continue with Google
Sign Up

Full Name

Email address

Confirm Email Address

Password

or

Continue with Facebook

Continue with Google

Examining the Technical Details Behind the Public IM Connectivity Scenario

To understand network message flow in the Public IM Connectivity scenario, let's look at two scenarios and the accompanying illustrations of the resulting message flows.

Scenario One: Adding a Contact in Office Communicator 2007

In this scenario, the user enters an account name for a recipient she wants to send instant messages to, performs a search, and adds the recipient account name as a contact. We'll examine seven steps in this process, and these steps are numerically keyed to Figure 8-10. Where possible, each step is illustrated using a corresponding sample SIP message. The illustrative SIP output following the steps is what an admin might see using logging to trace the messages.

Figure 8-10. Communicator Startup

Step 1: Specify Recipient's Account

The user types in [email protected] for a user search. The 'Message Body' shows that the information was sent to the recipient's public IM servers:

Start-Line: SUBSCRIBE sip:[email protected] SIP/2.0
From: "PIC Test (pic1)
lcsent01"<sip:[email protected]>;tag=dfac414f0f;epid=ce4ccd49ad
To: <sip:[email protected]>
CSeq: 1 SUBSCRIBE
Call-ID: cecb8c21ba01462a90f2f7235673f2b9
Via: SIP/2.0/TLS 10.55.55.22:4231;branch=z9hG4bK0D6A9383.D119DEC5;branched=FALSE
Max-Forwards: 68
Via: SIP/2.0/TLS 10.55.55.33:47696;branch=z9hG4bKC45BE092.1A435385;branched=FALSE;ms-
received-port=47696;
    ms-received-cid=200
ms-user-data: ms-publiccloud=true;ms-federation=true
Via: SIP/2.0/TLS 10.55.55.22:4317;ms-received-port=4317;ms-received-cid=67F00
Contact:
<sip:[email protected];opaque=user:epid:XHiWcZA4TlaDkwMgksvyrQAA;gruu>
User-Agent: UCCP/2.0.6362.0 OC/2.0.6362.0 (Microsoft Office Communicator)
Event: presence
Accept: application/msrtc-event-categories+xml, application/xpidf+xml, text/
xml+msrtc.pidf, application/pidf+xml,
    application/rlmi+xml, multipart/related
Supported: com.microsoft.autoextend
Supported: ms-piggyback-first-notify
Expires: 0
Require: adhoclist, categoryList
Supported: eventlist
Content-Type: application/msrtc-adrl-categorylist+xml
Content-Length: 472
Message-Body: <batchSub xmlns="http://schemas.microsoft.com/2006/01/sip/batch-subscribe"
uri=
    "sip:[email protected]" name=""><action name="subscribe"
id="1008728"><adhocList><resource uri=
    "sip:[email protected]"/></adhocList><categoryList xmlns="http://schemas.microsoft.com/
2006/09/sip/categorylist">
    <category name="calendarData"/><category name="contactCard"/>
    <category name="note"/><category name="services"/><category name="state"/></
categoryList></action></batchSub>

Step 2: Recipient's Presence Displayed as Unknown

The account comes up, presence shows as unknown after a short delay, and the information relating to the reason is reflected in the ms-diagnostics

"SIPPROXY_E_EPROUTING_MSG_INT_GET_RICH_PRESENCE_FILTERED", indicating that the presence information was filtered.

Start-Line: SIP/2.0 403 Forbidden
From: "PIC Test (pic1)
lcsent01"<sip:[email protected]>;tag=dfac414f0f;epid=ce4ccd49ad
To: <sip:[email protected]>;tag=C122BE2A56CD774DA0AC6DEC165DB900
CSeq: 1 SUBSCRIBE
Call-ID: cecb8c21ba01462a90f2f7235673f2b9
ms-edge-proxy-message-trust: ms-source-type=EdgeProxyGenerated;ms-ep-fqdn=lcs-ncx-
appool.lcsent01.directtaps.net;
    ms-source-verified-user=verified;ms-source-network=federation
Via: SIP/2.0/TLS
10.55.55.22:4231;branch=z9hG4bK0D6A9383.D119DEC5;branched=FALSE;received=10.154.154.101;
    ms-received-port=1239;ms-received-cid=400
Via: SIP/2.0/TLS 10.55.55.33:47696;branch=z9hG4bKC45BE092.1A435385;branched=FALSE;ms-
received-port=47696;
    ms-received-cid=200
Via: SIP/2.0/TLS 10.55.55.22:4317;ms-received-port=4317;ms-received-cid=67F00
ms-diagnostics: 2;reason="See response code and reason phrase";source="lcs-ncx-
appool.lcsent01.directtaps.net";
    HRESULT="C3E93D80(SIPPROXY_E_EPROUTING_MSG_INT_GET_RICH_PRESENCE_FILTERED)"
Content-Length: 0
Message-Body:

Step 3: Recipient's Account Added as a Contact

The user adds the account as a contact, allowing for Rich Presence information to be acknowledged and displayed in the client.

Start-Line: SUBSCRIBE sip:[email protected] SIP/2.0
From: "PIC Test (pic1)
lcsent01"<sip:[email protected]>;tag=f14fbece50;epid=ce4ccd49ad
To: <sip:[email protected]>
CSeq: 1 SUBSCRIBE
Call-ID: 44047f96df734fc5a6de19b16d3b8376
Via: SIP/2.0/TLS 10.55.55.22:4231;branch=z9hG4bK59C2C040.5D93021D;branched=FALSE
Max-Forwards: 68
Via: SIP/2.0/TLS 10.55.55.33:47696;branch=z9hG4bK93B4551E.58F79B23;branched=FALSE;ms-
received-port=47696;
    ms-received-cid=200
ms-user-data: ms-publiccloud=true;ms-federation=true
Via: SIP/2.0/TLS 10.55.55.22:4317;ms-received-port=4317;ms-received-cid=67F00
Contact:
<sip:[email protected];opaque=user:epid:XHiWcZA4TlaDkwMgksvyrQAA;gruu>
User-Agent: UCCP/2.0.6362.0 OC/2.0.6362.0 (Microsoft Office Communicator)
Event: presence
Accept: application/msrtc-event-categories+xml, application/xpidf+xml, text/
xml+msrtc.pidf,
     application/pidf+xml, application/rlmi+xml, multipart/related
Supported: com.microsoft.autoextend
Supported: ms-piggyback-first-notify
Content-Type: application/msrtc-adrl-categorylist+xml
Content-Length: 501
Message-Body: <batchSub xmlns="http://schemas.microsoft.com/2006/01/sip/batch-subscribe"
uri=
"sip:[email protected]" name=""><action name="subscribe"
id="1008912"><adhocList><resource uri="sip:[email protected]"><context></context></
resource></adhocList><categoryList xmlns="http://schemas.microsoft.com/2006/09/sip/
categorylist"><category name="calendarData"/>
    <category name="contactCard"/><category name="note"/><category name="services"/
><category name="state"/></categoryList></action></batchSub>

Step 4: Recipient's Presence Displayed as Offline

Account presence shows as offline, indicating that the Rich Presence is now working as expected and that the contact is offline at the current time.

Start-Line: NOTIFY
sip:[email protected];opaque=user:epid:XHiWcZA4TlaDkwMgksvyrQAA;gruu SIP/2.0
From: <sip:[email protected]>;tag=65d68a1bc4
To: <sip:[email protected]>;epid="ce4ccd49ad;tag=f14fbece50
CSeq: 1 NOTIFY
Call-ID: 44047f96df734fc5a6de19b16d3b8376
Via: SIP/2.0/TLS 65.54.227.22:19001;branch=z9hG4bK2AAD5BF8.2DEAC26F;branched=FALSE;ms-
internal-info=
    "ca_zFI1fCgvjcqhFOqV_3zHH3WpGMA"
Max-Forwards: 69
ms-asserted-verification-level: ms-source-verified-user=verified
Via: SIP/2.0/TLS 65.54.230.13:8624;branch=z9hG4bKa69bfffe;ms-received-port=8624;ms-
received-cid=38892800
Route: <sip:lcs-ncx-
appool.lcsent01.directtaps.net:5061;transport=tls;epid=ce4ccd49ad;lr>
CONTACT: <sip:[email protected]:5061;transport=tls;maddr=BAYM-TG399.tgw.messenger.msn.com>
CONTENT-LENGTH: 489
EVENT: presence
SUBSCRIPTION-STATE: active
CONTENT-TYPE: application/pidf+xml
Message-Body: <?xml version="1.0" encoding="utf-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:ep="urn:ietf:params:xml:ns:pidf:status:rpid-status"
xmlns:et="urn:ietf:params:xml:ns:pidf:rpid-tuple"
xmlns:ci="urn:ietf:params:xml:ns:pidf:cipid"
    entity="sip:[email protected]">
  <tuple id="0">
    <status>
      <basic>closed</basic>
    </status>
  </tuple>
 <ci:icon>https://images.edge.messenger.live.com/wlnavbtn.png</ci:icon>
  <ci:display-name>lcs</ci:display-name>
</presence>

Step 5: Recipient Receives Notification

User [email protected] gets a popup window that indicates that Office Communicator user 'pic1' has added Kim to her contacts.

Step 6: Recipient Adds a User to Buddy List

User [email protected] adds the Office Communicator user to his buddy list.

Step 7: Recipient's Presence Displayed as Online

Presence shows as online in Office Communicator for [email protected] because a full round trip series of SIP messages from sender to recipient are now being sent and received.

Start-Line: NOTIFY
sip:[email protected];opaque=user:epid:XHiWcZA4TlaDkwMgksvyrQAA;gruu SIP/2.0
From: <sip:[email protected]>;tag=65d68a1bc4
To: <sip:[email protected]>;epid="ce4ccd49ad;tag=f14fbece50
CSeq: 1 NOTIFY
Call-ID: 44047f96df734fc5a6de19b16d3b8376
Max-Forwards: 69
ms-asserted-verification-level: ms-source-verified-user=verified
Via: SIP/2.0/TLS 65.54.230.13:8624;branch=z9hG4bKa69bfffe;ms-received-port=8624;ms-
received-cid=38892800
Route: <sip:lcs-ncx-
appool.lcsent01.directtaps.net:5061;transport=tls;epid=ce4ccd49ad;lr>
CONTACT: <sip:[email protected]:5061;transport=tls;maddr=BAYM-TG399.tgw.messenger.msn.com>
CONTENT-LENGTH: 489
EVENT: presence
SUBSCRIPTION-STATE: active
CONTENT-TYPE: application/pidf+xml
Message-Body: <?xml version="1.0" encoding="utf-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:ep="urn:ietf:params:xml:ns:pidf:status:rpid-status"xmlns:et=
  "urn:ietf:params:xml:ns:pidf:rpid-tuple" xmlns:ci="urn:ietf:params:xml:ns:pidf:cipid"
    entity="sip:[email protected]">
  <tuple id="0-id002">
    <status>
      <basic>open</basic>
    </status>
  </tuple>
 <ci:icon>https://images.edge.messenger.live.com/wlnavbtn.png</ci:icon>
  <ci:display-name>lcs</ci:display-name>
</presence>

Scenario Two: Sending a Single Message

In this scenario, the user sends a single message to the recipient. Once again, we'll examine some steps in this process, with these steps being numerically keyed to Figure 8-11. And when possible, each step is illustrated using a corresponding sample SIP message.

Figure 8-11. Communicator Startup

Step 1: User Selects a Recipient from the Buddy List in Office Communicator

User double-clicks on '[email protected]' in Office Communicator to initiate a communication with her.

Step 2: User Types a Message to a Recipient

A messaging window opens, and the Office Communicator user types a message to [email protected].

Start-Line: INVITE sip:[email protected] SIP/2.0
From: "PIC Test (pic1)
lcsent01"<sip:[email protected]>;tag=d277e1abbb;epid=ce4ccd49ad
To: <sip:[email protected]>
CSeq: 1 INVITE
Call-ID: a9c41d4b12da43e4be363596f309fe4e
Record-Route: <sip:h06-
lct.lcsent01.directtaps.net:5061;transport=tls;lr>;tag=CE46965240D18C4A3635495C069DC843
Via: SIP/2.0/TLS 10.55.55.22:4231;branch=z9hG4bKEC456A32.C97CB7D0;branched=FALSE
Max-Forwards: 68
Content-Length: 201
Via: SIP/2.0/TLS 10.55.55.33:47696;branch=z9hG4bKC2D8526B.D28FDC17;branched=FALSE;ms-
received-port=47696;
    ms-received-cid=200
Via: SIP/2.0/TLS 10.55.55.22:4317;ms-received-port=4317;ms-received-cid=67F00
ms-user-data: ms-publiccloud=true;ms-federation=true
Record-Route: <sip:eepool07.lcsent01.directtaps.net:5061;transport=tls;ms-fe=h05-
lct.lcsent01.directtaps.net;
    ms-role-rs-to;lr>;tag=A520B519F64AB62075583DC8E1FC916C
Contact:
<sip:[email protected];opaque=user:epid:XHiWcZA4TlaDkwMgksvyrQAA;gruu>
User-Agent: UCCP/2.0.6362.0 OC/2.0.6362.0 (Microsoft Office Communicator)
ms-text-format: text/plain; charset=UTF-
8;msgr=WAAtAE0ATQBTAC0ASQBNAC0ARgBvAHIAbQBhAHQAOgAgAEYATgA9AE0AUwAlA

DIAMABTAGgAZQBsAGwAJQAyADAARABsAGcAJQAyADAAMgA7ACAARQBGAD0AOwAgAEMATwA9ADAAOwAgAEMAUwA9A
DAAOwAgAFAARgA9A
    DAACgANAAoADQA;ms-body=aGk=
Supported: ms-delayed-accept
Supported: ms-renders-isf
Supported: ms-renders-gif
Supported: ms-renders-mime-alternative
Ms-Conversation-ID: Acfmq6qEY4LFypq3QkiyeHTKN1rRTg==
Supported: timer
Supported: ms-sender
Supported: ms-early-media
Roster-Manager: sip:[email protected]
EndPoints: <sip:[email protected]>, <sip:[email protected]>
Supported: com.microsoft.rtc-multiparty
ms-keep-alive: UAC;hop-hop=yes
Supported: ms-conf-invite
Content-Type: application/sdp
Message-Body: v=0
o=- 0 0 IN IP4 10.55.55.22
s=session
c=IN IP4 10.55.55.22
t=0 0
m=message 5060 sip null
a=accept-types:text/rtf application/x-ms-ink image/gif multipart/alternative application/
ms-imdn+xml

Start-Line: SIP/2.0 200 OK
From: "PIC Test (pic1) lcsent01"
<sip:[email protected]>;tag=d277e1abbb;epid=ce4ccd49ad
To: <sip:[email protected]>;tag=1187999459aol
CSeq: 1 INVITE
Call-ID: a9c41d4b12da43e4be363596f309fe4e
Via: SIP/2.0/TLS 10.154.154.6:33660;branch=z9hG4bK81B1A184.E55C7B7D;branched=FALSE;ms-
internal-info="aahcQlfV2sxVHSijae9Oyn6FrB6JjlXHt9jtKVswAA"
Via: SIP/2.0/TLS
10.55.55.22:4231;branch=z9hG4bKEC456A32.C97CB7D0;branched=FALSE;received=10.154.154.101;
    ms-received-port=1239;ms-received-cid=400
Via: SIP/2.0/TLS 10.55.55.33:47696;branch=z9hG4bKC2D8526B.D28FDC17;branched=FALSE;ms-
received-port=47696;
    ms-received-cid=200
Via: SIP/2.0/TLS 10.55.55.22:4317;ms-received-port=4317;ms-received-cid=67F00
Record-Route:
<sip:sip.oscar.aol.com:5061;transport=tls;sag_conn_id=14509788;sag_qid=349;lr>
Record-Route: <sip:lcs-ncx-
appool.lcsent01.directtaps.net:5061;transport=tls;epid=ce4ccd49ad;lr;ms-key-info=

jACAAB63AIzSs4V0rObHAQECAAADZgAAAKQAAEq0o08howd1ofPQstatonzKqkw0xTDqkgxWH_u_jrMEmRFTjHu4
0odKnCTJhs
    5dWtmALBA9QzE6O-Xo0pCckSR6ntVyZSnCjAWZO3snPm2yL0s4nqlcEePfA2pIy1_HjCkIU-
2gr5mUfd9USmP3_p1sHtAO5d1Ic8QnhP-N
    GuWY55EM2SAZRvp7Zgtx6HHKug5Xgb7t-3a7-
qA6y0VBY51q_GmcNj7xcj9uKbMzhGkCjeWOXqCS0Tw6GlSvsNKqdASpsh8bh0wLxSZp
    PgCOn9L73HQq1bJwB_6QkmE0yniNzKX3sSq5w-JjW6vL_FFPjf75bsVtT5sU1xDyINWZVKkA;ms-route-
sig=aa0eCMX_rEFywBlBHQ
    lgewbsiUXbLlXHt94I5_cgAA>;msrrsig=aakgoM1icuCWdSXpbU9QJ60H6YKuzlXHt94I5_cgAA;
    tag=C122BE2A56CD774DA0AC6DEC165DB900
Record-Route: <sip:h06-
lct.lcsent01.directtaps.net:5061;transport=tls;lr>;tag=CE46965240D18C4A3635495C069DC843
Record-Route: <sip:eepool07.lcsent01.directtaps.net:5061;transport=tls;ms-fe=h05-
lct.lcsent01.directtaps.net;
    ms-role-rs-to;lr>;tag=A520B519F64AB62075583DC8E1FC916C
Contact: <sip:sip.oscar.aol.com:5061;maddr=64.12.162.248;transport=tls>
Ms-asserted-verification-level: ms-source-verified-user=verified
Content-Type: application/sdp
Content-Length: 102
Message-Body: v=0
o=- 0 0 IN IP4 64.12.162.248
s=session
c=IN IP4 64.12.162.248
t=0 0
m=message 5060 sip null
Start-Line: ACK sip:sip.oscar.aol.com:5061;maddr=64.12.162.248;transport=tls SIP/2.0
From: <sip:[email protected]>;tag=d277e1abbb;epid=ce4ccd49ad
To: <sip:[email protected]>;tag=1187999459aol
CSeq: 1 ACK
Call-ID: a9c41d4b12da43e4be363596f309fe4e
Via: SIP/2.0/TLS 10.55.55.22:4231;branch=z9hG4bKA38E2D41.9F92ED13;branched=FALSE
Max-Forwards: 68
Via: SIP/2.0/TLS 10.55.55.33:47696;branch=z9hG4bK668ACE7F.395877BC;branched=FALSE;ms-
received-port=47696;
    ms-received-cid=200
Via: SIP/2.0/TLS 10.55.55.22:4317;ms-received-port=4317;ms-received-cid=67F00
Route: <sip:lcs-ncx-appool.lcsent01.directtaps.net:5061;transport=tls;lr>
Route: <sip:sip.oscar.aol.com:5061;transport=tls;sag_conn_id=14509788;sag_qid=349;lr>
User-Agent: UCCP/2.0.6362.0 OC/2.0.6362.0 (Microsoft Office Communicator)
Content-Length: 0
Message-Body:

Step 3: Recipient Receives a Message from a User

The AOL user sees message text in the popup window and status information that says the Office Communicator user is typing.

Start-Line: MESSAGE sip:sip.oscar.aol.com:5061;maddr=64.12.162.248;transport=tls SIP/2.0
From: <sip:[email protected]>;tag=d277e1abbb;epid=ce4ccd49ad
To: <sip:[email protected]>;tag=1187999459aol
CSeq: 2 MESSAGE
Call-ID: a9c41d4b12da43e4be363596f309fe4e
Via: SIP/2.0/TLS 10.55.55.22:4231;branch=z9hG4bK9309E25C.B523C951;branched=FALSE
Max-Forwards: 68
Via: SIP/2.0/TLS 10.55.55.33:47696;branch=z9hG4bK37466F08.68B7CC23;branched=FALSE;ms-
received-port=47696;
    ms-received-cid=200
Via: SIP/2.0/TLS 10.55.55.22:4317;ms-received-port=4317;ms-received-cid=67F00
Route: <sip:lcs-ncx-appool.lcsent01.directtaps.net:5061;transport=tls;lr>
Route: <sip:sip.oscar.aol.com:5061;transport=tls;sag_conn_id=14509788;sag_qid=349;lr>
User-Agent: UCCP/2.0.6362.0 OC/2.0.6362.0 (Microsoft Office Communicator)
Supported: timer
Content-Type: text/plain; charset=UTF-
8;msgr=WAAtAE0ATQBTAC0ASQBNAC0ARgBvAHIAbQBhAHQAOgAgAEYATgA9AE0AUwAlA

DIAMABTAGgAZQBsAGwAJQAyADAARABsAGcAJQAyADAAMgA7ACAARQBGAD0AOwAgAEMATwA9ADAAOwAgAEMAUwA9A
DAAOwAgAFAARgA
    9ADAACgANAAoADQA
Content-Length: 2
Message-Body: hi

Start-Line: SIP/2.0 200 OK
From: <sip:[email protected]>;tag=d277e1abbb;epid=ce4ccd49ad
To: <sip:[email protected]>;tag=1187999459aol
CSeq: 2 MESSAGE
Call-ID: a9c41d4b12da43e4be363596f309fe4e
Via: SIP/2.0/TLS 10.154.154.6:33712;branch=z9hG4bK43E6514E.539273D2;branched=FALSE;ms-
internal-info="aaoiubm6MQ3y7wu_irYnn_hcAGaQdTknPSjtKVswAA"
Via: SIP/2.0/TLS
10.55.55.22:4231;branch=z9hG4bK9309E25C.B523C951;branched=FALSE;received=10.154.154.101;
    ms-received-port=1239;ms-received-cid=400
Via: SIP/2.0/TLS 10.55.55.33:47696;branch=z9hG4bK37466F08.68B7CC23;branched=FALSE;ms-
received-port=47696;
    ms-received-cid=200
Via: SIP/2.0/TLS 10.55.55.22:4317;ms-received-port=4317;ms-received-cid=67F00
Record-Route:
<sip:sip.oscar.aol.com:5061;transport=tls;sag_conn_id=4012686;sag_qid=351;lr>
Contact: <sip:sip.oscar.aol.com:5061;maddr=64.12.162.248;transport=tls>
Ms-asserted-verification-level: ms-source-verified-user=verified
Content-Length: 0
Message-Body:

Step 4: Recipient Types a Reply to the User

The AOL user types a message to the Office Communicator user in return.

Start-Line: INFO sip:[email protected] SIP/2.0
From: <sip:[email protected]>;tag=1187999459aol
To: <sip:[email protected]>;tag=d277e1abbb;epid=ce4ccd49ad
CSeq: 2 INFO
Call-ID: a9c41d4b12da43e4be363596f309fe4e
Via: SIP/2.0/TLS sip.oscar.aol.com:5061;branch=z9hG4bK.15d.46cf6eeb.6c72324
Record-Route: <sip:sip.oscar.aol.com:5061;transport=tls;sag_conn_id=14509963;
sag_qid=349;lr>
Contact: <sip:[email protected]:5061;maddr=64.12.162.248;transport=tls>
User-agent: AOL/1.0
Ms-asserted-verification-level: ms-source-verified-user=verified
Max-Forwards: 68
Content-Type: application/xml
Content-Length: 91
Message-Body: <?xml version="1.0"?>
<KeyboardActivity>
 <status status="type" />
</KeyboardActivity>

Start-Line: SIP/2.0 200 OK
From: <sip:[email protected]>;tag=1187999459aol
To: <sip:[email protected]>;tag=d277e1abbb;epid=ce4ccd49ad
CSeq: 2 INFO
Call-ID: a9c41d4b12da43e4be363596f309fe4e
Via: SIP/2.0/TLS
10.154.154.16:33589;branch=z9hG4bK9792A2C3.4400EA88;branched=FALSE;received=10.55.55.1;
    ms-received-port=31328;ms-received-cid=600
Via: SIP/2.0/TLS
sip.oscar.aol.com:5061;branch=z9hG4bK.15d.46cf6eeb.6c72324;received=64.12.162.248;
    ms-received-port=9577;ms-received-cid=2100
Contact:
<sip:[email protected];opaque=user:epid:XHiWcZA4TlaDkwMgksvyrQAA;gruu>
User-Agent: UCCP/2.0.6362.0 OC/2.0.6362.0 (Microsoft Office Communicator)
Content-Length: 0
Message-Body:

Start-Line: MESSAGE sip:[email protected] SIP/2.0
From: <sip:[email protected]>;tag=1187999459aol
To: <sip:[email protected]>;tag=d277e1abbb;epid=ce4ccd49ad
CSeq: 3 MESSAGE
Call-ID: a9c41d4b12da43e4be363596f309fe4e
Via: SIP/2.0/TLS 10.154.154.16:33589;branch=z9hG4bKA09E3A6E.C8BDC4F0;branched=FALSE
Max-Forwards: 67
ms-edge-proxy-message-trust: ms-source-type=AuthorizedServer;ms-ep-fqdn=lcs-ncx-
appool.lcsent01.directtaps.net;
    ms-source-verified-user=verified;ms-source-network=publiccloud
Via: SIP/2.0/TLS
sip.oscar.aol.com:5061;branch=z9hG4bK.15d.46cf6eeb.6c72325;received=64.12.162.248;
    ms-received-port=9577;ms-received-cid=2100
Record-Route:
<sip:sip.oscar.aol.com:5061;transport=tls;sag_conn_id=14509963;sag_qid=349;lr>
Contact: <sip:[email protected]:5061;maddr=64.12.162.248;transport=tls>
User-agent: AOL/1.0
Content-Type: text/plain; charset=UTF-8
Content-Length: 2
Message-Body: hi

Start-Line: SIP/2.0 200 OK
From: <sip:[email protected]>;tag=1187999459aol
To: <sip:[email protected]>;tag=d277e1abbb;epid=ce4ccd49ad
CSeq: 3 MESSAGE
Call-ID: a9c41d4b12da43e4be363596f309fe4e
ms-application-via: backend_token;ms-server=h05-lct.lcsent01.directtaps.net;ms-
pool=eepool07.lcsent01.directtaps.net;
    ms-application=51FB453D-5B9F-45df-83B4-ADD1F7E604A8
Via: SIP/2.0/TLS
10.154.154.16:33589;branch=z9hG4bKA09E3A6E.C8BDC4F0;branched=FALSE;received=10.55.55.1;
    ms-received-port=31328;ms-received-cid=600
Via: SIP/2.0/TLS
sip.oscar.aol.com:5061;branch=z9hG4bK.15d.46cf6eeb.6c72325;received=64.12.162.248;
    ms-received-port=9577;ms-received-cid=2100
Contact:
<sip:[email protected];opaque=user:epid:XHiWcZA4TlaDkwMgksvyrQAA;gruu>
User-Agent: UCCP/2.0.6362.0 OC/2.0.6362.0 (Microsoft Office Communicator)
Content-Length: 0
Message-Body:

Step 5: User Receives a Message from the Recipient

The Office Communicator user receives the message and status information that says the AOL user is typing.

Step 6: Conversation Finished

The Office Communicator user closes the IM window, which effectively ends the conversation and is indicated by the 'bye' message.

Start-Line: BYE sip:sip.oscar.aol.com:5061;maddr=64.12.162.248;transport=tls SIP/2.0
From: <sip:[email protected]>;tag=d277e1abbb;epid=ce4ccd49ad
To: <sip:[email protected]>;tag=1187999459aol
CSeq: 3 BYE
Call-ID: a9c41d4b12da43e4be363596f309fe4e
Via: SIP/2.0/TLS 10.55.55.22:4231;branch=z9hG4bK7CE0B719.C8CE110A;branched=FALSE
Max-Forwards: 68
Via: SIP/2.0/TLS 10.55.55.33:47696;branch=z9hG4bK08021091.03FE3863;branched=FALSE;ms-
received-port=47696;
    ms-received-cid=200
Via: SIP/2.0/TLS 10.55.55.22:4317;ms-received-port=4317;ms-received-cid=67F00
Route: <sip:lcs-ncx-appool.lcsent01.directtaps.net:5061;transport=tls;lr>
Route: <sip:sip.oscar.aol.com:5061;transport=tls;sag_conn_id=14509788;sag_qid=349;lr>
User-Agent: UCCP/2.0.6362.0 OC/2.0.6362.0 (Microsoft Office Communicator)
Content-Length: 0
Message-Body:

Start-Line: SIP/2.0 200 OK
From: <sip:[email protected]>;tag=d277e1abbb;epid=ce4ccd49ad
To: <sip:[email protected]>;tag=1187999459aol
CSeq: 3 BYE
Call-ID: a9c41d4b12da43e4be363596f309fe4e
Via: SIP/2.0/TLS 10.154.154.6:33712;branch=z9hG4bK7D675457.97F0C5F5;branched=FALSE;
    ms-internal-info="aa45b3VbBTS4SvYmwjsNPOk2BVBYaX8MX1jtKVswAA"
Via: SIP/2.0/TLS
10.55.55.22:4231;branch=z9hG4bK7CE0B719.C8CE110A;branched=FALSE;received=10.154.154.101;
     ms-received-port=1239;ms-received-cid=400
Via: SIP/2.0/TLS 10.55.55.33:47696;branch=z9hG4bK08021091.03FE3863;branched=FALSE;ms-
received-port=47696;
    ms-received-cid=200
Via: SIP/2.0/TLS 10.55.55.22:4317;ms-received-port=4317;ms-received-cid=67F00
Record-Route:
<sip:sip.oscar.aol.com:5061;transport=tls;sag_conn_id=4012686;sag_qid=351;lr>
Contact: <sip:sip.oscar.aol.com:5061;maddr=64.12.162.248;transport=tls>
Ms-asserted-verification-level: ms-source-verified-user=verified
Content-Length: 0
Message-Body:

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.

Table of Contents for Examining the Technical Details Behind the Public IM Connectivity Scenario

Create new playlist

Sign In

Sign Up