[OpenSER-Users] Presence/XCAP Problem

Schumann Sebastian Sebastian.Schumann at t-com.sk
Wed Aug 22 11:09:12 CEST 2007


Thanks both of you. You helped me clarify two issues.

First issue is that the eyeBeam in the version I am currently using is
not compliant to the RFC. I will try to do an update, hope it is fixed
in a newer version.

Second thing I got clear about is that not the XCAP-Lite server
performes the changes in the watchers table, but the OpenSER _according
to_ the XML data, which is simply just written by the XCAP-Lite client.
Good to know.

Best regards
Sebastian

-----Original Message-----
From: Anca-Maria Vamanu [mailto:anca at voice-system.ro] 
Sent: Wednesday, August 22, 2007 10:16 AM
To: Klaus Fleischmann
Cc: Schumann Sebastian; users at openser.org
Subject: Re: [OpenSER-Users] Presence/XCAP Problem

Hello,

In fact the problem with the xcap document sent by the eyebeam client is

not with that it does not comply with the draft, but with RFC 4745. The 
syntax of the 'identity' element is not as described in section 7.1.

Klaus Fleischmann wrote:
> Sebastian,
> as far as I see, the authorization XML data of openser 1.3 is based on

>  the latest draft (draft-ietf-simple-presence-rules-10.txt), your 
> xcap.xml looks elder. I attach a xml that works with openser 1.3.
>
> /Klaus
>
> Schumann Sebastian wrote:
>> Hi Anca
>>
>> The authorization XML data is attached. The normal generated by
eyeBeam
>> which was successful in the past.
>>
>> In the meantime, I figured out, that the subs_state changed from
"words"
>> to "numbers".
>>
>> Is there a documentation about the mapping or are the changes noticed
>> somewhere? Maybe I didn't check a previous annoucement, but I think
this
>> will most likely cause the error, as the XCAP-Lite uses "activated"
>> "terminated" etc. instead of just "1" or "2", which my OpenSER uses
>> right now. The XCAP-Lite changes the state according to the XML data,
am
>> I right?
>>
The change in status syntax does not affect in any way the document 
interpretation. The XCAP-Lite server only writes the whole document in 
xcap_xml table without interpretation so it does not have to know about 
the changes.

regards,
Anca
>> Best regards
>> Sebastian
>> -----Original Message-----
>> From: Anca-Maria Vamanu [mailto:anca at voice-system.ro] Sent: Tuesday, 
>> August 21, 2007 6:33 PM
>> To: Schumann Sebastian
>> Cc: users at openser.org
>> Subject: Re: [OpenSER-Users] Presence/XCAP Problem
>>
>> Hello,
>>
>> The problem is with the xcap  document with authorization rules, and 
>> of its interpretation made by the server and the client. There might 
>> be either a bug or lack of synchronization. The document defining the

>> syntax for this document is still a draft so changes might have
occurred
>>
>> in the gap between the client and OpenSer implementation(presence_xml

>> hasn't been updated to the new draft version). Could you send in the 
>> xcap document sent by the client that generates these messages?
>>
>> regards,
>> Anca Vamanu
>>
>> Schumann Sebastian wrote:
>>> Dear all
>>>
>>>  
>>>
>>> I changed the used Software for my Presence Agent after couple of
time
>>
>>> and have problems to use presence with XCAP authorization.
>>>
>>>  
>>>
>>> The debug messages
>>>
>>>  
>>>
>>> PRESENCE_XML:get_rule_node:ERROR didn't found identity tag
>>>
>>> PRESENCE_XML:get_rule_node:ERROR didn't found identity tag
>>>
>>> PRESENCE: build_str_hdr: ERROR bad status flag= 136681324
>>>
>>> PRESENCE:send_notify_request:ERROR while building headers
>>>
>>> PRESENCE:notify: ERROR send Notify not successful
>>>
>>> PRESENCE:update_subscribtion: Could not send notify for presence
>>>
>>>  
>>>
>>> appear.
>>>
>>>  
>>>
>>> I have no idea what I did wrong. I am still using my XCAP-Lite 
>>> server version 1.0.0 and adjusted the config to using with the 
>>> presence_xml module, not only presence. Furthermore I did a complete

>>> database update, so all tables are in the current version.
>>>
>>>  
>>>
>>> One client requests authorization which is granted by the other. The

>>> accordant XCAP data is right in the xcap_xml table. But still, no 
>>> NOTIFY is sent :(
>>>
>>>  
>>>
>>> Does anyone experience similar problems? Where can be the issue for 
>>> the posted error messages?
>>>
>>>  
>>>
>>> Thanks as always for your help!
>>>
>>>  
>>>
>>> Best regards
>>>
>>> Sebastian
>>>
>>>  
>>>
>>> *Sebastian Schumann*
>>> Diploma Student Architecture and Design Department
>>>
>>> Slovak Telekom, a. s.
>>> T-Com, Operations Unit
>>> Production and Service Division
>>> Innovations and Enterprise Solution Subunit
>>>
>>> Address: Namestie Slobody 6, 817 62 Bratislava, Slovakia
>>> Office: Room 449, Jarabinkova 1, 821 09 Bratislava, Slovakia
>>>
>>> +421 2 588 13332 (tel)
>>> +421 910 643010 (mobile)
>>> +49 175 1925928 (mobile)
>>>
>>> sebastian.schumann at t-com.sk <mailto:sebastian.schumann at t-com.sk>
>>> _http://www.t-com.sk_ <http://www.t-com.sk/>
>>>
>>>  
>>>
>>
------------------------------------------------------------------------
>>> _______________________________________________
>>> Users mailing list
>>> Users at openser.org
>>> http://openser.org/cgi-bin/mailman/listinfo/users
>>>   
>>
>>
>>
------------------------------------------------------------------------
>>
>> _______________________________________________
>> Users mailing list
>> Users at openser.org
>> http://openser.org/cgi-bin/mailman/listinfo/users





More information about the sr-users mailing list