Hi Juha,
the MI internal tree does no accept nodes with no name and no value, so
the MI FIFO implementation just discards the empty lines as they have no
corresponding MI node.
Here is something working for me:
<quoted>
:t_uac_dlg:reply_fifo
INVITE
sip:[EMAIL PROTECTED]
sip:sip.domain.com:5060
.
"X-Info: test
To: [EMAIL PROTECTED]
From: [EMAIL PROTECTED]
Callid: qwerty
CSeq: 1 INVITE
"
</quoted>
that is a request with no body - it has 5 nodes (from MI point of view);
last node stretches over 5 line as it is quoted. Similar you may push a
body also.
regards,
bogdan
Juha Heinanen wrote:
Bogdan-Andrei Iancu writes:
> the changes are here:
>
> Syntax of "t_uac_dlg" (as lines):
>
> (old version) (new version)
> method method
> RURI RURI
> NEXT_HOP?|socket? NEXT_HOP?
> new_headers* socket?
> \n new_headers?
> Body* [Body]
> .
>
> Legend:
> * can be multiple lines
> ? if empty value, the line contains only the '.' char
> [] can completely miss
> in new version, for multiple lines values (like new_headers and body) a quoted
string can be used (inline '"' must be escaped)
does this mean that in new version the string that is given as the only
parameter to xml-rpc request consists of 5 or 6 lines (depending if Body
exists or not) separated by newline chars, where NEXT_HOP, socket and
new_headers lines may consist of . char only if the line would otherwise
be empty? new_headers and Body, in turn, are strings starting and
ending with " char and where lines are separated by newline chars?
i tried, but got back "Too few or too many arguments" error. a concrete
example would be highly appreciated.
why is . char needed to tell that a line is empty?
-- juha
_______________________________________________
Devel mailing list
Devel@openser.org
http://openser.org/cgi-bin/mailman/listinfo/devel
