<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7226.0">
<TITLE>RE: [Serusers] ser-0.9.0 and PA clients</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Hello,<BR>
I got myself an eyebeam this evening and tried it out using my current (working) configuration of ser-0.9.0.<BR>
It seems that SER does not handle the SUBSCRIBE/PUBLISH from eyebeam very well. I've added information from sip-scenario (I've removed some information):<BR>
<BR>
I've read that the eyebeam SDK includes a pa module for SER.......<BR>
<BR>
I will try to debug more later.<BR>
<BR>
<BR>
SIP MESSAGE 7 80.203.x.x:55547() -> 195.18.x.x:5060()<BR>
UDP Frame 7 12/Jan/05 20:55:18.5705 TimeFromPreviousSipFrame=0.0017 TimeFromStart=0.5251<BR>
SUBSCRIBE sip:67830xxx@xxx.xxx SIP/2.0<BR>
To: <sip:67830xxx@xxx.xxx><BR>
From: 67830xxx<sip:67830xxx@xxx.xxx>;tag=3544bd3b<BR>
Via: SIP/2.0/UDP 10.0.0.6:8322;branch=z9hG4bK-d87543-588658107-1--d87543-;rport<BR>
Call-ID: a83fe920817d483f<BR>
CSeq: 1 SUBSCRIBE<BR>
Contact: <sip:6783xxx@10.0.0.6:8322><BR>
Expires: 3600<BR>
Max-Forwards: 70<BR>
Accept: application/watcherinfo+xml<BR>
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE<BR>
User-Agent: eyeBeam release 3003x stamp 16296 (sn:4b7196e19649bda632a5)<BR>
Event: presence.winfo<BR>
Content-Length: 0<BR>
<BR>
SIP MESSAGE 8 195.18.xxx.xxx:5060() -> 80.203.xxx.xxx:55547()<BR>
UDP Frame 8 12/Jan/05 20:55:18.5898 TimeFromPreviousSipFrame=0.0192 TimeFromStart=0.5444<BR>
SIP/2.0 400 Bad Request<BR>
To: <sip:67830xxx@xxx.xxx>;tag=f6cf184986e86bc8dffc7813fc0be2e4-11a5<BR>
From: 67830xxx<sip:67830xxx@xxx.xxx>;tag=3544bd3b<BR>
Via: SIP/2.0/UDP 10.0.0.6:8322;branch=z9hG4bK-d87543-588658107-1--d87543-;rport=55547;received=80.203.xxx.xxx<BR>
Call-ID: a83fe920817d483f<BR>
CSeq: 1 SUBSCRIBE<BR>
P-NATed-Caller: Yes<BR>
Error while parsing headersServer: Sip EXpress router (0.9.0 (i386/linux))<BR>
Content-Length: 0<BR>
Warning: 392 195.18.xxx.xxx:5060 "Noisy feedback tells: pid=13719 req_src_ip=80.203.xxx.xxx req_src_port=55547 in_uri=sip:67830xxx@xxx.xxx out_uri=sip:67830xxx@xxx.xxx via_cnt==1"<BR>
<BR>
<BR>
As for PUBLISH:<BR>
<BR>
SIP MESSAGE 9 80.203.xxx.xxx:55547() -> 195.18.xxx.xxx:5060()<BR>
UDP Frame 9 12/Jan/05 20:55:19.5746 TimeFromPreviousSipFrame=0.9848 TimeFromStart=1.5291<BR>
PUBLISH sip:67830xxx@xxx.xxx SIP/2.0<BR>
To: <sip:67830xxx@xxx.xxx><BR>
From: 67830xxx<sip:67830xxx@xxx.xxx>;tag=5c3ff501<BR>
Via: SIP/2.0/UDP 10.0.0.6:8322;branch=z9hG4bK-d87543-908356443-1--d87543-;rport<BR>
Call-ID: bb42e678f246d35e<BR>
CSeq: 1 PUBLISH<BR>
Contact: <sip:67830xxx@10.0.0.6:8322><BR>
Expires: 3600<BR>
Max-Forwards: 70<BR>
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE<BR>
Content-Type: application/pidf+xml<BR>
User-Agent: eyeBeam release 3003x stamp 16296 (sn:4b7196e19649bda632a5)<BR>
Event: presence<BR>
Content-Length: 602<BR>
<BR>
<?xml version="1.0" encoding="UTF-8"?><BR>
<presence xmlns="urn:ietf:params:xml:ns:pidf"<BR>
xmlns:pp="urn:ietf:params:xml:ns:pidf:person"<BR>
xmlns:et="urn:ietf:params:xml:ns:pidf:rpid:rpid-tuple"<BR>
xmlns:ep="urn:ietf:params:xml:ns:pidf:rpid:rpid-person"<BR>
xmlns:es="urn:ietf:params:xml:ns:pidf:rpid:status:rpid-status"<BR>
xmlns:ci="urn:ietf:params:xml:ns:pidf:cipid"<BR>
entity="sip:67830xxx@xxx.xxx"><BR>
<pp:person><BR>
<status><BR>
</status><BR>
</pp:person><BR>
<tuple id="t14"><BR>
<contact priority="1">sip:67830xxx@xxx.xxx</contact><BR>
<status><BR>
<basic>open</basic><BR>
</status><BR>
</tuple><BR>
</presence><BR>
<BR>
<BR>
SIP MESSAGE 10 195.18.xxx.xxx:5060() -> 80.203.xxx.xxx:55547()<BR>
UDP Frame 10 12/Jan/05 20:55:19.5876 TimeFromPreviousSipFrame=0.0131 TimeFromStart=1.5422<BR>
SIP/2.0 400 Bad Request<BR>
To: <sip:67830065@smartnet.no>;tag=f6cf184986e86bc8dffc7813fc0be2e4-d986<BR>
From: 67830xxx<sip:67830xxx@xxx.xxx>;tag=5c3ff501<BR>
Via: SIP/2.0/UDP 10.0.0.6:8322;branch=z9hG4bK-d87543-908356443-1--d87543-;rport=55547;received=80.203.xxx.xxx<BR>
Call-ID: bb42e678f246d35e<BR>
CSeq: 1 PUBLISH<BR>
P-NATed-Caller: Yes<BR>
Event header field missingServer: Sip EXpress router (0.9.0 (i386/linux))<BR>
Content-Length: 0<BR>
Warning: 392 195.18.xxx.xxx:5060 "Noisy feedback tells: pid=13707 req_src_ip=80.203.xxx.xxx req_src_port=55547 in_uri=sip:67830xxx@xxx.xxx out_uri=sip:67830xxx@xxx.xxx via_cnt==1"<BR>
<BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Jamey Hicks [<A HREF="mailto:jamey.hicks@hp.com">mailto:jamey.hicks@hp.com</A>]<BR>
Sent: Tue 1/11/2005 11:41 PM<BR>
To: Helge Waastad<BR>
Cc: serusers@lists.iptel.org<BR>
Subject: Re: [Serusers] ser-0.9.0 and PA clients<BR>
<BR>
Helge Waastad wrote:<BR>
<BR>
> Hello,<BR>
> I've started to use the 0.9.0 release and to me it seems to work as a<BR>
> charm :-)<BR>
> <BR>
> However does anybody know which SIP clients which is compliant for the PA?<BR>
> I'm using kphone and it works fine, but I would like to try out some<BR>
> for use on Microsoft?<BR>
> Messenger 5.0 does not work.<BR>
<BR>
Eyebeam from xten.com seems to be the farthest along in terms of<BR>
implementing SIMPLE presence support, according to their website. I<BR>
know Xten was testing against the SER PA this fall. That being said,<BR>
testing Eyebeam against SER 0.9 is on my todo list for this week. I<BR>
just need to set up a SER 0.9 PA on the same side of the HP firewall as<BR>
my Windows box.<BR>
<BR>
Jamey<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>