/gateway
section.Worker server
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 | 🔑 |
Audio codecs
DTMF transmission methods
Number transformation rules
Priority
Caller ID and Caller Name
Screenshot with PBX→SIP.TG connection settings
Show account and Reset password
Trusted IPs
Screenshot with SIP.TG→PBX connection settings
Login, Password, Domain and Proxy
Number on the PBX
Screenshot with IP⇿IP connection settings
Address:port
Field:Value
{SIP field name}:{SIP field value}
, separated by a colon :
.Number on the PBX
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 |
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.
Examples of Caller ID formation
0
be used — this tag allows resolving ambiguity in the interpretation of the identifier type.{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).Example of Caller Name formation
+
, followed by the display name written in parentheses,@
, followed by the display name written in parentheses,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.
Detailed rule processing algorithm
{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.{userid}
, {username}
, {phone}
.How does the PBX learn about the client's number?
How to initiate a call from CRM?
Setup example
/gateway
in @siptg_bot.Extended SIP header fields
Need a forwarded CallerID
Enabling call recording in CRM