<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/4.4.4">
</HEAD>
<BODY>
Hello,<BR>
<BR>
One of my colleagues at Crocodile has been doing some testing with the msrp module. With the auth change that was made yesterday, and the updated configuration I put in the README example it seems to mostly work. However, there is one set of scenarios relating to failure REPORTs that don't seem to be possible with the current module.<BR>
<BR>
RFC 4976 section 6.4.1 paragraph 3 states:<BR>
<BR>
<PRE>
If the Failure-Report header is "yes" or "partial", and if there is a
problem processing the SEND request or if an error response is
received for that SEND request, then the relay MUST respond with an
appropriate error response in a REPORT back to the original source of
the message.
</PRE>
<BR>
This means that when a SEND request that contains a Failure-Report: header with value of "yes" or "partial" is relayed by Kamailio we need to maintain some state so that when the TCP send fails, or we receive a failure response from the next hop, Kamailio can generate and send a REPORT. At the moment I don't think the msrp module has these capabilities.<BR>
<BR>
If the module is getting some re-work before the next release it would be good to get this in there. I am quite happy to help out in any way I can, but I am not sure of the best way to proceed with this.<BR>
<BR>
Regards,<BR>
<BR>
Peter<BR>
<BR>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<PRE>
--
Peter Dunkley
Technical Director
Crocodile RCS Ltd
</PRE>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>