Unexpected ppp connection termination
Home › Forums › Conduit: AEP Model › Unexpected ppp connection termination
Tagged: ppp cellular modem hangup
- This topic has 2 replies, 2 voices, and was last updated 7 years ago by
Aleksandr Semuka.
-
AuthorPosts
-
April 16, 2018 at 12:56 am #23101
Aleksandr Semuka
ParticipantHi,
I am using MTCDTIP-LEU1-266A base station with the Firmware 1.4.4.
I am trying to establish ppp connection and get modem hangup.
When I try ping external ip, I see in /var/log/messages the connection process:Apr 16 15:33:55 mtcdt daemon.info pppd[5101]: Starting link
Apr 16 15:33:56 mtcdt local2.info chat[12556]: info: Attempting Basic Radio Communication
Apr 16 15:33:56 mtcdt local2.info chat[12556]: send (AT^M)
Apr 16 15:33:57 mtcdt local2.info chat[12556]: expect (OK)
Apr 16 15:33:57 mtcdt local2.info chat[12556]: ^M
Apr 16 15:33:57 mtcdt local2.info chat[12556]: OK
Apr 16 15:33:57 mtcdt local2.info chat[12556]: — got it
Apr 16 15:33:57 mtcdt local2.info chat[12556]: info: Checking if SIM is inserted
Apr 16 15:33:57 mtcdt local2.info chat[12556]: send (AT#SIMDET?^M)
Apr 16 15:33:57 mtcdt local2.info chat[12556]: expect (#SIMDET: 2,1)
Apr 16 15:33:57 mtcdt local2.info chat[12556]: ^M
Apr 16 15:33:57 mtcdt local2.info chat[12556]: ^M
Apr 16 15:33:57 mtcdt local2.info chat[12556]: #SIMDET: 2,1
Apr 16 15:33:57 mtcdt local2.info chat[12556]: — got it
Apr 16 15:33:57 mtcdt local2.info chat[12556]: info: Checking if SIM is locked
Apr 16 15:33:57 mtcdt local2.info chat[12556]: send (AT+CPIN?^M)
Apr 16 15:33:57 mtcdt local2.info chat[12556]: expect (READY)
Apr 16 15:33:57 mtcdt local2.info chat[12556]: ^M
Apr 16 15:33:57 mtcdt local2.info chat[12556]: ^M
Apr 16 15:33:57 mtcdt local2.info chat[12556]: OK^M
Apr 16 15:33:57 mtcdt local2.info chat[12556]: ^M
Apr 16 15:33:57 mtcdt local2.info chat[12556]: +CPIN: READY
Apr 16 15:33:57 mtcdt local2.info chat[12556]: — got it
Apr 16 15:33:57 mtcdt local2.info chat[12556]: info: SIM was unlocked
Apr 16 15:33:57 mtcdt local2.info chat[12556]: info: Waiting for minimum signal strength
Apr 16 15:33:57 mtcdt local2.info chat[12556]: send (AT+CSQ^M)
Apr 16 15:33:57 mtcdt local2.info chat[12556]: expect (+CSQ: )
Apr 16 15:33:57 mtcdt local2.info chat[12556]: ^M
Apr 16 15:33:57 mtcdt local2.info chat[12556]: ^M
Apr 16 15:33:57 mtcdt local2.info chat[12556]: OK^M
Apr 16 15:33:57 mtcdt local2.info chat[12556]: ^M
Apr 16 15:33:57 mtcdt local2.info chat[12556]: +CSQ:
Apr 16 15:33:57 mtcdt local2.info chat[12556]: — got it
Apr 16 15:33:57 mtcdt local2.info chat[12556]: expect (99,99)
Apr 16 15:33:57 mtcdt local2.info chat[12556]: 31,99^M
Apr 16 15:33:57 mtcdt local2.info chat[12556]: ^M
Apr 16 15:33:57 mtcdt local2.info chat[12556]: OK^M
Apr 16 15:33:58 mtcdt local2.info chat[12556]: alarm
Apr 16 15:33:58 mtcdt local2.info chat[12556]: send (AT^M)
Apr 16 15:33:58 mtcdt local2.info chat[12556]: expect (OK)
Apr 16 15:33:58 mtcdt local2.info chat[12556]: ^M
Apr 16 15:33:58 mtcdt local2.info chat[12556]: OK
Apr 16 15:33:58 mtcdt local2.info chat[12556]: — got it
Apr 16 15:33:58 mtcdt local2.info chat[12556]: send (AT^M)
Apr 16 15:33:58 mtcdt local2.info chat[12556]: abort on (NO CARRIER)
Apr 16 15:33:58 mtcdt local2.info chat[12556]: abort on (BUSY)
Apr 16 15:33:58 mtcdt local2.info chat[12556]: abort on (ERROR)
Apr 16 15:33:58 mtcdt local2.info chat[12556]: expect (OK)
Apr 16 15:33:58 mtcdt local2.info chat[12556]: ^M
Apr 16 15:33:58 mtcdt local2.info chat[12556]: ^M
Apr 16 15:33:58 mtcdt local2.info chat[12556]: OK
Apr 16 15:33:58 mtcdt local2.info chat[12556]: — got it
Apr 16 15:33:58 mtcdt local2.info chat[12556]: send (AT+CSQ^M)
Apr 16 15:33:58 mtcdt local2.info chat[12556]: expect (OK)
Apr 16 15:33:58 mtcdt local2.info chat[12556]: ^M
Apr 16 15:33:58 mtcdt local2.info chat[12556]: ^M
Apr 16 15:33:58 mtcdt local2.info chat[12556]: +CSQ: 31,99^M
Apr 16 15:33:58 mtcdt local2.info chat[12556]: ^M
Apr 16 15:33:58 mtcdt local2.info chat[12556]: OK
Apr 16 15:33:58 mtcdt local2.info chat[12556]: — got it
Apr 16 15:33:58 mtcdt local2.info chat[12556]: send (AT+CGDCONT=1,\”IP\”,\”telstra.m2m\”^M)
Apr 16 15:33:58 mtcdt local2.info chat[12556]: expect (OK)
Apr 16 15:33:58 mtcdt local2.info chat[12556]: ^M
Apr 16 15:33:58 mtcdt local2.info chat[12556]: ^M
Apr 16 15:33:58 mtcdt local2.info chat[12556]: OK
Apr 16 15:33:58 mtcdt local2.info chat[12556]: — got it
Apr 16 15:33:58 mtcdt local2.info chat[12556]: send (ATDT*99***1#^M)
Apr 16 15:33:58 mtcdt local2.info chat[12556]: expect (CONNECT)
Apr 16 15:33:58 mtcdt local2.info chat[12556]: ^M
Apr 16 15:33:58 mtcdt local2.info chat[12556]: ^M
Apr 16 15:33:58 mtcdt local2.info chat[12556]: CONNECT
Apr 16 15:33:58 mtcdt local2.info chat[12556]: — got it
Apr 16 15:33:58 mtcdt local2.info chat[12556]: send (^M)
Apr 16 15:33:58 mtcdt daemon.info pppd[5101]: Serial connection established.
Apr 16 15:33:58 mtcdt daemon.notice pppd[5101]: Connect: ppp0 <–> /dev/modem_at0
Apr 16 15:34:00 mtcdt daemon.info pppd[5101]: Hangup (SIGHUP)
Apr 16 15:34:00 mtcdt daemon.notice pppd[5101]: Modem hangup
Apr 16 15:34:00 mtcdt daemon.notice pppd[5101]: Connection terminated.
Apr 16 15:34:01 mtcdt daemon.info pppd[5101]: Exit.As you can see, in the end I got Modem hangup for some reason.
Ifconfig looks like:
ppp0 Link encap:Point-to-Point Protocol
inet addr:10.64.64.64 P-t-P:10.112.112.112 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:53 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:0 (0.0 B) TX bytes:106 (106.0 B)Route command:
Destination Gateway Genmask Flags Metric Ref Use Iface
default 10.112.112.112 0.0.0.0 UG 0 0 0 ppp0
10.112.112.112 * 255.255.255.255 UH 0 0 0 ppp0
192.168.250.0 * 255.255.254.0 U 0 0 0 eth0What can be possible solution for that?
Thanks.April 16, 2018 at 7:57 am #23111Jeff Hatch
KeymasterAleksandr,
Please open a support portal case at https://support.multitech.com and they can help you.
Jeff
April 18, 2018 at 12:43 am #23149Aleksandr Semuka
ParticipantThe problem solved. The cable inside the station was disconnected.
-
AuthorPosts
- You must be logged in to reply to this topic.