VoIP.infoThe independent guide to business communications.
VoIP.info Provider research

MaxoTel SIP Trunking: registration, routing and media evidence

Evaluate MaxoTel Business SIP Trunking without turning portal settings, dated 3CX examples, registration state, network symptoms or product claims into deployment proof.

Reviewed 2026-10-26MaxoTel Business SIP Trunking and support records were reviewed October 26, 2026. Several configuration articles name older creation or modification dates and remain bounded examples rather than current universal PBX compatibility evidence; the selected portal record, current order, current Critical Information Summary and provider confirmation govern. No MaxoTel account, trunk, credential, SIP proxy, DID, caller ID, PBX, router, firewall, NAT mapping, packet, call, codec negotiation, audio, diversion, port, emergency outcome, price, availability, compatibility, status incident or support response was inspected or testedAdvancedDocumentation based · not lab tested

Start with the ordered service and portal-generated identity

MaxoTel presents Business SIP Trunking as a connection between an existing on-premises PBX and its VoIP network. The 3CX guide requires a SIP Trunk Extension created in the customer portal and then uses the portal-issued SIP proxy, registration username and password with Register or Account Based authentication. Preserve the exact service, plan, trunk object, enabled state and retrieval time.

The portal account login is not the SIP credential. A created trunk, copied fields and an enabled PBX object are also different from a successful REGISTER, accepted call, routed DID or working media.

Documented service facts

Reviewed 2026-10-26. Compare SIP trunk services →

SIP authentication

Documented

The reviewed MaxoTel path uses portal-created, register or account-based SIP trunks with a registration username and password. Portal login and SIP credentials remain separate.

SIP registration

Documented

The 3CX example uses the portal-issued proxy, username, password, a 120-second re-registration timeout and UDP. Loaded fields, REGISTER response and continued reachability remain separate.

Inbound delivery and identity

Documented

MaxoTel documents a portal option to send DID information to Asterisk or 3CX. Number assignment, provider attempt, delivered called number, PBX match and completed call remain unverified.

Continuity options

Documented

The portal describes Offline diversion when a device is not registered. Configured destination, trigger, completed alternate call, restoration and established-call behavior remain unverified.

Network and serviceability

Not verified

The product uses customer broadband and MaxoTel publishes outage communications. Account eligibility, route, latency, current incident state, availability and lead time require dated evidence.

Codecs, RTP and audio

Documented

MaxoTel lists G.711 µ-law and A-law as preferred plus G.729, G.726, G.722, GSM and iLBC. Offer, answer, packetization, RTP directions, decoding and audibility remain unverified.

Fax

Not verified

The product portfolio mentions fax-to-email, but the reviewed SIP-trunk records do not establish T.38, passthrough, fallback, gateway support or completed-page results for one trunk.

Transport, firewall and credentials

Documented

The reviewed service path uses SIP over UDP. MaxoTel discusses SIP-server allowlisting, SIP ALG and NAT separately. Historical addresses and setup examples are not universal current firewall or encryption claims.

Lines and concurrent calls

Documented

The 3CX guide maps simultaneous calls to the number of lines or concurrent calls supported by the selected service. Ordered entitlement, PBX limits, starts and completed calls remain separate.

Emergency routing

Documented

MaxoTel says VoIP can connect 000 but advises using a traditional landline or mobile. Effective IPND association, presented identity, callback, power, internet and alternate access remain unverified.

Pricing, porting and contract

Not verified

Product and porting pages expose date-sensitive offers, fees and time estimates. The current order, Critical Information Summary, port category, taxes, terms and provider confirmation govern.

Portal, outages and support

Documented

The portal manages trunk fields, DID behavior, caller ID and diversion; the outage policy names communication channels. Neither proves one account, route, call or restoration result.

SMS and virtual mobile numbers

Not verified

The product page mentions SMS on virtual mobile numbers. The reviewed trunk records do not establish SMS or MMS on ordinary trunk DIDs, sender approval, API access, throughput, retention or price.

Interpret registration and transport within the dated guide

The reviewed 3CX example uses a 120-second re-registration timeout and UDP. MaxoTel separately states that its platform supports SIP over UDP, while its registration-loss article warns that TCP can prevent registration. Record the loaded transport and the first request and response rather than silently inheriting a PBX default.

The article was last modified in 2023 and names version-sensitive 3CX controls such as Auto Discovery. It is a bounded setup example, not proof that every current 3CX release, other PBX, firewall or network is compatible.

Keep DID delivery, caller ID and call capacity separate

The 3CX guide says the portal option “Send DID info to Asterisk/3CX” is required when inbound routing depends on the called number. The portal also has a separate control allowing Asterisk or 3CX to set CLIP, while MaxoTel limits presentation to caller IDs authorized on the account. Preserve called-number delivery, inbound-route match, outbound identity authorization, provider acceptance and remote presentation independently.

The 3CX simultaneous-call field is populated from the number of lines or concurrent calls supported by the selected service. Ordered entitlement, PBX configuration, attempted starts, accepted dialogs and measured media load remain different quantities.

Diagnose blocklists, SIP ALG and NAT as separate mechanisms

MaxoTel documents one 3CX failure pattern in which unexpected DID traffic contributes to the provider SIP server being blocklisted. Its guide recommends configuring all delivered DIDs and allowlisting the provider addresses it names. Those historical addresses must not be copied as an evergreen firewall inventory; use the provider’s current network guidance and the observed source.

The SIP ALG and NAT articles list overlapping symptoms including registration loss, missed ringing and one-way or no audio. Disabling ALG, changing a local SIP port or rebooting a router changes different mechanisms. Make one controlled correction, preserve before-and-after evidence and avoid treating a temporary router reboot as a durable repair.

Separate codec support, SDP negotiation and audible media

MaxoTel lists G.711 µ-law and A-law as preferred and also publishes G.729, G.726, G.722, GSM and iLBC support. A published list does not prove that a particular service, PBX or call can use every codec. Preserve the offer, answer, payload mapping, packetization, RTP tuples, packet directions, decoding and listener result for the same authorized attempt.

Registration, a green PBX icon and a completed SIP dialog do not establish two-way audio. Likewise, one-way audio does not by itself prove SIP ALG or NAT as the cause.

Treat porting, offline diversion, outages and 000 as live operations

The portal documents Offline diversion when a handset is not registered, while the porting FAQ documents cutover unreachability and warns that rare downtime can extend beyond the usual few minutes. Configured diversion, provider trigger, completed alternate call, port acceptance, cutover and restoration require separate evidence.

MaxoTel’s outage policy names status-page and direct communication channels; a service-wide notice does not prove one account or path. Its emergency guide says VoIP can connect 000 but strongly advises using a traditional landline or mobile, and the IPND guide binds addresses to numbers. Preserve effective location, presented identity, callback, power, internet and an independent method; never place an uncoordinated emergency test. Pricing, porting fees and time estimates are date-sensitive and must come from the current order and policy.

Sources & applicability

Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.

Examples require adaptation to your topology. No live PBX or hardware testing is claimed.

Continue your research

Hub · Provider records reviewed individually on their listed dates; account-specific terms and availability require direct confirmation

SIP trunk provider research

Compare the connection model, call routing, media support and cost structure of documented SIP trunk services.

Explore topic →
Troubleshooting · MaxoTel Business SIP Trunking and support records were reviewed October 26, 2026. Several configuration articles name older creation or modification dates and remain bounded examples rather than current universal PBX compatibility evidence; the selected portal record, current order, current Critical Information Summary and provider confirmation govern. No MaxoTel account, trunk, credential, SIP proxy, DID, caller ID, PBX, router, firewall, NAT mapping, packet, call, codec negotiation, audio, diversion, port, emergency outcome, price, availability, compatibility, status incident or support response was inspected or tested

MaxoTel SIP trunk loses registration or calls fail

Find the first divergence across portal identity, UDP registration, blocklists, DID delivery, caller ID, routing, NAT, signaling, codec and media evidence.

Read guide →
Guide

SIP trunking: numbers, capacity and operational control

Plan the carrier relationship that connects a self-managed PBX to outside calling.

Read guide →
Guide

SIP trunk channels and simultaneous calls

Size external capacity around busy-hour demand and the provider’s counting rules.

Read guide →
Guide

SIP trunk failover and redundant calling paths

Design alternate routing without assuming active calls will survive.

Read guide →
Protocol reference · RFC 3261 SIP, RFC 3711 SRTP, RFC 4568 SDP Security Descriptions, RFCs 5763 and 5764 DTLS-SRTP, and current Asterisk PJSIP documentation reviewed October 6, 2026; deployed endpoints, intermediaries, certificates and calls require direct verification

SIP TLS and SRTP: what each protects

Distinguish adjacent-hop signaling protection, SRTP media protection, SDES and DTLS-SRTP keying, and the actual termination points on every call leg.

Read guide →
Guide

Firewall rules for VoIP

Define management, signaling and media access separately using actual deployment requirements.

Read guide →
Guide

NAT for VoIP: signaling and media addresses

Map each translation boundary and compare advertised destinations with reachable addresses.

Read guide →
Guide

PBX credentials and extension secrets

Keep administrator, handset, trunk and backup identities separate and retire them deliberately.

Read guide →
Guide

Planning emergency calling for a VoIP deployment

Assign responsibility for location, routing and outage procedures before rollout.

Read guide →
Guide

Business number porting: a cutover checklist

Keep ownership records, dependencies and a fallback plan aligned with the gaining provider’s process.

Read guide →
Guide · Wireshark 4.x / current upstream tool documentation; inspect installed versions

VoIP packet-capture methodology

Select interfaces, time windows and paired capture points that distinguish network loss from missing evidence.

Read guide →
Guide · FreePBX 17 and current Asterisk res_pjsip documentation reviewed October 5, 2026; Sangoma's generic module pages are responsibility guides rather than an exact installed field map; no FreePBX host, module, account, credential, trunk, route, registration, number, identity, call, media path, failover, capacity, emergency workflow or compatibility was tested

Configure and verify a FreePBX 17 PJSIP trunk

Translate current carrier requirements into FreePBX-owned PJSIP trunk, route and identity controls, then verify the generated Asterisk objects and each call direction independently.

Read guide →
Guide · Current Asterisk PJSIP object, outbound-registration, configuration-example and res_pjsip references reviewed October 1, 2026; no account, carrier, PBX, endpoint, registration, identifier, route, call, emergency workflow, media stream, capacity or failover path was tested

Plan and configure an Asterisk SIP trunk

Translate each carrier direction into explicit PJSIP objects, identification, restricted dialplan, retry policy and leg-by-leg acceptance evidence.

Read guide →
Troubleshooting · Current SIPTRUNK IP-authentication, registration, status, inbound-call, failover, interconnection and general-configuration documentation reviewed October 14, 2026; the sources describe mutually exclusive credential-registration and static-public-IP modes but do not prove the selected account mode, public address, gateway resolution, Contact, registration, number assignment, route, failover treatment, capacity, compatibility or completed call, and no account, portal, credential, PBX, firewall, DNS answer, packet, registration, number, route, failover event, media stream or live call was inspected or tested

SIPTRUNK registration or IP-authentication mode does not match the call path

Determine whether the trunk uses credential registration or static-IP authentication, then trace the exact public address, gateway, Contact or stored destination, provider state, inbound route and failover treatment.

Read guide →
Troubleshooting · First-party Asterisk documentation and SIP standard reviewed September 30, 2026; FreePBX 17 terminology retained; no PBX, provider, number, route or live call test

Inbound VoIP calls do not reach the business

Trace carrier delivery, Asterisk endpoint identification, DID matching and the final destination without collapsing the boundaries.

Read guide →
Troubleshooting · Asterisk 22 LTS · FreePBX 17 / Debian 12 checks

One-way VoIP audio

Trace the missing direction from advertised media address to receiving endpoint.

Read guide →
Troubleshooting · Asterisk 22 LTS · FreePBX 17 / Debian 12 checks

VoIP call connects but has no audio

Separate endpoint audio selection from a media path that fails in both directions.

Read guide →
Hub

VoIP troubleshooting

Use symptoms and evidence to isolate registration, routing, media and device faults.

Explore topic →