osmith has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-sip-connector/+/32018 )
Change subject: sip: log release caused by status >= 300 as error ......................................................................
sip: log release caused by status >= 300 as error
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, 15 insertions(+), 2 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/osmo-sip-connector refs/changes/18/32018/1
diff --git a/src/sip.c b/src/sip.c index 9124752..60c2682 100644 --- a/src/sip.c +++ b/src/sip.c @@ -380,13 +380,13 @@ 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); + 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);
if (other) { - LOGP(DSIP, LOGL_INFO, "Releasing MNCC leg (%p) with status(%d)\n", other, status); + LOGP(DSIP, LOGL_ERROR, "Releasing MNCC leg (%p) with status(%d)\n", other, status); other->cause = status2cause(status); other->release_call(other); }