Hungary: SIP providers and connecting a number to the PBX

This page continues the general guide to connecting a provider's number to the PBX, which covers everything that is the same for any operator — the two trunk modes, what to ask the provider, what to enter in the form, network requirements and connection testing. Here we cover what is specific to Hungary: who sells a number with a SIP trunk, what such an operator issues and which of it goes into Telephony → "Trunks and connections" → "Add provider".

The data was collected on 9 September 2026 from operator documentation and materials of the regulator NMHH; the links are in the "Sources" section.

In brief#

• You can buy a number with a SIP trunk in Hungary, and the venue needs no permits. There is no separate "VoIP licence": under Act C of 2003 on electronic communications the market runs on notification — the regulator NMHH enters the operator into its register, and the notification is filed by whoever sells you the number and the trunk, not by you.
• Start with MCN Telecom Magyarország / KOMPaaS. It is the only Hungarian operator that has published its full Asterisk trunk configuration: server sip.mcntele.com, registration, the G.711 A-law codec, RFC 2833 tone dialling. It has its own numbering — geographic, nomadic and toll-free 06-80.
• The easiest self-service start is Ephone. Online sign-up, a self-service portal, an official Asterisk/FreePBX setup page, server sip.ephone.hu, a 06-21 or geographic number for HUF 99 per month gross.
• The main local trap is the type of number. Under the national numbering plan a geographic number (06-1 Budapest, 06-72 Pécs…) may only be assigned to a subscriber access point physically located in that zone, and a nomadic service may not be provided on it. For a cloud PBX the correct Hungarian number is a nomadic 06-21; a geographic one only fits if the provider registers it as "secondary number use" tied to the venue's real address.
• The second trap is seven digits. The PBX matches a line by the last seven digits of the number, and in Hungary 06 1 234 5678 (Budapest), 06 21 234 5678 (nomadic) and 06 20 234 5678 (mobile) produce the same tail. If the venue has several numbers, the tails have to be checked by hand.
• The third is spoofed caller ID blocking. Since October 2025 Hungarian operators, together with NMHH, block an inbound international call carrying a Hungarian fixed caller ID; from the summer of 2026 the same applies to mobile numbers. Outbound calls into Hungary with a Hungarian caller ID only work through a Hungarian operator.
• Incumbents do not sell a trunk "outwards". One Magyarország delivers the trunk on top of its own internet access with IP authentication, Magyar Telekom has no public "trunk to your PBX" product at all, and Pro-M and Drávanet deliver the trunk over their own managed network. For a cloud PBX this is usually a dead end.
• Codecs match. The native Hungarian codec is G.711 A-law: it appears in the official examples of both MCN Telecom and Ephone. No "G.729 only" provider was found in the country.
• Paperwork. Hungarian operators sign contracts with a Hungarian entity (adószám / cégjegyzékszám). A foreign owner will find it easier to buy a Hungarian number from an international provider — but they will ask for company registration documents and an address in the number's zone.

Numbers in the country#

• Country code — 36, international prefix — 00 (+ is accepted), domestic trunk prefix — 06. International dialling looks like 00 – 36 – national number.
• Geographic numbers come in two shapes, both giving an 8-digit national number: Budapest (1 plus 7 digits, subscriber part 200 0000 – 999 9999) and a two-digit area code plus 6 digits (22 Székesfehérvár, 46 Miskolc, 52 Debrecen, 62 Szeged, 72 Pécs, 96 Győr and others).
• Mobile numbers — codes 20, 30, 31, 50, 70 plus 7 digits, 9 digits in total. Code 31 is not tied to any particular mobile operator.
• Nomadic numbers — 21 plus 7 digits (9 digits). This is a separate service class: fixed, mobile, toll-free and premium services may not be provided on a nomadic number, and conversely a nomadic service may not be provided on a geographic one.
• Toll-free — 06-80 (zöldszám), premium rate — 90/91, machine-to-machine — 71. Corporate networks 38 are not a public service.
• Emergency numbers — 104 (ambulance), 105 (fire), 107 (police), 112 (the single European number); calls are free for the subscriber. Harmonised social services use 116xxx.
• Dialling. Domestically it is 06 plus the national number; within your own zone the subscriber part alone is accepted. For outbound calls from the PBX it is safer to send the international format +36…: Hungarian providers use both 06… and 00 with the country code in their own examples.

In the "Lines" tab the number can be entered in any format: the PBX matches the last seven digits, so both +3612345678 and 0612345678 will find the same line.

⚠️ The seven-digit trap is sharper in Hungary than in neighbouring countries. A Budapest number has exactly seven subscriber digits, so the tail equals the subscriber part in full — which means the Budapest 06 1 234 5678, the nomadic 06 21 234 5678 and the mobile 06 20 234 5678 are indistinguishable to the PBX. For provincial numbers (a two-digit area code plus six) the last digit of the area code falls into the tail, so 06 22 345 678 and 06 32 345 678 merge as well. The practice is simple: enter lines using the full national number and compare the tails before saving — "Adding a number and routing". If the trunk carries a single number, you may skip the line entirely: the call is accepted anyway.

Who provides a number with a SIP trunk#

Three operators get their own cards below: their trunk mode is known, and for the first two so is the server address — meaning it is clear what to enter. The rest issue parameters only after a contract — see "by contract".

MCN Telecom Magyarország / KOMPaaS#

A licensed Hungarian operator with its own numbering in the major cities, plus nomadic and toll-free 06-80 numbers; it operates in four EU countries. The storefront lives on two domains — mcntelecom.hu and kompaas.hu (the KOMPaaS platform) — with a shared knowledge base. This is the only operator in the country that has published its full Asterisk trunk configuration, so connecting requires no correspondence with engineers. The portal is self-service: a number is activated within minutes.

What to enter in the admin panel

What to set up with the provider: sign up for MyKOMPaaS and order the trunk service → create a SIP account and enter the PBX's public static address (the "Server" tab) into its binding → buy the required number of voice channels (they are sold separately from numbers) → point the purchased number at the trunk.

Pitfalls ⚠️ The account with this operator is bound to an IP address: if the PBX address changes, registration dies, and the portal will say that connections from a different address are restricted rather than "wrong password" — it is easy to look for the cause in the wrong place. Channels and numbers are separate line items: a number on its own buys you no conversations at all (as of 09.09.2026 the trunk starts at HUF 7,990, an extra voice channel is HUF 1,199 per month, a Hungarian number starts at HUF 399 per month; confirm prices when ordering). In the operator's registration string the server address is followed by the extension the calls are directed to, so the call may arrive carrying that identifier rather than the dialled number — if the trunk carries several numbers, ask support how to enable dialled-number delivery. The operator's guide is written for the older Asterisk configuration style, but it maps onto our form line by line. Source: SIP Trunk setup on Asterisk — 09.09.2026.

Ephone#

A VoIP operator with online sign-up and a self-service portal in five languages. It sells nomadic 06-21 numbers (the right choice for a cloud PBX) and geographic numbers from any zone of the country, ports existing analogue and ISDN lines to VoIP, offers kék and zöld numbers and call recording as a paid extra. What matters for us is its official Asterisk/FreePBX setup page: the server address and the mode are stated outright.

What to enter in the admin panel

What to set up with the provider: sign up and obtain the SIP line login and password → order a 06-21 or geographic number (HUF 99 per number per month gross, no setup fee) → set daily and monthly spending limits and block international destinations — the operator explicitly disclaims liability for a badly configured PBX being hacked → when porting a number, fill in their form.

Pitfalls ⚠️ The password must contain no special characters — this is a direct requirement of the operator's guide, and a password generated in the portal easily contains them; if registration fails, start here. The website domain is ephone.ch while the SIP host is sip.ephone.hu: these are often mixed up when entering the data. The operator carries the caller's number in the Remote-Party-ID header, which the PBX does not send by default — if outbound calls show the main line number instead of the employee's, write to our support: sending the number in that header is enabled on the server side. The port is not named in the guide, so we use the standard 5060; user configurations have also been seen with port 5062 — confirm this when connecting. Source: Tudásbázis: Asterisk - FPBX — 09.09.2026.

One Magyarország (One Solutions)#

The merged operator of the 4iG group — the former Vodafone Magyarország, UPC and DIGI. Its fixed corporate telephony portfolio includes a separate SIP Trunk product for a third-party IP PBX: the customer is identified by IP address, there is no registration, and their session border controller (SBC) controls which numbers and how many channels you use. The product sheet is published, but the server address is not named in it — it is issued when the service is provisioned.

What to enter in the admin panel

What to set up with the provider: first ask whether they will accept a PBX in a public cloud, without their own link to the premises → give them the PBX's static address from the "Server" tab → agree the number of channels and the list of numbers on the SBC → check whether they require the caller's number in the P-Asserted-Identity header.

Pitfalls ⚠️ The service is designed around the operator's own access: on a coaxial connection it requires their 10/10 Mbps internet plan and caps you at 14 simultaneous calls, on fibre it needs a separate VLAN with dedicated bandwidth, and historically (from the UPC days) the service arrived in a dedicated subnet bound to the equipment at the customer's site. A cloud PBX does not fit that picture — that is the first question for the account manager, before any contract. Codecs are not named in the sheet, but the bandwidth budget (150 kbps per voice channel) implies G.711, which the PBX does have. According to the professional community as of 09.09.2026 the operator expects the caller's number in the P-Asserted-Identity header on outbound calls, and the PBX does not send it by default: without contacting support, "Show as" will not work. Up to 1,000 numbers can be attached to the service, and billing is per second. Source: SIP Trunk és SIP Account (PDF) — 09.09.2026.

Providers "by contract"#

These operators do have a service for a third-party PBX (or, conversely, have not publicly confirmed one), but the server address, login and password are issued only after a contract — so there can be no "what to enter" table here. Ask for the parameters using the list in "What to ask the provider" and always spell out the main point: the PBX sits in the cloud, not on the venue's premises, and it needs a trunk over the ordinary internet to a public static address.

• N-System (N-Trunk). A VoIP operator since 2007 and the official Yeastar and Fanvil distributor in Hungary. The service explicitly allows a cloud PBX ("a telephone system or a cloud-based service is required") and has a public price list: 5, 10 and 20 simultaneous channels for HUF 4,360 / 5,050 / 7,350 per month net, HUF 0 setup, HUF 3.2 per minute to Hungarian fixed numbers. ⚠️ The trunk parameters are not published, and their wholesale voice comes from another company — technical questions travel one floor down and are answered slowly.
• Invitech ICT Services. A large corporate operator. Its voice portfolio includes a nomadic telephone service (meaning it holds 06-21 numbering — the right number type for a cloud PBX), the "IP Account" trunk service and its own cloud PBX. ⚠️ It is an infrastructure seller: it will almost certainly offer the trunk bundled with its own link. Ask directly whether they will accept a PBX in a public cloud.
• Opennetworks (VIPeX). More than 20 years on the market; the flagship product is the VIPeX cloud PBX, but a trunk is also offered outwards, for third-party solutions and integrations. Numbers come from any zone of the country, plus toll-free, vanity and short numbers. ⚠️ Their default scenario is "our PBX, your phones": ask specifically for a trunk without VIPeX, otherwise you will be sold a second PBX on top of ours. The parameters page is behind their portal login.
• ArenimTel. A cloud contact centre provider. Its value is in interconnects: it has direct links with Magyar Telekom, Yettel and Vodafone, so through it you can get numbers of operators that do not sell trunks outwards themselves onto our PBX. ⚠️ There is no public price list or parameters, and the conversation will start from their contact centre rather than from our PBX.
• Calliotel. A Hungarian VoIP provider with a SIP Trunk service and a declared availability above 99.8%. ⚠️ Parameters are not published and there is next to nothing about the company in open sources — it is worth checking it in the NMHH register of operators before signing.
• BudgeTalk (OneWeb Kft.). IP PBX, mobile VoIP and SIP Trunk services. ⚠️ The service page is purely educational: not a single technical parameter and not a single price. Note that the service operator and the brand differ — the contract will come from a legal entity that is not named on the front page.
• Pro-M Zrt. A state operator (the EDR system and government communications). The "Hangösszeköttetés (SIP Trunk)" service is described publicly: connecting your own IP PBX to the telephone network over Ethernet, with DDI, number porting and HD voice. ⚠️ The link runs over their closed managed network, and the customer base is government bodies and critical infrastructure: for a venue this is most likely the wrong counter.
• Drávanet Zrt. A regional operator from Pécs with its own network; the SIP-CON service addresses subscribers with their own PBX, numbers are chosen from their ranges and the tariffs are public. ⚠️ The service is delivered over their fibre or microwave link to the customer's site — for a cloud PBX you have to ask separately about connecting over the internet.
• Magyar Telekom. The incumbent, yet there is no "SIP trunk to your PBX" product in its public catalogue: small businesses are offered a bundle of "phone + internet + their IP PBX + security" on their equipment, where our PBX is redundant. ⚠️ A corporate trunk under an individual contract may well exist, but that can only be checked through their sales team. For our scenario Telekom is mainly of interest as a donor of a number to be ported.
• Yettel Magyarország. A mobile operator. No public SIP trunk product for a third-party PBX was found: the business offering consists of mobile solutions and a virtual PBX. ⚠️ Yettel numbers can be brought to our PBX through an aggregator with a direct interconnect (see ArenimTel).

International providers with Hungarian numbers#

Hungarian numbers are sold by Telnyx, DIDWW, Zadarma, Twilio and other international services; for a foreign owner this is often the only route, because local operators sign contracts with a Hungarian entity.

• Telnyx — a local number requires a company registration certificate, an address within the same area code as the number, and proof of address no older than three months; national and toll-free numbers need a Hungarian address without the zone requirement. This directly mirrors the Hungarian rule on "primary use" of a geographic number.
• DIDWW — Hungary is in coverage (local and toll-free numbers), with a dedicated regulatory requirements page and two-way trunking.
• Zadarma — Budapest +36 1 numbers in the public price list.
• Twilio, Telxi, AstraQom, didlogic, Sonetel, Bandwidth, Vonage, Plivo — Hungarian numbers are advertised; check the availability of a particular +36 by searching in the provider's own portal.

The parameters and modes of these providers are already described in the catalogue when adding a provider — the server address and mode are filled in automatically, so there is no need to copy them from a country page.

⚠️ The Hungarian caveat that applies to all of them. Since October 2025 a Hungarian operator blocks an inbound international call carrying a spoofed Hungarian fixed caller ID (and from the summer of 2026, a mobile one as well). If the Hungarian number is only needed to receive calls, an international provider is fine. If you also need outbound calls with that number into Hungary, take a Hungarian operator: otherwise the call will simply not reach the subscriber, and nothing on the PBX side will show why.

Number porting#

• Number porting (számhordozás) is required by law, with the detailed rules in a separate regulator act, NMHH decree 2/2012. (I. 24.). Porting is initiated by the receiving operator, so that is who you take the application to.
• The subscriber may withdraw the request until 16:00 of the second working day before the number transfer window. For business subscriptions covering more than 10 numbers the donor operator may require the transfer time to be agreed in advance.
• In practice porting is a routine operation at VoIP operators: at Ephone it is a standard procedure with its own form and is the whole point of their offer (an analogue or ISDN line lives on as a VoIP number after porting), and it is an ordinary service at MCN / KOMPaaS and the rest.
• ⚠️ The number's zone does not change. A ported geographic number remains a number of its own zone, and the rule that it is tied to an access point in that zone still applies. If the venue moves to another city, you need a new number or a nomadic 06-21.
• After porting, the address for 104, 105, 107 and 112 calls has to be filed with the receiving operator again. The contract and the porting follow whoever the number is registered to: changing the holder is a separate procedure at the donor operator.

Rules and paperwork#

If it does not work#

1. MCN / KOMPaaS: registration worked and disappeared after server maintenance. The account with this operator is bound to an IP address, so when the PBX address changes registration is rejected — in the portal this looks like connections from a different address being restricted, not like a wrong password. Update the address in the SIP account binding.
2. Ephone: registration fails with the correct password. The password must contain no ?, ! or @ characters — a password generated in the portal easily contains them. Change it to an alphanumeric one and save the trunk again.
3. Calls come in, but they all land on the same line. Hungarian numbers share their last seven digits across Budapest, nomadic and mobile numbers — and that is exactly what the PBX matches the line by. Compare the tails of your numbers; with a single number on the trunk you can skip the line altogether.
4. Outbound calls show the wrong number. Ephone works via the Remote-Party-ID header and One via P-Asserted-Identity, and the PBX sends neither by default, so the operator substitutes the main contract number. Write to our support — sending the number in that header is enabled on the server side.
5. The operator says the service only runs over its own link. That is how the trunks of One, Pro-M and Drávanet are built, and Magyar Telekom has no public trunk at all. Such a trunk is unreachable from the cloud — insist on a publicly routable server address, or take a number from one of the operators in the cards above.
6. International inbound calls do not reach a Hungarian number bought from an international provider. This is the caller ID spoofing filter at work: since October 2025 Hungarian operators block calls arriving from abroad with a Hungarian fixed caller ID. Outbound calls into Hungary need a Hungarian operator.
7. The provider only offers an encrypted connection. The PBX does not support encrypted trunks — ask for an ordinary UDP account.

The general causes — a wrong login, a disabled line, blocked ports — are covered in "If calls do not get through".

Frequently asked questions#

Which number should a cloud PBX use — a Budapest one or 06-21?#

The nomadic 06-21. This is not a matter of taste: under the numbering plan a geographic number is tied to an access point in its own zone, and providing a nomadic service on it is prohibited. A geographic number only fits if the provider registers it as "secondary number use" tied to the venue's real address — ask about this directly when ordering.

Do I need a Hungarian company to get a number?#

With local operators — in practice yes: the contract is signed with a Hungarian entity holding an adószám. If you have no company in Hungary, buy a +36 number from an international provider, but prepare company registration documents and proof of an address in the number's area code, no older than three months.

Which operator involves the least correspondence?#

Ephone: sign-up is online, the number and the SIP line are created in the portal, and the operator publishes the connection parameters itself. MCN Telecom / KOMPaaS is slightly more involved (you must give them the PBX address and buy channels separately), but it owns its numbering and has the most detailed documentation in the country.

Why is a Hungarian minute more expensive than in neighbouring countries?#

The telecom tax is built into the price: HUF 3 per started minute of an outbound call for non-individual subscribers, capped at HUF 5,000 per number per month. The operator pays it but builds it into the tariff.

Can I receive calls on a Hungarian number from a foreign provider?#

Yes, receiving works. The restriction concerns outbound calls: since October 2025 a call arriving in Hungary from abroad with a Hungarian fixed caller ID is blocked, and from the summer of 2026 the same applies to mobile numbers.

Sources#

Operators

• KOMPaaS / MCN Telecom — SIP Trunk setup on Asterisk: https://help.kompaas.tech/en/support/solutions/articles/43000295471-sip-trunk-setup-on-asterisk
• KOMPaaS / MCN Telecom — SIP account (IP binding): https://mcntele.freshdesk.com/en/support/solutions/articles/43000728825-sip-account
• KOMPaaS — trunk and Hungarian number pricing: https://kompaas.hu/arak/siptronk/
• MCN Telecom Magyarország: https://mcntelecom.hu/
• Ephone — Tudásbázis: Asterisk - FPBX: https://www.ephone.ch/help/asterisk
• Ephone — Szolgáltatások and Tarifák: https://www.ephone.ch/hu/services
• One Solutions — SIP Trunk és SIP Account (PDF): https://www.one.hu/static/documents/kozep-nagyvallalatok/One-Solutions_SIP_Trunk_es_SIP_Account_szolgaltatas.pdf
• Magyar Telekom — IPsound+: https://www.telekom.hu/uzleti/szolgaltatasok/iot-adatatvitel/adatatvitel/ipsound-plusz
• Invitech — SME portfolio: https://www.invitech.hu/kkv
• N-System — SIP Trunk VoIP telefonszolgáltatás (N-Trunk): https://n-system.hu/sip-trunk-voip-telefonszolgaltatas/
• Pro-M — Hangösszeköttetés (SIP Trunk): https://szolgaltataskatalogus.pro-m.hu/menedzselt-kommunikacio/hangszolgaltatasok/sip-trunk/
• Drávanet — SIP-CON: https://dravanet.hu/index.php/uzleti-ugyfelek/sip-con
• Opennetworks — Telekommunikáció: https://www.opennet.hu/telekommunikacios-szolgaltatasok/telekommunikacio/
• ArenimTel — SIP trunk telefonközponthoz: https://arenimtel.com/hu/call-center/sip/
• Calliotel — SIP Trunk: https://callio.tel/siptrunk/
• BudgeTalk — SIP Trunk: https://budgetalk.com/szolgaltatasok/sip-trunk/

Regulator and numbering

• NMHH decree 14/2020. (XII. 15.) — the national numbering plan (ANFT): https://net.jogtar.hu/jogszabaly?docid=a2000014.nmh
• Act C of 2003 on electronic communications: https://net.jogtar.hu/jogszabaly?docid=a0300100.tv
• NMHH — Számhordozás (number porting): https://nmhh.hu/azonositogazdalkodas/szamhordozas
• NMHH decree 2/2012. (I. 24.) on the rules of number porting: https://njt.jog.gov.hu/jogszabaly/2012-2-20-3H
• NMHH — notification of starting operations as a provider: https://nmhh.hu/cikk/417/Eljarasi_tajekoztato_elektronikus_hirkozlesi_szolgaltato_es_vagy_szolgaltatas_bejelenteserol
• NAV — the telecom tax (information leaflet, 30.01.2026): https://nav.gov.hu/pfile/file?path=/ugyfeliranytu/nezzen-utana/inf_fuz/2026/39.-A-tavkozlesi-ado-20260130

International providers

• Telnyx — Hungary DID requirements: https://support.telnyx.com/en/articles/3739452-hungary-did-requirements
• DIDWW — regulatory requirements, Hungary: https://www.didww.com/coverage-and-prices/regulatory-requirements/registration-required/Hungary
• Zadarma — Budapest numbers: https://zadarma.com/en/tariffs/numbers/hungary/budapest/

Related pages#

• Connecting a provider's number to the PBX — the general steps, trunk modes, network, connection testing.
• Setting up SIP phones — how to connect desk phones and DECT handsets to extensions.