Thats a good idea but how exactly we get the redirect reason(unconditional, busy, no answer) in script from this module?
On Mon, Jul 14, 2008 at 1:47 PM, Bogdan-Andrei Iancu <[EMAIL PROTECTED]> wrote: > Try to use extra accounting to push some text details for the CDRS. > > Regards, > Bogdan > > Ruchir wrote: > >> This works fine. All cdr legs have same call-id so we can associate them >> to single call but how to get forwarding reason? >> >> On Wed, Jul 9, 2008 at 8:56 PM, Bogdan-Andrei Iancu < >> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: >> >> Hi there, >> >> if you allow the 3xx to be interpreted by the end-device (and not >> by the proxy), You will have 2 separate calls (first with 3xx and >> second triggered by 3xx) and there is no way to put these calls >> together - from SIP connections there is no connection between the >> calls in order to do proper accounting. >> >> But you should try to use the uac_redirect module - it can >> intercept the 3xx on the proxy and to do the redirect in the >> client behalf. >> >> Regards, >> Bogdan >> >> >> Ruchir wrote: >> >> I have problem with CDR manipulation in case of call >> forwarding from client. I'm testing with Linksys pap2 and I've >> set unconditional call forwarding. When linksys receives the >> call, it'll send 302, temporarily moved. I have done proper >> ACL checking using Diversion header in the new INVITE but I'm >> having difficulty associating the forwarded leg CDR to >> original call as this is totally new INVITE and none of the >> fields match in CDR. Can anyone guide me in right direction? >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Users mailing list >> [email protected] <mailto:[email protected]> >> http://lists.openser.org/cgi-bin/mailman/listinfo/users >> >> >> >> >
_______________________________________________ Users mailing list [email protected] http://lists.openser.org/cgi-bin/mailman/listinfo/users
