PLS8-X : AT&T 3G dialing issue | Telit Cinterion IoT Developer Community
April 20, 2016 - 10:30am, 4811 views
We're having troubles when trying to connect to AT&T network during a series of tests last week in the U.S., especially when we sent dialing command for 3G connection : ATD*99***1#<CR><LF>
Can someone confirms our AT dialing command is correct ?
When connects to AT&T or Verizon :
- Do the dialing command requires a specific syntax ? (I heard, without being able to validate the information, that a semicolon might be added at the end of ATD*99***1# ... is it a possibility ?)
- Are we miss some specific steps, for connecting, the other providers do not requires ?
ATI4 of or our PLS8-X :
We're using, before dialing the AT+CGDCONT=1,"IP","***"<CR><LF> command.
Thanks in advance...
- Note : there is '3G' in the title, but of course it should be '3G or 4G'... -
Could you write more details and some log fragment with the module configuration and ATD attempt and result?
Does it always fail? Are there any other problems with other connections?
What software/device are you using for dialup connection?
How about the APN you are using? Is that possible that it requires a specific user and password? Are you providing it during PPP negotiation?
Semicolon is used with ATD command for sending *# codes or making voice calls (if supported by the module).
Is it possible that this is a network coverage or antenna problem?
Here is a link to the log (Bell network, Canada... but it is the same behavior for AT&T in U.S.) : https://www.dropbox.com/s/zzfq0o495gw0nef/PLS8-X_BellCanada_21-Apr-2016_...
It will give you information about ****m configuration, APN, initialization and dialing sequence, and network coverage.
I'm not allowed to post it directly to the forum, the filters believe that is spamming...
And to answer to your other questions :
- We are using an industrial proprietary embedded device, the demo board AH6-DSB75-1 on DSB-Mini is connected through USB to this device, we use the USB serial interface (ACM) to communicate with the ****m, the SSRVSET configuration number 10 is activated, we're using USB0 channel only.
- It does not work : with our device, it always fails in AT&T networks in the U.S. and Bell networks in Canada. We do not have the opportunity yet to test with Verizon in the U.S.
It works : with our device, here in Belgium, but in GPRS **** (of course not 4G because of the different frequencies -> I will ask to my colleague to force the ****m to fallback, with AT+COPS, to 3G/GPRS network, to see what's the ****m behavior).
It works : with the devkit connected directly to a laptop, with the Gemalto Connection Manager software. Here is what my colleague (who did the testing in U.S.) is telling : "So the Connection Manager application uses the Ethernet device contexts to communicate with the DevKit, not a serial connection. When I configure a dial-up connection (means : in windows) using the ****m device, I cannot establish a PPP session. Nothing seems to work when using the PLS8-X in PPP ****. This is quite different from the PLS8-US which had no issues establishing a PPP connection on an LTE network."
- This configuration (Operator/SIM card/APN) has already been tested, and is working with other devices. Yes we may provide user/password, aimed to be used during the PPP negotiation... but we never reached it because the issue is when we dial.
- I don't believe we have antenna or network coverage issues.
Thanks a lot for your help.
Thank you for so detailed answer.
I've had a chance to test with PLS8-V in Verizon 4G network. It was possible to get CONNECT but with CID other than 1. Generally the conclusion is that for PLS8-X module profile 1 is dedicated to IMS services and should not be used for other connections. So maybe this is a case here and difference to PLS8-US.
Here's my log:
+COPS: 0,0,"Verizon Wireless",7
You can find more details about APNs configuration for PLS8-X (for Verizon) in AT^SGAPN command description in the AT commands specification.
Thank you, a lot, for your instructive answer, and the test you did.
(I didn't realized there is such 'restrictive' link between APN & CID. To my knowledge, this is not the case here in Belgium).
Unfortunately, my colleague will not be able to do a test in Canada/US, with different CID, before next monday.
I'll keep you in touch.
It's working, both with AT&T and Verizon ! You were right : it was a CID vs APN issue...
That's a real relief for us...
Great that everything is working!
Thanks for information.