Why do I have a daily CWMP session on my router?

[#1]

Every day, at 16:27, I see the following reported in my router logs

16:27:06, 12 May.	(1617198.190000) CWMP: session completed successfully
16:27:05, 12 May.	(1617198.000000) CWMP: HTTP authentication success from https://dbtpnhdm.bt.mo
16:27:04, 12 May.	(1617196.610000) CWMP: Server URL: https://dbtpnhdm.bt.mo; Connecting as user: ACS username
16:27:04, 12 May.	(1617196.610000) CWMP: Session start now. Event code(s): '2 PERIODIC,4 VALUE CHANGE'
16:27:04, 12 May.	(1617196.270000) CWMP: Initializing transaction for event code 2 PERIODIC

Doesn't appear to be causing any harm but I am curious to know what is going on. Can anyone explain?

[#2]

Hi @aeneareid

The CWMP contact (also referred to sometimes as TR-069) is our remote admin program checking in with the router.

It can (but doesn't always) perform a number of functions which you can read about here.

Nothing to worry about

Thanks

Dave

[#3]

OK. Thanks for the reference but still curious as to why there is a daily check and what it is checking for.

And why is it linking to https://dbtpnhdm.bt.mo which I gather is an abbreviated version of https://pbthdm.bt.motive.com

Not worried - just curious.

[#4]

Hi @aeneareid

TR-069 will check in every 24 hours to ascertain whether several maintenance features needs to be performed on the router - for example, firmware updates, carrying across any changes that have been made to the Member Centre password etc. This shouldn't affect your router performance or connection stability and is 100% how TR-069 is designed to behave.

Best wishes

Dave

[#5]

Thanks. Curiosity satisfied.

[#6]

It's actually your router checking in with the hardware management platform, not the other way round.

The router has a URL stored for the management platform and an 'inform period' set, which determines how frequently it should make contact (every 24hrs in this case). The actual time it happens likely coincides with when you first plugged the device in (or 'activated' it).

Typically, all it will be saying is "I'm still here!", and relaying some basic info like firmware version and subscriber ID/PPP info. This is helpful from an asset management perspective, and allows us to easily determine how many routers we have in active use.

As others have alluded to, it can also be used when remotely pushing software updates or running ad-hoc reports etc.

It is possible to trigger your router to make a call to the remote management server from this side, but that's not what you're seeing here.