Interoperability problems between   CPE and ACS

dBm069 provides visibility into TR-069 implementation errors that can cause interoperability problems with the ACS. If a CPE responses include HTTP or SOAP values that do not comply with the protocol, the ACS may reject the message from the CPE and it could not perform the configuration, leave it unfinished, or it could even cause the loss of communication with the ACS.

An unfinished configuration would leave the CPE in a total or partial non-functional status.

The result of an unfinished configuration in the CPE could thus mean:

• if the ACS is configuring the WLAN, an unfinished configuration could cause the loss to the access to the internet via WIFI
  
• if the ACS is configuring VoIP parameters, an unfinished configuration could cause the user’s loss of the telephone connection 
  
• if the ACS is configuring a STB, an unfinished configuration could cause the loss of TV signal
  
• if the ACS is configuring an AccessPoint, an unfinished configuration could cause to leave it in a non-operational state 
  
• if the ACS is opening a port, an unfinished configuration would result in a non-open port
  
• An unfinished configuration could also leave the CPE in a blocked state where it could be necessary to perform a manual FactoryReset to allow it recovering.
  

BasePort Test plan

This is a good example of a real case detected in a BesePort. When testing test 5.29 from ATP-069, this BasePort did not complied with the protocol regarding the HTTP part of the message.

This is the error message that dBm069 will report:

More info about dBm069-ATP069

dBm069-ATP069

---