APN settings not applying on dual-SIM devices — fix MCC/MNC values and Supervisor Plugin

Android

When an APN configuration is pushed to a dual-SIM Android device, the settings may appear to save but fail to activate on either SIM. The device continues using its default carrier APN instead of the one you configured.

Why this happens

Esper matches APN configurations to a SIM slot using the Mobile Country Code (MCC) and Mobile Network Code (MNC) embedded in the JSON payload. If the payload still contains placeholder strings such as <VODACOM_MCC> or <MTN_MNC> instead of real numeric values, Android cannot associate the APN with the correct SIM and silently discards it. Additionally, APN management through Esper requires the Esper Supervisor Plugin to be installed and active on the device — without it, even a correctly formed payload will not apply.

Steps

1. Replace all placeholder MCC/MNC values with real carrier codes.
   Open the APN JSON payload you intend to deploy and locate any placeholder strings. Replace them with the correct numeric values for South African carriers:

   Carrier	MCC	MNC	numeric
   Vodacom	655	01	65501
   MTN	655	10	65510

   The numeric field must be the direct concatenation of MCC and MNC with no separator. Android uses all three fields together to match the APN to the SIM card reported by the modem.
2. Check that the apn field contains no leading or trailing spaces.
   A value like  a2l.co.za  will not match the carrier gateway. The field must read exactly a2l.co.za. Check every string field in the payload if you copied it from a spreadsheet or document.
3. Use the correct key for each SIM slot's intent.
   Use addNewApnAndSetDefault for the SIM slot whose APN should become the default data connection. Use addNewApn for additional SIM slots where you want the APN registered but not set as default. Using the wrong key will either override an unintended slot or leave the APN inactive.

   Corrected payload for Vodacom / Flickswitch (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\"}"
       }
     ]
   }

   Corrected payload for MTN / a2pay (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\"}"
       }
     ]
   }

4. Confirm the Esper Supervisor Plugin is installed and active on the device.
   Navigate to Devices & Groups → [Device Name] → Apps and locate Esper Supervisor Plugin in the app list. Its status must show Active. The Supervisor Plugin is required for AgentParams-based APN commands to be processed; the Esper Agent alone cannot apply APN changes without it.
   • If the plugin is listed but shows a status other than Active, select it and use the Restart action.
   • If the plugin is not listed, go to Apps & Configuration → Apps, upload the Supervisor Plugin APK, then install it to the device or group via a Blueprint or direct push.
5. Deploy the corrected APN payload to the device.
   Navigate to Devices & Groups → [Device Name] → Settings → Esper AgentParams, paste the corrected JSON, and save. Alternatively, add the payload under Blueprints → [Blueprint Name] → Additional Settings → Esper AgentParams and apply the blueprint to the target group. Deploying through a blueprint ensures the configuration is re-applied consistently if a device is re-enrolled.

Verify: On the device, open Settings → Network → SIM & Mobile Network → [SIM slot] → Access Point Names. The APN you configured should appear in the list and be selected as active within 2–3 minutes of the payload being acknowledged. In the Esper Console, the device's Activity Feed should show the AgentParams command with a Success status.

If this doesn't resolve it

Before contacting Esper Support, collect the following:

• A copy of the exact JSON payload you deployed (with all placeholder values already replaced)
• A screenshot of the Activity Feed entry for the AgentParams command, including the status and any error message shown
• The Esper Supervisor Plugin version visible under Devices & Groups → [Device Name] → Apps → Esper Supervisor Plugin
• The device make, model, and Android version from Devices & Groups → [Device Name] → Device Info
• Confirmation of which SIM slots are physically populated and which carrier is in each slot

Contact Esper Support with the above information so the team can investigate the AgentParams execution logs for your device.

Still need help?

If APN settings still aren't applying on your dual-SIM devices after verifying MCC/MNC values and updating the Supervisor Plugin, please submit a support ticket with your device model, SIM carrier information, and current Supervisor Plugin version.