This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sierra Wireless Aircard 313U Issues Connecting to Carrier

Hello, everyone.

I've pretty much tried everything I could looking through old posts and searching for answers so I figured as my last course of action perhaps someone out there might be able to help.

I have just deployed UTM 9.6 installed an a Dell R210 II and I am attempting to get working a Sierra Wireless AirCard 313U with T-Mobile. I had this card working on the previous router, which was a PepLink Balance One as a cell failover and it had been working with out issue just before the switch over to UTM 9.6.

Following all the directions to get the interface confifgured, it seems like everything was good to go, UTM 9.6 was recognizing the device without issue, so I went ahead and tried to connect and you can see the result in the log file clipping below:

2019:01:11-14:53:12 cerberus pppd[6766]: pppd 2.4.7 started by root, uid 0
2019:01:11-14:53:13 cerberus chat[6785]: abort on (NO CARRIER)
2019:01:11-14:53:13 cerberus chat[6785]: abort on (NO DIALTONE)
2019:01:11-14:53:13 cerberus chat[6785]: abort on (RINGING RINGING)
2019:01:11-14:53:13 cerberus chat[6785]: abort on (ERROR)
2019:01:11-14:53:13 cerberus chat[6785]: abort on (NO ANSWER)
2019:01:11-14:53:13 cerberus chat[6785]: abort on (BUSY)
2019:01:11-14:53:13 cerberus chat[6785]: abort on (DELAYED)
2019:01:11-14:53:13 cerberus chat[6785]: abort on (Username/Password Incorrect)
2019:01:11-14:53:13 cerberus chat[6785]: timeout set to 5 seconds
2019:01:11-14:53:13 cerberus chat[6785]: timeout set to 5 seconds
2019:01:11-14:53:13 cerberus chat[6785]: send (ATZ^M)
2019:01:11-14:53:13 cerberus chat[6785]: expect (OK)
2019:01:11-14:53:13 cerberus chat[6785]: ATZ^M^M
2019:01:11-14:53:13 cerberus chat[6785]: OK
2019:01:11-14:53:13 cerberus chat[6785]: -- got it
2019:01:11-14:53:13 cerberus chat[6785]: send (ATI^M)
2019:01:11-14:53:13 cerberus chat[6785]: expect (OK)
2019:01:11-14:53:13 cerberus chat[6785]: ^M
2019:01:11-14:53:13 cerberus chat[6785]: ATI^M^M
2019:01:11-14:53:13 cerberus chat[6785]: Manufacturer: Sierra Wireless, Incorporated^M
2019:01:11-14:53:13 cerberus chat[6785]: Model: AirCard 313U^M
2019:01:11-14:53:13 cerberus chat[6785]: Revision: SWI9200X_00.07.07.00AP R2016 CARMD-EN-10526 2011/05/14 14:26:10^M
2019:01:11-14:53:13 cerberus chat[6785]: IMEI: 012698000085545^M
2019:01:11-14:53:13 cerberus chat[6785]: IMEI SV: 1^M
2019:01:11-14:53:13 cerberus chat[6785]: FSN: CDF1691240010^M
2019:01:11-14:53:13 cerberus chat[6785]: 3GPP Release 8^M
2019:01:11-14:53:13 cerberus chat[6785]: +GCAP: +CGSM^M
2019:01:11-14:53:13 cerberus chat[6785]: ^M
2019:01:11-14:53:13 cerberus chat[6785]: ^M
2019:01:11-14:53:13 cerberus chat[6785]: OK
2019:01:11-14:53:13 cerberus chat[6785]: -- got it
2019:01:11-14:53:13 cerberus chat[6785]: send (AT+CGDCONT?^M)
2019:01:11-14:53:13 cerberus chat[6785]: expect (OK)
2019:01:11-14:53:13 cerberus chat[6785]: ^M
2019:01:11-14:53:13 cerberus chat[6785]: AT+CGDCONT?^M^M
2019:01:11-14:53:13 cerberus chat[6785]: +CGDCONT: 1,"IP","fast.t-mobile.com","0.0.0.0",0,0^M
2019:01:11-14:53:13 cerberus chat[6785]: +CGDCONT: 2,"IP","wap.voicestream.com","0.0.0.0",0,0^M
2019:01:11-14:53:13 cerberus chat[6785]: +CGDCONT: 3,"IP","fast.t-mobile.com","0.0.0.0",0,0^M
2019:01:11-14:53:13 cerberus chat[6785]: ^M
2019:01:11-14:53:13 cerberus chat[6785]: OK
2019:01:11-14:53:13 cerberus chat[6785]: -- got it
2019:01:11-14:53:13 cerberus chat[6785]: send (AT+CGDCONT=1,"IP","fast.t-mobile.com"^M)
2019:01:11-14:53:13 cerberus chat[6785]: expect (OK)
2019:01:11-14:53:13 cerberus chat[6785]: ^M
2019:01:11-14:53:13 cerberus chat[6785]: AT+CGDCONT=1,"IP","fast.t-mobile.com"^M^M
2019:01:11-14:53:13 cerberus chat[6785]: OK
2019:01:11-14:53:13 cerberus chat[6785]: -- got it
2019:01:11-14:53:13 cerberus chat[6785]: send (AT+CGDCONT?^M)
2019:01:11-14:53:14 cerberus chat[6785]: report (+CGDCONT:)
2019:01:11-14:53:14 cerberus chat[6785]: clear abort on (ERROR)
2019:01:11-14:53:14 cerberus chat[6785]: expect (OK)
2019:01:11-14:53:14 cerberus chat[6785]: ^M
2019:01:11-14:53:14 cerberus chat[6785]: AT+CGDCONT?^M^M
2019:01:11-14:53:14 cerberus chat[6785]: +CGDCONT: 1,"IP","fast.t-mobile.com","0.0.0.0",0,0^M
2019:01:11-14:53:14 cerberus chat[6785]: +CGDCONT: 2,"IP","wap.voicestream.com","0.0.0.0",0,0^M
2019:01:11-14:53:14 cerberus chat[6785]: +CGDCONT: 3,"IP","fast.t-mobile.com","0.0.0.0",0,0^M
2019:01:11-14:53:14 cerberus chat[6785]: ^M
2019:01:11-14:53:14 cerberus chat[6785]: OK
2019:01:11-14:53:14 cerberus chat[6785]: -- got it
2019:01:11-14:53:14 cerberus chat[6785]: send (AT+CSQ^M)
2019:01:11-14:53:14 cerberus chat[6785]: report (+CSQ:)
2019:01:11-14:53:14 cerberus chat[6785]: abort on (ERROR)
2019:01:11-14:53:14 cerberus chat[6785]: expect (OK)
2019:01:11-14:53:14 cerberus chat[6785]: ^M
2019:01:11-14:53:14 cerberus chat[6785]: AT+CSQ^M^M
2019:01:11-14:53:14 cerberus chat[6785]: +CSQ: 21,99^M
2019:01:11-14:53:14 cerberus chat[6785]: ^M
2019:01:11-14:53:14 cerberus chat[6785]: OK
2019:01:11-14:53:14 cerberus chat[6785]: -- got it
2019:01:11-14:53:14 cerberus chat[6785]: send (ATH0^M)
2019:01:11-14:53:14 cerberus chat[6785]: expect (OK)
2019:01:11-14:53:14 cerberus chat[6785]: ^M
2019:01:11-14:53:14 cerberus chat[6785]: ATH0^M^M
2019:01:11-14:53:14 cerberus chat[6785]: OK
2019:01:11-14:53:14 cerberus chat[6785]: -- got it
2019:01:11-14:53:14 cerberus chat[6785]: send (ATZ^M)
2019:01:11-14:53:14 cerberus chat[6785]: timeout set to 45 seconds
2019:01:11-14:53:14 cerberus chat[6785]: expect (OK)
2019:01:11-14:53:14 cerberus chat[6785]: ^M
2019:01:11-14:53:14 cerberus chat[6785]: ATZ^M^M
2019:01:11-14:53:14 cerberus chat[6785]: OK
2019:01:11-14:53:14 cerberus chat[6785]: -- got it
2019:01:11-14:53:14 cerberus chat[6785]: send (\d\d\d\d\dATD*99#^M)
2019:01:11-14:53:19 cerberus chat[6785]: expect (CONNECT)
2019:01:11-14:53:19 cerberus chat[6785]: ^M
2019:01:11-14:53:19 cerberus chat[6785]: ATD*99#^M^M
2019:01:11-14:53:19 cerberus chat[6785]: NO CARRIER
2019:01:11-14:53:19 cerberus chat[6785]: -- failed
2019:01:11-14:53:19 cerberus chat[6785]: Failed (NO CARRIER)
2019:01:11-14:53:19 cerberus pppd[6766]: Script /usr/sbin/chat -v -e -f /etc/chat/REF_IntPppTmobiCelluLink -r /tmp/REF_IntPppTmobiCelluLink finished (pid 6785), status = 0x4
2019:01:11-14:53:19 cerberus pppd[6766]: Connect script failed
2019:01:11-14:53:20 cerberus pppd[6766]: Exit.
 
 
As you can see above, when it does the ATD*99#^M^M connect string it gets a NO CARRIER status.
 
Thinking this may be something wrong with the device I removed it and plugged it into a laptop and verified it was working corectly. I the placed it back and tried to follow a couple of different messages and knowledge base entires but to no avail. Has anyone been able to get one of these cards working on T-Mobile? Any sort of guidance would be appreciated. Some of th things I have tried already:
 
1. Power cycled the entire system with the Aircard attached.
2. Change the connect string according to some notes (to be honest I dont' remeber the setting off hand, sorry, it's been a long couple of days).
3. On the off chance it was a antenna issue, purcahsed and connected an external 8dbi antennna and connected it. Still getting a NO CARRIER error.
 
Any thoughts and/or reccomendations for a course of action would be apprecaited. Also, if you have a working cell failover on T-Mobile, I'd love to know what you used.
 
Thanks in advance.


This thread was automatically locked due to age.
Parents Reply Children
  • Hi Rudolf and welcome to the UTM Community!

    You might try a Google on site:community.sophos.com/products/unified-threat-management/f "Sierra Wireless Aircard"

    I bet that card's not supported.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • I had been searching through the community info and did find it listed on the modem compatibility list as "Possible" so that would seem that is the best compatibility status I could hope for.

    I have since moved to the XG firewall and now have another issue, but that is for another forum. :D