I've noticed a problem with SIP presence ,
In some situations when using openser in the pidf xml there is more than one person
and I saw in the code that the method parsing the pidf xml returns in such situations and so
the contact always stays Offline as no status is dispatched.
I don't know if there is some priority in the persons list, but what you think
is it ok to select the first person and get its status ?

actually we must continue dispatching xml no matter how much persons are there,
but then there are multiple tuple elements and I'm wondering which one should we choose
as one of them is the last one

damencho

Damian Minkov wrote:

···

Hi Ben,

I've noticed a problem with SIP presence ,
In some situations when using openser in the pidf xml there is more than one person
and I saw in the code that the method parsing the pidf xml returns in such situations and so
the contact always stays Offline as no status is dispatched.
I don't know if there is some priority in the persons list, but what you think
is it ok to select the first person and get its status ?

I don't really understand your problem. As far as I understand, you think that when there are many 'tuple' elements in the document, we aren't parsing it ? If it's what you want to say, I think that you're wrong, every tuple element is parsed in the current SIMPLE implementation.
If there are many statuses for the same contact, the final status will be the status with the lowest priority as the rfc recommends to handle the statuses in order of priority.

If I didn't understand you, can you precise the problem ?

Cheers,
Ben

Damian Minkov a �crit :

···

Hi again,

actually we must continue dispatching xml no matter how much persons are there,
but then there are multiple tuple elements and I'm wondering which one should we choose
as one of them is the last one

damencho

Damian Minkov wrote:

Hi Ben,

I've noticed a problem with SIP presence ,
In some situations when using openser in the pidf xml there is more than one person
and I saw in the code that the method parsing the pidf xml returns in such situations and so
the contact always stays Offline as no status is dispatched.
I don't know if there is some priority in the persons list, but what you think
is it ok to select the first person and get its status ?

yes you are right about the tuples, my fault. But what I at first
want to ask was for the person element. I've searched and saw in rfc that there
can be more than one person in such message, but we are ignoring the message
if there is such occasion. What do you think ?

damencho

Benoit Pradelle wrote:

···

Hi Damian,

I don't really understand your problem. As far as I understand, you think that when there are many 'tuple' elements in the document, we aren't parsing it ? If it's what you want to say, I think that you're wrong, every tuple element is parsed in the current SIMPLE implementation.
If there are many statuses for the same contact, the final status will be the status with the lowest priority as the rfc recommends to handle the statuses in order of priority.

If I didn't understand you, can you precise the problem ?

Cheers,
Ben

Damian Minkov a �crit :

Hi again,

actually we must continue dispatching xml no matter how much persons are there,
but then there are multiple tuple elements and I'm wondering which one should we choose
as one of them is the last one

damencho

Damian Minkov wrote:

Hi Ben,

I've noticed a problem with SIP presence ,
In some situations when using openser in the pidf xml there is more than one person
and I saw in the code that the method parsing the pidf xml returns in such situations and so
the contact always stays Offline as no status is dispatched.
I don't know if there is some priority in the persons list, but what you think
is it ok to select the first person and get its status ?