Home > Support > Knowledge Base
Knowledge Base
 
Reset Search
Search
 

 

Knowledge

How to Set Up a TransPort with a Gobi 2000/3000 for use with Sprint

« Go Back

Information

 
Article Number000001272
Problem Resolution
Gobi 2000/3000 Sprint Provisioning
Overview
This document is intended for Gobi Transport units over the Sprint network.  The purpose is to quickly walk you through running the Gobi Carrier Wizard, how to provision the device for Sprint networks.  It also highlights items to look at and how to test the unit. 
 
Assumptions
This guide assumes that you have a PC that is able to reach the TransPort through the Ethernet interface to gain access to the WebUI for configuration purposes.
 
Information You Might Need
If possible, please try to gather the following information from Sprint as it might be necessary for possible issues:
MSL – Master Subsidiary Lock is required to allow the PTN and the MSID to be programmed
PTN – The phone number, which should contain 10 digits
MSID – The Mobile Station Identity or MIN, again 10 digits
 
Running the Gobi Carrier Wizard
The first thing that will need to do be done is run the Gobi Carrier Wizard to enable the device for Sprint. The following steps will guide you through this process:
 
1) Log into the WebUI through the Ethernet interface. (Default IP address is 192.168.1.1)
 
2) Once in the WebUI, click on Wizards on the upper-left hand side, as shown in the screenshot below:
User-added image

3) Click on the GOBI Carrier Wizard, and then click Next, as shown in the screenshot below:
User-added image
4) Choose Sprint, and click Next, as shown below:
User-added image

5) On the next page, you will see a line that says “Save configuration changes here”, with the “here” being blue in color and underlined. Click the ‘here’ link and then click Save on the next screen. Reboot the device after saving.
 
6) After the device reboots, log back into the WebUI.
 
7) Navigate to Configuration > Network > Interfaces > Mobile > CDMA Provisioning.
 
8) Under the section titled Automatic Provisioning, click the Start button. DO NOT fill in any of the 3 parameters unless told to by Digi.  DO NOT fill out anything under Manual Provisioning.  
User-added image

9) This process will take ~2 minutes to complete. Once the process completes, a message at the top of the page will indicate if it has either been successful or failed to provision. If successful, click the Reboot link and reboot the device.  If failed, try provisioning again.  Please email Digi Technical Support with the debug.txt file (please see “When contacting Digi Technical Support” below) if the failure continues. 
 
Once the unit is provisioned, it could take another minute or so before it establishes an IP address.
 

Indicators, WebUI
 
LED Displays
 
For the WR41 & WR44
W-WAN NET
Will illuminate steady if the unit is able to log on to the Sprint mobile network.

W-WAN SIM
This LED should not light up since you do not a SIM for a Sprint account.

W-WAN DAT
Represents data passing to and from the network.

Signal Strength
Here is a guide for the signal strength:
  • -113 dBm or less (0 LED) -> effectively no signal
  • -112 dBm to –87 dBm (1 LED) -> weak signal
  • -86 dBm to –71 dBm (2 LEDs) -> medium strength signal
  • -70 dBm or greater (3 LEDs) -> strong signal
The minimum recommended strength indication is 2 LEDs. If you have no or 1 LEDs lit, it is recommended that you fit an external antenna to the unit.
 
For the WR21
Service
Illuminates steady when there is a network connection to the WWAN interface and flashes when data is transmitted or received.

WWAN
Flashes to show which network mode the unit is operating in:
Off - no service
1 blink - GPRS mode
2 blinks - EDGE mode
3 blinks - UMTS mode
4 blinks - HSDPA mode
5 blinks - HSUPA mode
On steady - CDMA mode

Strength
Here is a guide for the signal strength:
  • -113 dBm or less (0 LED) -> effectively no signal
  • -112 dBm to –87 dBm (1 LED) -> weak signal
  • -86 dBm to –71 dBm (2 LEDs) -> medium strength signal
  • -70 dBm or greater (3 LEDs) -> strong signal
The minimum recommended strength indication is 2 LEDs. If you have no or 1 LEDs lit, it is recommended that you fit an external antenna to the unit.

 

WebUI
 
Locating the Mobile IP Address
On the Home page, you should see the Mobile IP address under PPP1 (W-WAN (CDMA)).

 NOTE: If you get an IP address of 120.x.x.x, this is a false mobile IP address.  Please see the Troubleshooting section of this document.
 User-added image

Under Management > Network Status > Interfaces > Mobile
 User-added image 
 
NOTE:  Use the above screenshot as a reference for the below information.
 
Mobile Connection  
 
Registration Status
This is the registration status of the mobile module with respect to the cellular network.
Ideally, it will show up as registered.

Signal Strength
The signal strength in dBm being received by the mobile module.
Here is a guide for the signal strength:
  • -113 dBm or less (0 LED) -> effectively no signal
  • -112 dBm to –87 dBm (1 LED) -> weak signal
  • -86 dBm to –71 dBm (2 LEDs) -> medium strength signal
  • -70 dBm or greater (3 LEDs) -> strong signal
The minimum recommended strength indication is 2 LEDs. If you have no or 1 LEDs lit, it is recommended that you fit a high-gain external antenna to the unit.
 
 Mobile Statistics
 IP Address
The IP address of the mobile interface.

Primary DNS Address / Secondary DNS Address
The primary and secondary DNS addresses used by the mobile interface

Data Received
The number of data bytes that have been received on the mobile interface whilst it has been connected.

Data Sent
The number of data bytes that have been sent on the mobile interface whilst it has been connected.   
 
Mobile Information  
Current system ID
The current system ID reported by the mobile module.

Current network ID
The current network ID reported by the mobile module.

Network
The current network reported by the mobile module.

Signal strength 1xRTT
The signal strength in dBm being received by the mobile module from 1xRTT networks.

Signal strength EVDO
The signal strength in dBm being received by the mobile module from EVDO networks.

Manufacturer
The manufacturer of the mobile module.  For a Gobi module, you should see either Huawei Incorporated or Qualcomm Incorporated.

Model
The model of the mobile module.  Examples for the Gobi would be Huawei EM680, Qualcomm Gobi 2000, Qualcomm Gobi 3000.

MDN
The Mobile Directory Number (MDN) of the mobile module.

MIN
The Mobile Identification Number (MIN) of the mobile module.

ESN
The Electronic Serial Number (ESN) of the mobile module.

MEID
The Mobile Equipment Identifier (MEID) of the mobile module.

Firmware
The firmware running on mobile module.

Bootcode
The bootcode firmware running on the mobile module.

Hardware version
The hardware version of the mobile module.

Registration State
See Registration Status.

Roaming status
The current roaming status of the mobile module.

Service capabilities
EVDO, CDMA 1x, or both

Radio band
1900 MHz for Sprint. 

Channel
The transmission channel in use.  25 for Sprint.

Preferred system
Specifies what you configured it for: CDMA, EVDO, or Auto.  You can set this under Configuration > Network > Interfaces > Mobile > Advanced.

PRL version
The version of the Preferred Roaming List (PRL) loaded on the mobile module.

Activation status
The activation state of the mobile module. It can be of the following:
  • 0 – Not activated
  • 1 – Activated
 Raising and Lowering the Cellular Link
Under Management > Connections > PPP Connections > PPP 1 – W-WAN, you should see the Mobile IP Address, the Primary and Secondary DNS Address, as well as buttons to Drop or Raise the link.
NOTE: If you get an IP address of 120.x.x.x, this is a false mobile IP address.  Please see the Troubleshooting section of this document.  
 User-added image
 
 Locating the Event Log
 
Under Management > Event Log
This page displays the current contents of the event log on the router.  This log records events throughout the Digi device’s system including cellular information.  Some of this cellular information you might see would be status codes, error codes, signal strengths, tower locations, & service available.
Note: The newest information is on top of this file.
 
 
Testing
Once you have set up the mobile settings on your unit and you see a mobile IP address, there are a couple of quick tests you can do to ensure your device is working.
 
Ping test
 
Unfortunately, you cannot do a ping test on the Sprint Network.  Sprint blocks this port (please see Sprint EVDO Blocked Ports under Troubleshooting, below).
 
Accessing the Internet
 
If you have a laptop or computer directly connected to your Transport, you can try opening a browser and accessing the Internet (for example ‘http://www.digi.com’).
 
NOTE: In order for this step to be a valid test, you must ensure you do not have another source to the Internet, such as being connected to your company’s network either via Ethernet or over Wi-Fi.
 
If this fails, please email Digi Technical Support with the debug.txt file (please see “When contacting Digi Technical Support” below).
 
Access the Transport Remotely
 
With Sprint as a cellular provider, they block certain ports.  A complete list of these blocked ports may be found in the Troubleshooting section below.  One of those ports is port 80, which is HTTP, which is the protocol normally used to access the Internet. With Sprint blocking this port, a user will no longer be able to remote into the Transport by simply entering the address (i.e. http://x.x.x.x where the x’s are representing the mobile IP address of the Transport).  Locally, the user will still have access to it using the local IP address.
 
In order to resolve the issue of getting into the Transport using the mobile IP address, there are two methods. 
  1. With the Transport, there are two services for entering the Web GUI, HTTP or HTTPS.  Sprint blocks port 80, which is HTTP, but they do not block port 443, which is HTTPS.  To change to HTTPS, go to Configuration > Network > Network Services, then click the “Enable Secure Web Server” button.  You will then click the Apply button and then the Save.  Then click the Save All button.  Note that you will lose your connection.  At this point, in order to access either remotely or locally, you will need to specify “https” (i.e. https://x.x.x.x where the x’s are representing your local or remote address of the Transport).
  2. The HTTP service, in the Transport, besides the normal port 80, also accepts port 8080.  This means that you can keep the default settings and then enter the unit remotely specifying port 8080 (i.e. http://x.x.x.x:8080 where the x’s are representing the mobile IP address of the transport).  Note that locally you may still enter the WebUI of the Transport as you normally would (http://x.x.x.x where the x’s are representing the local IP address of the Transport).  To change to HTTP (which is the default setting), go to Configuration > Network > Network Services, then click the “Enable Web Server” button.  You will then click the Apply button and then the Save.  Then click the Save All button. 
 
If you have a mobile terminated account, you should be able to access the Transport remotely.  Find a laptop or PC that has Internet access (outside of the Transport), open a browser, and specify, using https, the mobile IP address of the Transport (i.e. https://166.55.x.x).
 
If this fails, please verify that you have Web Server enabled (Configuration > Network > Network Services).  Having IP Forwarding (Configuration > Network > IP Routing/Forwarding > IP Port Forwarding/Static NAT Mapping) or IP Passthrough (Configuration > Network > IP Passthrough) enabled could affect these results as well.  Otherwise, if you cannot access your Transport remotely, the issue could be that you have a mobile originated account or a private account.  You should check this with your provider.
 
Mobile Originated vs. Mobile Terminated
 
Mobile Origination – Allows for outbound data to pass through the Digi and receive responses from the data request, but it does not allow for data originating from the Internet to pass through the Digi or to devices beyond it.
 
Mobile Termination – Allows for 2-way communication of data, where data from the Internet can reach the Digi and beyond, and data from the Digi can go to the Internet.
 
 
Troubleshooting
Ensure you are on the latest firmware
Updating your firmware may resolve your issue as well as enhancements to both your Transport and traces for troubleshooting.
  1. To check your firmware, go to Administration > System Information and note your Firmware Version
  2. Compare the firmware version to our latest release by going to www.digi.com > Support > Firmware Updates.
  3. Enter your Transport Model (i.e. WR21) in the field and then click on your particular model.
  4. It should bring you to a page for your product.  Choose the fimrware for the type of upgrade you will performing, either via FTP (WebUI) or FlashWriter, from the options on the page and save the file to your PC.
  5. Please follow “TransPort Firmware Upgrade Instructions” that is available under the General Firmware page listed above.
 
False Mobile IP Address Sprint units
120.x.x.x – If you see an IP address in the 120.x.x.x network for your mobile IP address, you should note that this is a false IP address.  Please attempt to re-provision your Transport.  If you still receive a false IP address, please provide the debug.txt file to Tech Support (please see “When contacting Digi Technical Support” below).  You may also need to contact Sprint, as well. 
 

Sprint EVDO Blocked Ports
80/tcp filtered http
113/tcp filtered auth
135/tcp filtered msrpc
137/tcp filtered netbios-ns
138/tcp filtered netbios-dgm
139/tcp filtered netbios-ssn
445/tcp filtered microsoft-ds
559/tcp filtered teedtap
901/tcp filtered samba-swat
1022/tcp filtered unknown
1023/tcp filtered netvenuechat
1025/tcp filtered NFS-or-IIS
1433/tcp filtered ms-sql-s
3128/tcp filtered squid-http
3306/tcp filtered mysql
4000/tcp filtered remoteanything
4899/tcp filtered radmin
5000/tcp filtered UPnP
17300/tcp filtered kuang2
27374/tcp filtered subseven
 
When contacting Digi Technical Support
 
To contact Digi Technical Support, please call 952-912-3456 or email tech.support@digi.com.  If you already have a Tech Support case number, please reference this number when contacting Support.
 
Please provide the debug.txt file.  You can gather this either via FTP or the WebUI by going to Administration - File Management > FLASH Directory, right-click on debug.txt and select Save Target As (or whatever term your browser uses).  For more details see http://ftp1.digi.com/support/documentation/QN_024_Extracting%20the%20debug.txt%20file%20from%20a%20Digi%20TransPort%20or%20Sarian%20router.pdf.

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255