This post about sharing one case about SE2900. Please see more details below.
A customer has reported one issue about the Esrvcc failure due to STN-SR. We need to check for the reason.
【Version information】
SE2900_V500R018C10SPH101
【Analysis progress】
1. To check the trace on SE2900, after SE2900 has received 200 OK (register) as below.
2. ATS sends a message to SE2900 for a very short time after SE2900 has received 200 OK (register). This will trigger a SE2900 software issue:
There is an internal software defect. During the initial registration, the SE2900 receives a MESSAGE message from the ATS9900 when processing the 200 (to REGISTER) message from the core network. In this case, SE2900 may fail to update the C-MSISDN information to the CSDB. It will lead SE2900 reply 500 server internal error to ATS. When the subscriber has sent the 'invite' message from iwf to ATCF, ATCF update C-MSISDN information failed due to register flow - it can’t record 'C-MSISDN' to CSDB. It will reply with the '404 not found' error code including 'Number of eMSC Invite Requests with Incorrect C-MSISDNs'.
【Root cause】
SE2900 receives the 200 (to REGISTER) message from the core network and the MESSAGE message from the ATS9900 at the same time, so it triggers a SE2900 software bug and leads to the SE2900 update C-MISDN failed. It will lead to SRVCC to fail.
【Resolution summary】
Please install the new patch SE2900_V500R018C10SPH102 to solve this issue:
