Razvan, Thanks for your reply. I'll give this a shot, but shouldn't use_next_gw automatically set the gw_id_avp upon calling it? It's almost like it deletes it, but doesn't re-populate it? All the other auto-populated avps with drouting appear to be working.
On Mon, Oct 8, 2012 at 3:40 AM, Răzvan Crainea <[email protected]> wrote: > Hi, Brett! > > I think the problem is that the 'use_next_gw' function deletes the > gw_id_avp of the "failed" leg, and therefore the acc module cannot see it. > My suggestion is to use a different avp for the db_extra parameter, and for > each leg to copy the gw_id_avp into that avp. > Let me know if this works like this. > > Best regards, > > Razvan Crainea > OpenSIPS Core Developerhttp://www.opensips-solutions.com > > On 10/07/2012 09:44 PM, Brett Nemeroff wrote: > > Hello all, > I'm using opensips 1.8.0-beta-notls and I've seen this happen several > times. Using the ACC module to write calls to mysql (both to acc and > missed_calls). I have gw_id_avp value being written to an avp and that avp > is added as a db_extra. About half of the time, this value is written as a > 0, even though I have a perfectly valid destination that was attempted. In > fact, all of the other avps for that call that are in db_extra are passed > just fine. Just the gw_id_avp for that leg isn't being written. I'm seeing > this happen in both the acc and missed_calls table and so far I can't find > a correlation to what happened on the call and why the value is 0. > > Has anyone else seen this? > > Thanks, > Brett > > > > > > _______________________________________________ > Users mailing > [email protected]http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
