Common problems and solutions

It doesn't turn off. You can reject a call using the special Reject button during the second call.

During a parallel call, you will receive a notification message with options for action. For more information about calls on the second line, see here

No.

The quality of communication depends, among other things. from the telephony provider used and sip account settings on the SIP.TG side. If this is definitely not a consequence of an extremely unstable Internet connection or problems with the SIP provider, then you need to contact us for support on behalf of the user who is experiencing problems.

If the called phone is clearly available for calling, then in this case the problem is on the side of the telecom operator, contact their support service.

There is no option to change your voice. Check with your IP telephony service provider for the possibility of number substitution.

Description of error codes see here

Most often this is due to the passage of the RTP voice stream from the Worker server to the SIP server; the causes of the problem can be different. Try changing the Worker used, or deploy the Worker software on your own equipment.
Sometimes the audio codec used is out of sync, then in the SIP account settings, explicitly specify one codec - for tests we recommend alaw. More about codecs

The audio codec used is out of sync. In the SIP account settings, explicitly specify one - for tests we recommend alaw. More about codecs

Video calling is not currently 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 chapter /softphone bot @siptg_bot should explicitly enable the previous Callback method.

Reason 1: The SIP account for calls has been disabled. It is necessary, according to the instructions, to turn it on again. Possible reasons for shutdown:

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

Reason 2: The settings for the number conversion rules have gone wrong. Open the SIP account settings in the @siptg_bot bot and make sure that the correct rules are used. Or reset them by entering the value =. (the period at the end is important)

Some countries restrict the operation of the SIP protocol at the state level. However, connecting via SIP.TG will always work, because... Our servers are located in different countries where the SIP protocol is not blocked.

In addition to the general reasons associated with packet loss, the problem can also occur when a large number of audio codecs are enabled: this leads to a large SIP packet size, which can be discarded by the receiving side. Try to leave only a few audio codecs (the default is opus,g722/16000,alaw,mulaw,g729). More about codecs

Make sure that you connect to the SIP server (PBX or telecom operator) only through SIP.TG. When connecting from different devices at the same time, calls may be lost.

Most likely yours Telegram the client ends the 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 it is not working correctly, or is in “do not disturb” mode. Try to complete all active locations Telegram except the current one, or reboot all devices.