PLS62 SISX="Ping" and "HostByName" silent failure? | Thales IoT Developer Community

I'm working on upgrading some userware to work on the PLS62. When trying to ping either a valid URL or an IP, the module just returns with "OK" after 1-3 seconds of delay.

I can get a PPP connection up and running as a dialup connection in Windows, and I can definitely see that I'm getting an IP, so I know that this should at least be possible. I'm probably just making a dumb misstep somewhere.

11:39:33.648> at+cops?
11:39:33.648> 
11:39:33.648> +COPS: 0,0,"T-Mobile",2
11:39:33.648> 
11:39:33.648> OK
11:39:42.396> at+cgatt=1
11:39:44.967> 
11:39:44.967> OK
11:39:49.405> AT+CGDCONT=1,"IP","[our apn]"
11:39:49.478> 
11:39:49.478> OK
11:39:56.708> AT^SICS=1,"dns1","[dns ip 1]";^SICS=1,"dns2","[dns ip 2]"
11:39:56.785> 
11:39:56.785> OK
11:40:06.146> AT^SICA=1,1
11:40:06.221> 
11:40:06.221> OK
11:40:08.332> AT+CGPADDR=1
11:40:08.408> 
11:40:08.408> +CGPADDR: 1,"[valid ip]"
11:40:08.408> 
11:40:08.408> OK
11:40:27.896> at^sisx="Ping",1,"[url or ip]",4,8000
11:40:29.282> 
11:40:29.282> OK

The same thing happens when I try a HostByName, but the response is closer to 100ms.

Important tidbit: if I try some bogus url like "ashdgfkjahsdf.com", then the module responds appropriately with "resolve host name failure". That makes it seem like the commands are working under the hood, at least partially.

Any ideas?