Numbers
Where the call comes from and how it gets in.
This page is written carefully, because it is the easiest place on the site for something false to slip in. The code for our own switch exists and looks finished. It is not.
Exactly one path works end to end today: a number bought or imported through Twilio, routed to an assistant. Our own FreeSWITCH switch, SIP trunks, IVR and ring groups exist as real objects in the product, but an inbound call over a SIP trunk does not reach an assistant yet, and number porting does not exist at all.
Three ways a call can reach an assistant
One is proven on real calls. The other two have code, tables, screens and tests, but each has one missing piece between it and a real call. That piece is named on the card.
A number through Twilio
Buy a number or import your own from your Twilio account, route it to an assistant, and the call arrives by webhook and goes on as an audio stream. Inbound and outbound, with recording, transcription and per-call cost.
What is missing: The eleven real calls so far all went this way. Six of them failed, for the reasons written on the status page.
Your own SIP trunk
There is a trunk table with direction, auth mode, registration with expiry and transport, proxy and custom SIP headers, plus a generator that writes the gateway configuration for the switch. Outbound over a trunk is real code that runs an originate on the switch.
What is missing: The inbound call does not reach an assistant. The switch hands it on over a socket the gateway does not listen on, and the generated configuration is written to a directory the switch does not read. No real trunk has ever been connected.
Our own switch
FreeSWITCH runs in the same stack, boots clean and passes 11 of 14 SIPp scenarios: digest registration, a wrong password refused, call setup and teardown, cancel, hold and resume, DTMF, transfer.
What is missing: Extensions and voicemail are attached to a live path. An IVR can be built and published, but nothing executes it on a call. Ring groups have complete screens and no caller.
What is built, piece by piece
The table below is split by the only criterion that matters to someone buying: does this piece carry a real call, or does it merely exist?
We wrote "no" where it is no. A serious buyer respects that more than they respect finding out in month three.
| SIP trunks | A complete table and complete screens: direction, auth mode, registration with expiry, transport, proxy, SRTP policy, codecs, custom headers, several gateways with priority. The generator writes correct mod_sofia XML. None of what it generates reaches the running switch in the topology shipped today. |
|---|---|
| extensions | Attached to a live path. Created from the console and the API, and the browser softphone resolves against them. |
| voicemail | Attached to a live path on the Twilio route: a box, messages, playback from the console. |
| IVR | Can be built, validated and published from the console. Execution on a live call has no caller: the methods that would run the menu are called from nowhere, and the HTTP routes the switch would call do not exist in the application. |
| ring groups | Model, migration, screens and API all complete. The service that would turn a group into a dial string for the switch is not called by any code that carries a call. This is exactly the kind of gap the rest of this site promises to name. |
| SIPp scenarios | 11 of 14 pass against a live switch in a single run. The last two need a carrier gateway pointed back at the test bench. |
What a minute to a Romanian number costs
The figures beside this are Twilio's published rates for Romania as they are recorded in the application's provider registry, with the source and the date they take effect.
On top of them sits the platform margin of €0.10 a minute, applied to the real billable seconds. We do not mark telephony up: the carrier cost goes in at list price.
- Inbound call, per minute
- $0,0100
- Outbound to landline, per minute
- $0,0125
- Outbound to mobile, per minute
- $0,0320
The rates are in dollars because that is how the carrier publishes them. A row only enters the registry if it was checked against the vendor's own price list, and this one was.[1]
The seven questions everyone asks
Six have a real answer. One is a plain no. We would rather have a page that answers six honestly than one that answers seven vaguely.
Can I keep my current number?
Not by porting — there is nothing for porting in the product: no model, no migration, no screen, no route. What you can do today is import your existing numbers from a Twilio account of your own, which means the numbers stay yours and only their routing comes to us.
Can I use my own carrier?
Not yet for inbound calls. SIP trunks are fully configurable in the console, outbound over a trunk is real code, and the switch passes 11 of 14 SIPp scenarios — but a call arriving on a trunk does not reach an assistant today, and no real carrier trunk has ever been connected.
Do both inbound and outbound calls work?
Yes, over Twilio, which is the only proven path today. Outbound includes campaigns, with calling windows, suppression lists and a written reason for every contact that was not called.
Can I point several numbers at one assistant?
Yes. An assistant can have any number of numbers; the link lives on the number rather than the other way round, and there is no uniqueness constraint. The reverse — one number routing to different assistants by time of day or by a menu choice — can be declared in the model but is not executed on a live call yet.
Can I have numbers in more than one country?
Yes. Number search and purchase are per country through the Twilio account, and the registry keeps separate rate cards per country — today for the United States and Romania.
What happens to the number if we leave?
You release it, number by number, from the console or the API, and the release really happens at the carrier. There is no automatic organization deletion that releases every number for you, because there is no organization deletion yet. If the numbers are in your own Twilio account, they never left you in the first place.
What does telephony cost?
The carrier cost goes in at its list price with no markup from us; for Romania the verified Twilio rates are in the table above. Separately, the platform charges €0.10 per minute of call.
What the registry says, unprettified
The telephony provider registry is the gate that decides what appears in a customer's selection list. We show it as it is, with both halves.
Selectable today 1
- Twilio
In the registry, not implemented 4
- Telnyx
- Vonage
- DIDWW
- BYO SIP trunk
Adapter code exists for several in the second list too. Code written and provider opened are two different things, and this page keeps them different.
Notes
-
1
The Romanian rates: the Twilio row in
app/Services/Registry/RegistryData.php, marked verified. The source recorded there: Twilio Programmable Voice pricing — https://www.twilio.com/en-us/voice/pricing and /ro (US and Romania rate cards) -
2
Trunks and switch:
app/Models/SipTrunk.php,app/Services/Telephony/Sip/SofiaProfileGenerator.php,app/Services/Pbx/and the dialplan intelephony/freeswitch/conf/. The SIPp scenarios and the 11 of 14: the build report in the repository root.
Porting a number you already own
Keeping a number people already dial is the part with the paperwork and the waiting. Tell us the range and the current carrier and you will get a realistic timeline rather than an optimistic one.