Frequent problems and solutions

This is not disconnected. You can reject a call with the special Reject button during a second call.

If you make a parallel call, you will receive a notification message with options. For more information on second line calls, see here

No.

The quality of the connection depends among other things on the telephony provider used and the sip account settings at SIP.TG. If this is not the result of an extremely unstable internet connection or a problem with the SIP provider, you should contact our support team on behalf of the user who is experiencing the problem.

If the called phone is clearly available to call, the problem is on the service provider's side, contact their customer service.

There is no voice spoofing option. Check with your IP telephony service provider if it is possible to swap numbers.

For a description of the error codes , see here

Most often this is due to the RTP voice stream passing from the Worker server to the SIP server, the reasons for the problem can be different. Try to change the Worker used, or deploy the Worker software on your hardware.
Sometimes the audio codec used is out of sync, then specify one codec explicitly in SIP account settings - we recommend alaw for tests. Read more about codecs

The audio codec used is out of sync. Specify one explicitly in the SIP account settings - we recommend alaw for tests. Read more about codecs

Video calls are currently not supported.

There is currently no support for group voice chats.

For some reason the Callback for the outgoing call did not work. You need to manually open a chat with @siptg and call within a minute of receiving such a message. In the section /softphone bot @siptg_bot you should explicitly enable the old way of Callback.

Reason 1: The SIP account has been disabled for calls. You need to switch it back on again according to the instructions. Possible reasons for disconnection:

• the account has not been used for a long time (more than 3 months);
• an account with an identical login/password/server address has been added by another user;
• The SIP server has reported that the account no longer exists/is no longer available.

Reason 2: Number conversion rule settings have been corrupted. Open the SIP account settings in bot @siptg_bot and make sure the correct rules are being used. Or reset them by entering =. (the dot at the end is important)

Some countries restrict the operation of the SIP protocol at the national level. However, a connection via SIP.TG will always work as our servers are located in different countries where the SIP protocol is not blocked.

Apart from the common causes related to packet loss, the problem can also occur when a large number of audio codecs are enabled: this results in a large SIP packet size, which can be dropped by the receiving side. Try to leave only a few audio codecs (default value is opus,g722/16000,alaw,mulaw,g729). Read more about codecs

Make sure that you only connect to the SIP server (PBX or the service provider) via SIP.TG. If you connect from different devices at the same time, calls may be lost.

Your Telegram client is probably terminating an incoming call. This usually happens for one of the following reasons:
1. One physical device initiates and receives the call. To check this - make a call from another phone.
2. Telegram on some of your devices is not working properly, or is in "do not disturb" mode. Try to end all active Telegram locations except the current one, or restart all devices.