Peru: SIP providers and connecting a number to the PBX

We do not issue numbers: the venue buys a Peruvian number from a local provider and brings it into its own PBX as a trunk. The steps that are the same everywhere — trunk modes, form fields, network and the connectivity test — are in the overview «Connecting a provider's number to the PBX»; this page covers only the Peruvian part: where to get a number, what that provider issues and which of it goes into the admin panel.

The data was collected on 9–10 September 2026 from the providers' own documentation and materials of the MTC and OSIPTEL; links are in the «Sources» section.

In brief#

• The national carriers are unusable for a cloud PBX. Movistar delivers its SIP trunk «a través de una conexión de red de datos privada IP VPN», Claro over a «red IP privada segura», Entel over its own radio or fibre link, Bitel «a través de enlaces dedicados», and Optical Networks says it outright: «nuestro servicio NO es por Internet». Such a trunk terminates in the router at the venue, and a dedicated PBX in the cloud cannot reach it — this is not a matter of configuration.
• The first choice is net2phone Perú (IDT): the only player in the market with a public guide and parameters — proxy siptrunk.net2phone.com, port 5060/UDP, either registration or IP authorisation, and G.711u in the codec list.
• Next come the local ITSPs that deliver over the internet: Anura Perú (a ready-made guide for FreePBX/Elastix, numbering in six regions, free porting including 0800), Yautalk (published tariffs from S/165 + IGV per month, PE and EC), Netvoice, Interfono, Gamanet. Most of them issue the server address at activation, so you cannot pre-configure the trunk.
• Ask about codecs before you sign. The Peruvian market runs on G.729: for net2phone it is the «códec estándar de IDT», and Anura promises compatibility with PBXs «que soporten códec G.729». The PBX speaks G.711 and G.722 — without a written «G.711 first» the call will be set up without a common codec and you will get silence.
• Choose REGISTER as the mode. IP authorisation is offered by net2phone (as an option) and by Convergia (as the only option), but both have two signalling addresses, while the trunk recognises a provider by a single host — half of the incoming calls will not be recognised.
• Outside Lima the subscriber part is six digits. The PBX compares the last seven digits, so for a provincial number the last digit of the area code is compared as well: numbers from departments whose codes end in the same digit (44 and 54, 74 and 64) collapse into a single line.

Numbers in the country#

The country code is +51. The numbering plan was approved by Resolución Suprema N° 022-2002-MTC: the country is split into zones, area codes have two digits, and Lima with Callao has a single-digit code — 1.

• The subscriber part has different lengths: 7 digits in Lima and Callao, 6 digits in the other regions. Either way the national landline number has eight digits: 1 + 7 digits or NN + 6 digits.
• Mobile numbers have 9 digits and start with 9; the numbering is non-geographic, the number is not tied to a department.
• Toll-free and service numbers have eight digits in the form 80C XXXXX: 800 — free for the caller, 801 — shared cost, 802, 804, 805, 806, 808 — other services. Providers and everyday use write them as 0800-XXXXX.
• Dialling: inside the country a landline is 0 + area code + number, a mobile is just nine digits, international is 00 + country code. A Lima landline is often printed as (01) 234-5678.
• Emergency numbers have three digits: 105 police, 106 ambulance (SAMU), 116 fire brigade, 115 civil defence, 100 helpline; Lima and Callao also have a unified 911. Through a number from an international aggregator an emergency call usually does not work.
• What the number looks like in an incoming call:

Who issues a number with a SIP trunk#

The first five rows are the providers for which there are «What to enter in the admin panel» tables below. For the rest the server address, port and mode are given after the contract is signed; what exactly to ask is in the collapsed blocks below.

net2phone Perú#

The Peruvian arm of net2phone (IDT Corporation) with an office in Lima: the Unite cloud PBX, uContact and a separate SIP Trunk — a trunk to a third-party PBX. It is the only provider in the country with a public guide, «Guía de configuración del SIP trunk net2phone». The document covers all of Latin America and its dialling examples are Argentinian, so confirm the Peruvian specifics (dialling plan, ANI list) at activation.

What to enter in the admin panel (Telephony → «Trunks and connections» → «Add provider» → the «SIP trunk (custom provider)» card):

What to set up with the provider: order the SIP Trunk and Peruvian DIDs → get the credentials, the «plan de discado» and the ANI list → insist on G.711 u-law first: the provider's standard codec is G.729, which the PBX does not have → for the IP mode, give them the public static address of the PBX (the «Server» tab, the «Static IP» field; with a dynamic address only registration is available) → ask which addresses the incoming calls will come from.

Pitfalls ⚠️ Incoming calls arrive from a different address than the one the outbound calls go to: the provider names 169.132.196.33:5060 and 206.20.196.19:5060 — two hosts, while the trunk recognises a provider by one. With IP authorisation half of the calls will not be recognised as trunk calls, so with net2phone use registration. The DID arrives in the international format with the 011 prefix (01151…) rather than as +51… — the search by the last seven digits survives this, an exact comparison does not. The default outbound number is the account's «header» ANI, additional numbers are enabled on request, so fill the «Show as» field only with agreed numbers. The provider expects media on UDP 20000–24000 from its proxies 200.115.186.65 and 200.115.187.65; the stated link requirements are latency below 100 ms (250 max), loss below 2 %, jitter below 30 ms.

Source: Guía de configuración del SIP trunk net2phone (PDF) · net2phone Perú — 09.09.2026.

Anura Perú#

The Peruvian arm of the Argentinian ANURA S.A.: a cloud PBX and a separate «Troncal IP» for those who have already invested in their own PBX — the service page explicitly lists Asterisk, Issabel, FreePBX, Elastix, Panasonic, Avaya, Yeastar and Grandstream. Numbering covers Lima, Ica, Arequipa, Piura, La Libertad and Cusco; the base package is 10 concurrent channels, porting is free, including 0800 numbers. The parameters below come from the group's knowledge base for FreePBX and Elastix; it is shared across the group, so confirm the Peruvian SBC address when ordering.

What to set up with the provider: order the Troncal IP and the number of channels you need → hand over the list of numbers or start porting → get the DOMINIO, usuario and password → confirm G.711 a-law in writing (the provider's guide has allow=alaw, while the product page promises G.729 compatibility) → ask in which format the incoming DID will arrive.

Pitfalls ⚠️ Port 55090 is the most common mistake when creating this trunk. In Anura's registration the DID is specified right in the connection string, so every new number means changing the credentials at the provider, not just adding a line. The provider expects its own From domain — <DOMINIO>.grancentral.com.ar — while the PBX puts the trunk host there: if outbound calls are rejected, ask Anura to accept calls with their SBC domain. Calls arrive from four networks — 179.0.14.0/24, 200.13.42.0/24, 200.13.43.0/24, 200.33.82.0/24; if the provider asks where we expect traffic from, give them the PBX's static address.

Source: Anura Perú — Troncal IP · KB: Configuración troncal SIP — FreePBX — 09.09.2026.

Eds Perú — the same net2phone through a reseller#

A Peruvian net2phone reseller with its own «Trunking SIP para centrales IP-PBX» section and — a rarity for this market — published Asterisk parameters. Signing up is simpler than going direct: registration on the website, topping up the balance, «bolsa de minutos» or flat-rate tariffs. The trunk is the very same net2phone one, so look up the codecs and the incoming number format in the section above.

What to set up with the provider: open an account and top up the balance → order a Peruvian DID → ask for the current signalling addresses (the reseller's page is older than the net2phone guide) → confirm G.711 in the codec list: the published configuration has g729, g711 and g723, and the PBX only understands g711.

Pitfalls ⚠️ Two different domains in two documents from the same provider — until the first call it is unclear which one works; enter the one you are given at activation and check the trunk with the «Test connection» button, which shows whether the address answers at all. Everything else is as with net2phone: the 011 prefix in the incoming DID and G.729 first in the negotiation.

Source: Eds Perú — Troncal SIP para centrales IP — 09.09.2026.

Yautalk#

A Peruvian ITSP (operating in Peru and Ecuador) selling a cloud PBX, a Cloud Call Center and a separate Troncal SIP — «vinculando tu central telefónica física (IP-PBX) o software de Call Center»; its blog covers Asterisk, Issabel, FreePBX, VICIdial and OmniLeads as supported platforms. Tariffs are published: Starter S/165, Premium S/195, Gold S/210 + IGV per month. The order of connection: pick a new number or port your current one → choose a minute bundle and the number of channels → get the SIP parameters from support.

What to set up with the provider: choose the tariff by the number of channels → order a number or hand over the current one for porting → request the host, port, transport and a codec list with G.711 by email → clarify which number goes out on outbound calls: the provider advertises «números aleatorios para evitar SPAM telefónico», meaning the platform may substitute different numbers, while a venue needs one recognisable number.

Pitfalls ⚠️ Not a single technical parameter is published, so there is nothing to check before the contract; make the first test call before you route the flow of guests to the number. The full list of what to obtain from the manager is in «What to ask the provider».

Source: Yautalk — Troncal SIP para Empresas — 09.09.2026.

Convergia#

An international carrier, one of the three vendors in the official 3CX list «Troncales SIP soportadas — Perú» (together with Telxi and Twilio). What matters for us is that the template has been verified with a self-hosted PBX and that it does have Peruvian numbers. It works by IP authorisation only: «Es necesaria una IP pública estática» — a dedicated PBX has such an address, on the «Server» tab.

What to set up with the provider: give them the PBX's static public address → get the SBC address and the trunk number (entered in the national format) → ask for a single address for incoming calls → if you need your own caller ID, request «Clip No Screening» separately: by default only the contract's numbers go out.

Pitfalls ⚠️ Convergia issues two signalling addresses — the main one and a backup «proxy alternativo» — while the trunk recognises incoming calls by a single host: calls from the second address simply will not be recognised as trunk calls. Either ask for one address for incoming calls or choose a provider with registration. SMS and fax do not work over this trunk.

Source: 3CX — Proveedores de Troncales SIP, Perú — 09.09.2026.

Movistar, Claro, Entel, Bitel and Optical Networks — a trunk on their own link#

This is the main local specific, and it is worth clarifying before signing a contract. For all the large Peruvian carriers a «SIP Trunk» is not a trunk over the internet but a service on their own access link: the addressing comes to the venue together with the pipe, the trunk terminates on equipment in the office, and there is no registration through which one could «arrive from outside». A cloud PBX physically cannot reach such a trunk.

The question that decides everything: «do you deliver the trunk over the internet to our static public address — or only inside your own access link?» The full list of what to obtain from the manager is in «What to ask the provider».

Providers that issue parameters on connection#

International providers with Peruvian numbers#

Peruvian numbers are sold by Telnyx, Twilio, DIDWW and Zadarma; the Telnyx, Twilio and Zadarma cards are already in the catalogue when adding a provider — the server address and mode are filled in automatically. There is no Peruvian specific in their parameters; it is all in the paperwork for the number.

• Telnyx — the strictest checks. A Peruvian number requires the registration certificate of a Peruvian company, the representative's document and an address within the zone of the number's area code, with proof no older than three months; «business use is required, private use is not allowed». Provisioning takes about 72 hours. For shared-cost numbers the requirements are milder: an address in any country will do.
• Twilio. Peru is supported for both inbound and outbound calls, toll-free numbers are available, and DTMF is sent per RFC 2833. The outbound caller ID inside the country is marked «Local (Non-guaranteed)» — Peruvian carriers may not deliver it; an international number must be sent strictly in E.164. Emergency calls through Twilio are prohibited.
• DIDWW and Zadarma list Peruvian numbers in their coverage; check the number types and the list of documents in the provider's portal — requirements differ by country.
• Emergency numbers do not work through an international aggregator. For a venue with a dining room that is an argument for a local provider: keep a mobile phone on shift.

Number porting#

• Porting is mandatory and free of charge, and OSIPTEL runs the process. The standard time is less than 24 hours: a request during the day, the transfer at night between 00:00 and 03:00 the next day.
• For a «Cliente Especial» it takes up to 4 calendar days. That is a contract for more than 10 numbers, which covers almost any corporate trunk.
• Since 2025 the request is confirmed with a PIN that the donor carrier sends to the number being ported. For a «number at the reception desk» that means somebody has to be at the phone when the request is filed.
• Common reasons for rejection: an outstanding invoice, a suspended service, less than a month with the current carrier, a mismatch in the owner's details.
• Register the number to a legal entity (RUC). A number registered to an employee's DNI leaves with them.
• 0800 numbers are ported the same way — Anura explicitly promises porting for them too — but with the donor carrier this is usually a separate request.
• ⚠️ Changing the PBX's public address breaks a trunk with IP authorisation. When the dedicated machine is recreated, give the provider the new address in advance, otherwise the trunk will die silently.

Rules and paperwork#

If it does not work#

1. The carrier gave an address from its own network, or a link together with the trunk. That is a trunk on their access link and it is unreachable from the cloud in principle. Either switch to a provider that delivers the trunk over the internet, or put a PBX on the venue's premises.
2. The call connects but there is silence one way or both. Almost always the codec: G.729 is the default at net2phone and at some local providers, while the PBX understands G.711 and G.722. Ask them to put G.711 first.
3. Anura: the trunk does not register. Check the port — with this provider it is 55090, while the form fills in 5060. Also verify that the right DID is specified in the registration at the provider.
4. Anura: incoming calls work, outbound are rejected. The provider expects your <DOMINIO>.grancentral.com.ar in the From domain, while the PBX puts the trunk host there — ask Anura to accept calls with their SBC domain.
5. net2phone or Convergia: registered, but no incoming calls. Both have two signalling addresses, while the trunk recognises a provider by one host. Ask for a single address for incoming calls or switch to registration.
6. Incoming calls do not match a line. Look at what actually arrives in the call: with net2phone it is 01151…, an international number with the 011 prefix. The search by the last seven digits survives that; rules written for an exact match do not.
7. A call to the second number follows the first number's scenario. Outside Lima the subscriber part is six digits, so the last digit of the area code takes part in the seven-digit comparison: numbers in departments with codes 44 and 54 (or 74 and 64) collapse into one line. Separate the numbers by their endings or handle both with a single routing rule.
8. The provider requires TLS or SRTP. That is not supported for trunks — ask for a plain UDP account (almost everyone has one) or change providers. The other common causes are in the general section of the overview.

Frequently asked questions#

The venue already has a SIP Trunk from Movistar or Claro — can we connect it?#

Most likely not. Both carriers deliver the trunk over their private network: it arrives on the link at the venue's office and terminates there on equipment. A cloud PBX cannot reach such a trunk. Ask the manager directly: «do you deliver the trunk over the internet to our static public address?» If the answer is no, you need an ITSP from this page.

Do we need a Peruvian legal entity to buy a number?#

In practice, yes. Local providers and carriers invoice a RUC, and Telnyx requires the registration certificate of a Peruvian company, the representative's document and an address within the zone of the number's area code. Without a local entity you are left with numbers of other countries or shared-cost numbers.

The provider says it only has G.729 — what do we do?#

That provider will not work: the PBX speaks G.711 (a-law and u-law) and G.722, and this is not configurable. net2phone, Anura and most local ITSPs do have G.711 on the list — you need to ask in writing for it to be first in the negotiation. If the provider refuses, look for another one.

Can we port an existing landline number or an 0800?#

Yes, porting in Peru is mandatory and free, and the request is filed by the receiving carrier. The standard time is under a day, and up to four calendar days for contracts with more than 10 numbers; the request is confirmed with a PIN sent to the number being ported. 0800 numbers can be ported too, usually with a separate request.

Which trunk mode should we choose in Peru?#

Registration. IP authorisation is offered by net2phone (as an option) and by Convergia (as the only option), but both have two signalling addresses, while the trunk recognises a provider by one host — some incoming calls will be lost. Registration does not have this problem and survives a change of server capacity.

Sources#

All links checked on 09.09.2026.

Providers

• net2phone — Guía de configuración del SIP trunk (PDF): https://net2phone.us-east-1.linodeobjects.com/Tm0aBdSlW1f1n5i3pPlRu9tgy2mCRultZUCozS5k.pdf · net2phone Perú: https://www.net2phone.com/es-pe/soluciones/solucion-de-telefonia-y-videoconferencia-para-industiras
• Anura Perú — Troncal IP: https://anura.pe/soluciones/troncal-ip/ · KB, FreePBX: https://kb.anura.com.ar/es/articles/2414055-configuracion-troncal-sip-freepbx · KB, Elastix: https://kb.anura.com.ar/es/articles/2414370-configuracion-troncal-sip-elastix
• Eds Perú — Troncal SIP para centrales IP: https://www.edsperu.com/servicios-de-comunicacion-de-llamadas-a-bajo-costo/troncal-sip-para-centrales-centrales-ip-pbx-centrales-ip-asterisk-trixbox-elastix/
• Yautalk — Troncal SIP para Empresas: https://www.yautalk.com/troncal-sip-empresas/ · VoIP Perú: https://www.yautalk.com/voip-peru/
• Netvoice: http://netvoice.pe/ · Interfono — Troncales SIP: https://interfono.com/pe/telefonia-ip/troncales-sip/ · Gamanet — Troncales SIP: https://gamanet.pe/proveedores-troncales-sip-call-center-voip-troncal-sip/
• 3CX — Proveedores de Troncales SIP, Perú (Convergia, Telxi, Twilio): https://www.3cx.es/partners/troncal-sip/peru/
• Movistar Empresas — Sip Trunk: https://empresas.movistar.com.pe/sip-trunk · Claro Empresas — Telefonía Troncal SIP: https://www.claro.com.pe/empresas/fijos/telefonia-fija/telefonia-troncal-sip/
• Entel Empresas — Telefonía Fija: https://www.entel.pe/empresas/conectividad/telefonia-fija/ · Bitel Empresas — SIP Trunk: https://empresas.bitel.com.pe/telefonia-fija-siptrunk?categoryId=1834938 · Optical Networks — SIP Trunk (web archive): https://web.archive.org/web/2025/https://www.optical.pe/comunicaciones-unificadas/sip-trunk-troncal-ip/

Regulator, numbering and law

• Plan Técnico Fundamental de Numeración, R.S. N° 022-2002-MTC (PDF, OSIPTEL): https://www.osiptel.gob.pe/media/5mgpmw2v/rs022-2002-mtc-plan-numeracion.pdf
• OSIPTEL — number portability, frequently asked questions: https://www.osiptel.gob.pe/portal-del-usuario/preguntas-frecuentes/portabilidad-numerica
• MTC / gob.pe — concesión única for telecommunications operators: https://www.gob.pe/46912-solicitar-concesion-unica-para-prestar-servicios-publicos-de-telecomunicaciones-sin-asignacion-de-espectro-radioelectrico-persona-juridica
• Decreto Legislativo N° 1723 («El Peruano» text, PDF): https://img.lpderecho.pe/wp-content/uploads/2026/02/Decreto-Legislativo-1723-LPDerecho.pdf
• Indecopi — unwanted telephone calls and Decreto Legislativo N° 1390: https://consumidor.gob.pe/2025/06/20/llamadas-telefonicas-no-deseadas-llamadas-spam/
• Reglamento of Ley 29733 — D.S. N° 016-2024-JUS: https://lpderecho.pe/reglamento-ley-proteccion-datos-personales-decreto-supremo-016-2024-jus/

International providers

• Telnyx — Peru DID requirements: https://support.telnyx.com/en/articles/3739545-peru-did-requirements · porting: https://support.telnyx.com/en/articles/3267436-peru-number-porting
• Twilio — Peru: Voice Guidelines: https://www.twilio.com/en-us/guidelines/pe/peru--voice-guidelines---twilio

Related pages#

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