pespin submitted this change.
sccp: Drop error logging for expected scenario
The CN is free to release the SCCP conn at any point through an RLSD,
eg. because the end user on the other side decided to do so.
This was spotted in a osmo-hnbgw deployed in production, where the CN is
sometimes not answering the SCCP-CR[RANAP["Activate PDP Context Req"]]
(only answering with CC but never answering the DTAP on the upper layers).
As a result, most probably the peer times out and decides to
unilaterally release the SCCP conn.
Related: SYS#7454
Change-Id: Ia0941574b05256d6e49babe58df59d938cf637a2
---
M src/osmo-hnbgw/context_map_sccp.c
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/src/osmo-hnbgw/context_map_sccp.c b/src/osmo-hnbgw/context_map_sccp.c
index 5ee584d..987e410 100644
--- a/src/osmo-hnbgw/context_map_sccp.c
+++ b/src/osmo-hnbgw/context_map_sccp.c
@@ -360,9 +360,7 @@
case MAP_SCCP_EV_RX_RELEASED:
ranap_msg = data;
- /* The CN sends an N-Disconnect (SCCP Released) out of the usual sequence. Not what we expected, but
- * handle it. */
- LOGPFSML(fi, LOGL_ERROR, "CN sends SCCP Released sooner than expected\n");
+ /* The CN sends an N-Disconnect (SCCP Released). */
handle_rx_sccp(fi, ranap_msg);
map_sccp_fsm_state_chg(MAP_SCCP_ST_DISCONNECTED);
return;
To view, visit change 40232. To unsubscribe, or for help writing mail filters, visit settings.