Configuring CDMA/EVDO with ConnectPort X2e SE (Smart Energy) Cellular Gateways
Configuration with CDMA/EVDO Networks
Mobile device provisioning is required to properly configure your ConnectPort X2e SE Cellular device with the required information used to access the cellular network. Typically, an automatic provisioning process is used to provision the device. For Verizon, that process is OTASP (Over the Air Service Programming). For Sprint, the process is OMA DM (Open Mobile Alliance Device Management. This automatic provisioning requires the cellular modem in the ConnectPort X2e SE Cellular device to communicate over the cellular network, and requires a good cellular signal.
- Your ConnectPort X2e has a unique ID called an MEID, located on the product label on the bottom of the device. Write down the MEID.
- Obtain an account with your cellular carrier. Give the carrier account representative the MEID of the device. The representative will create an account for the ConnectPort X2e SE Cellular device based on the MEID.
- Power on the device.
- Navigate to the web interface by pressing the button on the gateway face plate. You have about 10 seconds from the time you press the reset button to open the web interface, after which it becomes inaccessible again.
- If the provisioning process is successful, the ConnectPort X2e SE Cellular device connects to the cellular network. The Mobile Status fields will change to reflect the connectivity status. Look for these fields: Provisioning status: Provisioned and Connection state: Connected as in the example Mobile Status page below.
If the device does not connect to the network, you do not see SIM Pin State on the Mobile Status page, and/or the Connection state field has any other value than Connected, additional setup and troubleshooting is necessary.
Digi SureLink™ is an optional feature that monitors the integrity of an established network
connection. Several settings and tests can be configured to perform a selected test to examine the
functional integrity of the network connection, and take action to recover the connection in the
event that it is lost.
Currently SureLink is supported for cellular communications only. The SureLink feature and its
settings are off by default, and must be enabled and configured.
The Link Integrity Monitoring settings can be configured to perform a selected test to examine
the functional integrity of the network connection, and take action to recover the connection in the
event that it is lost.
Link integrity monitoring settings:
*Enable Link Integrity Monitoring using the test method selected below.
Enables or disables the link integrity monitoring tests. If this setting is enabled, the other Link
Integrity Monitoring settings may be configured and are used to verify the functional
integrity of the mobile connection. The default is off (disabled).
There are several tests available:
– Ping Test
– TCP Connection Test
– DNS Lookup Test
– Device Cloud Connection Test
You can use these tests to demonstrate that two-way communication is working over the
mobile connection. Several tests are provided because different mobile networks or
firewalls may allow or block Internet packets for various services. Select the appropriate
test may be selected according to mobile network constraints and your preferences.
The link integrity tests are performed only while the mobile connection is established. If
the mobile connection is disconnected, the link integrity tests are suspended until the
connection is established again.
For the link integrity tests to provide meaningful results, the remote or target hosts must
be accessible over the mobile connection and not through the LAN interface of the
device (if it has one). That is, the settings should be configured to guarantee that the
mobile connection is actually being tested.
The link integrity test settings may be modified at any time. The changes are used at the
start of the next test interval
Enables or disables the use of “ping” (ICMP) as a test to verify the integrity
of the mobile connection. The test is successful if a valid ping reply is received in
response to the ping request sent. The ping test actually sends up to 30 ping requests, one
per second, to test the link. When a valid reply is received, the test completes
successfully and immediately. If a reply is received for the first request sent, there is no
need to send the other two requests.
Two destination hosts may be configured for this test. If the first host fails to reply to all
three ping requests, the same test is attempted to the second host. If neither host replies
to any of the ping requests sent, the test fails. The primary and secondary addresses may
be either IP addresses or fully qualified domain names.
– Primary Address: First host to test.
– Secondary Address: Second host to test (if the first host fails)
*TCP Connection Test:
Enables or disables the creation of a new TCP connection as a
test to verify the integrity of the mobile connection. The test is successful if a TCP
connection is established to a specified remote host and port number. If the remote host
actively refuses the connection request, the test is considered a failure. The TCP
connection test waits up to 30 seconds for the connection to be established or refused.
When the TCP connection is established, the test completes successfully, and the TCP
connection is closed immediately.
Two destination hosts may be configured for this test. If the first host fails to establish
(or refuse) the TCP connection, the same test is attempted to the second host. If neither
host successfully establishes (or refuses) the TCP connection, the test fails. The primary
and secondary addresses may be either IP addresses or fully qualified domain names.
– TCP Port: The TCP port number to connect to on the remote host. The default is 80.
*DNS Lookup Test:
Enables or disables the use of a Domain Name Server (DNS) lookup as a
test to verify the integrity of the mobile connection. The test is successful if a valid
reply is received from a DNS server. Typically, this means the hostname is successfully
“resolved” to an IP address by a DNS server. But even a reply such as “not found” or
“name does not exist” is acceptable as a successful test result, since that demonstrates
successful two-way communication over the mobile connection. When a valid reply is
received, the test completes successfully and immediately.
The DNS servers used in this test for the hostname lookup, are the primary and
secondary DNS servers obtained from the mobile network when the mobile PPP
connection is first established. These addresses can be viewed on the
Administration > Mobile Status page.
*Device Cloud Connection Test:
Enables or disables verification of the Device Cloud connection. The
test is successful if a connection can be established to the configured Digi Device Cloud by Etherios
server, and if keep-alive messages can be exchanged with the server. The test fails if a connection
cannot be established, the connection is closed, or if keep-alive messages stop. The
Device Cloud server is configured on the Configuration - Device Cloud Connectivity page.
*Repeat the selected link integrity test every N seconds:
Specifies the interval, in seconds, at which the selected test is initiated (repeated). A new test will be started every N seconds while the mobile connection is established. This value must be between 10
and 65535. The default is 240. This setting is used by Ping, TCP Connection, and DNS
Lookup tests only, not Device Cloud Connection.
If the configured interval is less time than it takes a test to complete, the next test will
not be initiated until the previous (current) test has completed.
*Test only when idle if no data is received for the above period of time:
Specifies that the test repeat interval (above) is to be used as an idle period interval. That is, initiate the selected link integrity test only after no data has been received for the specified interval
of time. This changes the behavior of the test in that the test interval varies according to
the presence of other data received from the mobile connection. This setting is used by
Ping, TCP Connection, and DNS Lookup tests only, not Device Cloud Connection.
Although using this idle option may result in less data being exchanged over the mobile
connection, it also prevents the link integrity tests from running as often to verify the
true bi-directional state of that connection.
*Reset or Reconnect the link after the following number of consecutive link integrity
Specifies that after the configured number of consecutive link integrity test
failures, the mobile connection should be either reset or reconnected:
– Reset: The cellular modem is reset.
– Reconnect: The mobile interface is reconnected.
This value must be between 1 and 255. The default is 3. When the mobile connection is
reestablished, the “consecutive failures” counter is reset to zero.
If the mobile connection is disconnected for any reason (including not as a result of a
link integrity test failure), the consecutive failures count is reset to zero when the mobile
connection is reestablished.
*Primary Test Hostname:
Secondary Test Hostname:
These settings apply to Ping, TCP Connection, and DNS Lookup tests only. Two
hostnames may be configured for the link integrity monitoring test. Hostnames can be
specified in the form of domain names or IP addresses. If the first hostname fails to get a
reply, the same test is attempted for the second hostname. If no reply is received for
either hostname, the test fails. The primary and secondary DNS names should be fully
qualified domain names. Note that the reverse lookup of an IP address is possible, but
that is usually unlikely to succeed in returning a name. Still, such a reverse lookup can
be used to demonstrate the integrity of the mobile connection.
– Primary Test Hostname: The first hostname to look up.
– Secondary Test Hostname: The second hostname to look up (if the first hostname
|Color and blink pattern||Ethernet||Wi-Fi||Cellular|
|OFF||No Ethernet detected.||No Wi-Fi AP or Ad-Hoc networks detected.||No cellular network detected.|
|Blinking yellow, slow||Ethernet interface identified; waiting for link.||Wi-Fi AP or Ad-Hoc network detected. Connecting to Wi-Fi. Waiting for association.||Cellular network(s) detected. Registering on cellular network.|
|Blinking yellow, fast||Connected to Ethernet. Establishing LAN connection. Waiting for IP address.||Connected to Wi-Fi. Establishing LAN connection. Waiting for IP address.||Registered on cellular network. Establishing WAN connection. Waiting for IP address.|
|Solid yellow||An IP address has been assigned to the gateway. Connected to LAN. Waiting for Device Cloud service to take control, and for DNS resolution of server chosen by Device Cloud.||An IP address has been assigned to the gateway. Connected to LAN. Waiting for Device Cloud service to take control, and for DNS resolution of server chosen by Device Cloud.||An IP address has been assigned to the gateway. Connected to WAN. Waiting for Device Cloud service to take control, and for DNS resolution of server chosen by Device Cloud.|
|Alternating between yellow and green||
The gateway cannot connect to Device Cloud. The two most common reasons for this state are:
|Blinking green, slow||Verifying Internet connection. Waiting for network connection to the chosen server.|
|Blinking green, fast||Connected to Internet. Establishing Device Cloud connection. Waiting for protocol level “connection” with Device Cloud server, which might include authentication.|
|Solid green||Gateway is connected to Device Cloud server.
Following are some key provisioning-related fields on the Mobile Status page.
Mobile Status field Description SIM PIN status
GSM Indicates whether a PIN needs to be entered to unlock the SIM card. There area many possible status values; some common ones are:
- READY: SIM is ready. PIN has been entered or no PIN is needed.
- SIM PIN: PIN is required to unlock the SIM. It can be entered on the Mobile Configuration page.
- SIM PUK, SIM PIN2, SIM PUK2, and similar codes: SIM is locked and cannot be unlocked by the ConnectPort X2e SE Cellular device. It must be placed in another device or phone to be unlocked.
- Error: SIM not inserted or other SIM problem.
SIM slot index
Displayed for products that support multiple SIMs only. Indicates which SIM slot is currently in use by the device. 0 means the first slot, 1 means the second slot.
Received cellular signal strength indicator (RSSI). A measure of the signal level of the network.
For GSM, a signal strength of -108 or more is equivalent to 1 bar, -93 to 2 bars, and -77 to 3 bars.
An indicator of the received cellular signal, in bars.
0: No signal
1: Poor signal
2: Adequate signal
3: Good signal
Signal quality An indicator of the quality of the received cellular signal, measured in dB.This value is also known as Ec/Io. Registration status The status of the cellular modem’s connection to a cellular network.
- Not registered
- Registered (Home network)
- Searching for Network
- Not Registered (Access Denied)
- Not Available (Reason not Known)
- Registered (Roaming)
Mobile country code /
Mobile network code
These codes are used to uniquely identify a mobile phone operator/carrier with which the cellular modem is registered. For example, for AT&T, these codes would be 310 and 410. Connection state The operating state of the cellular modem:
- Initializing: Modem is being reset and configured
- Registering: Modem is searching for a network
- Delay before connecting: Modem is delaying after an unsuccessful connection (Verizon only)
- Connecting: Mobile data connection is being established
- Connected: Mobile data connection is active
- Disconnecting: Mobile data connection is ending
- Disconnected: Mobile data connection has ended. See Disconnect reason for the cause.
- Disabled: Mobile data connection is not enabled by configuration settings.
- No device found: Modem is not available or is malfunctioning.
Displayed after a connection error occurs only. Indicates the reason the previous connection attempt failed:
- SIM PIN required: The SIM PIN must be entered on the Mobile Configuration page.
- SIM PIN incorrect: The SIM PIN entered does not match the actual one for the SIM.
- SIM not ready: No SIM inserted or other SIM problem.
- Not registered: Modem did not register with a cellular network.
- Dial failed: Error starting data connection.
- Authentication failed: Incorrect login or password entered on the Mobile Configuration page.
- Connection timeout: Connection did not complete.
- Device reset error: Modem could not be reset.
- Device open error: Modem is malfunctioning.
- Device config error: Modem could not be configured.
- PPP error: Internal system error
Disconnect reason Displayed after a previous connection was ended. Indicates the reason the previous connection was ended:
- User requested: Initiated by user action.
- Network disconnect: Initiated by cellular network or carrier.
- Carrier loss: Poor signal or disconnected by network.
- Connection timer: Connection did not complete.
- Receive idle timer: No data received for configured receive idle time.
- Device monitoring error: Error while monitoring the modem status. May indicate a malfunctioning modem.
IP address Internet protocol address of the mobile data interface. The device may be contacted at this IP address if permitted by the carrier. DNS primary address
IP address of the primary Domain Name System (DNS) server assigned by the mobile carrier. This server resolves domain names to IP addresses. For more information on how the ConnectPort X2e ZB device uses this value and DNS secondary address, go here.
DNS secondary address IP address of the backup DNS server assigned by the mobile carrier.