> For the complete documentation index, see [llms.txt](https://helpcenter.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.verifone.com/v240m-connections/mobile-data-setup.md).

# Mobile Data Setup

1. **Open the Main Menu** \
   Tap the bar at the top of the screen or press the \* button.
2. **Go to Supervisor Menu** \
   Select Supervisor and enter the password (default is 12345, unless changed). If you have amended this please refer to <mark style="color:purple;">page 43</mark> on the [Webcom Manual](/webcom-manual/webcom-manual.md).
3. **Open Communication Settings** \
   Select Communication.
4. **Choose Mobile Data** \
   In the Communication Panel, tap the Mobile Data tile.
5. **Open Configuration** \
   Select Configuration.
6. **Check SIM Slot** \
   Tap Select SIM Slot and ensure it is set to 1.
7. **Skip SIM PIN** \
   Leave the SIM PIN option as skipped.
8. **Open Mobile Settings** \
   Select Mobile Settings.
9. **Verify Settings** \
   Ensure the following values are correct:
   * APN: mobius.m2m (KPN via Mobius), verifone.inc.cxn (TELENOR) or internet.cxn (Mobius)
   * Auto Start: Yes&#x20;
   * PPP Username: web&#x20;
   * Password: web
10. **Save Settings** \
    Tap Save, then press X repeatedly to return to the login screen.
11. **Start Interface** \
    Press OK when prompted to start the interface.
12. **Exit and Log In** \
    Tap the top bar or press the Red X button to exit menus, then log in.

#### [<mark style="color:$success;">Back to V240M - Connection Guides</mark>](/v240m-connections/v240m-connection-guides.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://helpcenter.verifone.com/v240m-connections/mobile-data-setup.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.