From b98bdc21dc495ca2f4babcc6a556b9c0dc63884a Mon Sep 17 00:00:00 2001 From: Henning Westerholt Date: Mon, 3 Feb 2020 11:53:55 +0100 Subject: [PATCH] tm: use WARN log level for status rewrite by UAS (were decreased before SER tm integration) - use WARN log level for status rewrite by UAS (log level decreased before SER tm integration, e.g. v1.5.x) - for bad interconnection or gateways this might be reported frequently (cherry picked from commit e1a01699af450292859e4f2cd69b6a6d85246e5e) --- src/modules/tm/t_reply.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/modules/tm/t_reply.c b/src/modules/tm/t_reply.c index 331bdbdf71b..77747d34c0c 100644 --- a/src/modules/tm/t_reply.c +++ b/src/modules/tm/t_reply.c @@ -1307,7 +1307,7 @@ static enum rps t_should_relay_response( struct cell *Trans , int new_code, } /* this looks however how a very strange status rewrite attempt; * report on it */ - LM_ERR("status rewrite by UAS: stored: %d, received: %d\n", + LM_WARN("status rewrite by UAS: stored: %d, received: %d\n", Trans->uac[branch].last_received, new_code); goto discard; }