RV50x Connection Issues with native Verizon Profile using Alternate APN

AirLink Routers
1

Hello,

I’ve been testing my LX60 and RV50x routers with some Hologram SGP.02 eSIMs. The LX60 is working fine, but the RV50x - running the latest firmware - is having some problems.

The eSIM has both a native Verizon profile - that uses the “hologram” APN - and a Hologram G3 Roaming profile - that uses the same “hologram” APN. Again, the LX60 is working fine with both profiles.

On my RV50x, when using the G3 Roaming profile, the router switches to the Generic radio firmware and connects and works fine. When I switch to the Verizon profile, the router switches to the Verizon radio firmware and fails to open a data session.

Looking at the router status, and the Admin Logs, the router is registering on the tower just fine, and is reporting “Service”, but then fails when trying to create the data session. I can see it attempt the “vzwinternet” APN, and then attempt the “hologram” APN, but both fail. The same SIM in the LX60 works just fine.,

I’m trying to understand the various configuration settings in the RV50x in the latest v4.18.2 firmware that might be impacting the connection. I’m not able to find a way to issue AT Commands to the router modem to retrieve the PDP Contexts (AT+CGDCONT?) or to further dig into what might be going wrong.

I can provide logs or more information … can you provide some guidance on direction and next steps for debugging? This is related to a customer opportunity that is hundreds of potential routers.

Thank you … I look forward to your reply!

2

Can you provide the logs? here or to your Sierra Wireless distributor. I think Support will need to see the logs to view the call flow.

In the generic radio firmware profile, there is no IMS registration. I do not know yet if this is causing a problem.

IMS is the Verizon service under which they provide SMS messages. I have seen Verizon connections work though without IMS registration in place or successful.

I do not think there is a setting in the RV50x that you can change to influence this. But I think we are early in the support process.

3

Scott, one more thing, Sierra Wireless Support provided the logging instructions in another ticket last week,

To collect, the procedure is,

Go AceManager > Admin > Configure Logging

Set all log levels to DEFAULT

Set Linux Syslog to DISPLAY

Reboot the gateway

Perform your test again.

Go Admin → View log → Download Logs

4

Hello,

Thank you for the reply. Yes, I’m familiar with the “interesting” Verizon requirements. I thought I would try the Generic firmware as a test, but when using that it was not even allowed to register on the Verizon tower. (“Limited Service”) :frowning:

When I switched back to the Verizon radio firmware, I can see Verizon allowing the registration, and the logs show it sending “Service”, and then the failure to create the data session. I used AI for some suggestions on troubleshooting, and it provides some things to try, but no success on any of them. I’m just not familiar enough with the nuances of the RV50x and it’s web configuration.

I’m attaching my configuration template, and the latest log from the latest reboot. Hopefully someone might see something that gives a clue on what could be failing.

:face_with_raised_eyebrow: I’m actually NOT uploading the logs yet … I’m being told that “New Users cannot upload files!”

5

Hello @Donald or @jerdung ,

I noticed that you appear to be “Leaders” here … can I get upgraded somehow to be able to upload my logs for review?

6

Scott, I understand. Yes, @jerdung should respond and fix that. You are welcome to my email address, blackbow7@yahoo.com. I will review the logs and respond.

That generic test provides some good clues to review.

I researched the RV50x and LX60 today to refresh my memory. The 4G module inside is different. That could be a contributing factor to the behavior.

7

Well … I was just upgraded and am now able to upload files! Here is my log and configuration template!

20260712_163528_filteredlogs.txt (114.6 KB)

VerizonTest-Hologram.xml.txt (119.2 KB)

8

great! Yes, I have the logs. I am going to start reviewing now. Might reply tonight but tomorrow for sure

9

I see the connection errors for both APNs. Sample below. I am going to study this more tonight.

Jul 12 16:30:50 debug ALEOS_CELL_RadioTask: New Event received: RADIO_EVENT_CONNECT
Jul 12 16:30:50 notice ALEOS_CELL_RadioTask: Radio_state → RADIO_STATE_CONNECT
Jul 12 16:30:50 notice ALEOS_CELL_RadioTask: IPPreference : IPv4
Jul 12 16:30:50 debug SWI0 SDK Process: psrwds_setipfamily: instance: 0 IP family: V4 Active WDS Client: V4
Jul 12 16:30:50 debug SWI0 SDK Process: psrwds_starnet:
Jul 12 16:30:51 debug ALEOS_CELL_RadioTask: iSLQSStartStopDataSession/2975: WDS start interface verbose error: 1037
Jul 12 16:30:52 err ALEOS_CELL_RadioTask: Unable to establish data session, return value: 1014failurereason: 1, line: 732
Jul 12 16:30:52 notice ALEOS_CELL_RadioTask: Verbose call end type: 3, verbose call end code: 1037

10

Hi @scott.lemon,
Welcome to our community!

Based on the log below, it appears that when the APN is set to “vzwinternet”, the device registered on the network. Then it could not start data session because the requested service option is not included in the current subscription (error code: 33)

Jul 12 16:30:30 notice ALEOS_CELL_RadioTask: APN Selection: Primary APN: ‘vzwinternet’ (User Entered)
Jul 12 16:30:30 debug ALEOS_CELL_RadioTask: Authentication :1
Jul 12 16:30:30 debug ALEOS_CELL_RadioTask: Username :
Jul 12 16:30:30 notice ALEOS_CELL_RadioTask: Set APNName, PDN type and credentials in Profile: APN ‘vzwinternet’ and PDN type ‘0’ with auth 1 (PAP) , username ‘’
Jul 12 16:30:30 notice ALEOS_CELL_RadioTask: Updating ODIS information on Radio
Jul 12 16:30:30 debug ALEOS_CELL_RadioTask: Host Manufacturer: Sierra Wireless Host Model: RV50X Host Software Version: 4.18.2 Host Plasma ID: Host ID:
Jul 12 16:30:30 info ALEOS_CELL_RadioTask: Available Radio Bands [00,ALL BANDS;01,EUROPE 3G;02,NORTH AMERICA 3G;06,EUROPE;07,NORTH AMERICA;08,WCDMA ALL;09,LTE ALL;]
Jul 12 16:30:30 debug ALEOS_CELL_RadioTask: Checking lock/unlock timer…
Jul 12 16:30:30 debug ALEOS_CELL_RadioTask: current uptime : 45
Jul 12 16:30:30 debug ALEOS_CELL_RadioTask: Updating /tmp/lastLockUptime…
Jul 12 16:30:30 notice ALEOS_CELL_RadioTask: Customer has selected ALL BANDS
Jul 12 16:30:30 info ALEOS_CELL_RadioTask: Available Profile Bands: ALL BANDS: 1, 2, 3, 4, 5, 8, 13
Jul 12 16:30:30 info ALEOS_CELL_RadioTask: Custom Bands Mode 0
Jul 12 16:30:30 debug ALEOS_CELL_RadioTask: Emergency Mode: 0x
Jul 12 16:30:30 debug ALEOS_CELL_RadioTask: Mode Preference: 0x24
Jul 12 16:30:30 debug ALEOS_CELL_RadioTask: GW Band Preference: 0x562950083444736
Jul 12 16:30:30 debug ALEOS_CELL_RadioTask: CDMA PRL Preference : 0x65535
Jul 12 16:30:30 debug ALEOS_CELL_RadioTask: Roaming Preference : 0x255
Jul 12 16:30:30 debug ALEOS_CELL_RadioTask: LTE Band Preference : 0x4122
Jul 12 16:30:30 debug ALEOS_CELL_RadioTask: Network Selection Preference: 0x
Jul 12 16:30:30 debug ALEOS_CELL_RadioTask: Service Domain Preference : 0x2
Jul 12 16:30:30 debug ALEOS_CELL_RadioTask: GSM - WCDMA Acquisition Order Preference : 0x0
Jul 12 16:30:30 notice ALEOS_CELL_RadioTask: Current band setting: ALL BANDS
Jul 12 16:30:30 debug ALEOS_CELL_RadioTask: Releasing radio access (PID: 1273)…
Jul 12 16:30:30 debug ALEOS_CELL_MultiSIM: syncActiveMsciid: New: 11202, global: 11202, sim1: 10713, sim2: 10753 esim: 10679
Jul 12 16:30:30 debug ALEOS_CELL_MultiSIM: syncActiveMsciid: Update active Sim configuration. Current value APN Not Found - New Value vzwinternet
Jul 12 16:30:30 debug ALEOS_CELL_MultiSIM: syncActiveMsciid: MSCIID to Update = 10713
Jul 12 16:30:30 debug ALEOS_CELL_RadioTask: New Event received: RADIO_EVENT_CARRIER_SELECTION
Jul 12 16:30:30 debug ALEOS_CELL_MultiSIM: syncActiveMsciid: New: 10753, global: 11202, sim1: 10713, sim2: 10753 esim: 10679
Jul 12 16:30:30 notice ALEOS_CELL_RadioTask: Radio_state → RADIO_STATE_CARRIER_SELECTION
Jul 12 16:30:30 debug ALEOS_CELL_MultiSIM: syncActiveMsciid: Non active SIM configuration update. Nothing to do
Jul 12 16:30:30 notice ALEOS_CELL_RadioTask: Setting COPS mode start
Jul 12 16:30:30 notice ALEOS_CELL_RadioTask: Current COPS user setting: 0
Jul 12 16:30:30 debug ALEOS_CELL_MultiSIM: syncActiveMsciid: New: 10713, global: 11202, sim1: 10713, sim2: 10753 esim: 10679
Jul 12 16:30:30 debug ALEOS_CELL_MultiSIM: syncActiveMsciid: Global MSCIID already in sync
Jul 12 16:30:30 notice ALEOS_CELL_RadioTask: sending [AT+COPS=3,2]
Jul 12 16:30:30 notice ALEOS_CELL_RadioTask: Radio response [AT+COPS=3,2 OK]
Jul 12 16:30:30 notice ALEOS_CELL_RadioTask: sending [AT+COPS?]
Jul 12 16:30:30 alert ALEOS_EVENTS_gnssmgr: GPS disabled, Assisted Data Retrieval always off
Jul 12 16:30:30 notice ALEOS_CELL_detectrmdetach: 9McEmRmHal: radio module = ALEOS_RADIO_MODULE_MC7455 is active
Jul 12 16:30:30 notice ALEOS_CELL_RadioTask: Radio response [AT+COPS? +COPS: 0,2,“311480”,7 OK]
Jul 12 16:30:30 notice ALEOS_CELL_RadioTask: Current COPS mode read from radio: 0
Jul 12 16:30:30 notice ALEOS_CELL_RadioTask: Leaving COPS mode as default: automatic
Jul 12 16:30:30 debug ALEOS_CELL_RadioTask: New Event received: RADIO_EVENT_WAIT_UNTIL_READY
Jul 12 16:30:30 notice ALEOS_CELL_RadioTask: Radio_state → RADIO_STATE_NOTREADY_WAIT
Jul 12 16:30:30 info ALEOS_CELL_RadioTask: Backup APN timeout set to 224
Jul 12 16:30:30 debug ALEOS_CELL_RadioTask: New Event received: RADIO_EVENT_CONNECT
Jul 12 16:30:30 notice ALEOS_CELL_RadioTask: Radio_state → RADIO_STATE_CONNECT
Jul 12 16:30:30 notice ALEOS_CELL_RadioTask: IPPreference : IPv4
Jul 12 16:30:30 debug SWI0 SDK Process: psrwds_setipfamily: instance: 0 IP family: V4 Active WDS Client: V4
Jul 12 16:30:30 debug SWI0 SDK Process: psrwds_starnet:
Jul 12 16:30:30 debug ALEOS_CELL_detectrmdetach: Reserving Radio Access (PID: 1272)…
Jul 12 16:30:30 debug ALEOS_CELL_detectrmdetach: Reserved radio access (PID: 1272)
Jul 12 16:30:30 info ALEOS_CELL_detectrmdetach: Radio is in ATTACHED state
Jul 12 16:30:30 debug ALEOS_CELL_detectrmdetach: Releasing radio access (PID: 1272)…
Jul 12 16:30:30 debug ALEOS_CELL_RadioTask: iSLQSStartStopDataSession/2975: WDS start interface verbose error: 33
Jul 12 16:30:31 err ALEOS_CELL_RadioTask: Unable to establish data session, return value: 1014failurereason: 1018, line: 732
Jul 12 16:30:31 notice ALEOS_CELL_RadioTask: Verbose call end type: 6, verbose call end code: 33
Jul 12 16:30:31 info ALEOS_CELL_RadioTask: AL_startDataSession - attempt: 1, return code: -2
Jul 12 16:30:31 debug ALEOS_CELL_RadioTask: From error (‘33’) - Process to ‘eHourlyRetry’ handling
Jul 12 16:30:31 alert ALEOS_CELL_RadioTask: Carrier requested to not retry opening a data session. Retrying with the backup APN
Jul 12 16:30:31 debug ALEOS_CELL_RadioTask: New Event received: RADIO_EVENT_DISCONNECT
Jul 12 16:30:31 notice ALEOS_CELL_RadioTask: Radio_state → RADIO_STATE_DISCONNECT

Based on the log below, it appears that when the APN is set to “hologram”, the device could not register to the network, then it lead to the data session failed.

Jul 12 16:30:51 debug ALEOS_CELL_RadioTask: iSLQSStartStopDataSession/2975: WDS start interface verbose error: 1037
Jul 12 16:30:52 err ALEOS_CELL_RadioTask: Unable to establish data session, return value: 1014failurereason: 1, line: 732
Jul 12 16:30:52 notice ALEOS_CELL_RadioTask: Verbose call end type: 3, verbose call end code: 1037

Next steps:

  1. Recheck the service subscription with operator for vzwinternet and hologram APNs
  2. Could you please share the pass log from LX60 so I can check it further?

Thanks,

11

Hello @jerdung ,

Thank you for your quick response. Here is the template and log from the LX60. I did notice it is currently running an older version of ALEOS. I could upgrade it if you like.

If you look at the boot process, it came right up and worked. I did notice that although I had provided a backup APN that is the correct “hologram” APN, the LX60 appears to be using a different one - “HOLOGRAM.VZWENTP”? I have no idea where this one came from.

Both SIMs are assigned to the same service plan/subscription with Verizon, so there is no difference there. I’m curious what might be different that it selected that APN? Or am I reading this wrong?

I look forward to your thoughts!

LX60-VerizonTest-Hologram.xml.txt (123.6 KB)

LX60-20260714_144126_filteredlogs.txt (82.8 KB)

12

Scott, the HOLOGRAM.VZWENTP was received over the air from the Verizon LWM2M server as part of the SIM registration process. This APN is provisioned in the network and network database.

13

That is very interesting. During my troubleshooting, I found a post indicating to disable the ALMS LWM2M service. Is that the one being used to do this?

The log was filled with errors trying to reach the defined server.

14

I understand your question. No, this LWM2M service is another LWM2M service inside the 4G LTE module. A service specific to the Verizon required LWM2M service. This service updates the class 3 APN on the module, the Verizon FW settings. The SIM insertion starts a registration process with the network and in response the network queries the class 3 APN and changes it, if necessary.

15

@jerdung, I have a suggestion - when I had this problem in the past, we captured a QXDM type log from the RV50X.

How does Scott get access to the DM logging tool and instructions? me, I think this issue is a tricky one with two different 4G LTE modules in the scenario.

16

Hi @scott.lemon,

Based on the log below, it appears that the LX60 automatically selected the APN “HOLOGRAM.VZWENTP” when the APN was left blank.

Jul 14 14:37:58 notice ALEOS_CELL_RadioTask: OMA DM is supported, no Auto APN lookup of APN is possible
Jul 14 14:37:58 notice ALEOS_CELL_RadioTask: APN Selection: Primary APN: ‘’ (Auto Entered)
Jul 14 14:37:58 debug ALEOS_CELL_RadioTask: Authentication :0
Jul 14 14:37:58 debug ALEOS_CELL_RadioTask: Username :
Jul 14 14:37:58 notice ALEOS_CELL_RadioTask: Using APN from radio module: ‘HOLOGRAM.VZWENTP’

Could you please leave the APN blank and check which APN the RV50X automatically uses? If the issue still occurs, please share the full log with me so I can check it further.

Thanks,

17

Hello,

I want to make sure I understand … so you want me to remove the “hologram” APN from the Back-Up APN value? I’ll do that, but am not sure where else I can remove the APN value.

18

Hello @jerdung ,

I removed the APN and then rebooted. Here are the template and the log:

RV50x-NoAPN-20260712_181139_filteredlogs.txt (99.7 KB)

RV50x-NoAPN-Verizon-Hologram.xml.txt (119.3 KB)

19

Hi @scott.lemon,

As mentioned previously, it appears that when the APN is set to “vzwinternet”, the device registered on the network. Then it could not start data session because the requested service option is not included in the current subscription (error code: 33).
When the APN is set to “hologram”, the device could not register to the network, then it lead to the data session failed.

Based on the log below, it appears that when the APN was left blank, the device registered on the network. Then the data session failed because a PDN was attempted with a NULL APN, which is not supported (error code: 242).
Jul 12 18:07:51 notice ALEOS_CELL_RadioTask: APN Selection: Primary APN: ‘’ (User Entered)
Jul 12 18:07:51 debug ALEOS_CELL_RadioTask: Authentication :0
Jul 12 18:07:51 debug ALEOS_CELL_RadioTask: Username :
Jul 12 18:07:51 notice ALEOS_CELL_RadioTask: Using APN from radio module: ‘’
Jul 12 18:07:51 notice ALEOS_CELL_RadioTask: Updating ODIS information on Radio
Jul 12 18:07:51 debug ALEOS_CELL_RadioTask: Host Manufacturer: Sierra Wireless Host Model: RV50X Host Software Version: 4.18.2 Host Plasma ID: Host ID:
Jul 12 18:07:52 info ALEOS_CELL_RadioTask: Available Radio Bands [00,ALL BANDS;01,EUROPE 3G;02,NORTH AMERICA 3G;06,EUROPE;07,NORTH AMERICA;08,WCDMA ALL;09,LTE ALL;]
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: Checking lock/unlock timer…
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: current uptime : 44
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: Updating /tmp/lastLockUptime…
Jul 12 18:07:52 notice ALEOS_CELL_RadioTask: Customer has selected ALL BANDS
Jul 12 18:07:52 info ALEOS_CELL_RadioTask: Available Profile Bands: ALL BANDS: 1, 2, 3, 4, 5, 8, 13
Jul 12 18:07:52 info ALEOS_CELL_RadioTask: Custom Bands Mode 0
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: Emergency Mode: 0x
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: Mode Preference: 0x24
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: GW Band Preference: 0x562950083444736
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: CDMA PRL Preference : 0x65535
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: Roaming Preference : 0x255
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: LTE Band Preference : 0x4122
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: Network Selection Preference: 0x
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: Service Domain Preference : 0x2
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: GSM - WCDMA Acquisition Order Preference : 0x0
Jul 12 18:07:52 notice ALEOS_CELL_RadioTask: Current band setting: ALL BANDS
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: Releasing radio access (PID: 1269)…
Jul 12 18:07:52 debug ALEOS_CELL_MultiSIM: syncActiveMsciid: New: 11202, global: 11202, sim1: 10713, sim2: 10753 esim: 10679
Jul 12 18:07:52 debug ALEOS_CELL_MultiSIM: syncActiveMsciid: Update active Sim configuration. Current value APN Not Found - New Value APN Unknown - Chosen by Network
Jul 12 18:07:52 debug ALEOS_CELL_MultiSIM: syncActiveMsciid: MSCIID to Update = 10713
Jul 12 18:07:52 debug ALEOS_CELL_MultiSIM: syncActiveMsciid: New: 10753, global: 11202, sim1: 10713, sim2: 10753 esim: 10679
Jul 12 18:07:52 debug ALEOS_CELL_MultiSIM: syncActiveMsciid: Non active SIM configuration update. Nothing to do
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: New Event received: RADIO_EVENT_CARRIER_SELECTION
Jul 12 18:07:52 notice ALEOS_CELL_RadioTask: Radio_state → RADIO_STATE_CARRIER_SELECTION
Jul 12 18:07:52 notice ALEOS_CELL_RadioTask: Setting COPS mode start
Jul 12 18:07:52 debug ALEOS_CELL_MultiSIM: syncActiveMsciid: New: 10713, global: 11202, sim1: 10713, sim2: 10753 esim: 10679
Jul 12 18:07:52 debug ALEOS_CELL_MultiSIM: syncActiveMsciid: Global MSCIID already in sync
Jul 12 18:07:52 notice ALEOS_CELL_RadioTask: Current COPS user setting: 0
Jul 12 18:07:52 notice ALEOS_CELL_RadioTask: sending [AT+COPS=3,2]
Jul 12 18:07:52 notice ALEOS_CELL_RadioTask: Radio response [AT+COPS=3,2 OK]
Jul 12 18:07:52 notice ALEOS_CELL_RadioTask: sending [AT+COPS?]
Jul 12 18:07:52 notice ALEOS_CELL_RadioTask: Radio response [AT+COPS? +COPS: 0,2,“311480”,7 OK]
Jul 12 18:07:52 notice ALEOS_CELL_RadioTask: Current COPS mode read from radio: 0
Jul 12 18:07:52 notice ALEOS_CELL_RadioTask: Leaving COPS mode as default: automatic
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: New Event received: RADIO_EVENT_WAIT_UNTIL_READY
Jul 12 18:07:52 notice ALEOS_CELL_RadioTask: Radio_state → RADIO_STATE_NOTREADY_WAIT
Jul 12 18:07:52 info ALEOS_CELL_RadioTask: Backup APN timeout set to 223
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: Service state is: Service
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: > LTE:
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: SrvStatusInfo
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: Service status of the system : Service
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: True service status of the system : No Service
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: Whether the RAT is the preferred data path : Not preferred
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: SysInfoCommon
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: Service domain registered on the system : Packet-switched only
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: Current system’s service capability : Packet-switched only
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: Current SDK roaming status : [0] - Off
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: Whether the system is forbidden : Not forbidden
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: Voice support status on LTE : Voice is not supported
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: PLMN:311.480
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: New Event received: RADIO_EVENT_CONNECT
Jul 12 18:07:52 notice ALEOS_CELL_RadioTask: Radio_state → RADIO_STATE_CONNECT
Jul 12 18:07:52 notice ALEOS_CELL_RadioTask: IPPreference : IPv4
Jul 12 18:07:52 debug SWI0 SDK Process: psrwds_setipfamily: instance: 0 IP family: V4 Active WDS Client: V4
Jul 12 18:07:52 debug SWI0 SDK Process: psrwds_starnet:
Jul 12 18:07:52 alert ALEOS_EVENTS_gnssmgr: GPS disabled, Assisted Data Retrieval always off
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: iSLQSStartStopDataSession/2975: WDS start interface verbose error: 242
Jul 12 18:07:52 notice ALEOS_CELL_detectrmdetach: 9McEmRmHal: radio module = ALEOS_RADIO_MODULE_MC7455 is active
Jul 12 18:07:52 debug ALEOS_CELL_detectrmdetach: Reserving Radio Access (PID: 1268)…
Jul 12 18:07:52 debug ALEOS_CELL_detectrmdetach: Reserved radio access (PID: 1268)
Jul 12 18:07:52 debug ALEOS_CELL_RadioTask: RSSI bar=2
Jul 12 18:07:52 info ALEOS_CELL_detectrmdetach: Radio is in ATTACHED state
Jul 12 18:07:52 debug ALEOS_CELL_detectrmdetach: Releasing radio access (PID: 1268)…
Jul 12 18:07:53 debug ALEOS_CELL_RadioTask: Failed to add MSCIID [261] to CSM queue, attempting to resend message
Jul 12 18:07:53 debug ALEOS_CELL_RadioTask: cbkTestSetSignalStrengthCB - Radio interface: [8]-[LTE] RSSI: [81] AleosServiceType: [11]-[LTE]
Jul 12 18:07:53 err ALEOS_CELL_RadioTask: Unable to establish data session, return value: 1014failurereason: 1, line: 732
Jul 12 18:07:53 notice ALEOS_CELL_RadioTask: Verbose call end type: 2, verbose call end code: 242
Jul 12 18:07:53 info ALEOS_CELL_RadioTask: AL_startDataSession - attempt: 1, return code: -2
Jul 12 18:07:53 debug ALEOS_CELL_RadioTask: [eVerizon] The error type is not supported (‘2’) - Process to regular handling
Jul 12 18:07:53 info ALEOS_CELL_RadioTask: GenericBackoff [eStandard] - delay [15] - disconnected time [11]
Jul 12 18:07:53 debug ALEOS_CELL_RadioTask: New Event received: RADIO_EVENT_DISCONNECT
Jul 12 18:07:53 notice ALEOS_CELL_RadioTask: Radio_state → RADIO_STATE_DISCONNECT

Next steps:

  1. If the eSIM used on RV50X has the same service as the one used on LX60, could you please try entering the APN “HOLOGRAM.VZWENTP”? If not, could you please check with the operator for the correct APN for this eSIM?
  2. If the issue still occurs, please share the full log with me so I can check it further.

Thanks,