Hi Pat,

It is a bit confusion and the most of the report is about adding an AVP as hdr via append_hf() , but you also mention something about CDR...and I do not see the relation between the two.


First of all, is the append_hf() working fine ? is the header (in the sequential attempts) containing the correct aggregated value ?

Best regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 12.10.2016 22:59, Pat Burke wrote:
Hello,

I am in process of migrating from 1.11 to 2.2. We have a situation where we have a routing opensips that can make multiple attempts to complete a call. The information specific to each attempt is passed to the SBC opensips through headers. In order to not double up on headers, I moved the code that calls append_hf to a branch. As the call progresses, I update various AVP's and print them into the log (so I can see that they are being updated correctly). Below is an example scenario of what I am doing.



initial call setup logic
set the t_on_failure

setup for first carrier
branch
   setup headers with carrier information used by the SBC
   $avp(test) := "Step 1;";
t_relay

on_failure (for example 480 - timeout)
   setup for the next carrier
   branch
      setup header for next carrier information used by the SBC
$avp(test) := $avp(test) + "Step 2;"; # avp(test) now equal "Step 1;Step 2;"
t_relay

on_failure (for example 408 - timeout)
   no more carriers, end the call



What gets put into the cdr is "Step 1;" not "Step 1;Step 2;"

Also, the sip_code is set to the first failure received from the SBC, not the last.

If the call completes successfully, the cdr data is correct.

Thanks,
Pat Burke


_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to