Skip to main content
Do not use FileZilla. It can corrupt or skip hidden files during upload. We recommend WinSCP.
Enter your TebexTransactionID in API.lua. The music app will not work without a TebexID.

​
📋 Prerequisites

Before you begin, make sure you have:

Database Access

MySQL or MariaDB database with permissions to create tables

FTP Client

WinSCP or similar (not FileZilla)

Fivemanage / Fivemerr

Valid API key from Fivemanage or Fivemerr for media uploads

Discord Webhooks

Valid Discord webhooks for logging

​
🚀 Setup Instructions

1

Create Resource Folder

Create a folder named [phone] inside your server’s resources directory.Extract all scripts from the download into the [phone] folder.
2

Import Database

Import the roadphone.sql file into your database.
If you don’t import the SQL file, you will see a /fixphone message in-game.
3

Configure API

The script will not work without a valid key.
  • Open API.lua and enter your TebexTransactionID and your Fivemanage or Fivemerr API key.
Where to find your Transaction ID:
  • Check your purchase confirmation email from Tebex
  • Or log in to view your payment history:

Tebex Payment History

View and retrieve your transaction ID from past purchases
  • optional: Add your Discord webhooks in API.lua.
4

Configure Voice Chat

Edit roadphone/config.lua to set up your voice chat system.
If you don’t configure voice chat in config.lua, calling and radio features will not work.
Optional: Add Discord webhooks in API.lua for logging.
5

Update Server Config

Open server.cfg and add these lines after your framework (es_extended, qb-core, or qbox):
ensure xsound
ensure roadphone
The load order is important. Always load the phone after your core framework and dependencies.

​
🛡️ Anti-Cheat Configuration

If you use an anti-cheat system, whitelist these phone props:
  • phonesilver
  • phonepurple
  • phonegreen
  • phonelightblue
  • phonered
  • phoneblack
Installation complete! Restart your server and the RoadPhone system should be operational.

​
🔧 Troubleshooting

  • Verify all dependencies are installed
  • Check server console for error messages
  • Ensure the resource folder structure is correct
  • Confirm database credentials are correct
  • Check if the SQL file was imported successfully

​
📚 Next Steps

FAQ

Any problems or questions?

CustomApps

Learn how to create custom apps