sip: tweak log for release caused by status >= 300

Make it easier to spot when the sip server answers an invite with
anything that would cause osmo-sip-connector to release the call.

Related: SYS#6386
Change-Id: I64889d6ce174dc17d44d85aac12e7ee6e6b06164
---
M src/sip.c
1 file changed, 19 insertions(+), 1 deletion(-)

diff --git a/src/sip.c b/src/sip.c
index 9124752..ca8f4ba 100644
--- a/src/sip.c
+++ b/src/sip.c
@@ -380,7 +380,12 @@
 		else if (status >= 300) {
 			struct call_leg *other = call_leg_other(&leg->base);
 
-			LOGP(DSIP, LOGL_INFO, "INVITE got status(%d), releasing leg(%p).\n", status, leg);
+			if (status < 400)
+				LOGP(DSIP, LOGL_NOTICE, "INVITE got status(%d), releasing leg(%p) as redirect is not"
+				     " implemented\n", status, leg);
+			else
+				LOGP(DSIP, LOGL_ERROR, "INVITE got status(%d), releasing leg(%p)\n", status, leg);
+
 			nua_cancel(leg->nua_handle, TAG_END());
 			nua_handle_destroy(leg->nua_handle);
 			call_leg_release(&leg->base);

