Confirming that eDRX is disabled following CEDRXS=3

[EFrank]

According to the docs, when CEDRXS=3 is sent to the 9160, the modem disables eDRX and the unsolicited response code. However, this means there is no response code to listen for when attempting to validate that eDRX has been disabled.

Similarly, CEDRXS? returns the requested eDRX interval, not the actual.

Given both of these, what is the appropriate way to validate that the modem has, in fact, fully disabled eDRX following a request to do so (ActT-type=0)?

[Øyvind]

Hello, 

Do you have any logs of the issue? What modem FW are you running on your device? 

What does XMONITOR return after CEDRXS=3?

Kind regards,
Øyvind

[EFrank]

We don't have logs, but we can begin to gather them now. 

This isn't so much an issue as a question of best practice. After we issue CEDRXS=3, should we assume that the modem has gone into standard DRX and operate on that assumption? Or is there some method by which we can confirm the change back to DRX?

I'll get back to you with the XMONITOR results and logs if those are still needed to answer this, but I think it may be as simple as whether or not the network is allowed to reject a request to downgrade from eDRX to DRX

[Øyvind]

Testing on my side, you can see that issuing CEDRXS=3 will empty the eDRX field in XMONITOR. If the field is empty, then no eDRX is used.

> AT+CEDRXS=1,4,"1000"

OK
> AT+CEDRXS?

+CEDRXS: 4,"1000"

OK
> at%xmonitor

%XMONITOR: 5,"","","24201","8173",7,20,"01172803",327,6400,59,31,"1000","11100000","11100000","01011001"

OK
> AT+CEDRXS=3

OK
> at%xmonitor

Also,  +CEDRXP notification does not seem to be sent when eDRX is disabled

Kind regards,
Øyvind