<div>After more investigation, it seems my issue is not just with the accounting module. Instead of proxying the 487 back to the original UAC, Kamailio passes a 302. To simplify, I've removed the leg outbound from Kamailio to the carrier:<br>
</div><div><br></div><div><font face="courier new,monospace">0.000000 caller -> Kamailio SIP/SDP Request: INVITE sip:15202362038@Kama</font><font face="courier new,monospace">ilio, with session description
</font></div><div><font face="courier new,monospace">0.002294 Kamailio -> caller SIP Status: 100 trying -- your call is important to us</font></div><div><font face="courier new,monospace">0.002579 Kamailio -> LCR SIP/SDP Request: INVITE sip:15202362038@Kamailio, with session description
</font></div><div><font face="courier new,monospace">0.038023 LCR -> Kamailio SIP Status: 100 Trying
</font></div><div><font face="courier new,monospace">0.046877 LCR -> Kamailio SIP Status: 302 Redirect Request
</font></div><div><font face="courier new,monospace">0.047807 Kamailio -> LCR SIP Request: ACK sip:15202362038@Kamailio</font><font face="courier new,monospace"><br></font></div><div><font face="courier new,monospace">...<br>
</font></div><div><font face="courier new,monospace">2.262195 Kamailio -> caller SIP/SDP Status: 183 Session Progress, with session description
</font></div><div><font face="courier new,monospace">9.422170 calle</font><font face="courier new,monospace">r -> Kamailio SIP Request: CANCEL sip:15202362038@Kamailio</font><font face="courier new,monospace"> </font></div>
<div><font face="courier new,monospace">9.424296 Kamailio -> caller SIP Status: 200 canceling</font><font face="courier new,monospace"><br></font></div><div><font face="courier new,monospace">...</font><font face="courier new,monospace"><br>
</font></div><div> <font face="courier new,monospace">9.423958 Kamailio -> outbound_proxy SIP Request: CANCEL sip:15202362038@upstream_carrier</font><font face="courier new,monospace"><br></font></div><div><font face="courier new,monospace"> 9.</font><font face="courier new,monospace">487730 outbound_proxy -> Kamailio SIP Status: 200 canceling
</font></div><div><font face="courier new,monospace">9.576758 outbou</font><font face="courier new,monospace">nd_proxy -> Kamailio SIP Status: 487 Request Terminated</font><font face="courier new,monospace"><br></font></div>
<div><font face="courier new,monospace">...</font></div><div><strong><font face="courier new,monospace">9.579157 Kamailio -> caller SIP Status: 302 Redirect Request</font></strong><font face="courier new,monospace">
</font></div><div><font face="courier new,monospace">9.626503 caller -> Kamailio SIP Request: ACK sip:15202362038@Kamailio </font></div><div><br></div><div>This worked flawlessly in OpenSIPS so I'm sure it has something to do with a difference since the 2 split. Any advice would be much appreciated.</div>
<div><br></div><div>Thanks,</div><div>Ryan</div><div><br></div><div class="gmail_quote">On Mon, Jan 24, 2011 at 9:00 PM, thrillerbee <span dir="ltr"><<a href="mailto:thrillerbee@gmail.com">thrillerbee@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div>I'm converting my OpenSIPS routers to Kamailio & have run into a small complication. The proxy pushes all INVITEs to a least-cost router. This LCR responds with a list of routes as contact instances in a 302 Redirect. Calls are routing a serially forking normally. Connected & failed calls account normally. </div>
<div><br></div><div>However, if the caller cancels the call, the acc module includes the 302 in the transaction record as the final response as opposed to the actual final response - the 487 Request Canceled.</div><div><br>
</div><div>Is there something I could be missing that would cause this?</div><div><br></div><div>Thanks,</div><div>Ryan</div>
</blockquote></div><br>