3.2 SIP UAS Details
A QoE Monitoring Agent performs the role of a SIP UAS. The SIP UAS accepts the SERVICE message and responds with a SERVICE response code 202 or a SIP SERVICE response error code. The SIP SERVICE response error code that is returned depends on the issue. The following table lists the error codes that are returned depending on the content of the SIP SERVICE request.
|
Error code |
Reason |
|---|---|
|
606 |
Only VQReportEvent and CallQualityFeedbackReport are supported in current version. 606 is returned if received data is not one of the two specified types. |
|
400 |
If there is a schema validation failure or one or more metric values in the report contain an invalid value. |
|
401 |
If the From header in SIP request doesn’t match the value of LocalPAI or FromURI (when LocalPAI is missing) obtained from payload body. If the sender is an anonymous user, 401 could be returned when the focus-uri header in SIP request does not match ConfURI obtained from payload body. |
|
415 |
If the Content-Type header is not "application/vq-rtcpxr+xml" or "application/ms-cqf+xml". |
|
413 |
If metric report exceeds the maximum size limit of 300 kilobytes allowed by the QoE Monitoring Agent. |