CC: fix sanity expectations for call establishment
Recent 'add full SDP codec information to the MNCC...' patch has added a strict CC state sanity check, which is too strict: In tests with 200 concurrent calls, situations came up where the MNCC is faster than the Abis in establishing a call. If that happens, the CC state machine is already in GSM_CSTATE_ACTIVE when the RR channel assignment completes. Also allow GSM_CSTATE_ACTIVE state for accepting an Assignment Complete. Change-Id: I0e0767ec10232615bbf063181fc7f8738ef94f28
This commit is contained in:
parent
b691f58755
commit
0e6185b079
|
@ -1900,6 +1900,10 @@ int cc_assignment_done(struct gsm_trans *trans)
|
|||
/* MT call */
|
||||
break;
|
||||
|
||||
case GSM_CSTATE_ACTIVE:
|
||||
/* already active */
|
||||
break;
|
||||
|
||||
default:
|
||||
LOG_TRANS(trans, LOGL_ERROR, "Assignment done in unexpected CC state: %d\n", trans->cc.state);
|
||||
return -EINVAL;
|
||||
|
|
Loading…
Reference in New Issue