Actions
Bug #2718
closedipaccess_bts_handle_ccm() gets ID_REQ/ID_RESP/ID_ACK wrong
Start date:
12/06/2017
Due date:
% Done:
100%
Spec Reference:
Description
We've never had any documentation for the IPA CCM sub-protocol, but logic dictates [tm] that the sequence is as follows:
- BTS<-BSC IPA_IDENTITY_REQ (requesting unit-id etc.)
- BTS->BSC IPA_IDENTITY_RESP (responding with unit-id etc.)
- BTS<-BSC IPA_IDENTITY_ACK (acknowledging that the identity is known/welcome)
- BTS->BSC IPA_IDENTITY_ACK (another ack to ack the ack?)
- wait for any IPA_IDENTITY_REQ
- respond with IPA_IDENTITY_RESP
- immediately send an IPA_IDENTITY_ACK, no matter if the BSC/server sends an ACK first
And this code is used in our OsmoBTS code base :/
Related issues
Actions