[SIP Beyond VoIP] Another case where Sylk would reject Notifications

Iñaki Baz Castillo ibc at aliax.net
Thu Nov 15 21:29:46 CET 2012

2012/11/15 Saúl Ibarra Corretgé <saul at ag-projects.com>:
> This is really fun: while not syntactically incorrect (the schema does allow multiple 'person' elements) it's semantically forbidden (written in the RFC). So implementation have done whatever they wanted :-S ID elements, however, can't be duplicated, there is no way around that.

So two devices sharing the same AoR publishes different presence
bodies with different "person" elements... and the presence server
must choose which one to use in the "merged" document. And the server
must be ready to manipulate the XML nodes (imagine that both devices
don't use the same identifier for the same XML namespace...).


Iñaki Baz Castillo
<ibc at aliax.net>

More information about the SIPBeyondVoIP mailing list