#938 closed defect (fixed)
Presence PIDF document may be rejected by presence servers that implement strict XML checking (thanks Johan Lantz for the fix)
Reported by: | bennylp | Owned by: | bennylp |
---|---|---|---|
Priority: | normal | Milestone: | release-1.4 |
Component: | pjsip | Version: | trunk |
Keywords: | Cc: | ||
Backport to 1.x milestone: | Backported: |
Description (last modified by bennylp)
PJSIP's generated PIDF presence document may be rejected by presence servers that implement strict XML checking. This is due to the 'id' attribute of <tuple> element does not strictly comply with XML 'xs:ID' specification, which prohibits it from having number as the start of the character.
(Such presence server is Ericsson presence server)
Thanks Johan Lantz for the fix!
Change History (4)
comment:1 Changed 15 years ago by bennylp
- Description modified (diff)
comment:2 Changed 15 years ago by bennylp
- Summary changed from Presence PIDF document may be rejected by strict parser in some presence servers (thanks Johan Lantz for the fix) to Presence PIDF document may be rejected by presence servers that implement strict XML checking (thanks Johan Lantz for the fix)
comment:3 Changed 15 years ago by bennylp
- Resolution set to fixed
- Status changed from new to closed
comment:4 Changed 15 years ago by bennylp
Better fix in r2877, to make sure that we don't accidently generate duplicate tuple id in case the GUID string generator backend is not good.
Note: See
TracTickets for help on using
tickets.
Fixed in r2876