Article Original Creation Date: 2010-12-09
Informs that have a partial soap message
Informs that do not have a soap message, only having an HTTP header
Informs that contain invalid ASCII characters
- Incomplete informs: BBOX1=159 , BBOX2=9 , other (old Philips modems)=12
- Illegal char informs: other=60
- Empty soap msg: unknown=27
- Incomplete - Most probably coming back with a full inform and will then be logged.
- Empty - Most probably coming back with a full inform and will then be logged.
- Illegal - Most probably not been logged in SGW as the illegal characters are stored in there local database.
- How can we create reports on these cases, with unique ids, timestamp?
- Why the inform messages might be truncated (after HTTP header or part of the message)?
- Is it possible to strip illegal characters before the inform is processed? (as a patch on 4.1)
- While inform based session data is typically stored in the SPRT_NC_CWMP_SESSION table, it would not in this case as the inform message would not be parsed at processed correctly by the ACS servers. For informs that are complete and processed correctly the Service Gateway reporting engine can be used to generate reports from data in this table.
- A script could be written to parse the log data on the ACS servers and provide some detail around these partial informs.
- As indicated, the load balancer was allowing the establishment of TCP sessions with the device and then in some cases tearing down the session when it determined that the maximum concurrent session limit had been exceeded. This resulted in the truncated inform messages.
- This functionality was added in Service Gateway 4.1.4 and obsoleted in Service Gateway 4.3 with the addition of the "Event Pre-processing" functionality. Please refer to the respective release notes for additional information.