Huh! Looks like we both learned something. :-)
—
Sent from mobile, with due apologies for brevity and errors.
> On Aug 19, 2022, at 2:39 AM, Brett Nemeroff
> wrote:
>
>
> Hey Alex,
> I solved this, but I'm including my troubleshooting for the archives.
>
> It is in fact a failure route.
Hey Alex,
I solved this, but I'm including my troubleshooting for the archives.
It is in fact a failure route. I've tried to make it as simple as possible.
I was a little off on the contact header. It appears the contents of the
contact header are in fact the RURI that was used to send the call
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
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
