Hi Minh, Minh Phan wrote: > We bought an Eyebeam version more than 2 years ago just to test the presence > support with our SIP presence server. However, because the softphone crashed > often and send mal-formed packets that we stoped trying. I don't know if it > works better now but we haven't tried to support it again since then.
<snip> >> FYI - this is the payload from OW: >> <?xml version="1.0" encoding="UTF-8"?> >> <presence entity="sip:[EMAIL PROTECTED]"> >> <tuple id="azersdqre"> >> <status><basic>open</basic><note>Do Not Disturb</note></status> >> <contact priority="1">sip:[EMAIL PROTECTED]</contact> >> </tuple> >> </presence> Does this payload look right? I have no idea about SIP/SIMPLE. >> This is the payload from a PUBLISH from eyebeam. >> <?xml version='1.0' encoding='UTF-8'?> >> <presence xmlns='urn:ietf:params:xml:ns:pidf' >> xmlns:dm='urn:ietf:params:xml:ns:pidf:data-model' >> xmlns:rpid='urn:ietf:params:xml:ns:pidf:rpid' >> xmlns:c='urn:ietf:params:xml:ns:pidf:cipid' entity='sip:[EMAIL PROTECTED]'> >> <tuple id='tf135ab13'> >> <status><basic>open</basic></status> >> </tuple> >> <dm:person id='p0f475011'> >> <rpid:activities><rpid:busy/></rpid:activities> >> <dm:note>Busy</dm:note> >> </dm:person> >> </presence> With the different XML namespaces, and passing the contact and note via a dm:person, might Eyebeam be using extensions to SIP SIMPLE that make it incompatible with us? Cheers, Dave. -- Dave Neary OpenWengo Community Development Manager Email: [EMAIL PROTECTED] _______________________________________________ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
