24 Jun
2010
24 Jun
'10
8:59 p.m.
Yes - from (subscriber) user agents point of view it "solves" the original
problem. Now each Notify message (except the Subscribe confirmance notifications) include
PIDF bodies.
But as written on Monday, kamailio still produces the internal error messages that look
the same as before:
ERROR: presence_xml > [notify_body.c:515]: while parsing xml body message
ERROR: presence_xml > [notify_body.c:84]: while aggregating body
I think this should be clarified / tested....
That sounds more complex and we still have to use the E'' prefix. I
think it would be easier to just add the E'' prefix to the current code.
But now I wonder what data type is used currently - the recent bug
report on the bug-tracker mentions problems with BLOB, which would
indicate that the body is already saved as BLOB.
IIRC you said you already tried adding the E'' prefixes to the
db_postgresql code. Does this, together with the \0 patch from the
bug-tracker solve your problems?
regards
klaus
regards
klaus
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01