The phenomenon of description:
Avaya phone registration, USM returns 500 response, warning header field carries "Internal Error".
The analysis process:
1. Check the user's message tracking, and see a log print like "[SSDB_LOG]SsdbSREGQueryData SsdbQueryChargingInfoTbl fail" near the USM return 500
response;
2. according to the printing content combined with code view, is the call function SsdbQueryChargingInfoTbl according to IMPI to query the billing
address failed, it is suspected that IMPI belt is not correct;
3. There are two ways to obtain IMPI according to the code to find USM (from username in the registered authentication header field or from IMPU),
and BIT0 control of soft parameter 5004; Related function: RegGetIMPIFromMsgProc;
4. Check the environment that the value of the soft parameter configuration is 0, that is, get it from the username in the registration authentication
header field, and then see that the username is a string of pure Numbers in the registration request of the terminal, and the IMPI used by USM should be
in the domain name format.
Question why:
1. Username in the authentication header field of the terminal registration request is in pure digital format;
2. USM gets IMPI from username and fails to query the billing address according to this IMPI;
Processing steps:
Step 1: log in USM through LMT, execute the MOD SFP command under the USM network element, and modify the value of soft parameter 5004 to 205 (the original soft parameter value is 204, where BIT0 is changed to 1 and 205).
