RMS API /device endpoint not returning `mobile_ip`

Networking Solutions Issue
1

I am wondering why the RMS API does not return the LTE/mobile IP in the JSON payload for the /devices/{id} endpoint ?

The wan_ip is returned correctly, but the wwan/qmimux IP is not in the API responses.

The field is there, but it’s empty:

// partially redacted response
[
  {
    ...
    "status": 1,
    "is_authenticated": 1,
    "signal": -64,
    "bootloader_version": "3.0",
    "cell_id": "20384278",
    "connection_type": "4G+ (LTE-A)",
    "connection_state": "Connected",
    "iccid": "891480000076xxxxxxxx",
    "lac": "N/A",
    "mcc": "311",
    "mnc": "480",
    "sim_slot": 1,
    "sim_state": "Inserted",
    "operator": "US Mobile",
    "operator_number": "311480",
    "router_uptime": 23535630,
    "wan_state": "wired",
    "wan_ip": "100.2.165.13/24",
    "wan_proto": "dhcp",
    "mobile_ip": "\"\"",       <== e.g.
    "network_state": "Home",
    "network_state_2": null,
    "sent": 1536753668,
    ...

But ifconfig qmimux0 clearly shows an IP:

image
image1620×364 48.8 KB

3

Greetings, @luckman212 ,

Apologies for a delayed response,

Thank you for sharing your observations, I have forwarded this information to our RMS R&D team for further investigation.

Also, could you please clarify if the issue is persistent across multiple devices on your fleet or any specific one? Model(s) and firmware version(s) would be helpful as well.

Thank you for your cooperation and I will update you as soon as I have more information from our RMS R&D team.

All the best,
V.

4

Hello,

I have an update from our RMS team.

They have confirmed that this is a known issue and that a fix is planned for the upcoming RMS 5.27 release. At this time, however, I do not have an estimated release date (ETA) to share.

I will keep you informed if any additional information or timeline becomes available.

Thank you for your patience and understanding.

Kind regards,
V.