Routing and numbers: how to get calls to your assistant

In the Routing and numbers section you decide how calls reach your AI4CALL assistant. The five cards are split into two groups: at the top, the connections to your PBX; at the bottom, the AI4CALL numbers, which receive calls directly from the telephone network. They are two alternative paths: the first goes through your phone system, the second brings the call to the assistant with no intermediary.

Virtual number: the assistant's identifier

The virtual number is the unique number that identifies this assistant within the platform. It is not a public number you can dial from a phone: it tells your PBX which assistant should answer. As the notice explains, it goes in the To field of the SIP request. The button next to the number copies it in one click.

Extension registration on your PBX

The new Extension registration on your PBX card connects AI4CALL as a SIP client: it is AI4CALL that registers an extension on your PBX. The registration automatically includes the assistant's identifier in the SIP contact, so when the PBX routes the call to that contact the platform recognises which assistant it is for.

The fields to fill in under Configure

• PBX host or IP: preferably enter your PBX server name; you can use the IP address if your PBX supports it.
• Extension username and SIP password: these are the credentials of the extension AI4CALL has to register.
• Protocol: UDP is the default, but TCP and TLS are available too.
• Port: it must match the protocol and your PBX configuration.
• Realm: fill it in if required.
• Refresh: the registration renewal interval, expressed in seconds.

Once the details are ready, Save and register starts the extension registration.

Network and firewall requirements

To allow the connection, you may need to authorise the AI4CALL public address shown in the guide on your PBX firewall. If you choose TLS, the PBX must accept secure connections and have correctly configured certificates. Automatic assistant identification does not replace these network requirements. After registration, configure the PBX so that it sends calls to the AI4CALL contact or trunk.

SIP trunk without registration: the IP2IP card

The other path is the SIP trunk without registration, shown in the card as IP2IP: this is the card previously called IP for SIP. Here you authorise the public IP addresses of the PBX that needs to communicate with AI4CALL; requests coming from unauthorised addresses are rejected. This connection works without registering an extension.

The updated information indicates port 5060 for UDP and TCP, while for TLS the port is 5061. The service supports TLS from version 1.2 onwards. The guide also reports the details of the digital certificate used to protect SIP communications. Choose the transport and port that match your trunk configuration.

Authorised addresses apply to the entire account, not just to this assistant: you will find them in the other assistants of the same account as well. Additions and removals take effect immediately. Before deleting an address, check which PBXs and assistants are using it, because removing it may interrupt a connection already in use.

With Configure you open IP management and the guide for the PBX trunk. The example shows the host sip.ai4call.com, with UDP on port 5060, along with codecs, keypad tones and network settings. To direct the call to the assistant you can use the virtual number; the guide also shows destination examples with the API key. Use the identifier of the assistant that has to answer and adapt the parameters to your PBX.

In the IP field enter the actual public address from which the PBX sends SIP traffic. Add a recognisable description, for example Head office PBX. With Add IP you prepare further rows, and Save IP applies the list of authorised addresses. Remember that you are editing a configuration shared by the whole account.

Demo numbers and purchased numbers

Demo numbers are temporary AI4CALL numbers you can call from a phone to try the assistant. Each number can be assigned to only one assistant at a time. If a number is already assigned, to move it to another assistant open Configure first and free it with Release. The notice indicates a duration of thirty days from registration on the portal.

Purchased numbers, on the other hand, are permanent numbers to associate with your assistants. If you have a free number, you can assign it with Assign; with Configure you manage the available numbers and with Buy you open the request for a new one. The association determines which assistant will answer the calls.

What you need to request a number

• The area code, which you choose by searching by number, town or region.
• The ID document of the legal representative.
• A company registration certificate no older than six months.
• A business utility document, such as a bill or a contract.
• Files in PDF format, up to ten megabytes per document.

The form indicates a first automatic check and a final confirmation from the operator within two working days. Send request submits the application once it is completed.

Frequently asked questions

Can the virtual number be called from a phone?

No. The virtual number is not a public number to dial from a phone: it is the unique number that identifies the assistant in the platform and it goes in the To field of the SIP request sent by your PBX.

What is the difference between extension registration and an IP2IP trunk?

With extension registration it is AI4CALL that registers an extension on your PBX, and the assistant's identifier is automatically included in the SIP contact. With the IP2IP trunk there is no registration: you authorise the public IP addresses of the PBX, and requests from unauthorised addresses are rejected.

How long do demo numbers last?

The notice indicates a duration of thirty days from registration on the portal. Each demo number can be assigned to only one assistant at a time and must be freed with Release, from Configure, before moving it to another assistant.