# API Documentation
Source: https://www.sip.tg/api-external
# Catalog of Service Providers and Integrators
Source: https://www.sip.tg/en/catalog
SIP.TG services are not standalone — they require interaction with external service providers, and setup can be complex and have specifics.
Here you can select service providers for your needs and find a specialist who will help implement them. For convenience, you can choose a country and filter offers by tags.
| Tag | Description |
| -------------------- | ------------------------------------------------------------------------------------------------------------- |
| Partner | Provides SIP.TG services under their own brand |
| Integrator | Implements SIP.TG solutions turnkey, integrating them with existing telephony and CRM systems |
| Payments | Helps pay for SIP.TG services and prepare financial documents |
| Individuals | Works with end consumers (individuals) |
| PBX | Developer of PBX solutions compatible with SIP.TG |
| Telecom | Provider of IP telephony services where you can buy a virtual number and order international calling services |
| Bitrix24 amoCRM | Specializes in integration with the specified CRM systems |
Tags:
Country:
If your services are compatible with SIP.TG, you work on telephony service implementations, are interested in partnership, and want to be listed in the catalog, contact us on Telegram: [@siptg\_support](https://t.me/siptg_support).
# SIP.TG Documentation
Source: https://www.sip.tg/en/docs
Welcome to the updated documentation for the **SIP.TG** service.
Here you will find the most up-to-date information on how to connect and use the capabilities of SIP.TG: from basic operations with the **Gateway** and **Softphone** to deploying your own **Worker** modules and **Telegram Session Storage**.
## Main Sections
Use Telegram as a full-featured SIP client. Supports call recording, codec configuration.
Receive and make calls from Telegram via SIP PBX. Multi-line support and flexible Caller ID settings.
Subscriptions, limit changes, auto-renewal, various payment methods.
Worker module, Session Storage, managing third-party accounts.
## How to Get Help
1. We have a public group [@siptg\_public](https://t.me/siptg_public) where users help each other.
2. If you need a turn-key implementation or special conditions — contact service providers from our [catalog](/en/catalog) for assistance.
3. Support via [@siptg\_support](https://t.me/siptg_support) depends on your monthly SIP.TG service spend:
* AI-powered support — for monthly spend under **150 EUR**;
* Support by SIP.TG specialists — for monthly spend starting from **150 EUR**.
We usually don't send news updates to our users. Subscribe to our channel [@siptg\_news\_en](https://t.me/siptg_news_en) to stay informed about news and announcements.
Thank you for using SIP.TG!
# Worker and Storage Modules
Source: https://www.sip.tg/en/docs/additional/modules
The SIP.TG platform provides the ability to run **your own** server modules:
* **Worker** — responsible for processing/converting voice data (SIP ↔ Telegram).
* **Session Storage** (Storage) — stores keys and access data for Telegram accounts.
These modules can be hosted on your own server in a Docker container, with a dedicated IP address and guaranteed availability. Below is a description of how this works and what steps are needed for setup.
## Worker Servers
Worker processes and converts audio streams from SIP to Telegram format and vice versa in real time.
### Why it is needed
* **Performance guarantee**: you choose the equipment yourself, scale it to the needed load.
* **Minimal delay**: you can place the Worker as close as possible to your PBX to reduce RTT.
* **Confidentiality**: voice streams are not transmitted to SIP.TG public servers — you process audio data yourself.
* **Access to private networks**: if desired, the Worker can operate in a local (restricted) network and receive SIP traffic directly from the PBX.
### System Requirements
* **Docker CE** and **Docker Compose** on a Linux server (e.g., Ubuntu 22.04).
* Dedicated IP address (or TCP port forwarding) for connection from SIP.TG.
* Approximate performance: 1 call ≈ 2.5% CPU on one AMD Ryzen 5 1400 core, \~1 MB RAM when using G.711 (A-law).
### Setting Up Your Own Worker
1. In the [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) bot, execute the `/workers` command and click .
2. You will be sent 2 files: a private key and a certificate for secure connection with the SIP.TG platform.
3. Save them and do not share with third parties.
1. Install OS updates (if necessary).
2. Install Docker and Docker Compose.
3. Clone or download the Worker configuration template (see [GitHub](https://github.com/siptg/worker)).
4. Copy the certificates obtained from the bot to the server and specify paths to them in Docker/Worker settings.
5. If necessary, edit parameters in `docker-compose.yml` or in the corresponding configurations (SIP port, RTP range, etc.).
1. Start the Docker service:
```bash theme={null}
docker-compose up -d
```
2. Make sure the Worker container has successfully started and is listening on the specified ports.
3. Check the container logs (command `docker-compose logs`) if errors occur.
1. In the [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) bot, return to `/workers`, select the created Worker and click .
2. Enter the external address and port through which your server is accessible.
3. Click for SIP.TG to check the connection. If everything is normal, the Worker will switch to "Online" status.
### Public or Personal Mode
After enabling the Worker, you can specify:
* **Personal** (icon 🔑) — only the owner and administered Gateway sessions can use the Worker.
* **Public** (icon 🌐) — the Worker will be available to all SIP.TG users.
### Limitations for User Workers
* Connections of type **PBX→SIP.TG** on a user Worker are prohibited by default.
* In case of failure/unavailability of the Worker for more than 30 minutes, the platform may disconnect the associated SIP accounts.
## Telegram Session Storage
Storage — a server on which keys and login data for Telegram accounts are stored. Without it, Telegram sessions live in the SIP.TG "cloud", but if desired, you can store everything on your side.
### What Sessions Storage provides
* **Full control**: confidentiality of access to Telegram accounts, all keys are stored on your server.
* **Unlimited number of accounts** (subject to your subscription) in one storage.
* **Flexible configuration**: restriction on commands and events.
### System Requirements
* Docker CE / Docker Compose (Linux).
* Dedicated IP address (or TCP port forwarding) for connection from SIP.TG.
* The module uses the TDLib library, so 1-2 GB of RAM is sufficient (but depends on the number of Telegram accounts).
### Setting Up Your Own Storage
1. In the [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) bot, execute the `/storage` command and click .
2. The bot will send a private key and certificate. Save them to your server.
1. Install and configure Docker / Docker Compose.
2. Clone the storage configuration template (see [GitHub](https://github.com/siptg/storage)).
3. Place the certificates in the appropriate directories (as specified in `docker-compose.yml`).
4. If necessary, edit the configuration files (TCP port, database, etc.).
1. Execute in the folder with the configuration:
```bash theme={null}
docker-compose up -d
```
2. Check the container logs (`docker-compose logs`) for errors.
3. Make sure the specified TCP port is accessible externally.
1. Return to `/storage` in the [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) bot, select your storage and click .
2. Specify the external address and port through which the SIP.TG platform can connect.
3. Click to check availability. If everything is OK, the storage will be Online.
### Using the Storage
* When creating a new Telegram session (in the bot section `/gateway`), choose **your** Storage.
* It is **impossible** to transfer an already created session to another storage, however, you can recreate the session without deleting SIP connections.
## Frequently Asked Questions
The SIP.TG platform periodically checks the connection. If the server doesn't respond for more than 30 minutes, the Worker/Storage will switch to "Disabled" status. All SIP accounts working through this Worker will become inactive. The storage will stop servicing requests. You can resume operation by restoring server availability and re-enabling the module in the bot.
Yes. These modules are independent. You can store Telegram sessions in the SIP.TG cloud but process SIP streams on your Worker. Or vice versa: use public Worker servers but store sessions on your side.
The main task is to keep Docker containers operational, update software (Worker/Storage image) as new versions are released, and monitor network availability. If you don't have your own DevOps specialist, it's easier to use SIP.TG public resources.
* All connections between the SIP.TG platform and your modules are encrypted using certificates.
* By default, Docker images based on Ubuntu are used. All additional dependencies are pre-installed.
* See license and terms of use in GitHub repositories.
Change the Worker mode to "Public". Then any SIP.TG user can assign your Worker to themselves. You can also keep the Worker "Personal", but use it only with some of your SIP accounts in the [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs).
For full operation of Worker and Storage, a stable connection with the SIP.TG platform (Manager) is required. Make sure your server can access the internet without blockages and that ports are not filtered by the firewall.
# Gateway features overview
Source: https://www.sip.tg/en/docs/gateway
To use the Gateway, you must have your own Telegram account for this purpose. SIP.TG does not register Telegram accounts for its users.
**Gateway** is a mode that allows you to connect your Telegram account to a phone PBX (office or cloud-based) to forward voice calls **to** and **from** Telegram.
This means any call to your Telegram account is handled by the PBX, and for outbound calls from the PBX, the same Telegram account can be used as the “caller number”.
**When it's useful**: if you have a sales or support team working via PBX and want to make and receive calls through a Telegram account (not a bot) — to stay closer to your audience in the messenger.
### Key Use Cases
* **Business Telegram account** — use a single company Telegram account that can receive many simultaneous calls via PBX.
* **Support and sales** — route Telegram calls through your PBX to a call center, specific employee, or team.
* **Outbound calling** — agents make calls from the company’s “Telegram number” instead of their personal ones.
* **Any CRM integration** — if it works with your PBX, it works with your CRM module, auto-dialer, or analytics.
## How It Works
1. Connect your Telegram account in the `/gateway` section of the [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) (this creates a virtual “SIP.TG → Telegram” device).
2. Configure the connection method with your PBX (PBX→SIP.TG, SIP.TG→PBX, or IP⇿IP).
3. For incoming calls, a user "rings" your Telegram account — but the call is routed to your PBX.
4. For outgoing calls, your PBX connects to the Telegram account, which then initiates a call to the target Telegram user.
See [PBX SIP connection setup](/en/docs/gateway/pbx#general) for more on the three connection methods.
## General Setup Flow
* Choose a Telegram account that will be used to receive and make calls. You can either create a new account for the Gateway or use an existing one.
* Make sure in Telegram privacy settings that calls are allowed from everyone (or at least from the users you need).
* Go to [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) and run the `/gateway` command.
* Click and select the session storage where the access key for the Telegram account will be saved.
* Enter the phone number of the Telegram account and wait for the verification code from Telegram’s official service.
* Once authorized, a virtual "gateway session" will be created.
* Choose your connection method: PBX→SIP.TG, SIP.TG→PBX, or IP⇿IP.
* For PBX→SIP.TG: get the SIP login and password from the bot and enter them in your PBX settings as an external SIP trunk.
* For SIP.TG→PBX: enter your PBX SIP account credentials (login, password, server address) in the bot.
* For IP⇿IP: provide your PBX IP address and confirm with a test call if needed.
* Check that the trunk is registered in your PBX (or that the IP-to-IP connection is active).
* Make a test incoming call to the Telegram account and ensure it reaches the PBX.
* Try making an outbound call from the PBX to Telegram.
* Set up routing rules (IVR, voice menu) inside the PBX as needed.
## Next Steps
* [Telegram Integration](/en/docs/gateway/telegram) — defining roles, linking SIP.TG with your Telegram account, privacy, P2P, blocking other devices, message handling.
* [PBX Integration](/en/docs/gateway/pbx) — choosing and configuring the connection method (PBX→SIP.TG, SIP.TG→PBX, IP⇿IP); subscriber ID types and dialing behavior.
* [Troubleshooting](/en/docs/gateway/problems) — if something goes wrong.
The Gateway is a powerful tool for integrating Telegram with traditional telephony. For help, see [How to Get Help](/en/docs#help).
# Interaction with PBX
Source: https://www.sip.tg/en/docs/gateway/pbx
Integration with PBX systems occurs through SIP connections, which are jointly configured both on the PBX side and on the SIP.TG side.
To create a SIP connection on the SIP.TG side:
1. Launch the [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) and go to the `/gateway` section.
2. Select the Telegram session you want to connect to the PBX, or create a new one using the button (for more details, see [Step-by-step session connection](/en/docs/gateway/telegram#steps)).
3. Click one of the buttons to create a new SIP connection, corresponding to the connection type: , or .
## Configuring SIP Connection to PBX
Most settings are displayed directly on the buttons as current values. To change these settings, simply click the corresponding button and enter a new value when prompted by the bot.
However, some buttons work differently:
* **Worker**: when clicked, a list of available Worker servers appears. Select the desired server from the list to see its detailed description and assign it.
* **Checkmark buttons**, such as "", "", "", "", "", "" and "", work as toggles. One click activates or deactivates the option.
* **Connection protocol (UDP/TCP/TLS)**: each click switches to the next available protocol.
* and : display connection parameters to SIP.TG that need to be specified on the PBX side.
Allows you to select the server that will connect to the PBX or telephony provider.
There are 3 types of servers:
| Server type | Description | Symbol |
| ----------------------------- | ------------------------------------------------------ | ------ |
| Public SIP.TG servers | Main servers supported by SIP.TG | ✅ |
| Public servers of other users | Publicly available servers hosted by other users | 🌐 |
| Private servers | Your own servers, available only for your SIP accounts | 🔑 |
On a free subscription, only some of the public SIP.TG servers are available.
The choice of codecs affects the quality and compatibility of voice communication. Opus, alaw, mulaw, GSM and other codecs are supported.
DTMF is necessary for interacting with voice menus. Available methods are RFC2833 (recommended), INFO, and inband.
Allow you to set the number dialing format for compatibility with the PBX. More details in the [Outgoing dialing rules](/en/docs/softphone/settings#dialing-rules) section.
Priority allows you to set the order of calling SIP accounts when making a Telegram → SIP call.
The following rules apply:
1. Accounts with the same priority are called simultaneously.
2. The lower the priority, the earlier SIP accounts are called.
3. Transition to the next priority occurs after unsuccessful dialing to all SIP accounts of the previous priority.
Rules for forming the caller ID and displayed caller name when making a call, which applies to both directions.
For more details, see [Types of caller identifiers](#callerid).
Below are specific settings for each type of SIP connection.
### PBX → SIP.TG
In this mode, your PBX registers on SIP.TG as a SIP client. You receive a SIP login and password from the bot and specify them in your PBX.
This is the simplest connection method and is suitable for most systems (Asterisk, 3CX, FreePBX, etc.).
Show the login, password, and connection address of the current SIP line, which needs to be registered on your PBX side.
generates a new SIP password for this line in advance. After resetting, it will need to be updated on the PBX side.
A list of IP addresses and subnets from which connection to this account is allowed.
### SIP.TG → PBX
Here, the SIP.TG Worker server registers on your PBX. In the bot, you set the parameters of your PBX: login, password, and address.
Don't forget to add SIP.TG IP addresses to the whitelist on your PBX. Current list: [files.sip.tg/fw.txt](https://files.sip.tg/fw.txt).
Basic connection parameters that need to be filled in to make connection to your PBX possible.
should only be filled in if it differs from .
When a user clicks the call button 📞 in the Telegram app without sending any messages — this number will be used as the default number that will be sent to the PBX.
### IP ⇿ IP
Both sides know each other's IP address. Used in cases where registration is impossible or unnecessary (for example, static routing).
Suitable for advanced users. Requires route configuration on the PBX side.
IP address and port of the opposite side (your PBX).
For the connection to be established, on the PBX side, you also need to create a connection with a specific IP address of the SIP.TG server. For this, the IP address of the Worker server assigned to the SIP connection is used.
The current IP address of the Worker server being used will be displayed in the message when you request a change to the current parameter.
If you want to use multiple SIP connections between the same IP addresses, this field allows you to set an additional SIP header for correct connection identification.
The parameter is set as a pair `{SIP field name}:{SIP field value}`, separated by a colon `:`.
When a user clicks the call button 📞 in the Telegram app without sending any messages — this number will be used as the default number that will be sent to the PBX.
## Types of caller identifiers
Each Telegram user can have up to three types of identifiers:
* **Phone number**, on which the account is registered. It is always present, but by default is hidden by privacy settings for other users. With significant limitations, it's possible to establish contact with a user by phone number.
* **Username** — this is a unique alphabetic username. By default, it doesn't exist, many users set it up, but strictly speaking, it may be absent. Conversely, a user may have several collectible Usernames. You can establish contact with a user by Username, and the restrictions are much milder than for Phone number, but cloud PBXs often do not provide for the use of non-numeric caller identifiers.
* **User ID** — internal numeric identifier. Always present, never changes, but it's impossible to establish contact with a user only by User ID — it can be used only after contact has been established by one of the other methods.
| Identifier type | Format | Contact possibility | Mandatory | Changeable | PBX support |
| --------------- | ---------- | ------------------- | --------- | ---------- | ----------- |
| Phone number | numeric | limited | yes | yes | yes |
| Username | alphabetic | yes | no | yes | limited |
| User ID | numeric | no | yes | no | yes |
The table shows that each identifier has serious limitations that prevent it from being used in all scenarios. SIP.TG supports all types of identifiers and their combinations, and also allows you to set the priority of their use according to your needs.
### Telegram → PBX
For each SIP connection, you can set rules for forming the Caller ID, which will be transmitted in the `From` field in the `INVITE` message for Telegram → PBX calls.
Caller ID formation rules consist of several lines, with one rule per line. Each rule is a template string, in which `{phone}`, `{username}`, and `{userid}` are allowed as template parameters. When forming the final Caller ID, the first rule is used, all template parameters of which contain values about the calling Telegram user.
```
{phone}
{username}
0userid
```
Such a Caller ID in different situations can take all three types of identifiers, depending on which ones the user has:
* If the Phone number is not hidden — it will be used.
* Otherwise, if Username is set — the system will choose it.
* And only in the most exceptional case will User ID with prefix `0` be used — this tag allows resolving ambiguity in the interpretation of the identifier type.
```
{phone}
{username}
```
Here, the behavior is similar to Example 1, with the only difference that if the user has neither a Phone number nor a Username, such a call will be prohibited and will not reach the PBX.
```
{phone}
{username}
anonymous
```
And this example differs from the first two in that if the user does not have a Phone number and Username, the call will still reach the PBX, but with the number `anonymous`.
In addition to Caller ID, the From field can also contain the caller's name (Caller Name), the formation of which can also be controlled using similar rules, but in addition to the parameters listed above, there are two more:
* `{name}` — display name in UTF-8 (may cause problems on the PBX side due to emojis);
* `{name_ascii}` — display name converted to ASCII (safe option).
```
+{phone} ({name_ascii})
@{username} ({name_ascii})
{name_ascii}
```
Depending on whether the user has a Phone number and Username, one of the following will be used:
* either the Phone number with prefix `+`, followed by the display name written in parentheses,
* or the Username with prefix `@`, followed by the display name written in parentheses,
* or in the most extreme case — just the display name without extraneous characters.
### PBX → Telegram
When receiving an `INVITE` request from the PBX side, the called identifier will be interpreted in full accordance with the same Caller ID parameter described above. However, the algorithm for determining the identifier type and cutting off prefixes and extraneous characters in it does not look so obvious.
As in the case of Telegram → PBX calls, rules are checked sequentially and the selection stops at the first one that satisfies the given criteria after transformations:
1. All template parameters in the rule are replaced with their corresponding regular expressions:
* `{phone}` → `+?[1-9]\d*`: a number that cannot start with `0` and optionally can start with the `+` symbol;
* `{username}` → `@?[a-zA-Z]\w*`: an alphanumeric string that can only start with a letter and optionally with a prefix `@`;
* `{userid}` → `[1-9]\d*`: a number that cannot start with `0` and cannot have prefixes.
2. As a result of item 1, a complex regular expression is obtained, against which the received identifier from the INVITE URI is checked.
3. As a result of satisfying the regular expression, although this is only theoretical, several types of identifiers may be recognized in the identifier at once. In this case, the first value will be selected in the specified order: `{userid}`, `{username}`, `{phone}`.
This ensures bidirectionality of Caller ID formation rules and consistency of identifier formats for both call directions.
## CRM Integration
CRM integration is usually implemented not directly with SIP.TG, but through a PBX to which SIP.TG connects as a standard SIP trunk. The CRM itself "sees" calls and contacts thanks to the capabilities of the PBX. Separate modules or plugins specifically for SIP.TG in CRM, as a rule, do not need to be installed.
Most often, the interaction is arranged as follows:
1. A Telegram call comes to the SIP.TG Gateway (Telegram account).
2. The SIP.TG Gateway converts the call to SIP and passes it to the PBX (via SIP trunk).
3. The PBX, having the necessary module or plugin for CRM integration, recognizes the incoming call, displays the client card, logs the call, or performs other actions.
4. At the end of the conversation, data about the call (for example, duration, result) is also saved in the CRM.
Almost any modern PBX can use SIP headers (CallerID, From, etc.) during an incoming or outgoing call to "pass through" data to the CRM module. When calling from Telegram through the SIP.TG Gateway to a SIP trunk, the caller's identifier is transmitted (most often displayed as Telegram ID or username), and the logic in the PBX maps this identifier to CRM records.
If your PBX can manage CallerID for outgoing calls (for example, "substitutes" the desired number), then the CRM can automatically record both the real phone number and Telegram contacts in the card. But there are many details for each CRM and PBX; in general, this is not directly regulated by SIP.TG.
If a CRM "knows how" to initiate a call (for example, to click on a number and call), it usually does this through the PBX, sends a Call API or AMI command there (Asterisk, 3CX, etc.). Then the PBX translates the request to the SIP.TG SIP trunk, and the Gateway calls Telegram. All this is again standard interaction "CRM → PBX → SIP trunk", where SIP.TG simply performs the role of a telecom operator for Telegram.
1. In the PBX, create an account (SIP trunk) with the credentials provided when setting up `/gateway` in [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs).
2. In the CRM, activate a ready-made plugin or module (for Asterisk, 3CX, FreePBX, Yate, etc.) or configure external requests to the PBX through its API.
3. Check that the CRM receives events about calls (card pops up, logs are written) and, if necessary, connect deeper logic (call distribution, linking conversation recordings, automation).
4. For outgoing calls from CRM — check that the PBX can form a call via the "SIP.TG" SIP trunk (usually a route or dialing rule for such a line is selected).
### When additional configuration is needed
If your CRM forms or expects some specific headers (for example, X-CRM-ID), such situations are resolved by means of your PBX (AGI scripts in Asterisk, custom settings in 3CX, etc.). On the SIP.TG side, there is no way to directly influence arbitrary SIP headers.
In some cases, the CRM needs to see the original caller number in full (for example, to "link" to a specific client). If the call is from Telegram, then the number can be anything (or absent altogether), and here it depends on the logic of your PBX how to substitute CallerID. Sometimes an additional database of correspondence "Telegram ID → client phone" is added.
Call recording can be enabled both in the PBX itself and in the "Call recording" mode on the SIP.TG side (in the Softphone). If you want to store recordings specifically in the CRM, check if your PBX can transfer recording files there. From the point of view of SIP.TG, this is a "transparent" transmission of sound via SIP, and there are no additional settings for recording.
### Additional tips
* **Unified approach**: all settings related to CRM are usually performed in your PBX interface. You perceive SIP.TG as a regular telecom operator (SIP trunk).
* **Typical PBXs** (Asterisk, 3CX, FreeSWITCH, Yate, Oktell, Panasonic, etc.) have plugins or REST interfaces for CRM integration. Study the PBX documentation: most likely, there is a ready-made example.
* **Call reception and routing scenarios** (IVR, operator queue, automatic forwarding) — all these are common PBX functions. The SIP.TG Gateway does not limit or complicate such scenarios: they work the same way as with other SIP trunks.
**Don't overcomplicate**. To "befriend" CRM with Telegram calls, it's enough to connect the SIP.TG Gateway to your PBX and use the standard CRM integration tools that are available in the PBX.
If you encounter problems or errors, use the [Troubleshooting](/en/docs/gateway/problems) section.
# Troubleshooting
Source: https://www.sip.tg/en/docs/gateway/problems
Below are possible errors that may occur when using the **Gateway** (PBX→Telegram mode) — both during registration (PBX→SIP.TG) and at the moment of call establishment (SIP→Telegram or Telegram→SIP). Some of them appear in PBX logs, some — as a displayed code when trying to call a Telegram account. Not all errors are frequently encountered in real operation, but it's useful to know about them for diagnostic purposes.
For reference:
* **Manager** — the controlling component of SIP.TG, responsible for connecting to Worker servers and Session Storages.
* **Worker** — the working component that processes calls, RTP traffic, and performs SIP signaling.
If you're just getting started with the Gateway, we also recommend checking out these articles:
* [Interaction with Telegram](/en/docs/gateway/telegram) — how to authorize a Telegram account for calls.
* [Interaction with PBX](/en/docs/gateway/pbx) — detailed description of SIP connection options.
* [Subscriptions Overview](/en/docs/subscriptions/pricing) — to ensure your "Gateway" subscription covers the required number of lines.
## Frequently Asked Questions
When setting up the Gateway, the Telegram account forwards incoming calls to the PBX.\
If a person is on the list of allowed callers, the call will be directed to the PBX, and on the device where this account is open, you can also manually answer the call.\
It's usually recommended to disable call reception on other devices so that everything goes through the PBX.
Yes, in the "Gateway" subscription, you can pay for multiple Telegram accounts. The first account costs 15 EUR/month, each additional one costs 150 EUR/month.
The Gateway can process incoming messages if you enable the option in the gateway settings. This enables auto-reply, Callback mode, and message processing by an external bot.\
For more details, see [SIP.TG Session Settings](/en/docs/gateway/telegram#session-settings).
In your Telegram session settings, disable the following options: , , , and .
For more details, see [SIP.TG Session Settings](/en/docs/gateway/telegram#session-settings).
The entire SIP.TG infrastructure is distributed across multiple data centers. Nevertheless, for mission-critical systems, you might consider your own Worker servers.
It's recommended to create a separate work account for the company — so that your personal Telegram doesn't mix with business calls. It's important that this account is always online (or store the session in the SIP.TG Cloud Storage).
Telegram may limit or completely block your gateway Telegram account. We do not recommend this activity and we do not transfer a subscription to another Telegram account in case of blocking.
However, if you want to preserve the subscription, we have a solution:
1. Activate the "Gateway" subscription for an Administrator (see [Roles of session and administrator accounts](/en/docs/gateway/telegram)) with the option ≥ 1.
2. From the administrator, create a new Telegram session linked to the account used for calls.
3. Enable the option for the created session.
4. If the calling Telegram account gets blocked, Disconnect the session via the session settings in the `/gateway` section **while keeping the current settings**, and Connect a new Telegram account there.
Yes, but this means that everyone will be using the same Telegram account, and incoming calls will come to all devices simultaneously. As soon as one person answers, the call will be dropped for the others.
This is normal Gateway behavior: the PBX sees that the call has already been accepted. A CANCEL is sent to other clients. If you want each employee to have their own Telegram account, use multiple gateway subscriptions.
A Telegram account is created based on a phone number. Usually, you take any SIM card, register it with Telegram, and then the number may not be used for traditional operator voice calls. The main thing is not to lose access to this number for Telegram recovery.
Our SIP stack is based on Yate, where the default UDP port range is 16384-32768.
## General Issues
* Check that the Telegram account is active and not blocked by the messenger.
* Make sure that in Telegram privacy settings, calls from everyone are allowed.
As with the Softphone, this is most often a question of codecs or network restrictions.
* Try specifying a specific codec (`alaw` or `mulaw`).
* Make sure that UDP traffic is allowed.
* Make sure that in the SIP account settings (Gateway), the method RFC2833 or INFO is selected, compatible with your PBX.
* Try switching the codec, sometimes inband DTMF and high compression don't work well together.
## Common SIP Errors
Such responses may appear both during calls and during simple SIP trunk registration. The code below is sent by the SIP.TG server to your PBX.
**Essence:** Standard response when using SIP Digest Auth. The PBX sends an INVITE or REGISTER without a complete set of authorization data, and the SIP.TG server requests authorization.\
If error 401 appears repeatedly many times in a row, it means that either the password/login is incorrect, or Digest Auth support is disabled on the PBX side.
**What to do:**
* Make sure that the login/password from [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) (section `/gateway`) is correctly entered in your PBX settings.
* Check that SIP authorization mode (Digest Auth) is enabled in the PBX itself.
* If necessary, change the password in `/gateway` and enter it again.
**Essence:** "Gateway" subscription limitation. This means that the Telegram account has no paid lines for Gateway mode, the subscription has expired, or the resource volume is exceeded.
**What to do:**
* In the [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) with the command `/subscriptions`, check if the "Gateway" plan is active and if there are enough lines.
* If the subscription period has expired or additional lines are needed, arrange for renewal / extension of the subscription (see [Subscription Overview](/en/docs/subscriptions/pricing)).
* Make sure that the specific Telegram account is actually linked to the right subscription (when paying for multiple accounts).
**Essence:** Internal error on the SIP.TG side related to the database. Such cases are extremely rare.
**What to do:**
* Usually temporary in nature and is automatically resolved.
* Try again, if the error occurs regularly, seek help. For more details, see [How to Get Help](/en/docs#help).
**Essence:** The Worker cannot connect to the SIP.TG Manager server due to an internal network problem. Your PBX will see this as a `503 No response from Manager` response.
**What to do:**
* As a rule, these are short-term failures. Try waiting 1-2 minutes and repeat the call.
* If the problem persists, you can switch the SIP trunk to another Worker server (see [Interaction with PBX](/en/docs/gateway/pbx)).
## Errors during PBX → SIP.TG registration
Here are responses that may come when your PBX tries to register with the SIP.TG Worker server (connection with the PBX→SIP.TG type). All errors listed below usually have code 403 or 404.
**Essence:** The PBX correctly tries to authenticate, but the specified password does not match what SIP.TG expects.
**What to do:**
* Check the password in the `/gateway` section of [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) and compare with what is entered on the PBX.
* If necessary, change the password in the bot (the "Change password" button) and enter the new one on the PBX side.
* Make sure that the login (username) also does not contain typos.
**Essence:** The password is correct, but your IP address is not in the list of allowed addresses for this SIP connection.
**What to do:**
* In [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs), section `/gateway`, open the settings of the corresponding SIP connection and:
* Add your IP address to the trusted list.
* Or clear the list to allow connections from any IP (but observe security measures).
* If your external IP changes in your network, take this into account when configuring (perhaps it's worth completely disabling ACL).
**Essence:** The Telegram account to which the binding is going is inactive (authorization has been lost). As a result, SIP.TG refuses to register the trunk, as there is no real Telegram connection.
**What to do:**
* In [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) in the `/gateway` section, reconnect the Telegram account (authorize the phone number).
* If the Telegram account has been deleted, you will have to assign another phone number for the Gateway.
* For more details, see [Interaction with Telegram](/en/docs/gateway/telegram).
**Essence:** The storage where the Telegram session is saved (cloud or your own Sessions storage) is currently turned off or unavailable. Consequently, there is no possibility to work with the Telegram session.
**What to do:**
* If you use the SIP.TG cloud storage, check the status in `/gateway`. Usually such failures are short-lived.
* If you have your own Session Storage, make sure it is running and available. If necessary, switch to the SIP.TG cloud.
**Essence:** The selected Worker server is disabled on the SIP.TG side or is in the process of updating/restarting. The server cannot accept PBX→SIP.TG registration.
**What to do:**
* In the bot's `/gateway` section, check the Worker settings. If the server is disabled, select another one or wait until it becomes active again.
* If this is your [own Worker](/en/docs/additional/modules#worker), start/restart it.
**Essence:** The Worker server configuration does not provide for connections with the "PBX→SIP.TG" type. For example, the server is only configured for "SIP.TG→PBX" or "IP⇿IP".
**What to do:**
* In [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs), double-check the connection type (PBX→SIP.TG) and select an appropriate Worker.
* Create another type of SIP connection ("SIP.TG→PBX" or "IP⇿IP").
**Essence:** Access to the used Telegram session has been revoked or no longer belongs to you. For example, the administrator who created the session has been deprived of rights, and you cannot use this session.
**What to do:**
* Create your own Gateway session. In the bot's `/gateway` section, connect the Telegram number that you control.
* Make sure that the administrator who previously created the session did not take away your access.
**Essence:** The login specified in the SIP request does not exist or has already been deleted. The SIP.TG server does not find such an "account".
**What to do:**
* Double-check the login/username that you received in the `/gateway` section.
* If this record was previously deleted, create a new one.
* Make sure that your PBX has exactly the login that was issued by the bot (without extra characters or spaces).
## Errors when calling SIP → Telegram
These errors occur when your PBX is already registered (or IP-to-IP), and during an outgoing call to Telegram, the SIP.TG server returns a code if it cannot correctly call the Telegram account.
**Essence:** The Telegram user has restricted the circle of people who can call them (e.g., only contacts or users with premium subscription), and your gateway account is not on this list.
**What to do:**
* Ask the called user to configure call permission: "Settings → Privacy → Voice Calls" → "All users" or add your gateway account to "Always allow".
* Or use an account that is actually in the target user's contacts.
**Essence:** SIP.TG could not find the Telegram account by the transmitted identifier (number, user\_id, username). Telegram may return such a response if:
* The number is indeed not registered in Telegram.
* The username does not exist or has been released.
* The profile is unavailable due to restrictions.
* Your gateway account searches for a phone number too frequently.
**What to do:**
* Make sure you are using the correct identifier (if using a phone — it should be a real Telegram number).
* If it happens often, check if you made a mistake in the format. It might be better to use the internal user\_id.
**Essence:** You are sending an INVITE without a prior PBX→SIP.TG registration, while the Worker requires a full REGISTER.
**What to do:**
* Enable "Registration" mode on your PBX side (register the PBX→SIP.TG trunk). For more details, see [Interaction with PBX](/en/docs/gateway/pbx).
**Essence:** The Telegram server did not respond in time, or the SIP.TG request hung when accessing Telegram. This happens during overload or Telegram anti-spam filter, when there are many outgoing calls in a short time.
**What to do:**
* Reduce the intensity of outgoing calls.
* Wait and try again if it was a temporary failure.
**Essence:** SIP.TG is trying to call a user by their internal user\_id, with which there is no explicit confirmed contact. Telegram rejects such "anonymous" calls.
**What to do:**
* Usually you need to either call by a confirmed number or username, or have the user add you to contacts or write to you first.
**Essence:** Any other internal error on the Telegram side. Sometimes this designates unexpected failures during audio channel processing, internal overload, etc.
**What to do:**
* Check the stability of the network, repeat the call.
* If the error appears regularly on the same number, seek help. For more details, see [How to Get Help](/en/docs#help).
**Essence:** The SIP.TG Worker server received an INVITE, but there is no active session for the needed account. That is, the PBX could have sent an INVITE without waiting for a response to REGISTER.
**What to do:**
* Make sure that the PBX→SIP.TG trunk is successfully registered and the Worker sees an active account.
* Sometimes it helps to restart the trunk on the PBX. If necessary, see [Interaction with PBX](/en/docs/gateway/pbx).
**Essence:** The Telegram session is actually disconnected. It's possible that in the [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs), the session is displayed, but it's not actually authorized.
**What to do:**
* Double-check the session status in `/gateway`, if necessary, re-authorize the Telegram number.
* If the error occurs frequently, try switching to another Worker or restarting the account.
**Essence:** SIP.TG has lost connection with the Telegram session storage, so it cannot find out the current status or create a call.
**What to do:**
* If you use cloud storage, wait for recovery (usually a minute or two).
* If your own Session Storage, check the logs and status of the module.
**Essence:** This is Telegram's anti-spam protection, when too many outgoing calls occur in a short period, especially to unfamiliar numbers.
**What to do:**
* Reduce the dialing speed (on the PBX side or your script).
* Use several different Telegram accounts to distribute the load.
* Wait for the specified time "retry after N", then try again.
**Essence:** The Worker was recently restarted or is being updated, and has not yet completed initialization. As a result, calls are rejected at the SIP level.
**What to do:**
* Wait 1-2 minutes and try the call again.
* Or in [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs), select another Worker server for your connection.
## Errors when calling Telegram → SIP
Here we consider situations when a real user tries to call the Gateway account from the Telegram application, and the Worker tries to transfer the call to your PBX. If the PBX returns an error, or if an error occurs on the SIP.TG side, the user may see an error in the chat with the Gateway account.
In this section, we only list those errors that may occur on the SIP.TG side.
**Essence:** The SIP.TG Gateway is also activated on the caller's account. The service blocks such an attempt (Telegram→SIP) to prevent looping or unforeseen call loops.
**What to do:**
* If you really need to receive calls from an account that is also a gateway, it's better to use a different mode for it (e.g., [Softphone](/en/docs/softphone)) or another Telegram account without Gateway.
**Essence:** During an incoming call from Telegram, the Worker could not reach your PBX. This can happen if the PBX→SIP.TG trunk is down, or if you have IP-to-IP, but the required port is not responding.
**What to do:**
* Make sure that the PBX is registered (with PBX→SIP.TG) or that the IP-to-IP connection is active.
* Check that SIP/UDP packets are not blocked in your firewall, and that you have opened RTP ports.
* For more details, see [Interaction with PBX](/en/docs/gateway/pbx).
**Essence:** The Worker server is currently unavailable for call transfer (network problems or restart), and the call is rejected with code 503.
**What to do:**
* Wait for some time or switch the Gateway account to another Worker (the bot's `/gateway` section).
* If it's your own Worker server, check its logs and restart if necessary.
If none of the listed solutions helps, seek assistance. For more details, see [How to Get Help](/en/docs#help).
# Interaction with Telegram
Source: https://www.sip.tg/en/docs/gateway/telegram
For the **Gateway** mode to work, you need to connect a regular Telegram account through which calls will pass. **Two roles** are involved in this process: the session and the administrator.
## Session and Administrator Account Roles
* **Session account** — a Telegram account that will be used as a source and receiver of calls. Connected as a **virtual device** to SIP.TG.
* **Administrator account** — a Telegram account that interacts with [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) and manages the session: connects the session, can change settings, connect SIP-PBX, and receive error notifications.
The same Telegram account can be used in both roles. However, in a corporate environment, it is recommended to separate them.
## Step-by-Step Session Connection
Choose a Telegram account that will be used as a gateway. Make sure it is not used for personal calls or correspondence.
Go to [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) and execute the `/gateway` command. Click the button.
Specify where the session will be stored:
* — simple, fast, and secure.
* **Own storage** — for companies with increased privacy requirements. For more details, see [Telegram Session Storage](/en/docs/additional/modules#storage).
Enter the phone number of the selected Telegram account. A code will be sent to it from the official Telegram account, which needs to be entered into the bot for authorization.
If two-factor authentication (2FA) is enabled on the account, a secure recovery process will be initiated: Telegram will send an email to the linked email for password reset. This is done to avoid transmitting your password in plain text.
## Applying Telegram Settings to the Account
Immediately after connecting the session, the bot will offer to apply recommended settings. They enhance the reliability and convenience of receiving calls:
* — eliminates conflicts when a call arrives simultaneously in multiple places. Allows using the Telegram session as a channel only for calls, and other devices — for correspondence.
* — important, as by default calls from unknown numbers are blocked by Telegram settings and will not reach the PBX.
* — if supported, allows Telegram to transmit audio directly, without forwarding through servers, improving call quality and reducing delays.
* — reduces the risk of receiving unnecessary notifications unrelated to call tasks.
Some Telegram parameters can only be changed 24 hours after connecting the account. If you get an error — try again later.
## SIP.TG Session Settings
These parameters enable or disable the use of the DTMF keypad in different call directions:
* — used for incoming Telegram calls (Telegram → SIP direction);
* — used for outgoing calls to Telegram from your PBX (SIP → Telegram direction).
The DTMF keypad allows:
* interacting with the PBX voice menu (IVR);
* entering internal numbers;
* displaying information about the calling employee when calling a Telegram user.
The keypad is activated by swiping up during a conversation. Supported transmission modes (RFC2833, inband, SIP INFO) are changed in the SIP connection settings and should be coordinated with the PBX settings.
Enables or disables the and buttons for Telegram users who interact with the gateway account. The buttons appear in the chat after the call ends.
Clicking the button initiates a call to the internal number in the PBX that was used during the previous conversation, allowing to connect the user with a specific employee or department. The number is sent to the PBX without applying number transformation rules.
The button works approximately the same with the only difference that before initiating the call, it displays the connected lines through which a call can be made. The number is sent to the PBX after applying the number transformation rules of the selected SIP account.
Enables or disables the ability to react to text messages coming to the session's Telegram account. When enabled, additional functions open up:
* — after sending any message to the chat, the user will receive an incoming call from the gateway with subsequent connection to the number sent in the message (or the default number; behavior is configured in the SIP line settings).
* — if a suitable SIP account for calling is not found for the message, it can be processed through an external inline-bot.
* — a predefined template is sent for each message, for example:
> This account is for calls only. For correspondence, use @support\_bot.
These functions can be enabled separately and the behavior can be configured depending on the situation.
* / — allows removing administrator rights from the current account or assigning another Telegram user as administrator (see [Session and Administrator Account Roles](#roles)).
* — extend the administrator's subscription to this session (see [Session and Administrator Account Roles](#roles) and [Additional sessions](/en/docs/subscriptions/pricing#gateway)).
* — completely remove the virtual device, reset the session, and optionally clear SIP connection parameters.
### Inline-bot
You can connect your own inline-bot that will be used to process incoming messages. This is especially useful in cases where the message cannot be matched with a phone number or a call is not required. The inline-bot can:
* respond with a template;
* collect requests;
* integrate with external systems such as Helpdesk, CRM, etc.
Additionally, you can set the format of the inline-request that will be passed to the bot. This allows structuring the user's request for more accurate processing.
# Softphon features overview
Source: https://www.sip.tg/en/docs/softphone
To use the Softphone, you need a **SIP account** from a VoIP provider or PBX. SIP.TG is not a telecom operator, does not offer telephony services on its behalf, and does not register SIP accounts for users.
**Softphone** allows you to use the Telegram app as a SIP client. You can connect to any VoIP provider or office PBX using SIP credentials. Incoming and outgoing calls go through Telegram — you receive them right inside your favorite messenger.
**When it’s useful**: when you want to replace traditional softphones (Zoiper, MicroSIP, etc.) and manage all your voice communication within Telegram, without juggling multiple apps.
### Key Use Cases
* **Personal use**: make and receive IP calls in Telegram even abroad (saving on roaming fees).
* **Remote work**: call centers, support, and sales teams can connect corporate SIP numbers directly in Telegram.
* **Unified workspace**: combine messaging and SIP telephony in a single app.
## How It Works
1. In the `/softphone` section of the [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs), create a **SIP account** (enter login, password, and SIP server address).
2. SIP.TG registers on the SIP server using one of its Worker servers.
3. Incoming calls to the SIP account are forwarded to Telegram (a special account [@siptg](https://t.me/siptg) “calls” you in chat).
4. Outgoing calls are made by sending a phone number in chat with [@siptg](https://t.me/siptg) or by tapping the "Redial" button.
Your Telegram account remains fully functional for regular calls and chats. The Softphone simply adds SIP call support.
## Next Steps
* [Softphone Setup](/en/docs/softphone/settings) — how to configure a SIP account, enable call recording, and link an account to a specific user.
* [How to Use](/en/docs/softphone/usage) — how to make and receive calls, use IVR menus, and control recording during a call.
* [Troubleshooting](/en/docs/softphone/problems) — most common issues and how to resolve them.
We hope the Softphone makes your voice communication more convenient. For help, see [How to Get Help](/en/docs#help).
# Troubleshooting
Source: https://www.sip.tg/en/docs/softphone/problems
For the correct operation of the Softphone in Telegram, you need to:
* Have an active **Softphone** subscription in the [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs).
* Make sure that in Telegram privacy settings, voice calls are allowed from "Everyone" or at least from **@siptg**.
* Correctly specify the SIP server address (with the necessary port if it's non-standard), login, and password in the bot.
* If necessary, configure audio codecs and "Dialing Rules" so that they meet the requirements of your PBX or SIP provider.
## Frequently Asked Questions
**Softphone** — is when you use Telegram as a SIP client (linking to any SIP operator).
**Gateway** — is when you connect a Telegram account to a PBX so that Telegram calls are processed by the PBX.
Yes. Voice stream through Telegram is an internet channel, it doesn't interfere with your GSM calls.
When creating an account, activate the checkbox. Available on a paid subscription (5 EUR/month per account). If necessary, you can select a separate channel/chat where audio files will be saved.
Yes. In the `/softphone` section of the [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) bot, open the SIP account and click .
In the [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) bot, open the settings of the desired account, click and select your colleague's Telegram profile. Now all incoming calls will go to them, and you will remain the Owner.
Yes, if your "Softphone" subscription allows the required number of accounts. You can create several SIP accounts. For outgoing calls, a request to select an account will appear before each call.
If you have a non-standard port on the operator or PBX side, specify it in the or field with a colon (for example: `sip.example.com:5062`). For the standard 5060, it's not necessary to specify.
## Problems and Debugging
Below is an expanded list of problems that our users have encountered.
**Symptoms**
* No information about the incoming call appears in Telegram.
**Possible causes**
* Voice calls are prohibited at the level of your Telegram account.
* The SIP account is being used in parallel on another device (in another Softphone, in a widget for calls through the browser, etc.).
* The connection between your Telegram account and our **@siptg** was lost.
**Solution**
1. Check the settings in Telegram: make sure that in the "Privacy and Security → "Voice Calls" section, the "Everyone" option is selected.
2. Update the SIP account password on the SIP provider or PBX side, and specify the new password for the account in the `/softphone` section of the [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs).
3. Open the chat with [@siptg](https://t.me/siptg?text=👋) and send any message.
**Symptoms**
* When an incoming (or Callback) call arrives, the user doesn't have time to answer it, and in the **@siptg** chat it's shown with the status "Rejected call".
* As a result, all incoming calls are automatically rejected on all devices linked to the Telegram account.
* SIP log shows the error `486 User declined the call`.
**Possible causes**
* On one of the devices, the Telegram application is "stuck" in an active call state, although there are no signs of an active call.
* During an incoming call, you're talking through another application or via mobile connection, and Telegram doesn't have access to the device's microphone.
* You're trying to make a test call to yourself. For example, while making a call via mobile connection (thereby blocking the microphone), the call comes in through Telegram, and due to the other active call, the new Telegram call is rejected.
**Solution**
1. Identify the problematic device: each of your devices must be disconnected from the internet in turn until the incoming calls stop dropping. After that, the problematic device needs to be restarted or the Telegram application should be completely unloaded from memory on it.
2. Make a test call involving two different devices, and ensure that your Telegram account is not used on the second device.
3. If the problem repeats, collect logs from the problematic device for further analysis and troubleshooting. See [Getting Log Files from Telegram](https://telegra.ph/Telegram-App-Logs-11-02) for details.
When you send a number to the chat, the bot tries to call you back (callback). If you don't accept the incoming call in Telegram, the outgoing call won't happen.
**What to do**:
* Enable call notifications in Telegram.
* Check that calls are allowed from **@siptg**.
* Confirm the incoming call within 60 seconds.
This is most often related to codec incompatibility or UDP traffic blocking.
**Solution**
1. In the [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) bot in the `/softphone` section, select the SIP account, click and set a short list, for example: `opus,alaw,mulaw`.
If necessary, specify a specific audio codec (for example, only `alaw` or `mulaw`).
2. If the call is coming from abroad or through mobile internet, try another Worker server.
This is due to the free subscription. To remove the restriction — activate the Softphone subscription. See more at [Subscriptions Overview](/en/docs/subscriptions/pricing).
This is most often due to an unstable internet connection between the Telegram user and our server.
**Solution**
1. Allow peer-to-peer calls in Telegram settings:
☰ → Settings → Privacy and Security → Calls → Peer-to-peer → Always Allow → Add Users → **@siptg**
2. Change the connection type and device; try calling from your computer via Wi-Fi.
3. In the [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) bot in the `/softphone` section, select the SIP account, click **Worker** and choose another server that is closer in geographical location.
**Symptoms**
* During an outgoing or incoming call, the subscriber can't be heard, or the sound suddenly disappears.
* The call drops within 5-10 seconds.
**Possible causes**
* Unsuitable or conflicting audio codec.
* The provider or PBX doesn't accept the current set of codecs, or Telegram doesn't have time to negotiate the audio stream parameters.
* Incorrect RTP settings or errors in voice packet transmission.
**Solution**
1. In the [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) bot in the `/softphone` section, select the SIP account, click and set a short list, for example: `opus,alaw,mulaw`.
If necessary, specify a specific audio codec (for example, only `alaw` or `mulaw`).
2. Check the Worker server and firewall settings.
**Symptoms**
* When trying to make an outgoing call, the bot reports that there are no available lines.
* Possibly, a code error appears in the logs indicating line unavailability.
**Possible causes**
* Incorrectly configured "Dialing Rules" that exclude correct numbers.
* Exceeded the number of active SIP accounts allowed by the subscription.
* Errors in SIP account parameters (incorrect login, server, or password).
**Solution**
1. Check the current rules: in the `/softphone` section of the [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) select the SIP account. To reset the dialing rules, click and enter the value `=`.
2. Make sure that the total number of SIP accounts corresponds to the paid subscription.
3. Try to restart the SIP account: in the `/softphone` section of the [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) click and then .
**Symptoms**
* The bot reports that the limits of unsuccessful calls have been exceeded or that the current SIP account is not allowed by the tariff.
* Calls don't go through due to exceeding established limits.
**Possible causes**
* The user has independently activated a SIP account without linking it to the administrated subscription.
* Internal limitations of the tariff plan have been exceeded (for example, the number of unsuccessful attempts).
* SIP accounts are incorrectly distributed or activated.
**Solution**
1. Check that the SIP account is enabled and linked in the `/softphone` section of the bot.
2. Compare the number of active accounts with the data in the `/subscriptions` section.
3. If the account was activated independently, contact support to reconfigure it for administration.
**Symptoms**
* When I try to call, an error appears that the account is not started and the call does not start.
* In the `/softphone` section, the account is marked with the ⚠️ icon, and in the settings, the Domain / Proxy / Template fields have such an icon.
**Possible causes**
* Temporary outage in the SIP.TG infrastructure: no communication between Manager and Worker servers.
* Temporary outage on the side of the telephony provider or PBX: no communication between Worker and PBX/provider servers.
**Solution**
1. Change the Worker server to a different one in the `/softphone` section of the bot.
2. Wait for the connection to be restored.
Usually errors of this type are recovered automatically after a short time.
**Symptoms**
* When enabling a SIP account, the error "Invalid parameters (params)" appears. The account remains not connected.
**Possible causes**
* Required connection parameters are not specified: , , and .
* The selected **Settings Template** doesn't contain a preset value for and for connection.
**Solution**
1. Set the correct value for the and parameters (if it's different), and re-enable the SIP account.
**Symptoms**
* When enabling a SIP account, after some waiting the error "Time out (timeout)" appears. The account remains not connected.
**Possible causes**
* Incorrect SIP server address specified.
* Firewall is active on the SIP server.
* SIP server accepts requests on a non-standard port.
* The server's DNS name returns an incorrect IP address or multiple IP addresses.
* The server's DNS name returns an IPv6 address, but the SIP server is running only on IPv4.
**Solution**
1. Set the correct value for the and parameters (if it's different), and re-enable the SIP account.
2. For , specify the IP address explicitly, leaving pointing to the DNS name.
3. Check the receipt of SIP packets using the `sngrep` or `tcpdump` utilities.
4. Check the Firewall rules. Set up automatic updates of the whitelist IP addresses from the file `https://files.sip.tg/fw.txt`.
**Symptoms**
* Call recording only works if it's enabled manually during each call.
* Call recording stops after 15 seconds.
**Possible causes**
* The setting is not enabled in the SIP account settings.
* When paying for the "Softphone" subscription, the "Call Recording" option was not added.
**Solution**
1. Check the status of the SIP account settings. See [Configuring the Softphone](/en/docs/softphone/settings) for details.
2. Add the "Call Recording" option in the subscription settings. See [Softphone Subscription](/en/docs/subscriptions/pricing#softphone) for details.
**Symptoms**
* In the `/softphone` section of the bot, there are no buttons with account settings (, , , , Worker, , , ). There are only and buttons.
**Possible causes**
* You are a User of the SIP account, but not the Owner.
**Solution**
1. Contact the owner of the SIP account with a request to change your settings.
See [Owner and User roles for SIP account](/en/docs/softphone/settings#roles) for more details.
* **403 Forbidden**: incorrect password/login, or the provider has blocked you.
* **404 Not Found**: incorrect SIP domain or subscriber number not found.
* **408 Request Timeout**: the provider is not responding, try another Worker or check the firewall.
* **503 Service Unavailable**: the operator is experiencing temporary problems or Telegram limits have been exceeded (Too Many Requests).
* **603 Declined**: the call is rejected by the operator or the called party.
* **Telegram limitations with mass calls**:\
With a large number of outgoing calls, the system may issue `503 Too Many Requests` or `408 Timeout of waiting RPC result` errors. The solution is to reduce the speed of dialing.
* **Problems with DTMF**:\
If button presses are not recognized when interacting with the voice menu (IVR), change the DTMF transmission method in the settings (for example, switch from `inband` to `RFC2833` or `INFO`).
* **Problems with registration on the Worker server**:\
Sometimes SIP registration doesn't occur because the Worker server doesn't respond or the IP address isn't on the "whitelist". The solution is to check network settings and add the necessary IPs to the whitelist.
* **Conflicts when independently updating settings**:\
If users independently change SIP account parameters (for example, audio codecs, dialing rules), this can lead to errors in mass management. Centralized administration through a common "admin" account is recommended.
If the described actions didn't help, ask for assistance. See [How to Get Help](/en/docs#help) for details.
# Softphone Setup
Source: https://www.sip.tg/en/docs/softphone/settings
## Owner and user roles of SIP account
**SIP account Owner** — a Telegram user who creates a SIP account in the [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) bot. The owner has full control over creating, deleting, and changing SIP account settings, and can also assign accounts to other users.
**SIP account User** — a person to whom the owner has assigned a SIP account. They can use the account to make and receive calls, but cannot change the settings of the account itself.
The subscription for the softphone must be activated to the Telegram account of the **Owner**. The user's subscription has no effect on SIP accounts that belong to other owners!
## Principle of interaction with settings buttons
Most settings are displayed directly on the buttons in the form of current values. To change these settings, simply press the corresponding button and enter a new value as requested by the bot.
However, some buttons work differently:
* **Worker**: when pressed, a list of available Worker servers appears. Select the desired server from the list to assign it.
* **Buttons with checkboxes**: such as "Call Recording", work as toggles. One press activates or deactivates the option.
* : when pressed for the first time, an additional button for selecting a chat will appear. By pressing this button, you will see a list of chats and channels available for selection. Choose a suitable chat for call recordings to be saved there.
* : when pressed for the first time, an additional button for selecting a user will appear. By pressing this button, you can select another Telegram user to whom this SIP account will be assigned.
* **Connection protocol (UDP/TCP/TLS)**: each press switches to the next available protocol.
## Step by step setup
* Launch the [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) bot.
* Go to the `/softphone` section.
* Press the button to create a new SIP account.
* Enter the login and password received from your IP telephony provider or SIP PBX.
Don't use your login and password simultaneously in multiple programs (widgets, other softphones, or telephones). This can result in lost incoming calls and is due to the nature of the SIP protocol. You must create a separate SIP account in your PBX for each program (device).
* Specify the domain (SIP server address).
* If necessary, specify a separate Registrar Proxy (registration server).
* Prepared settings of the IP telephony operator can also be selected from the catalog, which is accessible via the button.
* Select the transport protocol: UDP, TCP, or TLS.
* Select and configure audio codecs supported by your provider.
* Configure the DTMF signal transmission method (RFC2833, INFO, inband).
* Set rules for transforming numbers for outgoing calls.
* Check in the SIP provider/PBX account that the account is registered.
* Try an outgoing call (send a number to the [@siptg](https://t.me/siptg) chat).
* If everything is well, try an incoming call (to the SIP account number).
* For authorization errors or problems, see [Troubleshooting](/en/docs/softphone/problems).
* If necessary, so that calls go not to you but to another employee, assign a Telegram user to this SIP account (button ).
* Now all calls will go to the employee, and you will receive notifications if there is a problem with the SIP account.
* : enable the option and select a chat for storing recordings.
* : for changing the format of the dialed number (for example, +7 → 8).
Some settings take effect after pressing the button, or after 5 minutes. After completing the steps, the account will become active and ready to work.
## Available settings
The choice of codecs affects the quality and compatibility of voice communication. Opus, alaw, mulaw, GSM, and other codecs are supported.
DTMF is necessary for interacting with voice menus. Available methods are RFC2833 (recommended), INFO, and inband.
You can activate or deactivate automatic call recording, and also select a separate chat or channel for saving audio recordings.
Allows assigning SIP accounts to other Telegram users, giving them the ability to use accounts for calls without access to settings.
Allows you to select the server that will connect to the PBX or telephony provider.
There are 4 types of servers:
| Server type | Description | Designation |
| ----------------------------------- | ------------------------------------------------------------------------- | ----------- |
| SIP.TG public servers | Main servers supported by SIP.TG | ✅ |
| Public servers of other users | Publicly available servers hosted by other users | 🌐 |
| Public servers of telecom providers | Available with some Settings Templates, provided by third-party providers | 📡 |
| Private servers | Your own servers, available only for your SIP accounts | 🔑 |
On a free subscription, only some of the SIP.TG public servers are available.
Allow transforming the number for an outgoing call before sending it to the SIP provider or PBX, as well as removing unsuitable SIP accounts from the line selection request for a call (for example, if you prefer to make calls to different countries through different SIP accounts).
See the detailed description in the [Transforming outgoing numbers](#dialing-rules) section.
## Transforming outgoing numbers
Sometimes for outgoing calls, it's necessary to automatically change the dialed number to meet the requirements of the SIP provider or PBX (for example, replace the first "8" with "+7" or remove spaces and brackets). In SIP.TG, this is configured using **Transformation Rules** in the SIP account settings.
If your provider accepts numbers in any format or you're using a ready-made **Settings Template**, dialing rules are most likely not needed. Before making changes, check the requirements for the number format with your SIP provider or within the PBX.
There are 2 types of rules:
* **Rules with "="** — replacing part of the number.\
If the left part of the rule (regular expression) is found, it's replaced with the right part.
* **Rules without "="** — filter (mask).\
If the number doesn't match the regular expression, the rule interrupts processing, and the call is not made.
All rules are separated by spaces and applied in sequence. As soon as the number stops matching even one filter rule (without "="), the use of the SIP account for calling that number is not allowed. Each replacement rule (with the "=" sign) changes the number before it's checked by the following filter rules.
### Editing rules in the bot
1. In the [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) bot, go to the `/softphone` section.
2. Select the desired SIP account, press the button.
3. Enter one or more rules, separating them with spaces.
4. Confirm the changes.
5. Check with a test call that the numbers are transformed correctly.
All rules work on the "left to right" principle. Note that adding too many filters or ambiguous replacements can lead to unexpected results. For complex scenarios, test with a couple of real numbers.
### Examples
Let's consider the task: we dial numbers like "8 (926) 123-45-67", but the provider requires "7XXXXXXXXXX".
Suppose we need to remove all non-digit symbols and turn the prefix 8 into 7.
Here are two rules (written with a space):
```text theme={null}
[^+*#\w]= ^8=7
```
**The first** removes all characters except digits, letters, plus, and some special characters (\*, #, \_).\
**The second** replaces the first digit 8 with 7.
Now if the user enters `8 (926) 123-45-67`, after the first rule the string will become `89261234567`, and after the second — `79261234567`.
If you need to allow outgoing calls only to Russian mobile numbers (starting with 79 and then 9 digits), use a filter rule:
```text theme={null}
^79\d{9}$
```
Without the "=" sign. If the number doesn't match `^79\d{9}$`, the SIP account won't be used.
Sometimes you need to discard everything if the user accidentally entered an invalid number. You can use a replacement rule to empty:
```text theme={null}
.*=
```
This will cause any number to be replaced with an empty string. If an empty string doesn't suit the operator, the call won't happen.
If you encounter problems or errors, see [Troubleshooting](/en/docs/softphone/problems).
# How to Use
Source: https://www.sip.tg/en/docs/softphone/usage
By using **Softphone**, you transform Telegram into a full-fledged SIP client. After you've added and configured a SIP account via [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs), you can immediately start making calls through it using Telegram.
To use Softphone, you need to activate a subscription with the ☎️ "Softphone" label — or use the **Free subscription**, which includes a limited number of calls. For more details, see [Subscriptions Overview](/en/docs/subscriptions/pricing).
## Making Calls
After setting up a SIP account, simply send the number you want to call to the [@siptg](https://t.me/siptg) account chat.
The number can contain not only digits but also letters, if supported by your PBX. The number is subject to customizable transformation rules that allow you to clean it of unnecessary characters, set prefixes, and more. For details, see [Outgoing Number Transformation](/en/docs/softphone/settings#dialing-rules).
If you have the **Callback** mode active, immediately after sending the number, you will receive an incoming call from the **@siptg** account. After answering it, a connection with the dialed number will begin. If Callback is disabled — you need to manually press 📞 in the chat with **@siptg**.
Send the phone number or SIP address you want to call to the **@siptg** chat.
If you have multiple connected SIP accounts, you will be prompted to select a line for the call.
If using Callback mode, you'll receive an incoming call from **@siptg**. Answer it — and the connection will be established.
If Callback is disabled — after sending the number, press 📞 in the chat with **@siptg** to start the call.
During your first call, Telegram may request permission to receive calls from the **@siptg** account. Allow calls for all or add **@siptg** to exceptions.
## Incoming Calls
Incoming calls appear as regular Telegram calls from the **@siptg** account. You can accept the call from the notification menu or directly from Telegram.
The name and number of the caller (if transmitted by your PBX) come as a separate text message in the chat with @siptg **at the moment of the incoming call**. You can pull down the notification shade to see the information before answering.
To see additional information about the caller at the moment of an incoming call, enable Telegram notifications for the chat with **@siptg**.
## Call Recording
If you have paid for call recording as part of your subscription, you can enable automatic recording of all calls for each SIP account separately. This is configured when editing the SIP account in the bot. There, you can also choose where to send the recordings: to a personal chat, channel, or group. For more details, see the [Softphone Settings](/en/docs/softphone/settings) page.
A subscription with call recording activates the recording capability **for all accounts**, but enabling automatic recording is done **separately for each account**.
### Manual Recording During a Call
If your subscription does not include recording, you can manually record **a call fragment up to 15 seconds long** — the recording button is available during the conversation.
If recording is paid for, but **automatic recording is disabled**, you can manually start and stop recording at any time — **without duration limitations**. The recorded files are sent to the chat immediately after the recording is completed.
The recording control button is located under the DTMF keypad. To see it, during a call, swipe up or left on the screen and open the chat with **@siptg**.
If you are a **SIP account user**, and the account owner has enabled automatic recording and specified a separate chat for saving, you will see that the conversation is being recorded, but **you cannot stop the recording**.
## Reconnecting to call
Below the DTMF keypad, there is another button — . It lets you reconnect to the same call from your another device without interrupting the conversation (for example, you can move a call from your laptop to your phone).
It works as follows:
1. When you press the button, your call is ended, and your interlocutor is put on hold.
2. The interlocutor hears repeating reconnection tones, and you receive an incoming call (if Callback mode is enabled) or are prompted to make an outgoing call to **@siptg**.
3. If you answer or call back within 60 seconds, the conversation is resumed. Otherwise, the call is terminated.
### Connection recovering
If your connection is suddenly lost during a call (for example, your phone battery dies), the call will automatically switch to reconnection mode. Your interlocutor will hear repeating reconnection tones, and you will be able to continue the conversation from another device within 60 seconds.
If a [second parallel call](#second-call) was active during reconnection, it will be dropped. Only the active interlocutor you were talking to at the moment the call was interrupted will be put on hold.
## DTMF Keypad
During a conversation, you can use the DTMF keypad to interact with voice menus (IVR) or enter extension numbers. It appears in the chat with **@siptg** during a call and disappears after it ends.
DTMF transmission methods (RFC2833, INFO, inband) are selected in the SIP account settings. For more details, see [Softphone Settings](/en/docs/softphone/settings).
## Second Parallel Call
During an active conversation, you can accept a second incoming call or make a second outgoing call:
* If another **incoming** call arrives during a conversation, you will hear periodic beeps.
* To make a second **outgoing** call without ending the current one, simply send the number for the second call as a regular message in the **@siptg** chat.
In both cases, a new message with action buttons will appear in the **@siptg** chat:
* — ends your current conversation and connects your interlocutors with each other;
* — puts the current conversation on hold, and connect you to the new call;
* — rejects the second incoming call.
When you have two active conversations, you can continue to switch between interlocutors several times using the button, or press the button to connect the interlocutors with each other and disconnect yourself.
Another button will also appear, — it terminates the current conversation and returns you to the second interlocutor, who was on hold during this time.
## Android Phone Book
To display the caller's name from your local Android address book, we have developed an integration based on Automate:
Install the [Automate app](https://play.google.com/store/apps/details?id=com.llamalab.automate) on your Android device.
Open the link to [our script](https://llamalab.com/automate/community/flows/45201) and install it in the Automate app.
Accept all requested permissions, including access to calls and contacts.
Press the START button in the app. After this, incoming calls will display with the name from your phone book.
Share your experience in the public group [@siptg\_public](https://t.me/siptg_public) and leave reviews in the [Automate catalog](https://llamalab.com/automate/community/flows/45201)!
# Connection and Renewal
Source: https://www.sip.tg/en/docs/subscriptions/activation
## Roles of subscription customer and payer
In SIP.TG, there is a separation of roles:
* **Customer** — the Telegram user for whom the subscription is actually registered. It is on this Telegram account that subscription limits and options are in effect (for example, the number of SIP accounts or Gateway lines). The Customer may not be the Payer: one person pays, and another uses the subscription.
* **Payer** — the person whose account or card will be charged for the subscription and its renewal. They manage the financial side: choosing the payment method in the `/billing` section of the [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) bot, setting the address and name of the buyer, as well as the tax number.
For simplified interaction, the Customer and Payer can be the same person, meaning the subscription is paid for and used by the same Telegram account.
## Interaction with the bot
The main subscription management takes place in the `/subscriptions` section of the [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) bot. Here you can see active subscriptions (both your own and those for which you are assigned as the Payer) and there is a button to activate a new subscription. Selecting an active subscription will open its current state with action buttons and , as well as the status.
To change a specific option (for example, the number of SIP accounts or the duration of call recording), click and on the subscription change screen simply click on the button with its current value. The bot will prompt you to enter a new value and will indicate the acceptable values.
All options and the subscription currency are selected by the **Payer**. If the Customer and Payer are different users, then changing subscription options by the Customer may be restricted.
## Payment and taxes
The subscription is tied to a **specific currency**, which the Payer chooses when first issuing an invoice. You cannot change the subscription currency later. Payment methods are configured in the `/billing` section of the same bot — here you also specify:
* The Payer's : affects the tax scheme (for example, VAT or other tax is added);
* (if required to exempt from VAT or apply a different tax rate);
* and , required for correct invoicing.
In some cases, the bot may request additional country verification if a payment method with tax status verification is selected. Without passing such verification, payment will be refused.
### Payment methods
SIP.TG supports various payment systems:
* Bank cards (through Telegram's built-in payment tools or a third-party provider);
* PayPal (in an external window);
* Cryptocurrencies (BTC, ETH, USDT, TON, etc.);
* Bank transfer (a PDF is generated with an order number).
## Changing an active subscription
If necessary, you can change (expand or reduce) an already **active** subscription. However, the expiration date behaves differently:
* **If the subscription is expanded** (paid options are added or their quantity is increased), then the expiration date is *shortened* proportionally to the required additional payment for the remaining days of the subscription.
* **If the subscription is reduced** (paid options are decreased), then the expiration date does not change.
This mechanism avoids complex recalculations and immediately accounts for the total cost.
To change a subscription, go to the `/subscriptions` section, select the active subscription, click , specify the new parameters, and click .
## Notifications and auto-renewal
SIP.TG sends notifications to the Payer several days before the subscription expires:
* Offers to renew manually;
* Or automatically withdraws funds (if auto-renewal is enabled) from the internal balance or active card/account.
Automatic renewal maintains all current subscription options and extends them for the same period. If there are insufficient funds in the balance, automatic withdrawal may not go through, and the subscription will not be renewed.
## Internal balance
In the `/balance` section of the [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) bot, there is an *internal balance* of SIP.TG. It serves for:
* Prepayment reservation of funds (to avoid dependence on regular card withdrawals);
* Debt repayment, if you have a credit limit;
* Automatic subscription renewal (if auto-renewal is enabled).
You can top up the balance by any amount convenient for you, and it will be spent on subscription payment according to the selected options.
With regular use of services, it is convenient to keep an amount sufficient for the next renewal on the balance. This way, you avoid unexpected subscription stops in case of card withdrawal failure.
# Subscriptions Overview
Source: https://www.sip.tg/en/docs/subscriptions/pricing
SIP.TG service offers three main subscriptions: Free, Gateway, and Softphone. Choose the optimal option based on your needs.
## Current Subscriptions
Ideal for quick introduction and testing of the service's basic functions.
Using Telegram as a SIP client for any PBX or IP telecom provider.
Connecting a Telegram account to your PBX for receiving and making calls.
Offering Telegram as a SIP client to telecom provider subscribers.
### Free Subscription
The free subscription is activated automatically when launching [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs). It will allow you to test the capabilities of Gateway and Softphone, but with serious resource limitations.
Limitations:
* 1 line in Gateway mode.
* 1 SIP account for Softphone.
* Maximum total call duration: 30 minutes per month.
* Maximum duration of one call: 2 minutes.
* Up to 10 unsuccessful calls per hour.
* No support for parallel or call transfer.
* Limited number of Worker servers are available.
### Softphone Subscription
Removes restrictions on using Telegram as a SIP client.
Main features:
* Unlimited number of SIP accounts (each paid for separately).
* Call recording with saving to Telegram chats or channels.
* Assigning SIP accounts to other Telegram users.
* Providing API access for process automation.
The cost depends on the number of SIP accounts and the presence of call recording:
* **SIP account**: 3 EUR/month (without recording), or 5 EUR/month (with recording) for each account.
* **Surcharge for large teams**: 150 EUR/month when paying for more than 10 accounts.
* **API access**: free when paying for more than 10 accounts, otherwise 150 EUR/month.
Call recording is activated immediately for all accounts within the subscription. You cannot pay for some accounts with recording and others without recording.
* **Minimal option**\
1 account without recording (3 EUR) = **3 EUR/month**
* **Medium option**\
5 accounts with recording (25 EUR) = **25 EUR/month**
* **Extended option**\
12 accounts with recording (60 EUR) + surcharge for large teams (150 EUR) = **210 EUR/month**
The "Softphone" subscription should be activated to the Telegram user who will be the **Owner** of the SIP accounts. For more details, see [Owner and user roles of SIP account](/en/docs/softphone/settings#roles).
### Gateway Subscription
Removes restrictions on connecting your Telegram account to a SIP PBX.
Main features:
* Multi-channel voice calls through a Telegram account.
* Unlimited total call duration.
* Connection of additional Telegram accounts.
* Providing API access for process automation.
The cost is formed from:
* **Lines**: 15 EUR/month for each line.
* **Main Telegram account**: 15 EUR/month.
* **Additional session** (Telegram account): 150 EUR/month for each session.
* **Surcharge for large teams**: 150 EUR/month when paying for more than 5 lines.
* **API access**: free when paying for more than 5 lines, otherwise 150 EUR/month.
- **Minimal option**\
1 line (15 EUR) + 1 account (15 EUR) = **30 EUR/month**
- **Medium option**\
3 lines (45 EUR) + 1 account (15 EUR) = **60 EUR/month**
- **Extended option**\
6 lines (90 EUR) + surcharge for the 6th line (150 EUR) + 1 main account (15 EUR) + 1 additional account (150 EUR) = **405 EUR/month**
In general, the "Gateway" subscription should be activated to the **Session Account** that will be used for calls.
But there are **exceptions**:
1. If you plan to frequently change the Telegram account used for calls (cold calling, account blocking, etc.) and want to avoid purchasing a subscription for every new Telegram account.
2. If you want to connect several Telegram accounts for calls (one for support, another for sales, etc.) and keep a single subscription.
In the above exceptions, the "Gateway" subscription must be activated to the **Administrator Account** with option ≥ 1, and in the settings of each additional session you need to enable the option.
For more details, see [Session and Administrator Account Roles](/en/docs/gateway/telegram#roles).
### Softphone for Provider Subscription
Allows IP telecom provider to offer their customers the SIP.TG Softphone as a SIP client. Using our API, you can integrate SIP settings assignment to a Telegram user through the subscriber's cabinet and make your services more convenient.
The subscription cost is available upon request.
## Payment Period and Discounts
Services can only be paid for the period specified in the table. Depending on the payment period, a discount is applied.
| Payment Period | Discount |
| -------------- | ----------- |
| 6 months | No discount |
| 12 months | 10% |
| 36 months | 30% |
When paying for services through our partners, special conditions may apply, including monthly/quarterly payments and implementation assistance. Find a suitable partner in the [Solutions Catalog](/en/catalog) section and learn about the conditions.
# Troubleshooting
Source: https://www.sip.tg/en/docs/subscriptions/problems
## Frequently Asked Questions
Previously, there were indeed "trial"/"starter" plans. Now everything has been replaced with three subscriptions:
* **"Free"** — provides basic functionality for testing, with limited minutes and no call recording.
* **"Softphone"** — a paid subscription for using Telegram as a SIP client (multiple SIP accounts, call recording, etc.).
* **"Gateway"** — a paid subscription for using a Telegram account as a SIP trunk for PBX (receiving/making calls through a single Telegram account).
If you want to connect your Telegram for incoming/outgoing calls through a PBX (SIP trunk), choose "Gateway". If you need to connect IP telephony/PBX accounts to Telegram for personal or team calls, use "Softphone".
It is **not possible** to transfer a subscription. In exceptional cases it is possible to terminate the subscription with crediting of funds to the balance in proportion to the unused validity period of the old subscription.
To check the possibility, write to support [@siptg\_support](https://t.me/siptg_support) from the account on which the subscription is paid, indicating:
1. Which account is the Payer and current Customer of the subscription;
2. Which account becomes the new Customer of the subscription;
3. The reason for the transfer.
Support will check if the subscription can be interrupted and report the results.
In some cases, it's easier to assign SIP accounts to another user than to transfer the entire subscription.
By default, after paying for a subscription, auto-renewal is enabled (if you saved a card or have a positive balance). A few days before the end of the next period, the bot tries to renew the subscription automatically.
* To disable auto-renewal, go to the [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) bot's `/subscriptions` section, select the active subscription, and uncheck .
* Funds already withdrawn for the current period are not automatically returned, but you can discuss the possibility of a partial refund with support, depending on the conditions.
In the `/subscriptions` section of the [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) bot, you can choose the payment period: 6 months (no discounts), 12 months (10% discount), or 36 months (30% discount). For the "Gateway" and "Softphone" subscriptions, monthly payment is not directly provided, but you can pay for six months and opt out of auto-renewal.
If you need more flexibility (for example, monthly or quarterly), **our partners** can help — for more details, see [Solutions Catalog](/en/catalog?tags=pay).
* In the [@siptg\_bot](https://t.me/siptg_bot?start=utm_docs) bot, open `/subscriptions` to see active subscriptions and their renewal date.
* If you can't figure out which Telegram account is being charged, contact support [@siptg\_support](https://t.me/siptg_support) with a confirming payment document (or a screenshot of the transaction). Specialists will find which account the subscription is linked to.
In the `/paysystem` section of the bot, you can choose the payment method (bank cards, PayPal, cryptocurrency, invoice for legal entities, etc.).
* Currency selection depends on the specific payment provider;
* If your local currency is not available, there will be a conversion.
* You can also pay for services through **our partners** in different countries — for more details, see [Solutions Catalog](/en/catalog?tags=pay).
Starting from the 9th of July 2025, we have obtained VAT payer status and received VAT number LT100018548216. This number will be included in all new invoices starting from the specified date.
There is a confusion between the roles of SIP Account Owner, SIP Account User, Customer and Payer. In the described case, the employee is considered as a Customer (because a subscription was activated in his name), and the SIP account owner (the one who assigned the employee as a User) is considered as a Payer.
Since the subscription does not apply to the Payer (if the Customer and the Payer are different persons), the SIP Account Owner is remaining with a free subscription, so he cannot assign Users to his SIP accounts.
In order for there to be no restrictions, the Softphone Subscription Customer must strictly be a SIP Account Owner.
See more at [Owner and user roles of SIP account](/en/docs/softphone/settings#roles).
I am trying to enter the subscription renewal period (for example, 12 months), but the renewal period is reset (for example, it becomes 1 month).
This is due to renewing too early. Try renewing the subscription closer to the expiration date or contact support [@siptg\_support](https://t.me/siptg_support) with a request to renew the subscription in advance.
If you still have questions, contact us for help. For more details, see [How to Get Help](/en/docs#help).
# We connect SIP telephony and Telegram calls
Source: https://www.sip.tg/en/home
Forward calls from personal or business phone numbers to Telegram. Use Telegram as a reliable softphone for your SIP accounts.\
\
The perfect addition to office telephony for teams of any size. A solution for collecting calls from many numbers or making calls from your number while roaming or abroad.
Receive and make voice calls through your company's Telegram account — in any volume.\
\
Your business can now stay voice-connected — one tap away from your Telegram sales or marketing channel.\
\
Route Telegram calls to support or sales teams via PBX and integrate with your CRM.
## Key Advantages
Multiple simultaneous calls and flexible call routing scenarios: from simple to highly complex.
SIP.TG servers operate in multiple data centers to minimize call latency.
Supports Asterisk, 3CX, FreeSWITCH, Oktell, Yate, Panasonic, and many more.
TLS/SRTP encryption, granular roles and permissions, dedicated Worker servers.
Free subscription, configuration bot, and detailed documentation to help you get started quickly.
## Ready to Connect?
Our directory includes PBX developers, integrators, and VoIP providers from around the world. They can implement SIP.TG turn-key, help you pay for services, and provide financial documentation.
We offer detailed documentation, and all settings are managed through a dedicated Telegram bot. If you have any questions, you can get help in the public group and through artificial intelligence.
This project was developed by a winner of the Telegram competition for improving the voice call infrastructure and core components of the messenger.
# Privacy and Cookies Policy
Source: https://www.sip.tg/en/privacy
Last updated: 2026-08-31
## Owner and Data Controller
MB "Žinučių linija", company code 305133662, V. Nagevičiaus g. 3, Vilnius 08237, Lithuania
**Owner contact email:** [info@sip.tg](mailto:info@sip.tg)
**Owner contact Telegram:** [@siptg\_support](https://t.me/siptg_support)
Since the use of third-party Trackers through SIP.TG cannot be fully controlled by the Owner, any specific references to third-party Trackers are to be considered indicative. In order to obtain complete information, Users are kindly requested to consult the privacy policies of the respective third-party services listed in this document.
Given the objective complexity surrounding tracking technologies, Users are encouraged to contact the Owner should they wish to receive any further information on the use of such technologies by SIP.TG.
## Definitions and legal references
* **Personal Data (or Data)**
Any information that directly, indirectly, or in connection with other information — including a personal identification number — allows for the identification or identifiability of a natural person.
* **Usage Data**
Information collected automatically through SIP.TG (or third-party services employed in SIP.TG), which can include: the IP addresses or domain names of the computers utilized by the Users who use SIP.TG, the URI addresses (Uniform Resource Identifier), the time of the request, the method utilized to submit the request to the server, the size of the file received in response, the numerical code indicating the status of the server's answer (successful outcome, error, etc.), the country of origin, the features of the browser and the operating system utilized by the User, the various time details per visit (e.g., the time spent on each page within the Application) and the details about the path followed within the Application with special reference to the sequence of pages visited, and other parameters about the device operating system and/or the User's IT environment.
* **User**
The individual using SIP.TG who, unless otherwise specified, coincides with the Data Subject.
* **Data Subject**
The natural person to whom the Personal Data refers.
* **Data Processor (or Processor)**
The natural or legal person, public authority, agency or other body which processes Personal Data on behalf of the Controller, as described in this privacy policy.
* **Data Controller (or Owner)**
The natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of Personal Data, including the security measures concerning the operation and use of SIP.TG. The Data Controller, unless otherwise specified, is the Owner of SIP.TG.
* **SIP.TG (or this Application)**
The means by which the Personal Data of the User is collected and processed.
* **Service**
The service provided by SIP.TG as described in the relative terms (if available) and on this site/application.
* **European Union (or EU)**
Unless otherwise specified, all references made within this document to the European Union include all current member states to the European Union and the European Economic Area.
* **Cookie**
Cookies are Trackers consisting of small sets of data stored in the User's browser.
* **Tracker**
Tracker indicates any technology — e.g Cookies, unique identifiers, web beacons, embedded scripts, e-tags and fingerprinting — that enables the tracking of Users, for example by accessing or storing information on the User’s device.
### Legal information
This privacy policy relates solely to SIP.TG, if not stated otherwise within this document.
## Types of Data collected
Among the types of Personal Data that SIP.TG collects, by itself or through third parties, there are: Trackers; Usage Data; number of Users; session statistics; payment info.
Complete details on each type of Personal Data collected are provided in the dedicated sections of this privacy policy or by specific explanation texts displayed prior to the Data collection.
Personal Data may be freely provided by the User, or, in case of Usage Data, collected automatically when using SIP.TG.
Unless specified otherwise, all Data requested by SIP.TG is mandatory and failure to provide this Data may make it impossible for SIP.TG to provide its services. In cases where SIP.TG specifically states that some Data is not mandatory, Users are free not to communicate this Data without consequences to the availability or the functioning of the Service.
Users who are uncertain about which Personal Data is mandatory are welcome to contact the Owner.
Any use of Cookies — or of other tracking tools — by SIP.TG or by the owners of third-party services used by SIP.TG serves the purpose of providing the Service required by the User, in addition to any other purposes described in the present document and in the Cookie Policy.
Users are responsible for any third-party Personal Data obtained, published or shared through SIP.TG.
## Mode and place of processing the Data
### Methods of processing
The Owner takes appropriate security measures to prevent unauthorized access, disclosure, modification, or unauthorized destruction of the Data.
The Data processing is carried out using computers and/or IT enabled tools, following organizational procedures and modes strictly related to the purposes indicated. In addition to the Owner, in some cases, the Data may be accessible to certain types of persons in charge, involved with the operation of SIP.TG (administration, sales, marketing, legal, system administration) or external parties (such as third-party technical service providers, mail carriers, hosting providers, IT companies, communications agencies) appointed, if necessary, as Data Processors by the Owner. The updated list of these parties may be requested from the Owner at any time.
### Place
The Data is processed at the Owner's operating offices and in any other places where the parties involved in the processing are located.
Depending on the User's location, data transfers may involve transferring the User's Data to a country other than their own. To find out more about the place of processing of such transferred Data, Users can check the section containing details about the processing of Personal Data.
### Retention time
Unless specified otherwise in this document, Personal Data shall be processed and stored for as long as required by the purpose they have been collected for and may be retained for longer due to applicable legal obligation or based on the Users’ consent.
## Cookies Policy
This document informs Users about the technologies that help SIP.TG to achieve the purposes described below. Such technologies allow the Owner to access and store information (for example by using a Cookie) or use resources (for example by running a script) on a User’s device as they interact with SIP.TG.
For simplicity, all such technologies are defined as "Trackers" within this document – unless there is a reason to differentiate.
For example, while Cookies can be used on both web and mobile browsers, it would be inaccurate to talk about Cookies in the context of mobile apps as they are a browser-based Tracker. For this reason, within this document, the term Cookies is only used where it is specifically meant to indicate that particular type of Tracker.
Some of the purposes for which Trackers are used may also require the User's consent. Whenever consent is given, it can be freely withdrawn at any time following the instructions provided in this document.
SIP.TG uses Trackers managed directly by the Owner (so-called “first-party” Trackers) and Trackers that enable services provided by a third-party (so-called “third-party” Trackers). Unless otherwise specified within this document, third-party providers may access the Trackers managed by them.
The validity and expiration periods of Cookies and other similar Trackers may vary depending on the lifetime set by the Owner or the relevant provider. Some of them expire upon termination of the User’s browsing session.
In addition to what’s specified in the descriptions within each of the categories below, Users may find more precise and updated information regarding lifetime specification as well as any other relevant information — such as the presence of other Trackers — in the linked privacy policies of the respective third-party providers or by contacting the Owner.
### How to manage preferences and provide or withdraw consent
There are various ways to manage Tracker related preferences and to provide and withdraw consent, where relevant:
Users can manage preferences related to Trackers from directly within their own device settings, for example, by preventing the use or storage of Trackers.
Additionally, whenever the use of Trackers is based on consent, Users can provide or withdraw such consent by setting their preferences within the cookie notice or by updating such preferences accordingly via the relevant consent-preferences privacy widget, if available.
It is also possible, via relevant browser or device features, to delete previously stored Trackers, including those used to remember the User’s initial consent preferences.
Other Trackers in the browser’s local memory may be cleared by deleting the browsing history.
With regard to any third-party Trackers, Users can manage their preferences via the related opt-out link (where provided), by using the means indicated in the third party's privacy policy, or by contacting the third party.
### Locating Tracker Settings
Users can, for example, find information about how to manage Cookies in the most commonly used browsers at the following addresses:
* [Google Chrome](https://support.google.com/chrome/answer/95647?hl=en\&p=cpn_cookies)
* [Mozilla Firefox](https://support.mozilla.org/en-US/kb/enable-and-disable-cookies-website-preferences)
* [Apple Safari](https://support.apple.com/guide/safari/manage-cookies-and-website-data-sfri11471/)
* [Microsoft Internet Explorer](http://windows.microsoft.com/en-us/windows-vista/block-or-allow-cookies)
* [Microsoft Edge](https://support.microsoft.com/en-us/help/4027947)
* [Brave](https://support.brave.com/hc/en-us/articles/360022806212-How-do-I-use-Shields-while-browsing)
* [Opera](https://help.opera.com/en/latest/web-preferences/#cookies)
Users may also manage certain categories of Trackers used on mobile apps by opting out through relevant device settings such as the device advertising settings for mobile devices, or tracking settings in general (Users may open the device settings and look for the relevant setting).
### Consequences of denying the use of Trackers
Users are free to decide whether or not to allow the use of Trackers. However, please note that Trackers help SIP.TG to provide a better experience and advanced functionalities to Users (in line with the purposes outlined in this document). Therefore, if the User chooses to block the use of Trackers, the Owner may be unable to provide related features.
## The purposes of processing
The Data concerning the User is collected to allow the Owner to provide its Service, comply with its legal obligations, respond to enforcement requests, protect its rights and interests (or those of its Users or third parties), detect any malicious or fraudulent activity, as well as the following: Access to third-party accounts, Analytics, Tag Management and Handling payments.
For specific information about the Personal Data used for each purpose, the User may refer to the section “Detailed information on the processing of Personal Data”.
## Telegram data retrieved by SIP.TG
SIP.TG may ask for some Telegram permissions allowing it to perform actions with the User's Telegram account and to retrieve information, including Personal Data, from it. This service allows SIP.TG to connect with the User's account on the Telegram Messenger, provided by Telegram Messenger Inc.
For more information about the permissions, refer to the [Telegram privacy policy](https://telegram.org/privacy/).
## Detailed information on the processing of Personal Data
Personal Data is collected for the following purposes and using the following services:
### Access to third-party accounts
This type of service allows SIP.TG to access the Data from your account and perform actions with it.
These services are not activated automatically, but require explicit authorization by the User.
* **Telegram account access**
This service allows SIP.TG to connect with the User's account on the Telegram Messenger, provided by Telegram Messenger Inc.
Place of processing: European Union.
### Analytics & marketing
SIP.TG uses Trackers to measure traffic and analyze User behavior to improve the Service.
The services contained in this section enable the Owner to monitor and analyze web traffic and can be used to keep track of User behavior.
* **Google Analytics 4 (Google Ireland Limited)**
Google Analytics 4 is a web analysis service provided by Google Ireland Limited (“Google”). Google utilizes the Data collected to track and examine the use of SIP.TG, to prepare reports on its activities and share them with other Google services.
Google may use the Data collected to contextualize and personalize the ads of its own advertising network.
In Google Analytics 4, IP addresses are used at collection time and then discarded before Data is logged in any data center or server. Users can learn more by consulting [Google’s official documentation](https://support.google.com/analytics/answer/12017362?hl=en\&ref_topic=2919631).
In order to understand Google's use of Data, consult [Google's partner policy](https://www.google.com/policies/privacy/partners/).
Personal Data processed: number of Users, session statistics, Trackers and Usage Data.
Place of processing: Ireland — [Privacy Policy](https://business.safety.google/privacy/) — [Opt Out](https://tools.google.com/dlpage/gaoptout?hl=en).
Storage of Cookies duration:
* `_ga`: 2 years
* `_ga_*`: 2 years
* **Yandex Metrica (YANDEX, LLC)**
Yandex Metrica is an analytics and heat mapping service provided by YANDEX, LLC.
Yandex Metrica is used to display the areas of SIP.TG that Users interact with most frequently. This shows where the points of interest are.
Personal Data processed: Trackers; Usage Data.
Place of processing: Russian Federation — [Privacy Policy](https://yandex.com/legal/confidential/?lang=en).
Storage of Cookies duration:
* `_ym_metrika_enabled`: 1 hour
* `_ym_isad`: 2 days
* `_ym_uid`: 1 year
* `_ym_d`: 1 year
* `_ym_ucs`: 1 year
* `gdpr`: up to 2 years
* `_ym_debug`: duration of the session
* `_ym_visorc_*`: 30 minutes
* `_ym_hostIndex`: 1 day
* `_ym_sup_debug`: 1 day
* **Referral program**
Referral program is managed by the Owner. We track the source from which the User come from.
Personal Data processed: Trackers.
Place of processing: European Union.
Storage of Cookies duration:
* `partner`: 30 days
### Handling payments
Unless otherwise specified, SIP.TG processes any payments by credit card, bank transfer or other means via external payment service providers. In general and unless where otherwise stated, Users are requested to provide their payment details and personal information directly to such payment service providers. SIP.TG isn't involved in the collection and processing of such information: instead, it will only receive a notification by the relevant payment service provider as to whether payment has been successfully completed.
* **Stripe (Stripe Payments Europe, Limited)**
Stripe is a payment service provided by Stripe Payments Europe, Limited.
Personal Data processed: payment info.
Place of processing: European Union — [Privacy Policy](https://stripe.com/ie/privacy).
* **PayPal (PayPal Inc.)**
PayPal is a payment service provided by PayPal Inc., which allows Users to make online payments.
Personal Data processed: payment info.
Place of processing: See the PayPal privacy policy — [Privacy Policy](https://www.paypal.com/webapps/mpp/ua/privacy-full).
* **Smart Glocal (Smart Glocal Services Limited)**
Smart Glocal is a payment service provided by Smart Glocal Services Limited, which allows Users to make online payments.
Personal Data processed: payment info.
Place of processing: Hong Kong — [Privacy Policy](https://smart-glocal.com/privacy-policy).
* **NOWPayments (NOWPayments Ltd.)**
NOWPayments is a payment service provided by NOWPayments Ltd., which allows Users to make online payments.
Personal Data processed: payment info.
Place of processing: See the NOWPayments privacy policy — [Privacy Policy](https://nowpayments.io/doc/privacy-policy.pdf).
## Further Information for Users
### Legal basis of processing
The Owner may process Personal Data relating to Users if one of the following applies:
* Users have given their consent for one or more specific purposes.
* provision of Data is necessary for the performance of an agreement with the User and/or for any pre-contractual obligations thereof;
* processing is necessary for compliance with a legal obligation to which the Owner is subject;
* processing is related to a task that is carried out in the public interest or in the exercise of official authority vested in the Owner;
* processing is necessary for the purposes of the legitimate interests pursued by the Owner or by a third party.
In any case, the Owner will gladly help to clarify the specific legal basis that applies to the processing, and in particular whether the provision of Personal Data is a statutory or contractual requirement, or a requirement necessary to enter into a contract.
### Further information about retention time
Unless specified otherwise in this document, Personal Data shall be processed and stored for as long as required by the purpose they have been collected for and may be retained for longer due to applicable legal obligation or based on the Users’ consent.
Therefore:
* Personal Data collected for purposes related to the performance of a contract between the Owner and the User shall be retained until such contract has been fully performed.
* Personal Data collected for the purposes of the Owner’s legitimate interests shall be retained as long as needed to fulfill such purposes. Users may find specific information regarding the legitimate interests pursued by the Owner within the relevant sections of this document or by contacting the Owner.
The Owner may be allowed to retain Personal Data for a longer period whenever the User has given consent to such processing, as long as such consent is not withdrawn. Furthermore, the Owner may be obliged to retain Personal Data for a longer period whenever required to fulfil a legal obligation or upon order of an authority.
Once the retention period expires, Personal Data shall be deleted. Therefore, the right of access, the right to erasure, the right to rectification and the right to data portability cannot be enforced after expiration of the retention period.
### The rights of Users based on the General Data Protection Regulation (GDPR)
Users may exercise certain rights regarding their Data processed by the Owner.
In particular, Users have the right to do the following, to the extent permitted by law:
* **Withdraw their consent at any time.** Users have the right to withdraw consent where they have previously given their consent to the processing of their Personal Data.
* **Object to processing of their Data.** Users have the right to object to the processing of their Data if the processing is carried out on a legal basis other than consent.
* **Access their Data.** Users have the right to learn if Data is being processed by the Owner, obtain disclosure regarding certain aspects of the processing and obtain a copy of the Data undergoing processing.
* **Verify and seek rectification.** Users have the right to verify the accuracy of their Data and ask for it to be updated or corrected.
* **Restrict the processing of their Data.** Users have the right to restrict the processing of their Data. In this case, the Owner will not process their Data for any purpose other than storing it.
* **Have their Personal Data deleted or otherwise removed.** Users have the right to obtain the erasure of their Data from the Owner.
* **Receive their Data and have it transferred to another controller.** Users have the right to receive their Data in a structured, commonly used and machine readable format and, if technically feasible, to have it transmitted to another controller without any hindrance.
* **Lodge a complaint.** Users have the right to bring a claim before their competent data protection authority.
Users are also entitled to learn about the legal basis for Data transfers abroad including to any international organization governed by public international law or set up by two or more countries, such as the UN, and about the security measures taken by the Owner to safeguard their Data.
### Details about the right to object to processing
**Where Personal Data is processed for a public interest, in the exercise of an official authority vested in the Owner or for the purposes of the legitimate interests pursued by the Owner, Users may object to such processing by providing a ground related to their particular situation to justify the objection.**
**Users must know that, however, should their Personal Data be processed for direct marketing purposes, they can object to that processing at any time, free of charge and without providing any justification. Where the User objects to processing for direct marketing purposes, the Personal Data will no longer be processed for such purposes. To learn whether the Owner is processing Personal Data for direct marketing purposes, Users may refer to the relevant sections of this document.**
### How to exercise these rights
Any requests to exercise User rights can be directed to the Owner through the contact details provided in this document. Such requests are free of charge and will be answered by the Owner as early as possible and always within one month, providing Users with the information required by law. Any rectification or erasure of Personal Data or restriction of processing will be communicated by the Owner to each recipient, if any, to whom the Personal Data has been disclosed unless this proves impossible or involves disproportionate effort. At the Users’ request, the Owner will inform them about those recipients.
## Additional information about Data collection and processing
### Legal action
The User's Personal Data may be used for legal purposes by the Owner in Court or in the stages leading to possible legal action arising from improper use of SIP.TG or the related Services.
The User declares to be aware that the Owner may be required to reveal personal data upon request of public authorities.
### Additional information about User's Personal Data
In addition to the information contained in this privacy policy, SIP.TG may provide the User with additional and contextual information concerning particular Services or the collection and processing of Personal Data upon request.
### System logs and maintenance
For operation and maintenance purposes, SIP.TG and any third-party services may collect files that record interaction with SIP.TG (System logs) or use other Personal Data (such as the IP Address) for this purpose.
### Information not contained in this policy
More details concerning the collection or processing of Personal Data may be requested from the Owner at any time. Please see the contact information at the beginning of this document.
### Changes to this privacy policy
The Owner reserves the right to make changes to this privacy policy at any time by notifying its Users on this page and possibly within SIP.TG. It is strongly recommended to check this page often, referring to the date of the last modification listed at the top.
Should the changes affect processing activities performed on the basis of the User’s consent, the Owner shall collect new consent from the User, where required.
# Service status
Source: https://www.sip.tg/en/status
Online:—
Total:—
Last updated:—
Next update in—
🔎Search services…
Loading…
Fetching monitored services…
Services
# Terms and Conditions
Source: https://www.sip.tg/en/terms
Last updated: 2026-08-31
These Terms govern
* the use of SIP.TG, and,
* any other related Agreement or legal relationship with the Owner
in a legally binding way. Capitalized words are defined in the relevant dedicated section of this document.
The User must read this document carefully.
## The Owner
MB "Žinučių linija", company code 305133662, V. Nagevičiaus g. 3, Vilnius 08237, Lithuania
**Owner contact email:** [info@sip.tg](mailto:info@sip.tg)
**Owner contact Telegram:** [@siptg\_support](https://t.me/siptg_support)
"SIP.TG" refers to
* the Service;
* any applications, sample and content files, source code, scripts, instruction sets or software included as part of the Service, as well as any related documentation.
## What the User should know at a glance
* Please note that some provisions in these Terms may only apply to certain categories of Users. In particular, certain provisions may only apply to Consumers or to those Users that do not qualify as Consumers. Such limitations are always explicitly mentioned within each affected clause. In the absence of any such mention, clauses apply to all Users.
* SIP.TG uses automatic renewal for Product subscriptions. Information about the a) renewal period, b) termination details and c) termination notice can be found in the relevant section of these Terms.
## Definitions and legal references
* **SIP.TG (or this Application)**
The property that enables the provision of the Service.
* **Agreement**
Any legally binding or contractual relationship between the Owner and the User, governed by these Terms.
* **User (or You)**
Indicates any natural person or legal entity using SIP.TG.
* **Consumer**
Is any User qualifying as such under applicable law.
* **Business User**
Any User that does not qualify as a Consumer.
* **Product**
A good or service available through SIP.TG, such as e.g. physical goods, digital files, software, booking services etc., and any other types of products separately defined herein, such as Digital Products.
* **Digital Product**
Is a Product that consists of content produced and supplied in digital form and/or a service that allows for the creation, processing, storing or accessing data in a digital form or the sharing or any other form of interaction with digital data uploaded or created by the User or any other user of SIP.TG.
* **European (or Europe)**
Applies where a User, regardless of nationality, is in the EU.
* **Owner (or We)**
Indicates the natural person(s) or legal entity that provides SIP.TG and/or the Service to Users.
* **Service**
The service provided by SIP.TG as described in these Terms and on SIP.TG.
* **Terms**
All provisions applicable to the use of SIP.TG and/or the Service as described in this document, including any other related documents or agreements, and as updated from time to time.
## Content on SIP.TG
Unless where otherwise specified or clearly recognizable, all content available on SIP.TG is owned or provided by the Owner or its licensors.
The Owner undertakes its utmost effort to ensure that the content provided on SIP.TG infringes no applicable legal provisions or third-party rights. However, it may not always be possible to achieve such a result.
In such cases, without prejudice to any legal prerogatives of Users to enforce their rights, Users are kindly asked to preferably report related complaints using the contact details provided in this document.
### Rights regarding content on SIP.TG — All rights reserved
The Owner holds and reserves all intellectual property rights for any such content.
Users may not, therefore, use such content in any way that is not necessary or implicit in the proper use of the Service.
In particular, but without limitation, Users may not copy, download, share (beyond the limits set forth below), modify, translate, transform, publish, transmit, sell, sublicense, edit, transfer/assign to third parties or create derivative works from the content available on SIP.TG, nor allow any third party to do so through the User or their device, even without the User's knowledge.
Where explicitly stated on SIP.TG, the User may download, copy and/or share some content available through SIP.TG for its sole personal and non-commercial use and provided that the copyright attributions and all the other attributions requested by the Owner are correctly implemented.
Any applicable statutory limitation or exception to copyright shall stay unaffected.
## Access to external resources
Through SIP.TG Users may have access to external resources provided by third parties. Users acknowledge and accept that the Owner has no control over such resources and is therefore not responsible for their content and availability.
Conditions applicable to any resources provided by third parties, including those applicable to any possible grant of rights in content, result from each such third parties’ terms and conditions or, in the absence of those, applicable statutory law.
## Acceptable use
SIP.TG and the Service may only be used within the scope of what they are provided for, under these Terms and applicable law.
Users are solely responsible for making sure that their use of SIP.TG and/or the Service violates no applicable law, regulations or third-party rights.
Therefore, **the Owner reserves the right to take any appropriate measure to protect its legitimate interests including by denying Users access to SIP.TG or the Service, terminating contracts, reporting any misconduct performed through SIP.TG or the Service to the competent authorities — such as judicial or administrative authorities — whenever Users engage or are suspected to engage in any of the following activities:**
* violate laws, regulations and/or these Terms;
* infringe any third-party rights;
* considerably impair the Owner’s legitimate interests;
* offend the Owner or any third party.
## Terms and conditions of sale
### Paid Products
Some of the Products provided on SIP.TG, as part of the Service, are provided on the basis of payment.
The fees, duration and conditions applicable to the purchase of such Products are described below and in the dedicated sections of SIP.TG.
### Product description
Prices, descriptions or availability of Products are outlined in the respective sections of SIP.TG and are subject to change without notice.
While Products on SIP.TG are presented with the greatest accuracy technically possible, representation on SIP.TG through any means (including, as the case may be, graphic material, images, colors, sounds) is for reference only and implies no warranty as to the characteristics of the purchased Product.
The characteristics of the chosen Product will be outlined during the purchasing process.
### Purchasing process
Any steps taken from choosing a Product to order submission form part of the purchasing process.
The purchasing process includes these steps:
* Users must choose the desired Product and verify their purchase selection.
* After having reviewed the information displayed in the purchase selection, Users may place the order by submitting it.
### Order submission
When the User submits an order, the following applies:
* The submission of an order determines contract conclusion and therefore creates for the User the obligation to pay the price, taxes and possible further fees and expenses, as specified on the order page.
* In case the purchased Product requires an action from the User, such as the provision of personal information or data, specifications or special wishes, the order submission creates an obligation for the User to cooperate accordingly.
* Upon submission of the order, Users will receive a receipt confirming that the order has been received.
### Prices
Users are informed during the purchasing process and before order submission, about any fees, taxes and costs (including, if any, delivery costs) that they will be charged.
Prices on SIP.TG are displayed excluding any applicable fees, taxes and costs.
### Methods of payment
Information related to accepted payment methods is made available during the purchasing process.
Some payment methods may only be available subject to additional conditions or fees. In such cases related information can be found in the dedicated section of SIP.TG.
All payments are independently processed through third-party services. Therefore, SIP.TG does not collect any payment information — such as credit card details — but only receives a notification once the payment has been successfully completed. The User may read the privacy policy of SIP.TG to learn more about the data processing and Users’ rights regarding their data.
If a payment through the available methods fails or is refused by the payment service provider, the Owner shall be under no obligation to fulfill the purchase order. If a payment fails or is refused, the Owner reserves the right to claim any related expenses or damages from the User.
### Retention of usage rights
Users do not acquire any rights to use the purchased Product until the total purchase price is received by the Owner.
### Fixed-term subscriptions
Paid fixed-term subscriptions allow Users to receive a Product continuously or regularly over time. It starts on the day the payment is received by the Owner and last for the subscription period chosen by the User or otherwise specified during the purchasing process.
Once the subscription period expires, the Product shall no longer be accessible.
### Automatic renewal of fixed-term subscriptions
**Subscriptions are automatically renewed through the payment method that the User chose during purchase.**
**The renewed subscription will last for a period equal to the original term.**
The User shall receive a reminder of the upcoming renewal with reasonable advance, outlining the procedure to be followed in order to cancel the automatic renewal.
### Termination
**Subscriptions may be terminated by sending a clear and unambiguous termination notice to the Owner using the contact details provided in this document, or — if applicable — by using the corresponding controls inside SIP.TG.**
**If the notice of termination is received by the Owner no later than 5 days before the subscription renews, termination shall take effect as soon as the current period is completed.**
### Terms and conditions applying to extra features
Users that have an active subscription may purchase single extra add-ons or features, described in the relevant section of SIP.TG.
Unless otherwise specified, such extras are subject to the same terms applicable to the main Product, including all provisions of this document.
## Right of withdrawal
Unless exceptions apply, the User may be eligible to withdraw from the contract within the period specified below (generally 14 days), for any reason and without justification. Users can learn more about the withdrawal conditions within this section.
### Exercising the right of withdrawal
To exercise their right of withdrawal, Users must send to the Owner an unequivocal statement of their intention to withdraw from the contract.
To this end, Users may express their intention to withdraw from the contract by making an unequivocal statement in any suitable way. In order to meet the deadline within which they can exercise such right, Users must send the withdrawal notice before the withdrawal period expires.
**Regarding the purchase of a service**, the withdrawal period expires 14 days after the day that the contract is entered into, unless the User has waived the withdrawal right.
### Effects of withdrawal
Users who correctly withdraw from a contract will be reimbursed by the Owner for all payments made to the Owner, including, if any, those covering the costs of delivery.
However, any additional costs resulting from the choice of a particular delivery method other than the least expensive type of standard delivery offered by the Owner, will not be reimbursed.
Such reimbursement shall be made without undue delay and, in any event, no later than 14 days from the day on which the Owner is informed of the User’s decision to withdraw from the contract. Unless otherwise agreed with the User, reimbursements will be made using the same means of payment as used to process the initial transaction. In any event, the User shall not incur any costs or fees as a result of such reimbursement.
## Legal guarantee of conformity for Digital Products under EU law
Under EU law, for a minimum period of 2 years from delivery or, in case of Digital Products supplied continuously for more than 2 years for the entire supply period, traders guarantee conformity of the Digital Products they provide to Consumers.
Where Users qualify as European Consumers, the legal guarantee of conformity applies to the Digital Products available on SIP.TG in accordance with the laws of the country of their habitual residence.
National laws of such country may grant Users broader rights.
## Liability and indemnification
### Indemnification
The User agrees to indemnify and hold the Owner and its subsidiaries, affiliates, officers, directors, agents, co-branders, partners and employees harmless from and against any claim or demand — including but not limited to lawyer's fees and costs — made by any third party due to or in relation with any culpable violation of these Terms, third-party rights or statutory provisions connected to the use of the Service by the User or its affiliates, officers, directors, agents, co-branders, partners and employees to the extent allowed by applicable law.
### Limitation of liability
Unless otherwise explicitly stated and without prejudice to applicable law, Users shall have no right to claim damages against the Owner (or any natural or legal person acting on its behalf).
This does not apply to damages to life, health or physical integrity, damages resulting from the breach of material contractual obligations such as any obligation strictly necessary to achieve the purpose of the contract, and/or damages resulting from intent or gross negligence, as long as SIP.TG has been appropriately and correctly used by the User.
Unless damages have been caused by way of intent or gross negligence, or they affect life, health or physical integrity, the Owner shall only be liable to the extent of typical and foreseeable damages at the moment the contract was entered into.
In particular, within the limits stated above, the Owner shall not be liable for:
* damages or losses resulting from interruptions or malfunctions of SIP.TG due to acts of force majeure, or unforeseen and unforeseeable events and, in any case, independent of the will and beyond the control of the Owner, such as, but not limited to, failures or disruptions of telephone or electrical lines, the Internet and / or other means of transmission, unavailability of websites, strikes, natural disasters, viruses and cyber attacks, interruptions in the delivery of products, third-party services or applications;
* any losses that are not the direct consequence of a breach of the Terms by the Owner;
* any loss of business opportunities and any other loss, even indirect, that may be incurred by the User (such as, but not limited to, trading losses, loss of revenue, income, profits or anticipated savings, loss of contracts or business relationships, loss of reputation or goodwill, etc.);
* any damage, prejudice or loss occurring due to viruses or other malware contained in or connected to files available for download from the internet or via SIP.TG. Users are responsible for implementing sufficient security measures — such as anti-viruses and firewalls to prevent any such infection or attack and for securing backup copies of all data or information exchanged via or uploaded to SIP.TG.
## Common provisions
### No Waiver
The Owner’s failure to assert any right or provision under these Terms shall not constitute a waiver of any such right or provision. No waiver shall be considered a further or continuing waiver of such term or any other term.
### Service interruption
To ensure the best possible service level, the Owner reserves the right to interrupt the Service for maintenance, system updates or any other changes, informing the Users appropriately.
Within the limits of law, the Owner may also decide to suspend or discontinue the Service altogether. If the Service is discontinued, the Owner will cooperate with Users to enable them to withdraw Personal Data or information and will respect Users' rights relating to continued product use and/or compensation, as provided for by applicable law.
Additionally, the Service might not be available due to reasons outside the Owner’s reasonable control, such as “force majeure” events (infrastructural breakdowns or blackouts etc.).
### Service reselling
Users may not reproduce, duplicate, copy, sell, resell or exploit any portion of SIP.TG and of its Service without the Owner’s express prior written permission, granted either directly or through a legitimate reselling programme.
### Privacy policy
To learn more about the use of their Personal Data, Users may refer to the privacy policy of SIP.TG — [Privacy and Cookies Policy](https://sip.tg/privacy).
### Intellectual property rights
Without prejudice to any more specific provision of these Terms, any intellectual property rights, such as copyrights, trademark rights, patent rights and design rights related to SIP.TG are the exclusive property of the Owner or its licensors and are subject to the protection granted by applicable laws or international treaties relating to intellectual property.
All trademarks — nominal or figurative — and all other marks, trade names, service marks, word marks, illustrations, images, or logos appearing in connection with SIP.TG are, and remain, the exclusive property of the Owner or its licensors and are subject to the protection granted by applicable laws or international treaties related to intellectual property.
### Changes to these Terms
The Owner reserves the right to amend or otherwise modify these Terms at any time. In such cases, the Owner will appropriately inform the User of these changes by updating the "Last updated" date of these Terms, and the User waive any right to receive specific notice of each such change. It is the responsibility of the User to periodically review these Terms to stay informed of updates. The User will be subject to, and will be deemed to have been made aware of and to have accepted, the changes in any revised Terms by their continued use of the Service after the date such revised Terms are posted.
### Assignment of contract
The Owner reserves the right to transfer, assign, dispose of by novation, or subcontract any or all rights or obligations under these Terms, taking the User’s legitimate interests into account. Provisions regarding changes of these Terms will apply accordingly.
Users may not assign or transfer their rights or obligations under these Terms in any way, without the written permission of the Owner.
### Contacts
All communications relating to the use of SIP.TG must be sent using the contact information stated in this document.
### Severability
Should any provision of these Terms be deemed or become invalid or unenforceable under applicable law, the invalidity or unenforceability of such provision shall not affect the validity of the remaining provisions, which shall remain in full force and effect.
Should any provision of these Terms be or be deemed void, invalid or unenforceable, the parties shall do their best to find, in an amicable way, an agreement on valid and enforceable provisions thereby substituting the void, invalid or unenforceable parts.
In case of failure to do so, the void, invalid or unenforceable provisions shall be replaced by the applicable statutory provisions, if so permitted or stated under the applicable law.
Without prejudice to the above, the nullity, invalidity or impossibility to enforce a particular provision of these Terms shall not nullify the entire Agreement, unless the severed provisions are essential to the Agreement, or of such importance that the parties would not have entered into the contract if they had known that the provision would not be valid, or in cases where the remaining provisions would translate into an unacceptable hardship on any of the parties.
### Governing law
These Terms are governed by the law of the place where the Owner is based, as disclosed in the relevant section of this document, without regard to conflict of laws principles.
### Venue of jurisdiction
The exclusive competence to decide on any controversy resulting from or connected to these Terms lies with the courts of the place where the Owner is based, as displayed in the relevant section of this document.
# API Documentation
Source: https://www.sip.tg/api-external
# Privacy and Cookies Policy
Source: https://www.sip.tg/en/privacy
Last updated: 2026-08-31
## Owner and Data Controller
MB "Žinučių linija", company code 305133662, V. Nagevičiaus g. 3, Vilnius 08237, Lithuania
**Owner contact email:** [info@sip.tg](mailto:info@sip.tg)
**Owner contact Telegram:** [@siptg\_support](https://t.me/siptg_support)
Since the use of third-party Trackers through SIP.TG cannot be fully controlled by the Owner, any specific references to third-party Trackers are to be considered indicative. In order to obtain complete information, Users are kindly requested to consult the privacy policies of the respective third-party services listed in this document.
Given the objective complexity surrounding tracking technologies, Users are encouraged to contact the Owner should they wish to receive any further information on the use of such technologies by SIP.TG.
## Definitions and legal references
* **Personal Data (or Data)**
Any information that directly, indirectly, or in connection with other information — including a personal identification number — allows for the identification or identifiability of a natural person.
* **Usage Data**
Information collected automatically through SIP.TG (or third-party services employed in SIP.TG), which can include: the IP addresses or domain names of the computers utilized by the Users who use SIP.TG, the URI addresses (Uniform Resource Identifier), the time of the request, the method utilized to submit the request to the server, the size of the file received in response, the numerical code indicating the status of the server's answer (successful outcome, error, etc.), the country of origin, the features of the browser and the operating system utilized by the User, the various time details per visit (e.g., the time spent on each page within the Application) and the details about the path followed within the Application with special reference to the sequence of pages visited, and other parameters about the device operating system and/or the User's IT environment.
* **User**
The individual using SIP.TG who, unless otherwise specified, coincides with the Data Subject.
* **Data Subject**
The natural person to whom the Personal Data refers.
* **Data Processor (or Processor)**
The natural or legal person, public authority, agency or other body which processes Personal Data on behalf of the Controller, as described in this privacy policy.
* **Data Controller (or Owner)**
The natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of Personal Data, including the security measures concerning the operation and use of SIP.TG. The Data Controller, unless otherwise specified, is the Owner of SIP.TG.
* **SIP.TG (or this Application)**
The means by which the Personal Data of the User is collected and processed.
* **Service**
The service provided by SIP.TG as described in the relative terms (if available) and on this site/application.
* **European Union (or EU)**
Unless otherwise specified, all references made within this document to the European Union include all current member states to the European Union and the European Economic Area.
* **Cookie**
Cookies are Trackers consisting of small sets of data stored in the User's browser.
* **Tracker**
Tracker indicates any technology — e.g Cookies, unique identifiers, web beacons, embedded scripts, e-tags and fingerprinting — that enables the tracking of Users, for example by accessing or storing information on the User’s device.
### Legal information
This privacy policy relates solely to SIP.TG, if not stated otherwise within this document.
## Types of Data collected
Among the types of Personal Data that SIP.TG collects, by itself or through third parties, there are: Trackers; Usage Data; number of Users; session statistics; payment info.
Complete details on each type of Personal Data collected are provided in the dedicated sections of this privacy policy or by specific explanation texts displayed prior to the Data collection.
Personal Data may be freely provided by the User, or, in case of Usage Data, collected automatically when using SIP.TG.
Unless specified otherwise, all Data requested by SIP.TG is mandatory and failure to provide this Data may make it impossible for SIP.TG to provide its services. In cases where SIP.TG specifically states that some Data is not mandatory, Users are free not to communicate this Data without consequences to the availability or the functioning of the Service.
Users who are uncertain about which Personal Data is mandatory are welcome to contact the Owner.
Any use of Cookies — or of other tracking tools — by SIP.TG or by the owners of third-party services used by SIP.TG serves the purpose of providing the Service required by the User, in addition to any other purposes described in the present document and in the Cookie Policy.
Users are responsible for any third-party Personal Data obtained, published or shared through SIP.TG.
## Mode and place of processing the Data
### Methods of processing
The Owner takes appropriate security measures to prevent unauthorized access, disclosure, modification, or unauthorized destruction of the Data.
The Data processing is carried out using computers and/or IT enabled tools, following organizational procedures and modes strictly related to the purposes indicated. In addition to the Owner, in some cases, the Data may be accessible to certain types of persons in charge, involved with the operation of SIP.TG (administration, sales, marketing, legal, system administration) or external parties (such as third-party technical service providers, mail carriers, hosting providers, IT companies, communications agencies) appointed, if necessary, as Data Processors by the Owner. The updated list of these parties may be requested from the Owner at any time.
### Place
The Data is processed at the Owner's operating offices and in any other places where the parties involved in the processing are located.
Depending on the User's location, data transfers may involve transferring the User's Data to a country other than their own. To find out more about the place of processing of such transferred Data, Users can check the section containing details about the processing of Personal Data.
### Retention time
Unless specified otherwise in this document, Personal Data shall be processed and stored for as long as required by the purpose they have been collected for and may be retained for longer due to applicable legal obligation or based on the Users’ consent.
## Cookies Policy
This document informs Users about the technologies that help SIP.TG to achieve the purposes described below. Such technologies allow the Owner to access and store information (for example by using a Cookie) or use resources (for example by running a script) on a User’s device as they interact with SIP.TG.
For simplicity, all such technologies are defined as "Trackers" within this document – unless there is a reason to differentiate.
For example, while Cookies can be used on both web and mobile browsers, it would be inaccurate to talk about Cookies in the context of mobile apps as they are a browser-based Tracker. For this reason, within this document, the term Cookies is only used where it is specifically meant to indicate that particular type of Tracker.
Some of the purposes for which Trackers are used may also require the User's consent. Whenever consent is given, it can be freely withdrawn at any time following the instructions provided in this document.
SIP.TG uses Trackers managed directly by the Owner (so-called “first-party” Trackers) and Trackers that enable services provided by a third-party (so-called “third-party” Trackers). Unless otherwise specified within this document, third-party providers may access the Trackers managed by them.
The validity and expiration periods of Cookies and other similar Trackers may vary depending on the lifetime set by the Owner or the relevant provider. Some of them expire upon termination of the User’s browsing session.
In addition to what’s specified in the descriptions within each of the categories below, Users may find more precise and updated information regarding lifetime specification as well as any other relevant information — such as the presence of other Trackers — in the linked privacy policies of the respective third-party providers or by contacting the Owner.
### How to manage preferences and provide or withdraw consent
There are various ways to manage Tracker related preferences and to provide and withdraw consent, where relevant:
Users can manage preferences related to Trackers from directly within their own device settings, for example, by preventing the use or storage of Trackers.
Additionally, whenever the use of Trackers is based on consent, Users can provide or withdraw such consent by setting their preferences within the cookie notice or by updating such preferences accordingly via the relevant consent-preferences privacy widget, if available.
It is also possible, via relevant browser or device features, to delete previously stored Trackers, including those used to remember the User’s initial consent preferences.
Other Trackers in the browser’s local memory may be cleared by deleting the browsing history.
With regard to any third-party Trackers, Users can manage their preferences via the related opt-out link (where provided), by using the means indicated in the third party's privacy policy, or by contacting the third party.
### Locating Tracker Settings
Users can, for example, find information about how to manage Cookies in the most commonly used browsers at the following addresses:
* [Google Chrome](https://support.google.com/chrome/answer/95647?hl=en\&p=cpn_cookies)
* [Mozilla Firefox](https://support.mozilla.org/en-US/kb/enable-and-disable-cookies-website-preferences)
* [Apple Safari](https://support.apple.com/guide/safari/manage-cookies-and-website-data-sfri11471/)
* [Microsoft Internet Explorer](http://windows.microsoft.com/en-us/windows-vista/block-or-allow-cookies)
* [Microsoft Edge](https://support.microsoft.com/en-us/help/4027947)
* [Brave](https://support.brave.com/hc/en-us/articles/360022806212-How-do-I-use-Shields-while-browsing)
* [Opera](https://help.opera.com/en/latest/web-preferences/#cookies)
Users may also manage certain categories of Trackers used on mobile apps by opting out through relevant device settings such as the device advertising settings for mobile devices, or tracking settings in general (Users may open the device settings and look for the relevant setting).
### Consequences of denying the use of Trackers
Users are free to decide whether or not to allow the use of Trackers. However, please note that Trackers help SIP.TG to provide a better experience and advanced functionalities to Users (in line with the purposes outlined in this document). Therefore, if the User chooses to block the use of Trackers, the Owner may be unable to provide related features.
## The purposes of processing
The Data concerning the User is collected to allow the Owner to provide its Service, comply with its legal obligations, respond to enforcement requests, protect its rights and interests (or those of its Users or third parties), detect any malicious or fraudulent activity, as well as the following: Access to third-party accounts, Analytics, Tag Management and Handling payments.
For specific information about the Personal Data used for each purpose, the User may refer to the section “Detailed information on the processing of Personal Data”.
## Telegram data retrieved by SIP.TG
SIP.TG may ask for some Telegram permissions allowing it to perform actions with the User's Telegram account and to retrieve information, including Personal Data, from it. This service allows SIP.TG to connect with the User's account on the Telegram Messenger, provided by Telegram Messenger Inc.
For more information about the permissions, refer to the [Telegram privacy policy](https://telegram.org/privacy/).
## Detailed information on the processing of Personal Data
Personal Data is collected for the following purposes and using the following services:
### Access to third-party accounts
This type of service allows SIP.TG to access the Data from your account and perform actions with it.
These services are not activated automatically, but require explicit authorization by the User.
* **Telegram account access**
This service allows SIP.TG to connect with the User's account on the Telegram Messenger, provided by Telegram Messenger Inc.
Place of processing: European Union.
### Analytics & marketing
SIP.TG uses Trackers to measure traffic and analyze User behavior to improve the Service.
The services contained in this section enable the Owner to monitor and analyze web traffic and can be used to keep track of User behavior.
* **Google Analytics 4 (Google Ireland Limited)**
Google Analytics 4 is a web analysis service provided by Google Ireland Limited (“Google”). Google utilizes the Data collected to track and examine the use of SIP.TG, to prepare reports on its activities and share them with other Google services.
Google may use the Data collected to contextualize and personalize the ads of its own advertising network.
In Google Analytics 4, IP addresses are used at collection time and then discarded before Data is logged in any data center or server. Users can learn more by consulting [Google’s official documentation](https://support.google.com/analytics/answer/12017362?hl=en\&ref_topic=2919631).
In order to understand Google's use of Data, consult [Google's partner policy](https://www.google.com/policies/privacy/partners/).
Personal Data processed: number of Users, session statistics, Trackers and Usage Data.
Place of processing: Ireland — [Privacy Policy](https://business.safety.google/privacy/) — [Opt Out](https://tools.google.com/dlpage/gaoptout?hl=en).
Storage of Cookies duration:
* `_ga`: 2 years
* `_ga_*`: 2 years
* **Yandex Metrica (YANDEX, LLC)**
Yandex Metrica is an analytics and heat mapping service provided by YANDEX, LLC.
Yandex Metrica is used to display the areas of SIP.TG that Users interact with most frequently. This shows where the points of interest are.
Personal Data processed: Trackers; Usage Data.
Place of processing: Russian Federation — [Privacy Policy](https://yandex.com/legal/confidential/?lang=en).
Storage of Cookies duration:
* `_ym_metrika_enabled`: 1 hour
* `_ym_isad`: 2 days
* `_ym_uid`: 1 year
* `_ym_d`: 1 year
* `_ym_ucs`: 1 year
* `gdpr`: up to 2 years
* `_ym_debug`: duration of the session
* `_ym_visorc_*`: 30 minutes
* `_ym_hostIndex`: 1 day
* `_ym_sup_debug`: 1 day
* **Referral program**
Referral program is managed by the Owner. We track the source from which the User come from.
Personal Data processed: Trackers.
Place of processing: European Union.
Storage of Cookies duration:
* `partner`: 30 days
### Handling payments
Unless otherwise specified, SIP.TG processes any payments by credit card, bank transfer or other means via external payment service providers. In general and unless where otherwise stated, Users are requested to provide their payment details and personal information directly to such payment service providers. SIP.TG isn't involved in the collection and processing of such information: instead, it will only receive a notification by the relevant payment service provider as to whether payment has been successfully completed.
* **Stripe (Stripe Payments Europe, Limited)**
Stripe is a payment service provided by Stripe Payments Europe, Limited.
Personal Data processed: payment info.
Place of processing: European Union — [Privacy Policy](https://stripe.com/ie/privacy).
* **PayPal (PayPal Inc.)**
PayPal is a payment service provided by PayPal Inc., which allows Users to make online payments.
Personal Data processed: payment info.
Place of processing: See the PayPal privacy policy — [Privacy Policy](https://www.paypal.com/webapps/mpp/ua/privacy-full).
* **Smart Glocal (Smart Glocal Services Limited)**
Smart Glocal is a payment service provided by Smart Glocal Services Limited, which allows Users to make online payments.
Personal Data processed: payment info.
Place of processing: Hong Kong — [Privacy Policy](https://smart-glocal.com/privacy-policy).
* **NOWPayments (NOWPayments Ltd.)**
NOWPayments is a payment service provided by NOWPayments Ltd., which allows Users to make online payments.
Personal Data processed: payment info.
Place of processing: See the NOWPayments privacy policy — [Privacy Policy](https://nowpayments.io/doc/privacy-policy.pdf).
## Further Information for Users
### Legal basis of processing
The Owner may process Personal Data relating to Users if one of the following applies:
* Users have given their consent for one or more specific purposes.
* provision of Data is necessary for the performance of an agreement with the User and/or for any pre-contractual obligations thereof;
* processing is necessary for compliance with a legal obligation to which the Owner is subject;
* processing is related to a task that is carried out in the public interest or in the exercise of official authority vested in the Owner;
* processing is necessary for the purposes of the legitimate interests pursued by the Owner or by a third party.
In any case, the Owner will gladly help to clarify the specific legal basis that applies to the processing, and in particular whether the provision of Personal Data is a statutory or contractual requirement, or a requirement necessary to enter into a contract.
### Further information about retention time
Unless specified otherwise in this document, Personal Data shall be processed and stored for as long as required by the purpose they have been collected for and may be retained for longer due to applicable legal obligation or based on the Users’ consent.
Therefore:
* Personal Data collected for purposes related to the performance of a contract between the Owner and the User shall be retained until such contract has been fully performed.
* Personal Data collected for the purposes of the Owner’s legitimate interests shall be retained as long as needed to fulfill such purposes. Users may find specific information regarding the legitimate interests pursued by the Owner within the relevant sections of this document or by contacting the Owner.
The Owner may be allowed to retain Personal Data for a longer period whenever the User has given consent to such processing, as long as such consent is not withdrawn. Furthermore, the Owner may be obliged to retain Personal Data for a longer period whenever required to fulfil a legal obligation or upon order of an authority.
Once the retention period expires, Personal Data shall be deleted. Therefore, the right of access, the right to erasure, the right to rectification and the right to data portability cannot be enforced after expiration of the retention period.
### The rights of Users based on the General Data Protection Regulation (GDPR)
Users may exercise certain rights regarding their Data processed by the Owner.
In particular, Users have the right to do the following, to the extent permitted by law:
* **Withdraw their consent at any time.** Users have the right to withdraw consent where they have previously given their consent to the processing of their Personal Data.
* **Object to processing of their Data.** Users have the right to object to the processing of their Data if the processing is carried out on a legal basis other than consent.
* **Access their Data.** Users have the right to learn if Data is being processed by the Owner, obtain disclosure regarding certain aspects of the processing and obtain a copy of the Data undergoing processing.
* **Verify and seek rectification.** Users have the right to verify the accuracy of their Data and ask for it to be updated or corrected.
* **Restrict the processing of their Data.** Users have the right to restrict the processing of their Data. In this case, the Owner will not process their Data for any purpose other than storing it.
* **Have their Personal Data deleted or otherwise removed.** Users have the right to obtain the erasure of their Data from the Owner.
* **Receive their Data and have it transferred to another controller.** Users have the right to receive their Data in a structured, commonly used and machine readable format and, if technically feasible, to have it transmitted to another controller without any hindrance.
* **Lodge a complaint.** Users have the right to bring a claim before their competent data protection authority.
Users are also entitled to learn about the legal basis for Data transfers abroad including to any international organization governed by public international law or set up by two or more countries, such as the UN, and about the security measures taken by the Owner to safeguard their Data.
### Details about the right to object to processing
**Where Personal Data is processed for a public interest, in the exercise of an official authority vested in the Owner or for the purposes of the legitimate interests pursued by the Owner, Users may object to such processing by providing a ground related to their particular situation to justify the objection.**
**Users must know that, however, should their Personal Data be processed for direct marketing purposes, they can object to that processing at any time, free of charge and without providing any justification. Where the User objects to processing for direct marketing purposes, the Personal Data will no longer be processed for such purposes. To learn whether the Owner is processing Personal Data for direct marketing purposes, Users may refer to the relevant sections of this document.**
### How to exercise these rights
Any requests to exercise User rights can be directed to the Owner through the contact details provided in this document. Such requests are free of charge and will be answered by the Owner as early as possible and always within one month, providing Users with the information required by law. Any rectification or erasure of Personal Data or restriction of processing will be communicated by the Owner to each recipient, if any, to whom the Personal Data has been disclosed unless this proves impossible or involves disproportionate effort. At the Users’ request, the Owner will inform them about those recipients.
## Additional information about Data collection and processing
### Legal action
The User's Personal Data may be used for legal purposes by the Owner in Court or in the stages leading to possible legal action arising from improper use of SIP.TG or the related Services.
The User declares to be aware that the Owner may be required to reveal personal data upon request of public authorities.
### Additional information about User's Personal Data
In addition to the information contained in this privacy policy, SIP.TG may provide the User with additional and contextual information concerning particular Services or the collection and processing of Personal Data upon request.
### System logs and maintenance
For operation and maintenance purposes, SIP.TG and any third-party services may collect files that record interaction with SIP.TG (System logs) or use other Personal Data (such as the IP Address) for this purpose.
### Information not contained in this policy
More details concerning the collection or processing of Personal Data may be requested from the Owner at any time. Please see the contact information at the beginning of this document.
### Changes to this privacy policy
The Owner reserves the right to make changes to this privacy policy at any time by notifying its Users on this page and possibly within SIP.TG. It is strongly recommended to check this page often, referring to the date of the last modification listed at the top.
Should the changes affect processing activities performed on the basis of the User’s consent, the Owner shall collect new consent from the User, where required.
# Terms and Conditions
Source: https://www.sip.tg/en/terms
Last updated: 2026-08-31
These Terms govern
* the use of SIP.TG, and,
* any other related Agreement or legal relationship with the Owner
in a legally binding way. Capitalized words are defined in the relevant dedicated section of this document.
The User must read this document carefully.
## The Owner
MB "Žinučių linija", company code 305133662, V. Nagevičiaus g. 3, Vilnius 08237, Lithuania
**Owner contact email:** [info@sip.tg](mailto:info@sip.tg)
**Owner contact Telegram:** [@siptg\_support](https://t.me/siptg_support)
"SIP.TG" refers to
* the Service;
* any applications, sample and content files, source code, scripts, instruction sets or software included as part of the Service, as well as any related documentation.
## What the User should know at a glance
* Please note that some provisions in these Terms may only apply to certain categories of Users. In particular, certain provisions may only apply to Consumers or to those Users that do not qualify as Consumers. Such limitations are always explicitly mentioned within each affected clause. In the absence of any such mention, clauses apply to all Users.
* SIP.TG uses automatic renewal for Product subscriptions. Information about the a) renewal period, b) termination details and c) termination notice can be found in the relevant section of these Terms.
## Definitions and legal references
* **SIP.TG (or this Application)**
The property that enables the provision of the Service.
* **Agreement**
Any legally binding or contractual relationship between the Owner and the User, governed by these Terms.
* **User (or You)**
Indicates any natural person or legal entity using SIP.TG.
* **Consumer**
Is any User qualifying as such under applicable law.
* **Business User**
Any User that does not qualify as a Consumer.
* **Product**
A good or service available through SIP.TG, such as e.g. physical goods, digital files, software, booking services etc., and any other types of products separately defined herein, such as Digital Products.
* **Digital Product**
Is a Product that consists of content produced and supplied in digital form and/or a service that allows for the creation, processing, storing or accessing data in a digital form or the sharing or any other form of interaction with digital data uploaded or created by the User or any other user of SIP.TG.
* **European (or Europe)**
Applies where a User, regardless of nationality, is in the EU.
* **Owner (or We)**
Indicates the natural person(s) or legal entity that provides SIP.TG and/or the Service to Users.
* **Service**
The service provided by SIP.TG as described in these Terms and on SIP.TG.
* **Terms**
All provisions applicable to the use of SIP.TG and/or the Service as described in this document, including any other related documents or agreements, and as updated from time to time.
## Content on SIP.TG
Unless where otherwise specified or clearly recognizable, all content available on SIP.TG is owned or provided by the Owner or its licensors.
The Owner undertakes its utmost effort to ensure that the content provided on SIP.TG infringes no applicable legal provisions or third-party rights. However, it may not always be possible to achieve such a result.
In such cases, without prejudice to any legal prerogatives of Users to enforce their rights, Users are kindly asked to preferably report related complaints using the contact details provided in this document.
### Rights regarding content on SIP.TG — All rights reserved
The Owner holds and reserves all intellectual property rights for any such content.
Users may not, therefore, use such content in any way that is not necessary or implicit in the proper use of the Service.
In particular, but without limitation, Users may not copy, download, share (beyond the limits set forth below), modify, translate, transform, publish, transmit, sell, sublicense, edit, transfer/assign to third parties or create derivative works from the content available on SIP.TG, nor allow any third party to do so through the User or their device, even without the User's knowledge.
Where explicitly stated on SIP.TG, the User may download, copy and/or share some content available through SIP.TG for its sole personal and non-commercial use and provided that the copyright attributions and all the other attributions requested by the Owner are correctly implemented.
Any applicable statutory limitation or exception to copyright shall stay unaffected.
## Access to external resources
Through SIP.TG Users may have access to external resources provided by third parties. Users acknowledge and accept that the Owner has no control over such resources and is therefore not responsible for their content and availability.
Conditions applicable to any resources provided by third parties, including those applicable to any possible grant of rights in content, result from each such third parties’ terms and conditions or, in the absence of those, applicable statutory law.
## Acceptable use
SIP.TG and the Service may only be used within the scope of what they are provided for, under these Terms and applicable law.
Users are solely responsible for making sure that their use of SIP.TG and/or the Service violates no applicable law, regulations or third-party rights.
Therefore, **the Owner reserves the right to take any appropriate measure to protect its legitimate interests including by denying Users access to SIP.TG or the Service, terminating contracts, reporting any misconduct performed through SIP.TG or the Service to the competent authorities — such as judicial or administrative authorities — whenever Users engage or are suspected to engage in any of the following activities:**
* violate laws, regulations and/or these Terms;
* infringe any third-party rights;
* considerably impair the Owner’s legitimate interests;
* offend the Owner or any third party.
## Terms and conditions of sale
### Paid Products
Some of the Products provided on SIP.TG, as part of the Service, are provided on the basis of payment.
The fees, duration and conditions applicable to the purchase of such Products are described below and in the dedicated sections of SIP.TG.
### Product description
Prices, descriptions or availability of Products are outlined in the respective sections of SIP.TG and are subject to change without notice.
While Products on SIP.TG are presented with the greatest accuracy technically possible, representation on SIP.TG through any means (including, as the case may be, graphic material, images, colors, sounds) is for reference only and implies no warranty as to the characteristics of the purchased Product.
The characteristics of the chosen Product will be outlined during the purchasing process.
### Purchasing process
Any steps taken from choosing a Product to order submission form part of the purchasing process.
The purchasing process includes these steps:
* Users must choose the desired Product and verify their purchase selection.
* After having reviewed the information displayed in the purchase selection, Users may place the order by submitting it.
### Order submission
When the User submits an order, the following applies:
* The submission of an order determines contract conclusion and therefore creates for the User the obligation to pay the price, taxes and possible further fees and expenses, as specified on the order page.
* In case the purchased Product requires an action from the User, such as the provision of personal information or data, specifications or special wishes, the order submission creates an obligation for the User to cooperate accordingly.
* Upon submission of the order, Users will receive a receipt confirming that the order has been received.
### Prices
Users are informed during the purchasing process and before order submission, about any fees, taxes and costs (including, if any, delivery costs) that they will be charged.
Prices on SIP.TG are displayed excluding any applicable fees, taxes and costs.
### Methods of payment
Information related to accepted payment methods is made available during the purchasing process.
Some payment methods may only be available subject to additional conditions or fees. In such cases related information can be found in the dedicated section of SIP.TG.
All payments are independently processed through third-party services. Therefore, SIP.TG does not collect any payment information — such as credit card details — but only receives a notification once the payment has been successfully completed. The User may read the privacy policy of SIP.TG to learn more about the data processing and Users’ rights regarding their data.
If a payment through the available methods fails or is refused by the payment service provider, the Owner shall be under no obligation to fulfill the purchase order. If a payment fails or is refused, the Owner reserves the right to claim any related expenses or damages from the User.
### Retention of usage rights
Users do not acquire any rights to use the purchased Product until the total purchase price is received by the Owner.
### Fixed-term subscriptions
Paid fixed-term subscriptions allow Users to receive a Product continuously or regularly over time. It starts on the day the payment is received by the Owner and last for the subscription period chosen by the User or otherwise specified during the purchasing process.
Once the subscription period expires, the Product shall no longer be accessible.
### Automatic renewal of fixed-term subscriptions
**Subscriptions are automatically renewed through the payment method that the User chose during purchase.**
**The renewed subscription will last for a period equal to the original term.**
The User shall receive a reminder of the upcoming renewal with reasonable advance, outlining the procedure to be followed in order to cancel the automatic renewal.
### Termination
**Subscriptions may be terminated by sending a clear and unambiguous termination notice to the Owner using the contact details provided in this document, or — if applicable — by using the corresponding controls inside SIP.TG.**
**If the notice of termination is received by the Owner no later than 5 days before the subscription renews, termination shall take effect as soon as the current period is completed.**
### Terms and conditions applying to extra features
Users that have an active subscription may purchase single extra add-ons or features, described in the relevant section of SIP.TG.
Unless otherwise specified, such extras are subject to the same terms applicable to the main Product, including all provisions of this document.
## Right of withdrawal
Unless exceptions apply, the User may be eligible to withdraw from the contract within the period specified below (generally 14 days), for any reason and without justification. Users can learn more about the withdrawal conditions within this section.
### Exercising the right of withdrawal
To exercise their right of withdrawal, Users must send to the Owner an unequivocal statement of their intention to withdraw from the contract.
To this end, Users may express their intention to withdraw from the contract by making an unequivocal statement in any suitable way. In order to meet the deadline within which they can exercise such right, Users must send the withdrawal notice before the withdrawal period expires.
**Regarding the purchase of a service**, the withdrawal period expires 14 days after the day that the contract is entered into, unless the User has waived the withdrawal right.
### Effects of withdrawal
Users who correctly withdraw from a contract will be reimbursed by the Owner for all payments made to the Owner, including, if any, those covering the costs of delivery.
However, any additional costs resulting from the choice of a particular delivery method other than the least expensive type of standard delivery offered by the Owner, will not be reimbursed.
Such reimbursement shall be made without undue delay and, in any event, no later than 14 days from the day on which the Owner is informed of the User’s decision to withdraw from the contract. Unless otherwise agreed with the User, reimbursements will be made using the same means of payment as used to process the initial transaction. In any event, the User shall not incur any costs or fees as a result of such reimbursement.
## Legal guarantee of conformity for Digital Products under EU law
Under EU law, for a minimum period of 2 years from delivery or, in case of Digital Products supplied continuously for more than 2 years for the entire supply period, traders guarantee conformity of the Digital Products they provide to Consumers.
Where Users qualify as European Consumers, the legal guarantee of conformity applies to the Digital Products available on SIP.TG in accordance with the laws of the country of their habitual residence.
National laws of such country may grant Users broader rights.
## Liability and indemnification
### Indemnification
The User agrees to indemnify and hold the Owner and its subsidiaries, affiliates, officers, directors, agents, co-branders, partners and employees harmless from and against any claim or demand — including but not limited to lawyer's fees and costs — made by any third party due to or in relation with any culpable violation of these Terms, third-party rights or statutory provisions connected to the use of the Service by the User or its affiliates, officers, directors, agents, co-branders, partners and employees to the extent allowed by applicable law.
### Limitation of liability
Unless otherwise explicitly stated and without prejudice to applicable law, Users shall have no right to claim damages against the Owner (or any natural or legal person acting on its behalf).
This does not apply to damages to life, health or physical integrity, damages resulting from the breach of material contractual obligations such as any obligation strictly necessary to achieve the purpose of the contract, and/or damages resulting from intent or gross negligence, as long as SIP.TG has been appropriately and correctly used by the User.
Unless damages have been caused by way of intent or gross negligence, or they affect life, health or physical integrity, the Owner shall only be liable to the extent of typical and foreseeable damages at the moment the contract was entered into.
In particular, within the limits stated above, the Owner shall not be liable for:
* damages or losses resulting from interruptions or malfunctions of SIP.TG due to acts of force majeure, or unforeseen and unforeseeable events and, in any case, independent of the will and beyond the control of the Owner, such as, but not limited to, failures or disruptions of telephone or electrical lines, the Internet and / or other means of transmission, unavailability of websites, strikes, natural disasters, viruses and cyber attacks, interruptions in the delivery of products, third-party services or applications;
* any losses that are not the direct consequence of a breach of the Terms by the Owner;
* any loss of business opportunities and any other loss, even indirect, that may be incurred by the User (such as, but not limited to, trading losses, loss of revenue, income, profits or anticipated savings, loss of contracts or business relationships, loss of reputation or goodwill, etc.);
* any damage, prejudice or loss occurring due to viruses or other malware contained in or connected to files available for download from the internet or via SIP.TG. Users are responsible for implementing sufficient security measures — such as anti-viruses and firewalls to prevent any such infection or attack and for securing backup copies of all data or information exchanged via or uploaded to SIP.TG.
## Common provisions
### No Waiver
The Owner’s failure to assert any right or provision under these Terms shall not constitute a waiver of any such right or provision. No waiver shall be considered a further or continuing waiver of such term or any other term.
### Service interruption
To ensure the best possible service level, the Owner reserves the right to interrupt the Service for maintenance, system updates or any other changes, informing the Users appropriately.
Within the limits of law, the Owner may also decide to suspend or discontinue the Service altogether. If the Service is discontinued, the Owner will cooperate with Users to enable them to withdraw Personal Data or information and will respect Users' rights relating to continued product use and/or compensation, as provided for by applicable law.
Additionally, the Service might not be available due to reasons outside the Owner’s reasonable control, such as “force majeure” events (infrastructural breakdowns or blackouts etc.).
### Service reselling
Users may not reproduce, duplicate, copy, sell, resell or exploit any portion of SIP.TG and of its Service without the Owner’s express prior written permission, granted either directly or through a legitimate reselling programme.
### Privacy policy
To learn more about the use of their Personal Data, Users may refer to the privacy policy of SIP.TG — [Privacy and Cookies Policy](https://sip.tg/privacy).
### Intellectual property rights
Without prejudice to any more specific provision of these Terms, any intellectual property rights, such as copyrights, trademark rights, patent rights and design rights related to SIP.TG are the exclusive property of the Owner or its licensors and are subject to the protection granted by applicable laws or international treaties relating to intellectual property.
All trademarks — nominal or figurative — and all other marks, trade names, service marks, word marks, illustrations, images, or logos appearing in connection with SIP.TG are, and remain, the exclusive property of the Owner or its licensors and are subject to the protection granted by applicable laws or international treaties related to intellectual property.
### Changes to these Terms
The Owner reserves the right to amend or otherwise modify these Terms at any time. In such cases, the Owner will appropriately inform the User of these changes by updating the "Last updated" date of these Terms, and the User waive any right to receive specific notice of each such change. It is the responsibility of the User to periodically review these Terms to stay informed of updates. The User will be subject to, and will be deemed to have been made aware of and to have accepted, the changes in any revised Terms by their continued use of the Service after the date such revised Terms are posted.
### Assignment of contract
The Owner reserves the right to transfer, assign, dispose of by novation, or subcontract any or all rights or obligations under these Terms, taking the User’s legitimate interests into account. Provisions regarding changes of these Terms will apply accordingly.
Users may not assign or transfer their rights or obligations under these Terms in any way, without the written permission of the Owner.
### Contacts
All communications relating to the use of SIP.TG must be sent using the contact information stated in this document.
### Severability
Should any provision of these Terms be deemed or become invalid or unenforceable under applicable law, the invalidity or unenforceability of such provision shall not affect the validity of the remaining provisions, which shall remain in full force and effect.
Should any provision of these Terms be or be deemed void, invalid or unenforceable, the parties shall do their best to find, in an amicable way, an agreement on valid and enforceable provisions thereby substituting the void, invalid or unenforceable parts.
In case of failure to do so, the void, invalid or unenforceable provisions shall be replaced by the applicable statutory provisions, if so permitted or stated under the applicable law.
Without prejudice to the above, the nullity, invalidity or impossibility to enforce a particular provision of these Terms shall not nullify the entire Agreement, unless the severed provisions are essential to the Agreement, or of such importance that the parties would not have entered into the contract if they had known that the provision would not be valid, or in cases where the remaining provisions would translate into an unacceptable hardship on any of the parties.
### Governing law
These Terms are governed by the law of the place where the Owner is based, as disclosed in the relevant section of this document, without regard to conflict of laws principles.
### Venue of jurisdiction
The exclusive competence to decide on any controversy resulting from or connected to these Terms lies with the courts of the place where the Owner is based, as displayed in the relevant section of this document.