Thank you for sending this patch (sorry for the long delay). I have committed it now in the trunk with small changes - rev 9432.
So now it is possible to add headers to the initial Invite(from request route before calling b2b_init_request) or for replies (from b2b_reply_route) or sequential requests (from b2b_request_route).
Regards,
Anca
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Unfortunately this patch only implements the possibility to add headers, not also to remove them.
But indeed for it to be consistent, the possibility to also remove a header should be available. I will try to implement this in the next period.
Regards,
Anca
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I would like to do the following:
route[b2b_reply] {
xlog("b2b_reply ($ci)\n");
if(remove_hf("Allow"))
{
append_hf("Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, INFO\r\n");
}
}
The remove_hf return true but the 180 ringing reply still has the same Allow header.
Will this patch make this happen? Thanks!
Hi Nick,
Thank you for sending this patch (sorry for the long delay). I have committed it now in the trunk with small changes - rev 9432.
So now it is possible to add headers to the initial Invite(from request route before calling b2b_init_request) or for replies (from b2b_reply_route) or sequential requests (from b2b_request_route).
Regards,
Anca
Hi a719719,
Unfortunately this patch only implements the possibility to add headers, not also to remove them.
But indeed for it to be consistent, the possibility to also remove a header should be available. I will try to implement this in the next period.
Regards,
Anca