# EM7590 Verizon Firmware – Unexpected Enterprise APN in PDP Context 3

**URL:** <https://forum.sierrawireless.com/t/em7590-verizon-firmware-unexpected-enterprise-apn-in-pdp-context-3/35974>\
**Category:** MC/EM Series\
**Tags:** faq\
**Created:** [August 25, 2026, 7:19pm UTC](https://forum.sierrawireless.com/t/em7590-verizon-firmware-unexpected-enterprise-apn-in-pdp-context-3/35974 "2026-08-25T19:19:15Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![liam1](https://avatars.discourse-cdn.com/v4/letter/l/e68b1a/32.png) [@liam1](https://forum.sierrawireless.com/u/liam1)\
**Post date:** [August 25, 2026, 7:19pm UTC](https://forum.sierrawireless.com/t/em7590-verizon-firmware-unexpected-enterprise-apn-in-pdp-context-3/35974/1 "2026-08-25T19:19:15Z")

</div>

We are testing an EM7590 using the Verizon firmware/PRI:

```auto
current fw version: 04.00.04.00
current carrier name: VERIZON
current config name: VERIZON_004.000_000
current subpri index: 000

```

```auto
>>> AT!PRIID?
PRI Part Number: 000004C
Revision: 001.001_002
Customer: Generic
Carrier PRI: SWIX12C_04.00.04.00_VERIZON_004.000_000

```

When querying the PDP contexts, we see:

```auto
AT+CGDCONT?

+CGDCONT: 1,"IPV4V6","ims","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 2,"IPV4V6","vzwadmin","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 3,"IPV4V6","BIINC.GW8.VZWENTP","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 4,"IPV4V6","vzwapp","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0
+CGDCONT: 5,"IPV4V6","vzwemergency","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,1

```

My understanding is that the default Verizon configuration should normally have `VZWINTERNET` in PDP context 3. Instead, this module has `BIINC.GW8.VZWENTP`, which appears to be a Verizon enterprise/private-network APN.

Can you clarify:

1. Is it expected for the EM7590 Verizon PRI to dynamically replace the default `VZWINTERNET` APN in CID 3 with an enterprise APN?
2. If so, what causes this change-SIM/UICC provisioning, Verizon network provisioning/OMA-DM, the PRI, or another mechanism?
3. Is `BIINC.GW8.VZWENTP` being obtained from the SIM/account, or is it stored persistently in the modem?
4. What is the supported method for restoring the Verizon default PDP-context configuration, including `VZWINTERNET` in CID 3?

We are performing Verizon certification testing, so we want to understand whether this APN table is expected for this firmware/SIM combination or whether the module has retained provisioning from an earlier configuration.

---

<div class="post-metadata">

**Author:** ![blackbow7](https://avatars.discourse-cdn.com/v4/letter/b/e495f1/32.png) [@blackbow7](https://forum.sierrawireless.com/u/blackbow7)\
**Post date:** [August 25, 2026, 7:43pm UTC](https://forum.sierrawireless.com/t/em7590-verizon-firmware-unexpected-enterprise-apn-in-pdp-context-3/35974/2 "2026-08-25T19:43:01Z")

</div>

I understand your questions. I have a lot of experience with this. I can help until Semtech Support responds.

Yes, this is expected based on the Verizon SIM card provisioning in the Verizon network database.

The cause of this change is Verizon network-based SIM provisioning using the LWM2M protocol.

The module from the factory, the class 3 APN is lower case vzwinternet.

BIINC.GW8.VZWENTP appears to be the class 3 APN provisioned on this SIM card.

I think the supported method to change this is using the AT+CGDCONT command or AT+VZWAPNE command

---

<div class="post-metadata">

**Author:** ![blackbow7](https://avatars.discourse-cdn.com/v4/letter/b/e495f1/32.png) [@blackbow7](https://forum.sierrawireless.com/u/blackbow7)\
**Post date:** [August 25, 2026, 7:45pm UTC](https://forum.sierrawireless.com/t/em7590-verizon-firmware-unexpected-enterprise-apn-in-pdp-context-3/35974/3 "2026-08-25T19:45:35Z")

</div>

I have another response or suggestion. Best to check or confirm the provisioning of this SIM card. What class 3 APN is this SIM card provisioned for? Verizon or the lab should know.

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [August 26, 2026, 12:41am UTC](https://forum.sierrawireless.com/t/em7590-verizon-firmware-unexpected-enterprise-apn-in-pdp-context-3/35974/4 "2026-08-26T00:41:09Z")

</div>

From google AI:

**`BIINC.GW8`** : The specific enterprise identifier/customer code assigned for the private network routing.

**`VZWENTP`** : Verizon’s standard designation for an enterprise private network (ENTP) APN Verizon Support.

Refer to your question,

1. Have you put in a mobile phone to confirm?
2. I guess it is Verizon network provisioning  
3.if you remove the sim card, what is the return of at+cgdcont?  
4.you can change APN by at+cgdcont command

---

<div class="post-metadata">

**Author:** ![liam1](https://avatars.discourse-cdn.com/v4/letter/l/e68b1a/32.png) [@liam1](https://forum.sierrawireless.com/u/liam1)\
**Post date:** [August 26, 2026, 1:23pm UTC](https://forum.sierrawireless.com/t/em7590-verizon-firmware-unexpected-enterprise-apn-in-pdp-context-3/35974/5 "2026-08-26T13:23:16Z")

</div>

@blackbow7 Is there any way to audit actions performed via LWM2M? Right now configuration can basically come from three unique sources:

- Firmware Defaults
- Direct module configuration (AT , QMI, MBIM, etc.)
- Carrier configuration (LWM2M, etc.)

It be great if the module would tell me which of these was used for a PDP Context configuration.

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [August 26, 2026, 3:28pm UTC](https://forum.sierrawireless.com/t/em7590-verizon-firmware-unexpected-enterprise-apn-in-pdp-context-3/35974/6 "2026-08-26T15:28:56Z")

</div>

you can disable MBIM interface by AT!USBCOMP, and then just leave the AT command to be controlled by you. (remember to disable modemmanager in linux as it will also send AT command)

After that you can change back the APN of context ID back to default “VZWINTERNET”.

If the APN still being changed, then that means the Verizon network pushes the APN to it.

---

<div class="post-metadata">

**Author:** ![blackbow7](https://avatars.discourse-cdn.com/v4/letter/b/e495f1/32.png) [@blackbow7](https://forum.sierrawireless.com/u/blackbow7)\
**Post date:** [August 26, 2026, 4:13pm UTC](https://forum.sierrawireless.com/t/em7590-verizon-firmware-unexpected-enterprise-apn-in-pdp-context-3/35974/7 "2026-08-26T16:13:50Z")

</div>

Right. I understand. The module should provide a notification of a class 3 APN change via LWM2M. But I can not recall the notification method. Windows requires this notification, too for proper operation. I am thinking - there is an AT command which can tell you the IP of the connection and the APN of that connection. I have to recall that command. I will try and then reply.

---

<div class="post-metadata">

**Author:** ![blackbow7](https://avatars.discourse-cdn.com/v4/letter/b/e495f1/32.png) [@blackbow7](https://forum.sierrawireless.com/u/blackbow7)\
**Post date:** [August 26, 2026, 7:39pm UTC](https://forum.sierrawireless.com/t/em7590-verizon-firmware-unexpected-enterprise-apn-in-pdp-context-3/35974/8 "2026-08-26T19:39:57Z")

</div>

The AT command I was thinking of is AT+CGDCONTRDP=3

This command will tell you the module values for CID number 3, the APN, and the IP address of the connection.

---

<div class="post-metadata">

**Author:** ![daniel.swanemar](https://avatars.discourse-cdn.com/v4/letter/d/df705f/32.png) [@daniel.swanemar](https://forum.sierrawireless.com/u/daniel.swanemar)\
**Post date:** [September 10, 2026, 2:24pm UTC](https://forum.sierrawireless.com/t/em7590-verizon-firmware-unexpected-enterprise-apn-in-pdp-context-3/35974/9 "2026-09-10T14:24:56Z")

</div>

FYI this FW is in test only, not commercial according to latest CRN.

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [September 11, 2026, 1:16am UTC](https://forum.sierrawireless.com/t/em7590-verizon-firmware-unexpected-enterprise-apn-in-pdp-context-3/35974/10 "2026-09-11T01:16:42Z")

</div>

The SOURCE website will be updated soon for the FW 04.00.04.00. (Release 7)  
It should have been certified for ATT/TMO/VZW.

---

<div class="post-metadata">

**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\
**Post date:** [September 16, 2026, 8:09am UTC](https://forum.sierrawireless.com/t/em7590-verizon-firmware-unexpected-enterprise-apn-in-pdp-context-3/35974/11 "2026-09-16T08:09:59Z")

</div>

The SOURCE website has been updated with Release 7 for ATT/VZW/TMO

> **[Sierra Wireless™ EM759x Approved FW Packages | Source](https://source.sierrawireless.com/resources/airprime/minicard/75xx/em7590/em7590-approved-fw-packages#sthash.QuzdpHaC.dpbs)**
