Technical Details Behind the Public IM Connectivity Scenarios

To understand network message flow in the Public IM Connectivity scenarios, the following sections will 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 that they want to send instant messages to, performs a search, and adds the recipient account name as a contact. This process has seven steps that are numerically keyed to Figure 8-9. Where possible, each step is illustrated by using a corresponding sample SIP message. The illustrative SIP output following the steps is what an administrator might see when using logging to trace the messages.

Communicator Startup

Figure 8-9. Communicator Startup

Step 1: Specify Recipient’s Account

The user types [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


<snip>

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 message that says "SIPPROXY_E_ EPROUTING_MSG_INT_GET_RICH_PRESENCE_FILTERED". This indicates 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
<snip>


HRESULT="C3E93D80(SIPPROXY_E_EPROUTING_MSG_INT_GET_RICH_PRESENCE_FILTERED)"

Step 3: Recipient’s Account Added as a Contact

The user adds the account as a contact, which allows 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


<snip>


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, which indicates 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:XHiWcZA4TlaDkwMgk
svyrQAA;gruu SIP/2.0
From: <sip:[email protected]>;tag=65d68a1bc4

To: <sip:[email protected]>;epid=ce4ccd49ad;tag=f14fbece50
CSeq: 1 NOTIFY


<snip>
EVENT: presence
SUBSCRIPTION-STATE: active
<snip>



    <status>
      <basic>closed</basic>
    </status>

Step 5: Recipient Receives Notification

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

Step 6: Recipient Adds a User to the Buddy List

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

Step 7: Recipient’s Presence Displayed as Online

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

From: <sip:[email protected]>;tag=65d68a1bc4
To: <sip:[email protected]>;epid=ce4ccd49ad;tag=f14fbece50
Start-Line: NOTIFY sip:[email protected];opaque=user:epid:XHiWcZA4TlaDkwMgk
svyrQAA;gruu SIP/2.0
From: <sip:[email protected]>;tag=65d68a1bc4
To: <sip:[email protected]>;epid=ce4ccd49ad;tag=f14fbece50
CSeq: 1 NOTIFY
<snip>CONTACT: <sip:[email protected]:5061;transport=tls;maddr=BAYM-TG399.tgw.messenger.
msn.com>
CONTENT-LENGTH: 489
EVENT: presence
SUBSCRIPTION-STATE: active
<snip>
    <status>
      <basic>open</basic>
    </status>

Scenario Two: Sending a Single Message

In this scenario, the user sends a single message to the recipient. This process has six steps that are numerically keyed to Figure 8-10. When possible, each step is illustrated by using a corresponding sample SIP message.

Communicator Startup; partner Access Edge Server to partner Access Edge Server communication

Figure 8-10. Communicator Startup; partner Access Edge Server to partner Access Edge Server communication

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

A user double-clicks [email protected] in Office Communicator to initiate communication.

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
<snip>


From: <sip:[email protected]>;tag=d277e1abbb;epid=ce4ccd49ad
To: <sip:[email protected]>;tag=1187999459aol
<snip>

Step 3: Recipient Receives a Message from a User

The AOL user sees message text in the pop-up 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


<snip>
<KeyboardActivity>
<status status="type" />
</KeyboardActivity>


<snip>
Start-Line: SIP/2.0 200 OK
From: <sip:[email protected]>;tag=d277e1abbb;epid=ce4ccd49ad
To: <sip:[email protected]>;tag=1187999459aol
CSeq: 2 MESSAGE


<snip>


Content-Length: 2
Message-Body: hi
<snip>

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


<snip>
<KeyboardActivity>
 <status status="type" />
</KeyboardActivity>
<snip>
Start-Line: SIP/2.0 200 OK
From: <sip:[email protected]>;tag=1187999459aol
To: <sip:[email protected]>;tag=d277e1abbb;epid=ce4ccd49ad


<snip>
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


<snip>
Message-Body: hi
<snip>
Start-Line: SIP/2.0 200 OK
From: <sip:[email protected]>;tag=1187999459aol
To: <sip:[email protected]>;tag=d277e1abbb;epid=ce4ccd49ad


<snip>

Step 5: User Receives a Message from the Recipient

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

Step 6: Conversation Finished

The Office Communicator user closes the IM window, which ends the conversation and which 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


<snip>
Start-Line: SIP/2.0 200 OK
From: <sip:[email protected]>;tag=d277e1abbb;epid=ce4ccd49ad
To: <sip:[email protected]>;tag=1187999459aol
CSeq: 3 BYE


<snip>
..................Content has been hidden....................

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