Hi Brett,
In what context are you performing these operations? Is it a failure_route? If not, can you try it in a failure_route?
I ask because this is very surprising behaviour. t_reply() should create an entirely brand-new reply message, and no elements of a previously received reply on some branch should leak into it.
— Alex
On Aug 19, 2022, at 12:26 AM, Brett Nemeroff brett+kamailio@voicefoxtelephony.com wrote:
Hello, I'm receiving calls which I forward to a server I KNOW will reply with a 302. When I get that 302, I parse some information and then t_reply(302) the originator. The 302 I create needs to have it's own contact header which I am adding with append_to_reply(). That works great. BUT the contact header from the original 302 is hanging around. Now I have two contact headers :(
How can I get rid of the original 302's contact header? remove_hf() doesn't work in this context since it's a reply. So I need a kind of "remove_header_from_reply()".
Thanks, Brett
Kamailio - Users Mailing List - Non Commercial Discussions
- sr-users@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: