Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
temesg
New Contributor

Supported 3G modem wont connect

Dear All,

 

I've a Huawei E220 connected to a FG40C with FOS5.0

I've tried my best to configure it correctly, but it still wont connect.

 

Diag shows the following: modemd: modem_ppp_stop:483 primary modemd: redails:1  isp:0 dev:/dev/ttyusb1 tel:*99# modemd: Begin dialing: redials left = 1 modemd: dev=/dev/ttyusb1 tel=*99# modemd: modem state changed: 4(hangingup) -> 2(dialing) chat: abort on (BUSY) chat: abort on (NO DIAL TONE) chat: abort on (NO DIALTONE) chat: abort on (NO ANSWER) chat: abort on (ERROR) chat: send (atz^M) chat: expect (OK) chat: atz^M^M chat: OK chat:  -- got it chat: send (ath0^M) chat: abort on (NO CARRIER) chat: expect (OK) chat: ^M chat: ath0^M^M chat: OK chat:  -- got it chat: send (ats7=30^M) chat: timeout set to 30 seconds chat: expect (OK) chat: ^M chat: ats7=30^M^M chat: OK chat:  -- got it chat: send (at+cgdcont=1,"ip","internet.vodafone.net"^M) chat: expect (OK) chat: ^M chat: at+cgdcont=1,"ip","internet.vodafone^M chat: ^BOOT:52394132,0,0,0,6^M chat: .net"^M^M chat: OK chat:  -- got it chat: send (atdt*99#^M) chat: expect (CONNECT) chat: ^M modemd: run_state_machine state 2(dialing) .... modemd: run_state_machine state 2(dialing) chat: atdt*99#^M^M chat: ^BOOT:52394132,0,0,0,6^M chat: alarm chat: Failed modemd: run_state_machine state 2(dialing) modemd: Unable to connect to remote server "*99#"

 

The CONNECT never arrives.

 

All idea is appreciated.

 

TIA

6 REPLIES 6
emnoc
Esteemed Contributor III

Qs;

Are you 100% sure *99# is correct and the APN for vodafone in your area? I've seen *999**1# before and a few others.

 

What I would do is to pull a mobile partner dialup dialer app & look and conduct  your testing using it. It does a few things for you;

 

1: ensure that the modem works ( the SIM is enabled for  data )

2: provide you the correct APN details

3: and dial#

4: and possible username/password if applicable

 

Once you know all of the DETAILs, than you can add that to your profile

PCNSE 

NSE 

StrongSwan  

PCNSE NSE StrongSwan
temesg
New Contributor

For *999**1# I get:

chat: send (atdt*999**1#^M) chat: expect (CONNECT) chat: ^M chat: atdt*999**1#^M^M chat: ERROR chat:  -- failed chat: Failed (ERROR)

*999**1# is definitley not working.

 

I tried with *99# and *99***1# before, both should work. There is no error, it just wont connect.

Modem and SIM is working fine in a Windows machine. Common settings (APN is internet.vodafone.net, dial # is *99#, no user and password auth) are already double checked.

What else could cause this?

emnoc
Esteemed Contributor III

Show us your  modem config?

PCNSE 

NSE 

StrongSwan  

PCNSE NSE StrongSwan
temesg
New Contributor

config system modem     set status enable     set dial-on-demand enable     set redial 2     set connect-timeout 30     set wireless-port 2     set phone1 "*99#"     set username1 "vodafone"     set passwd1 ENC bEXiSmlLEVqRQkIVDppULOq8B/p1iECwmM+r4VxAeosq/kyl5zjD2NNyK+IiSSSwuFYpWAtx/xpukFpNku95ZmostqIQCPfF4NkaRqtZYdk0JdWYGx8BYQJ7TXbfzE70T19Du+hZrGV8QI2R2438h1mNn6g5uHcmtpBXIVTj1eckZv0IobW9sRghtHbXc5J3mJzq8Q==     set extra-init1 "AT+CGDCONT=1,\"IP\",\"internet.vodafone.net\""     set altmode disable end

temesg
New Contributor

I just changed to wireless-port 1 and guess what? :)

It is connected!

 

emnoc
Esteemed Contributor III

Okay good ;)

 

PCNSE 

NSE 

StrongSwan  

PCNSE NSE StrongSwan
Announcements
Check out our Community Chatter Blog! Click here to get involved
Labels
Top Kudoed Authors