APN not applying via dpcParams: placeholder MCC/MNC values and Supervisor Plugin required for dual-SIM APN push on South African networks

Android

AndroidiOS

This article explains how to fix APN configurations that aren't applying to dual-SIM Android devices on South African networks. You'll learn how to correct placeholder carrier values and ensure the Esper Supervisor Plugin is properly installed.

Before you begin

APN management via Esper requires the Esper Supervisor Plugin to be installed and active on your devices. This article covers:

• Replacing placeholder MCC/MNC values with real carrier codes
• Verifying the Supervisor Plugin is installed
• Applying corrected APN configurations for South African carriers

This guide is specific to dual-SIM devices using Vodacom (MCC 655, MNC 01) and MTN (MCC 655, MNC 10) networks.

Step 1: Replace placeholder MCC/MNC values

If your APN JSON contains placeholder strings like <VODACOM_MCC> or <MTN_MNC>, they must be replaced with real numeric carrier codes. Android requires actual carrier identifiers to attach APNs to the correct SIM slot.

Use these values for South African carriers:

Example: Corrected Vodacom/Flickswitch payload (SIM slot 1 — set as default):

{
 "dpcParams": [
 {
 "key": "addNewApnAndSetDefault",
 "value": "{\"name\":\"Vodacom Flickswitch\",\"apn\":\"Flickswitch\",\"proxy\":\"\",\"port\":\"\",\"mmsproxy\":\"\",\"mmsport\":\"\",\"user\":\"\",\"server\":\"\",\"password\":\"\",\"mmsc\":\"\",\"authtype\":\"-1\",\"protocol\":\"IPV4V6\",\"roaming_protocol\":\"IPV4V6\",\"type\":\"default\",\"mcc\":\"655\",\"mnc\":\"01\",\"numeric\":\"65501\",\"current\":\"1\",\"bearer\":\"0\",\"carrier_enabled\":\"1\"}"
 }
 ]
}

Example: Corrected MTN/a2pay payload (SIM slot 2 — add only):

{
 "dpcParams": [
 {
 "key": "addNewApn",
 "value": "{\"name\":\"a2pay\",\"apn\":\"a2l.co.za\",\"proxy\":\"\",\"port\":\"\",\"mmsproxy\":\"\",\"mmsport\":\"\",\"user\":\"\",\"server\":\"\",\"password\":\"\",\"mmsc\":\"\",\"authtype\":\"-1\",\"protocol\":\"IPV4V6\",\"roaming_protocol\":\"IPV4V6\",\"type\":\"default\",\"mcc\":\"655\",\"mnc\":\"10\",\"numeric\":\"65510\",\"current\":\"1\",\"bearer\":\"0\",\"carrier_enabled\":\"1\"}"
 }
 ]
}

Important: Ensure the APN value is trimmed (no leading or trailing spaces). For example, use a2l.co.za instead of a2l.co.za .

Step 2: Verify the Esper Supervisor Plugin is installed

APN management via Esper AgentParams requires the Esper Supervisor Plugin to be installed and active on your devices.

1. In the Esper Console, navigate to Devices & Groups → [Device Name] → Apps
2. Locate Esper Supervisor Plugin in the app list and confirm its status is Active
3. If the plugin is not listed or is inactive, you need to install it:
   • Go to Apps → Add App
   • Select the Supervisor Plugin APK
   • Apply it to your device group via Blueprint or direct install

Step 3: Apply the corrected APN configuration

1. In the Esper Console, navigate to Devices & Groups → [Device Name] → Settings (or access Esper AgentParams via Blueprint → Additional Settings → Esper AgentParams)
2. Paste the corrected JSON payload for each APN block (Vodacom first, then MTN)
3. Save and apply the configuration
4. Check the device command history to confirm the status shows Applied

Step 4: Verify the APN configuration on your device

1. On the device, open Settings → Network & Internet → Mobile Network → [SIM 1] → Access Point Names
2. Confirm Vodacom Flickswitch appears as the default APN for SIM 1
3. Repeat for SIM 2 and confirm a2pay is listed under the MTN SIM's APN list
4. Test data connectivity on each SIM independently to verify both work correctly

Troubleshooting

The APN still isn't appearing on the device:

• Verify the MCC/MNC values match your SIM: Check your physical SIM's actual MCC/MNC values by opening Settings → About Phone → SIM Status on the device. You can also use ADB to confirm:

  adb shell dumpsys telephony.registry | grep -i mcc

  A mismatch of even one digit (for example, 01 vs 1) will prevent APN attachment on some devices. Correct the payload and reapply.
• Confirm the Supervisor Plugin version supports dual-SIM APN targeting: Some older plugin versions may not support per-slot APN assignment. If the APN is being applied to the wrong SIM slot, contact Esper Support to confirm your plugin version supports dual-SIM APN management.
• The APN appears but isn't being used: If the APN is created but data isn't routing through it, ensure it is set as the default APN for that SIM slot. You may need to manually select it in device settings, or verify the current field in the JSON is set to 1.

Still need help?

If you've completed all steps and the APN configuration still isn't working, contact Esper Support. include:

• The exact MCC/MNC values from your SIM (from Settings → About Phone → SIM Status)
• A screenshot of your