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 to the first redirect server.
ME=> Redirect server: Fails into "TEST FAILURE". Also has an onreply that checks for 302 and sets an avp. (nothing else)
ME => t_reply(302) to originator. Has 2 contact headers. One from the below append_to_reply. The other is verbatim the RURI I send to the redirect server.
failure_route[TEST_FAILURE] {
if (t_check_status("302")) {
append_to_reply("Contact:
me@here.com:5060\r\n");
t_reply("302","Redirect NOW");
exit;
OH... so after I went through the exercise of writing that out for you I thought I'd check the docs for t_reply based on your comment that it's a whole new reply message. Look what I found:
"If the code is in the range 300-399 (redirect reply), the current destination set is appended to the reply as Contact headers."
:facepalm:
So instead of using append_to_reply, I set $ru prior to the t_reply(302) and we good.
THANK YOU!
-Brett