Experience cases of DAE forced client offline failure

The customer's use of third-party software to create a DAE client failed to force the user to offline. By capturing packets, it was found that the device received a disconnect request (40) message and replied with a disconnect nak (42) message. Upon checking the disconnect nak (42) message, it was found that there was an error message in the attribute: error case (101), with the reason being resources unavailable (506). It was determined that there was a problem with the attribute field set by third-party software. After investigation, it was found that the username field was not carried, and the user was successfully forced to offline after being added.

Add the username field to the attribute in the disconnect request (40) message to solve the problem.