Re: [SR-Users] accounting serial forked transactions with 302 from LCR

2011-01-25 Thread thrillerbee
Will this kind of application require the multi_leg_info modparam for the acc module? I didn't have to use it with OpenSIPS, but I'm running out of ideas with Kamailio. Thanks, Ryan On Tue, Jan 25, 2011 at 2:29 PM, thrillerbee wrote: > Alex, > > Are you referring to the modparam that would incl

Re: [SR-Users] accounting serial forked transactions with 302 from LCR

2011-01-25 Thread thrillerbee
Alex, Are you referring to the modparam that would include accounting CANCELs? If so, no - I'm not doing that because I don't want to account the CANCEL transaction. I only wish to account the INVITE transaction & final response (487). I have found that I can force a 487 response back to the origi

Re: [SR-Users] accounting serial forked transactions with 302 from LCR

2011-01-24 Thread Alex Balashov
On 01/24/2011 05:53 PM, thrillerbee wrote: 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: 0.00 caller ->

Re: [SR-Users] accounting serial forked transactions with 302 from LCR

2011-01-24 Thread thrillerbee
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: 0.00 caller -> Kamailio SIP/SDP Request: INVITE sip:15202362

[SR-Users] accounting serial forked transactions with 302 from LCR

2011-01-24 Thread thrillerbee
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 n