> For the complete documentation index, see [llms.txt](https://rayn-scripts.gitbook.io/rayn-scripts-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rayn-scripts.gitbook.io/rayn-scripts-docs/rayn_simcards/troubleshooting.md).

# Troubleshooting

Fixes for the most common issues.

**A new phone still gets a random number** The two patched `uniquePhones/ox_inventory.lua` files are not in place, or lb-phone was not restarted after replacing them.

**"SetPhone failed" in F8** `functions_patch.lua` is missing at the end of `lb-phone/client/custom/functions/functions.lua`.

**Nothing happens when I use the SIM card** The `sim_card` item needs `server = { export = 'rayn_simcards.useSimCard' }`.

**ox\_inventory error `'}' expected ... near <eof>` after adding the Eject SIM button** A closing brace was lost when editing the `['phone']` entry. Replace the whole entry with the example from the *Installation* page.

**"Your phone already has a number" when inserting a card** The phone got an lb-phone number before the script was installed. Use an empty phone, or enable `ReplaceLegacyNumber`.

**The number does not stick (classic mode)** In classic mode lb-phone must run with `Config.Item.Unique = false`.

**Generated numbers look different from other numbers** Set `Config.LBPhone.NumberPrefixes` and `NumberLength` the same as `Config.PhoneNumber` in lb-phone.


---

# 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://rayn-scripts.gitbook.io/rayn-scripts-docs/rayn_simcards/troubleshooting.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.