Presence and IntComm WG

["Jeff King" <>]

This is the first build of Session (unreleased) with IM functionality
implemented with IETF RFC 3428 (SIP Extension for IM) in mind.

This build of Session does not support the sending content type
MESSAGE/CPIM but rather the sending content type text/plain.  This
initial implementation was based on the premise from Section 4 of RFC
3428 stating:

"All UACs which support the MESSAGE method MUST be prepared to send
MESSAGE requests with a body of type text/plain.  They may send bodies
of type message/cpim"

A subsequent Session build will support messages sent with body types of
message/cpim.  Can sipc be configured to send with text/plain?

The Session contact header is empty due to the following from RFC 3428
"User Agents MUST NOT insert Contact header fields into MESSAGE
requests."

Session is sending a 406 Unacceptable when it receives messages from
sipc due to the message/cpim content type.

Xiaotao, I will contact you to work through the details to ensure proper
interop.  Thanks for the feedback.

Jeff King
Wave Three Software


-----Original Message-----
From: Xiaotao Wu 
[mailto:]
 
Sent: Monday, April 19, 2004 4:34 PM
To: Candace Holman
Cc: 
;
 

Subject: [wg-pic] Re: Interop between sipc and Session

ok, in the MESSAGE request received by sipc, the From header is

From: David Reese
<sip:David%;transport=udp>;tag=dsd85ef1f8

That's why sipc displays 
sip:David%
 as the URI.

Don't know why Session not uses domainname in the From header's SIP URI

Also, the 'Contact' header in the MESSAGE request from Session is
wrong. It should not be empty.

sipc supports three content formats for IM, namely text/plain,
Message/CPIM, and application/xpidf+xml (interop with Windows
messenger).
so, sipc can display the message sent by Session (in text/plain)
format and return a 200 Ok.

sipc uses Message/CPIM as sending format. That supposed to be the
format recommended by IETF for IM. But got 406 Not acceptable response.

-Xiaotao

===========================================================
Name      : Xiaotao Wu
Email     : 

Homepage  : http://www.cs.columbia.edu/~xiaotaow
Phone     : (212)939-7054,  Fax: (801)751-0217
Phone-PC  : (212)939-7133
SIP       : 
sip:
Office    : Room 506, Mudd building, West 120th
===========================================================

On Mon, 19 Apr 2004, Candace Holman wrote:

> At 01:45 PM 4/19/2004, Xiaotao Wu wrote:
> >On Mon, 19 Apr 2004, Candace Holman wrote:
> >
> > > I find that I can use Session to contact another Session user, but
the
> > > reply comes up in my sipc window.
> > >
> > > Also, I"m on Win2000/sipc and Dave Reese is on OSX/Session and his
URI
> > > shows as 
> > > sip:David%...
> > >  in sipc
> >
> >sipc based on the From header to display the user. I need to see
what's in
> >the From header of the MESSAGE request sent by Session.
> >Can you send me the sipc.log file in the .sipc directory?
> >I will take a look at the interop issue.
>
> This might be helpful:
>
> 04/19/2004 13:41:43.019000
> Recv from: 207.75.164.71:5060
> MESSAGE 
> sip:;transport=udp
>  SIP/2.0
>
> Via: SIP/2.0/UDP 207.75.164.71;branch=z9hG4bK0d74.17684991.0
>
> Via: SIP/2.0/UDP
206.196.181.179:5060;branch=z9hG4bKJSnjj4qs00HVoeK+O7wFcw~~13
>
> Max-Forwards: 69
>
> To: cholman 
> <sip:;transport=udp>;tag=dsc3195702
>
> From: David Reese
> <sip:David%;transport=udp>;tag=dsd85ef1f8
>
> Call-ID: 
> 
>
> CSeq: 3 MESSAGE
>
> Content-Length: 122
>
> Contact:
>
> Content-Type: text/plain;application/w3f
>
>
>
> Hmmm, I'm not running sipc (cause I'm a Mac), odd{]Hmmm, I'm not
running
> sipc (cause I'm a Mac), odd~000$12^Monospaced[}{]
> 04/19/2004 13:41:43.239000
> Sent to: 207.75.164.71:5060/UDP
> SIP/2.0 200 OK
>
> Contact: 
> <sip::5060>
>
> CSeq: 3 MESSAGE
>
> Via: SIP/2.0/UDP 207.75.164.71;branch=z9hG4bK0d74.17684991.0
>
> Via: SIP/2.0/UDP
206.196.181.179:5060;branch=z9hG4bKJSnjj4qs00HVoeK+O7wFcw~~13
>
> From: David Reese
> <sip:David%;transport=udp>;tag=dsd85ef1f8
>
> Call-ID: 
> 
>
> To: cholman 
> <sip:;transport=udp>;tag=dsc3195702
>
> Content-Length: 0
>
>
>
>
> 04/19/2004 13:42:39.160000
> Recv from: 207.75.164.71:5060
> MESSAGE 
> sip:;transport=udp
>  SIP/2.0
>
> Via: SIP/2.0/UDP 207.75.164.71;branch=z9hG4bK0755.5ae09394.0
>
> Via: SIP/2.0/UDP
206.196.181.179:5060;branch=z9hG4bKJSnjj4qs00HVoeK+O7wFcw~~14
>
> Max-Forwards: 69
>
> To: cholman 
> <sip:;transport=udp>;tag=dsc3195702
>
> From: David Reese
> <sip:David%;transport=udp>;tag=dsa759cd50
>
> Call-ID: 
> 
>
> CSeq: 4 MESSAGE
>
> Content-Length: 96
>
> Contact:
>
> Content-Type: text/plain;application/w3f
>
>
>
> brought down my vpn, does that help?{]brought down my vpn, does that
> help?~000$12^Monospaced[}{]
> 04/19/2004 13:42:39.430000
> Sent to: 207.75.164.71:5060/UDP
> SIP/2.0 200 OK
>
> Contact: 
> <sip::5060>
>
> CSeq: 4 MESSAGE
>
> Via: SIP/2.0/UDP 207.75.164.71;branch=z9hG4bK0755.5ae09394.0
>
> Via: SIP/2.0/UDP
206.196.181.179:5060;branch=z9hG4bKJSnjj4qs00HVoeK+O7wFcw~~14
>
> From: David Reese
> <sip:David%;transport=udp>;tag=dsa759cd50
>
> Call-ID: 
> 
>
> To: cholman 
> <sip:;transport=udp>;tag=dsc3195702
>
> Content-Length: 0
>
>
>
>
> 04/19/2004 13:44:15.187999
> Recv from: 207.75.164.71:5060
> NOTIFY 
> sip::5060
>  SIP/2.0
>
> Via: SIP/2.0/UDP 207.75.164.71;branch=z9hG4bK62ea.1381c874.0
>
> To: Candace
<sip:>;tag=396072859129.206.196.181.129
>
> From: 
> <sip:>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-f296
>
> CSeq: 2 NOTIFY
>
> Call-ID: 
> 
>
> Content-Length: 886
>
> User-Agent: Sip EXpress router(0.8.13-dev-28 (i386/linux))
>
> Event: presence
>
> Content-Type: application/cpim-pidf+xml
>
> Subscription-State: active;expires=2635
>
>
>
> <?xml version="1.0"?>
>
> <!DOCTYPE presence PUBLIC "//IETF//DTD RFCxxxx PIDF 1.0//EN"
"pidf.dtd">
>
> <presence 
> entity="sip:">
>
> <tuple id="9r28r49">
>
>    <contact
priority="0.100000">sip:/portal</contact>
>
>    <status>
>
>      <basic>open</basic>
>
>      <geopriv><location-info><civilAddress>
> </civilAddress></location-info></geopriv>
>
>    </status>
>
> </tuple>
>
> <tuple id="9r28r49">
>
>    <contact
priority="0.700000">sip:/manual</contact>
>
>    <status>
>
>      <basic>open</basic>
>
>      <geopriv><location-info><civilAddress>
> </civilAddress></location-info></geopriv>
>
>    </status>
>
> </tuple>
>
> <tuple id="9r28r49">
>
>    <contact
priority="0.500000">sip::5060</contact>
>
>    <status>
>
>      <basic>open</basic>
>
>      <geopriv><location-info><civilAddress>
> </civilAddress></location-info></geopriv>
>
>    </status>
>
> </tuple>
>
> </presence>
>
>
> I think this is when I tried to send to Session and get a 406 Not
> Acceptable error.
>
> 04/19/2004 13:38:12.496000
> Sent to: pals.internet2.edu:5060/UDP
> MESSAGE 
> sip:
>  SIP/2.0
>
> Via: SIP/2.0/UDP 206.196.181.129:5060
>
> CSeq: 1 MESSAGE
>
> Contact: 
> <sip::5060>
>
> From: Candace 
> <sip:>;
> tag=396072859129.206.196.181.129
>
> Date: Mon, 19 Apr 2004 17:38:12 GMT
>
> Call-ID: 
> 
>
> Content-Type: Message/CPIM
>
> To: Dave Reese 
> <sip:>
>
> Content-Length: 195
>
>
>
> From: Candace 
> <sip:>;
> tag=396072859129.206.196.181.129
>
> To: Dave Reese 
> <sip:>
>
> Content-Type: text/plain
>
> Content-ID: 
> 
>
>
>
> Testing via sipc
> 04/19/2004 13:38:12.746000
> Recv from: 207.75.164.71:5060
> SIP/2.0 406 Not Acceptable
>
> Via: SIP/2.0/UDP 206.196.181.129:5060
>
> To: Dave Reese 
> <sip:>
>
> From: Candace
<sip:>;tag=396072859129.206.196.181.129
>
> Call-ID: 
> 
>
> CSeq: 1 MESSAGE
>
> Content-Length: 0
>
>
>
> Candace
>