Re: [OpenSIPS-Users] Changing message headers (Custom header) in serial forking

[Bogdan-Andrei Iancu]

Hi John,

Whatever change you do over the message in request route will be 
inherited by all branches. If you want to do a per branch change, use 
the branch route (instead of request route) .


Regards,

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

On 17.01.2015 15:31, John Nash wrote:
I tested drouting module and it is very good but when I try to change 
value of one custom header (Header was added in initial Invite), I see 
it added twice.


--Initial Invite---(Header added)Sent to dest1
---Failure comes from dest1--- Sent to dest2 (Using  
use_next_gw)---Remove header if present and add new one.


My guess is after I add header in failure route (after use_next_gw 
call) it is getting copied again from original invite. I also tried 
local_route but it seems its not going inside that.





___
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

[OpenSIPS-Users] Changing message headers (Custom header) in serial forking

[John Nash]

I tested drouting module and it is very good but when I try to change value
of one custom header (Header was added in initial Invite), I see it added
twice.

--Initial Invite---(Header added)Sent to dest1
---Failure comes from dest1--- Sent to dest2 (Using
use_next_gw)---Remove header if present and add new one.

My guess is after I add header in failure route (after use_next_gw call) it
is getting copied again from original invite. I also tried local_route but
it seems its not going inside that.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users