Hi Matt
Thanks yes I agree, Donald’s comment to try at!scact is the wrong command for this test - note that the command I used was the very similar AT+CGACT
I’ve updated the thread title to indicate I’m using a UART as the interface as opposed to USB networking.
Not sure about the multiple active contexts - the EE SIM supports multiple contexts on the RC76 and on the WP76 from Legato. I can activate two contexts without any issues
The issue appears to occur when the active RAT is LTE. I’m beginning to think the issue could be the way the WP76 handles LTE vs 2G/3G. Or it could be just a bug in the WP AT command handler 
Try using Legato
Just discovered something else which might give a clue as to why I see the issue, if I use Legato cm data to connect context 3 I do see an AT+CGPADDR IP address for context 3 - this is making me think that the issue is with the way that I am using AT commands to activate the context
For example
cm data connect
Setting up profile 3
Connecting ... ok
at+cgact?
+CGACT: 1,1
+CGACT: 2,1
+CGACT: 3,1
AT+CGPADDR
+CGPADDR: 1,100.65.190.114
+CGPADDR: 2,0.0.0.0
+CGPADDR: 3,100.67.47.76
cm data disconnect
Disconnecting ... ok
at+cgact?
+CGACT: 1,1
+CGACT: 2,1
+CGACT: 3,0
AT+CGPADDR
+CGPADDR: 1,100.65.190.114
+CGPADDR: 2,0.0.0.0
+CGPADDR: 3,0.0.0.0
Try using PPP over UART
Then I repeated the above using PPP over RC76 UART1 - this time the AT+CGPADDR returns 0.0.0.0 even though the ppp session is working OK -
pppd connect using context #2 with the boring bit missing
Mar 2 15:14:43 raspberrypi chat[3199]: send (ATDT*99***2#^M)
Mar 2 15:14:43 raspberrypi chat[3199]: CONNECT
Mar 2 15:14:44 raspberrypi pppd[3197]: using channel 3
Mar 2 15:14:44 raspberrypi pppd[3197]: Connect: ppp1 <--> /dev/ttyAMA0
Mar 2 15:14:45 raspberrypi pppd[3197]: local IP address 100.65.190.114
Mar 2 15:14:45 raspberrypi pppd[3197]: remote IP address 10.64.64.65
In the USB serial AT console query the modem whilst PPP is still working
at+cgpaddr
+CGPADDR: 1,100.65.190.114
+CGPADDR: 2,0.0.0.0
+CGPADDR: 3,0.0.0.0
at+cgact?
+CGACT: 1,1
+CGACT: 2,0
+CGACT: 3,0
Looks to me that command ATDT99**2# is actually using context 1 - should I raise another forum post for this maybe secondary issue or should we plough on with this post?
Donald - I’m not sure why your closed my thread as the original cgact issue isn’t resolved. The PPP context issue is, I suspect, related to the original CGACT issue - my guess is that serial based contexts other than context 1 are not supported with the current WP76xx FW. Happy to change this comment if I’m wrong though please let me know.