>> So I look for things like the $rd after calling cr_route. But if I do >> this, sometimes on re-invites, the IPs are reversed. Also, sometimes >> I've had carrier switches ACK with a different IP (That I don't >> recognize, but is valid). >> > > But the carrier is select when routing the initial request (the INVITE) - > why do you need this information in the ACK or re-INVITE acc records? >>
Since I'm logging failures as well as success, I see a few invites.. So I can't take the first one.. it failed.. Would it be 'syntactically correct' if I take the first invite that returned 200? I haven't tried logging with the missed flag.. I'm not sure how it get written any differently when you use it.. I'll try it out.. -Brett On Fri, Feb 20, 2009 at 11:22 AM, Bogdan-Andrei Iancu <[email protected]> wrote: > Brett Nemeroff wrote: >> >> Bogdan, >> This is really good information. But the problem I'm having is for >> more unusual circumstances. In general, I need to know two things: >> 1. When carriers fail >> > > use missed_calls for that - missed_call flag allows you to do accounting per > branch, so you can use it to log when an attempt to deliver a call via some > carrier failed. >> >> 2. What carrier a call used >> > > if the call was completed via (200OK), use the $ru in extra_accounting with > no problem - it should use. If there are some issue, let me know. >> >> So I look for things like the $rd after calling cr_route. But if I do >> this, sometimes on re-invites, the IPs are reversed. Also, sometimes >> I've had carrier switches ACK with a different IP (That I don't >> recognize, but is valid). >> > > But the carrier is select when routing the initial request (the INVITE) - > why do you need this information in the ACK or re-INVITE acc records? >> >> What I reallyneed is the ID from the carrier route table that was used >> to route the call.. >> > > you get it by extra-accounting the $ru for the initial INVITE > > Regards, > Bogdan >> >> Am I missing something simple? >> -Brett >> >> _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
