A SIP account is a registration toward a carrier, a GSM gateway, or another PBX. A SIP phone is an extension that registers toward DotSIP. Incoming calls on an account are decided by your route API, not by a menu on the account form.
SIP accounts
Open SIP accounts.
- Choose Add account.
- Set an ID you will recognise in logs, for example trunk-main.
- Fill the registrar host, the username, the password, and the transport the carrier gave you.
- Save. The row shows whether the account is registered.
The ID local is reserved. DotSIP uses it when it transfers a call to an extension on this machine. Do not create a carrier account with that ID.
Lines register when the license allows it and the initial password has been changed if the admin still asks you to change it. A missing key on a model does not block registration. The call fails later, when that model is asked to speak.
SIP settings
SIP settings is the exchange page. It stores:
- the local SIP address and ports
- which account is the default for outgoing calls
- checks applied to incoming accounts
- whether the registrar that accepts your phones is on
There is no OpenAI field on this page. The API key is on the live model under Models.
SIP phones
Open SIP phones and add an extension. Give it a number, a password, and the codecs you want. Point the IP phone or softphone at this DotSIP machine, using the registrar address from SIP settings and that extension password.
A phone can store an outbound route. A SIP account can store an inbound route. Those ids are used when they exist, as described on Routes. If neither is set, the call uses route-tools.
Groups
Groups stores an ID and a label. The built-in group all cannot be overwritten. Creating a group does not by itself change who can call whom. Call handling stays on the route API.