Actions
Bug #2896
closedN-DISCONNET.req in WAIT_CONN_CONF
Start date:
01/28/2018
Due date:
% Done:
0%
Spec Reference:
Description
In OsmoBSC, there are situations when the SCCP connection attempt is made, but the local SCCP user sends a disconnect request before the connection has been confirmed by the remote peer.
Sun Jan 28 15:23:29 2018 DLSCCP <001e> sccp_scoc.c:1657 SCCP-SCOC(3)[0x5614ebd26d30]{WAIT_CONN_CONF}: Event N-DISCONNECT.req not permitted
This case is specified in the upper left corner of Figure C.2/Q.714 and it is legal. The SCCP provider needs to still wait for CC, and then send a RLSD to the peer.
Files
Updated by laforge about 6 years ago
- Status changed from New to Rejected
- Assignee set to laforge
actually, this is wrong. We are handling this correctly. osmo-bsc was simply sending two N-DISC.req. The first transitioned from CONN_PEND_OUT into WAIT_CONN_CONF, and the second one was illegal.
Actions
