EHS6T - Authentication AT^SGAUTH - SM deactivation | Thales IoT Developer Community
February 6, 2017 - 4:00pm, 5140 views
Hi,
I'm trying to establish a connection to a customer private network with the EHS6T terminal.
The customer has a SIM card with static IP address assigned by the ISP. I setup de authentication parameters with the command AT^SGAUTH, setup the APN with AT+CGCONT and connect with ATD*99***1#.
The terminal respond CONNECT and then the pppd ****** start the negociation. See the log :
Serial connection established.
using channel 251
Using interface ppp0
Connect: ppp0 <--> /dev/ttyS3
rcvd [LCP ConfReq id=0x1 <asyncmap 0x0> <auth pap> <magic 0x225ffd20> <pcomp> <accomp>]
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x975999e8> <pcomp> <accomp>]
sent [LCP ConfNak id=0x1 <auth eap>]
rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0x975999e8> <pcomp> <accomp>]
rcvd [LCP ConfReq id=0x2 <asyncmap 0x0> <magic 0x225ffd20> <pcomp> <accomp>]
sent [LCP ConfAck id=0x2 <asyncmap 0x0> <magic 0x225ffd20> <pcomp> <accomp>]
sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns3 0.0.0.0>]
rcvd [LCP TermReq id=0x3]
LCP terminated by peer
sent [LCP TermAck id=0x3]
When I look at the error given by the terminal after the unsuccesful attemp I get this message:
AT+CEER
+CEER: "SM deactivation",129,"User authentication failed"
I'm sure that the APN, login, password are correct. They have been tested with an other equipement.
Can u help me to solve this problem? It's really urgent!
thanks in advance
Hello,
Do you have any special characters in user or password? Mayby it has something to do with character set encoding. Are you sure that you have configured the proper authentication type?
Regards,
Bartłomiej
Hello Bartlomiej,
There is no special characters in apn,user and password, only alpha-numeric character. I have tried the two authentication types CHAP and PAP with the command AT^SGAUTH without success. With the two authentication's type I get the same error code.
I tried also to change de characters encoding but it's doesn't help.
Best regards
Some news...
I finally found a solution to my problem. I changed the connection script to manually attach the PDP context before enter in data ****.
Here is the script, it may help someone else:
TIMEOUT 60
ABORT 'BUSY'
ABORT 'ERROR'
ABORT 'NO CARRIER'
'' 'AT'
OK 'AT+CGDCONT=1,"IP","my_apn"'
OK 'AT\^SGAUTH=1,1,"my_user","my_password"'
OK 'AT+CGATT=1'
OK 'AT+CGACT=1,1'
OK 'AT+CGATT?'
OK 'AT+CGPADDR'
OK 'ATD*99***1#'
CONNECT ''
I think that the problem was related to some delay introducted by the authentication.
Best regards
Hello,
I have noticed later on that there is eap authentication offered by your system (which is not supported by the module) but I can see that you have already found a solution.
Great that you finally got it working. This looks like a good solution.
Regards,
Bartłomiej
the eap authentication request seems to be sent when pppd is configured without pap and chap. The log I posted was with this configuration (-pap -chap) but it wasn't the problem's cause.
OK, so let's assume that your solution solves the problem in that particular case as it is also perfectly legal according to the documentation.
Regards,
Bartłomiej
Hello,
in which script must enter this commands?
Miloš
Solution. It is necessary to enter in the:
/etc/chatscripts/3g.chat
Best regards