ELS61T Windows Dialup Config | Telit Cinterion IoT Developer Community
July 2, 2020 - 7:43pm, 1205 views
ELS61ModemLog1.txt ELS61ModemLog2.txt
We've been having some problems initiating a PPP dialup connection through this new terminal. We can connect successfully to the EHS6 and TC65, but our old process isn't working on the ELS61T.
I should note that our old userware from the EHS6 works correctly on the ELS61 when making HTTP requests (it's the old code, but a new build using the eclipse install from the setup CD), and outside of our userware, SISX pings are also working. The only problem is when we're trying to connect with it as a dialup modem in Windows 10.
We noticed from the modem logs in Windows that trying to set the APN with AT+CGDCONT was causing an ERROR, so we removed that and got a step farther before it failed. Assuming that it would continue to fail without that CGDCONT call, we tried to make that call manually via terminal before initializing the dialup connection. AT+CGATT=0;+CGDCONT=1,"IP","[redacted]" followed up by a second AT+CGATT=1 were accepted by the Terminal, but it still wouldn't go through.
I've included the logs from a couple of attempts. Any ideas? We've been reading through the AT command documentation and trying random things, but so far we haven't had any luck.
Hello,
AT+CGDCONT is necessary to set APN. It may reply with an error if it's already used. If the module is registere to LTE CID1 is up and you may not change it then untill you deactivate it. Please set AT+CMEE=2 before to enable printing verbose error descriptions if available.
The dial-up command syntax is as follows:
ATD*99[* [<called_address>][* [<L2P>][* [<cid>]]]]#
ATDT should also work. This 'ATDT*##***##' looks strange for me.
Can you write what is the driver name that you use for this connection in Windows?
Regards,
Bartłomiej
I must have had something in a bad state, because when I went to make some logs to respond to you with, I ended up getting it to work! It might have been disabling dialing rules on the dialup connection's properties, which was trying to send it across as a "dial tone" (hence the DT in ATDT?).
For anyone who's having similar issues and gets here through a search: I did end up getting it working as a Standard PCMCIA Card Modem, and the APN was still getting set with AT+CGDCONT in the initialization parameters.