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