Setting up
Gateway mode

In Gateway mode it is possible to receive and make simultaneous parallel calls (up to 100 lines) via a single Telegram account of the company. A VoIP Trunk to office or cloud SIP PBX is created, where calls are distributed to employees according to the required logic.
The ideal solution for sales and support departments of companies communicating with customers via Telegram.
The cost of using Gateway mode depends on the number of lines required for concurrent calls. The cost of one line is 6 EURO/month. A minimum of 2 lines can be set up.
Important: The gateway is not suitable for outgoing cold calls on the phone number database. Telegram's anti-spam algorithms do not allow you to make a large number of outgoing calls to users with whom you haven't corresponded before, from whom you haven't made the first call, or in whose contact list your account is not present.

The main advantage of the Gateway is that a user from any country can call a business through Telegram for free. After that, such a user can call back without restriction. Also, if there was already some correspondence with the user through the Gateway account, he can call him without fear of being banned by Telegram.

Tell our support team about the nature of your company calls and we will tell you more about how you can adapt Telegram calls to your business.

Step 1: Choose a Telegram account to connect to

Setting up a Telegram account to connect the gateway for calls to the SIP-PBX
  • Determine which Telegram account you need to set up to forward incoming calls from it to your SIP PBX and/or make outgoing calls to Telegram.
  • Contact the bot @siptg_bot from the selected account. If the bot is not activated yet, start it with /start
  • To set up the Gateway function, type /gateway or select it from the bot menu.

Step 2: Connecting the virtual device

Setting up a Telegram account session repository to connect the gateway for calls to the SIP-PBX
Allow @siptg_bot create and connect a virtual device linked to the selected Telegram account to forward calls from it. This procedure is started by pressing the "Connect" button and is done in 3 steps:

  • Select the session store used for the device to be connected (by default the secure SIP.TG cloud store is used, the fastest and easiest option)
  • Give the bot access to the phone number on request
  • Give the bot the code from the official Telegram account to bind the device
Options for using the Session Store
In the case of using the Cloud Session Store from SIP. TG will not require any action from you, this option is selected by default at the appropriate virtual device connection step.

When connecting the virtual appliance, the bot does not receive any permanent password from your account, the appliance is used solely for call forwarding (unless the appropriate bot handling mode is explicitly enabled, e.g. for the text-to-speech feature).

Once set up, all virtual device sessions are stored on our secure servers.

If there are special requirements to confidentiality of data transmitted through the Gateway, you can install your own Session Store, configure the appropriate module, and then select it when creating a virtual device session. Connection of your own Session Store can be tested both on paid and free accounts.

Read more about setting up your own Session Store
Note regarding 2FA (two-factor authentication)
When two-step authentication is active, a new Telegram session for the SIP virtual device. TG can only be created if a backup email has been specified as the second authentication method, then a confirmation code will be sent to it.

For security reasons we do not request a 2FA password from the Telegram account the Gateway connects to, but are forced to change it once the device is connected, a new password for 2FA will be generated for the Gateway account automatically and sent on behalf of @siptg_bot.

When using other 2FA methods, two-step authentication should be disabled for the duration of session creation and can be re-enabled once the session has been created.

Step 3: Configuring registration between Worker Servers and SIP-PBX (VoIP Trunk creation)

Setting up a VoIP Trunk between Telegram and SIP-PBX
Our Worker Servers are SIP nodes that convert and transmit the voice stream between Telegram and your SIP PBX. In SIP telephony terms, a VoIP Trunk is created.

There are 3 possible ways of registering between the SIP. TG and your SIP-PBX:
PBX->SIP.TG (PBX registers to Worker)

In this case you must obtain the details of your SIP account from the bot, which must then be specified on the PBX for registration.
Setting up a VoIP Trunk between Telegram and SIP-PBX
SIP.TG->PBX (Worker registers with the PBX)

  • In this case the bot will need to specify the details of a SIP account on the PBX to make incoming and/or outgoing voice calls.
  • The current list of our server addresses can be found here and should be added to the firewall white list for the PBX.
  • After saving the PBX details, you must press the power button to activate registration.
Setting up a VoIP Trunk between Telegram and SIP PBX with registration
IP<->IP (связь Worker и АТС без регистрации)

  • In this case, a call must be initiated from the PBX to the ip address and port received from the bot to confirm the ip address of the PBX.
  • After saving the PBX details, you must press the power button to activate registration.
  • To identify multiple SIP accounts of this type hosted on the same IP address, additional identification based on a random field and its value in the SIP message is provided.
  • Be sure to specify the Number field on the PBX to receive incoming calls on the PBX side.
Setting up a VoIP Trunk between Telegram and SIP PBX without registration
Firewall settings on the PBX side
If you are using the Firewall to protect your PBX, make sure that the current addresses of our Worker Servers from which you connect to the PBX are on the white list.

All our server addresses are listed in the file:
https://www.sip.tg/fw.txt

Occasionally the Worker-server network is updated, we inform about it in the news channel @siptg_news (we recommend administrators to subscribe to it).
About the infrastructure of Worker Servers
The infrastructure of the SIP Worker servers. TG is secure, the servers are quickly scalable if necessary and are located in different geographical areas.

If required, a specific Worker server can be specified for all linked SIP accounts, including those located on your own servers.

To use your own Worker Server (or several Worker Servers), install and configure the appropriate module, then specify it in the connection settings (this option is NOT available on free tariff plans).

Read more about installing your own Worker Servers
Checking the status of the Gateway accounts
The SIP accounts created for the Gateway will be saved under /gatewayThe account is shown with its status for each account:

Gateway SIP account disabled
  • For SIP. TG -> PBX registrations this status appears if an incorrect login or password is entered, connection parameters are not filled in correctly, there is no access to the PBX (IP is blocked or there are network problems), or it has been disabled manually.
  • For PBX -> SIP. TG registrations this status appears if the PBX has not registered on our server, wrong login or password was entered, connection parameters are not filled in correctly, no access to Worker servers (IP is blocked or there are network problems)
  • Для IP <-> IP подключений это означает что этот SIP-аккаунт АТС не активен (в этом режиме используется UDP, постоянного соединения нет)

⬤ Gateway SIP account is connected
  • The gateway is correctly configured and ready for operation.
IP blocking for incorrect passwords
Specify the connection details to the SIP. TG servers carefully. We have password protection enabled, so the PBX IP can be blocked for an arbitrary period of time if it connects to the SIP. TG without the registration option enabled, with an incorrect username or password, from an untrusted IP and the like.
Limiting the number of SIP accounts per Gateway
The default Gateway mode has a limit of 10 SIP accounts to be connected. In rare cases this number may need to be increased to distribute a significant load, please contact support for this.

Step 4: Checking the operation and paying for the lines

Checking VoIP Trunk operation between Telegram and SIP-PBX
If all settings are correct, SIP account is marked with green indicator, the Gateway is ready to work.

Once the appropriate call routing is set up on the PBX side, you can make a test voice call to a connected Telegram account and/or make a call to a Telegram user through your PBX.
Cost of use at the Gateway rate
To pay tariff Gateway is used, the cost is calculated based on the number of lines needed for parallel calls.

The cost of one line is 600 rubles / month.

Lines are sold in packages of 2, 5, 10, 15, 20, 30, etc. up to 100 pieces (if you pay for several months there are discounts, the total amount is shown in the interface).

If necessary, the maximum number of parallel lines (100) can be increased upon request to customer support.

If you need an enterprise license, write to info@sip.tg
Testing on Free and Trial tariffs
On the Free tariff (connected by default), the following restrictions will apply:
  • 1 line only (no parallel calls possible)
  • A maximum of 30 minutes a month in total
  • maximum call duration 2 minutes
  • a maximum of 5 unsuccessful calls per hour
  • outgoing calls from one SIP account only

On the Trial tariff Up to 10 lines are available for simultaneous calls, all other restrictions are removed, cost 1 EURO/week. This tariff can only be activated once and is valid for 1 week.
Payment procedure for the Gateway tariff
To pay, you need to:

  • Go to /tariff section of bot @siptg_bot
  • Select tariff Gateway, proceed to tariff setting
  • Specify the required parameters:
Number of lines required for parallel calls
Payment period in months (1 to 12)
Payment method

  • Click on "Start payment", follow the instructions of the payment widget.

More about payment methods

See also


Allows receiving and making parallel calls via a unified company Telegram account. Integration with an office or cloud SIP PBX.

How to receive calls from Telegram on the PBX side via SIP.TG and make outgoing calls on behalf of the company's single Telegram account

What users see when calling a single Telegram account via SIP.TG, set of functions available to them

Limitations and specifics of making voice calls in Telegram via the SIP.TG Gateway

How to receive voice calls from Telegram, Gateway integration and connection

Integration of SIP.TG Gateway for Telegram Calls with CRM systems, receiving incoming and making outgoing calls to Telegram users via PBX

Payment options for the SIP.TG gateway for transferring calls between Telegram and SIP telephony

Frequent problems and solutions when setting up a gateway for calls between Telegram and SIP telephony

Purpose, benefits, installation and configuration of own Worker servers for SIP.TG

Purpose, benefits, installation and configuration of your own Telegram Session Store for SIP.TG