Bogdan,<br>Thanks. got this working already. very nice! Question tho.. what kind of performance hit should I expect by allowing avps to be available in onreply route?<br><br>-Brett<br><br><br><div class="gmail_quote">On Thu, Mar 26, 2009 at 8:17 AM, Bogdan-Andrei Iancu <span dir="ltr"><<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">there is a $Ts pseudovariable to get the current time from the script.<div class="im"><br>
<br>
Regards,<br>
Bogdan<br>
<br>
Brett Nemeroff wrote:<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
Oh cool.. I didn't know there was a timestamp method.. neato.. thanks for the tip, I'll give it a shot.<br>
-Brett<br>
<br>
<br></div><div><div></div><div class="h5">
On Thu, Mar 26, 2009 at 7:43 AM, Bogdan-Andrei Iancu <<a href="mailto:bogdan@voice-system.ro" target="_blank">bogdan@voice-system.ro</a> <mailto:<a href="mailto:bogdan@voice-system.ro" target="_blank">bogdan@voice-system.ro</a>>> wrote:<br>
<br>
hi Brett,<br>
<br>
well, this is a different story and you do not need acc . what you<br>
can do is to use onreply_route to catch the received 100 trying<br>
and to save the current timestamp into an avp. in the same route<br>
catch the 180 also and make the diff and place this result into<br>
another avp - account this avp via extra_accounting stuff.<br>
<br>
regards,<br>
bogdan<br>
<br>
Brett Nemeroff wrote:<br>
<br>
Ah, I'm trying to capture the one from the UAS (far end).<br>
<br>
Really, I'm trying to, best I can, capture signalling PDD. I<br>
understand that this is probably subject to interpretation,<br>
but in general, I measure PDD as the time between the first<br>
100 code and a 18X reply. Yes, admittedly a totally false<br>
expectation. However, in my limited environment for this<br>
application, I always get a 100 before a 18X and I'd like to<br>
be able to log the time delay in acc.<br>
<br>
I'd be interested in hearing other ways of doing what I'm<br>
attempting.. Maybe something more sane..<br>
-Brett<br>
<br>
<br>
On Wed, Mar 25, 2009 at 1:07 PM, Bogdan-Andrei Iancu<br>
<<a href="mailto:bogdan@voice-system.ro" target="_blank">bogdan@voice-system.ro</a> <mailto:<a href="mailto:bogdan@voice-system.ro" target="_blank">bogdan@voice-system.ro</a>><br>
<mailto:<a href="mailto:bogdan@voice-system.ro" target="_blank">bogdan@voice-system.ro</a><br>
<mailto:<a href="mailto:bogdan@voice-system.ro" target="_blank">bogdan@voice-system.ro</a>>>> wrote:<br>
<br>
Hi Brett,<br>
<br>
You do not get it because the 100 Trying is locally<br>
generated. The<br>
callback you tried to change is called for replies that were<br>
received and fwded to the UAC.<br>
<br>
But the 100 is not fitting here because it is going hop by<br>
hop -<br>
one locally generated and sent to UAC and the one received from<br>
UAS is discarded (not fwded).<br>
<br>
Regards,<br>
Bogdan<br>
<br>
Brett Nemeroff wrote:<br>
<br>
Hey All,<br>
I'm trying to log the 100 Trying in the acc module. I tried<br>
the acc_db_request, but it can't be called from onreply.<br>
<br>
So I tried editing acc_logic.c, but that isn't working<br>
either?! :/ Any ideas? Maybe I should edit<br>
acc_db_request so<br>
it can be called from ONREPLY?<br>
<br>
<br>
static inline int should_acc_reply(struct sip_msg<br>
*req,struct sip_msg *rpl,<br>
int code)<br>
{<br>
/* negative transactions reported otherwise only if<br>
explicitly * demanded */<br>
if (code == 100)<br>
return 1;<br>
if ( !is_failed_acc_on(req) && code >=300 )<br>
return 0;<br>
if ( !is_acc_on(req) )<br>
return 0;<br>
if ( code<200 && !(early_media &&<br>
parse_headers(rpl,HDR_CONTENTLENGTH_F, 0)==0 &&<br>
rpl->content_length &&<br>
get_content_length(rpl)>0 ) )<br>
return 0;<br>
<br>
return 1; /* seed is through, we will account<br>
this reply */<br>
}<br>
<br>
------------------------------------------------------------------------<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<mailto:<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>><br>
<mailto:<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<mailto:<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>>><br>
<br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
<br>
<br>
<br>
</div></div></blockquote>
<br>
</blockquote></div><br>