> For the complete documentation index, see [llms.txt](https://lt-studios.gitbook.io/lt-studios/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lt-studios.gitbook.io/lt-studios/assets/editor/user-guide/how-to-use-our-callsign-handling-esx.md).

# How to use our Callsign Handling (ESX)

You don't have a Callsign Handler in your server that adds a /callsign command in your server?

No problem, we can handle it for you. With our callsign handling you'll get access to this command and player's callsign management.

\*Important\*: At the moment, support for this feature is only given for ESX, as QBCore and QBox come with their own support for this feature by default.

In order to enable it on your server, Start with making sure this line in `shared/config.lua`  is set to true:

```lua
-- `true` by default, determines wether to use LT-10System's callsign handling or some other /callsign command,
-- If you're using ESX and don't have another command as /callsign, set it to true
-- If you're using any other framework it wont work by default
UseLTCallsigns = true,
```

Afterwards, go to the `db` folder in the `lt-10system` script folder. You'll find an SQL Query File there called `lt_callsigns.sql`. Run it using your SQL software (e.g HeidiSQL) and you're good to go. Btw make sure you have `oxmysql` on your server and started before `lt-10system` 

This is the SQL Query, pretty simple:

```sql
CREATE TABLE player_callsigns (
  identifier VARCHAR(255) PRIMARY KEY,
  callsign VARCHAR(50) NOT NULL
);
```

Now just make sure this is the order of starting these scripts in your server and you're good to go!

```
ensure oxmysql
ensure pma-voice
ensure MugShotBase64
ensure lt-10system
```

For any further assistance feel free to contact us on our Discord server.