Identify the product, platform and order
2talk presents SIP Trunks, Cloud PBX, DirectoR for Microsoft Teams, Faxmail, business messaging and connectivity as related but distinct services. Its support material also separates the Lyra and Plus voice platforms. Record the legal account, ordered service, platform banner, numbers, ports, trunk capacity, PBX or gateway, access path, support level and current provisioning values before choosing a template.
A generic-device guide is evidence for that guide and platform, not proof that a particular account has the same entitlement, endpoint, realm or feature set. Preserve the dated order, portal state and provider response independently.
Documented service facts
Reviewed 2026-10-11. Compare SIP trunk services →
SIP authentication
Documented2talk publishes registration credentials for both its Lyra and Plus platforms: the number as login and authorization identity, with a password configured for that number. The security guidance also distinguishes registration from IP peering. Confirm the account platform and ordered trunk before choosing either pattern, and do not expose a PBX or management interface to the public internet merely to make registration work.
SIP registration
DocumentedThe Lyra and Plus generic-device guides describe REGISTER with a 600-second expiry and 60-second NAT keep-alive, but use different realms and proxies. Those values document generic registration examples, not an observed account or a universal IP-peering contract. Verify the platform shown in the portal and retain the actual challenge, Contact, expiry and response.
Inbound delivery and number format
Not verified2talk says customers can add and port numbers and connect an existing gateway or IP PBX, but the reviewed public pages do not define one Request-URI, called-number format, identity-header or inbound-routing contract for every trunk. Preserve the assigned number, portal route, observed INVITE, PBX match and final destination.
Inbound resilience
Not verified2talk describes scalable trunks and publishes network incident history, but the reviewed material does not establish account-specific alternate delivery, detection or restoration timing, capacity on a backup path, active-call survival or return-to-primary behavior. Treat portal forwarding, PBX redundancy, access resilience and provider recovery as separate mechanisms and test only with an approved plan.
Number and regional availability
Not verifiedThe product and pricing pages advertise New Zealand, Australian, international and toll-free number options plus porting, but catalogue language does not prove inventory, portability, regulatory eligibility or activation timing for a specific number and address. Obtain a dated availability or port result for the selected order.
Audio codecs and DTMF
DocumentedBoth platform guides recommend G.711 A-law first, G.711 mu-law second and list G.722, G.729a and GSM as other defaults; they document RFC2833 or AVT out-of-band DTMF, with in-band guidance for fax machines or alarms. The Lyra guide also publishes a provider RTP range. These are configuration inputs, not proof of the negotiated codec, telephone-event mapping, RTP source or decoded result on a call.
Fax and T.38
DocumentedThe generic SIP guides recommend enabling T.38 for fax machines or alarms, while 2talk separately offers Faxmail. Keep trunk T.38, in-band audio fax and hosted email fax as different services. Confirm direction, endpoint and gateway interoperability, document limits and the observed result for the selected workflow.
Signaling and media encryption
Not verifiedThe Lyra guide lists UDP, TCP or TLS signaling and a TLS port, but the reviewed public sources do not establish certificate validation, TLS availability on the selected trunk or SRTP media protection. 2talk separately advises firewalling, provider-source restrictions for peering, unique credentials, protected management and provisioning paths, and fraud controls. Verify each signaling, media, access and account control independently.
Concurrent calls and call-start rate
Not verified2talk markets scalable capacity and the pricing page lists additional trunks in blocks, but those statements do not establish the selected account concurrency, bursting behavior or calls-per-second allowance. Obtain dated limits from the order and run only a separately approved bounded load test.
Emergency calling
Documented2talk warns that its non-copper business voice services may not be able to call 111 during a power outage, says they are not suitable for vulnerable consumers under the Commerce Commission 111 Contact Code, and recommends a charged mobile phone and optionally a UPS. Confirm ordinary 111 routing, callback identity, service address, nomadic use, power and network dependencies, and the provider-approved validation process for each site; do not place an uncoordinated emergency call.
Pricing and contract
Documented2talk publishes plan, number, additional-trunk and out-of-plan rate-card entries and labels its voice offering prepaid with no contracts. Those catalogue entries do not establish the complete current charge, tax, destination rate, feature entitlement, credit, cancellation consequence or terms for a selected account. Preserve a dated quote, rate card and accepted terms.
Administration and support
Documented2talk describes self-service portal management and lists ticket logging and support categories on its pricing page; it also publishes incident history. These sources do not prove a selected support entitlement, response or restoration commitment. Record the contracted support level, escalation path, maintenance notices and incident timestamps relevant to the account.
SMS and MMS
Not verified2talk presents business messaging as a separate service on its pricing surface, but the reviewed SIP-trunk material does not establish SMS or MMS eligibility, API scope, sender registration, throughput, retention or price for a trunk number. Qualify messaging separately rather than inferring it from voice service or number supply.
Bind registration or peering to the account
The Lyra guide uses lyra.2talk.co.nz, while the Plus guide uses sip.2talk.co.nz; both describe number-based login and authorization identity, a configured password, 600-second registration expiry and 60-second NAT keep-alive. The security advisory separately discusses IP peering. Do not combine those models or copy one platform realm into the other.
For registration, retain DNS result, transport, proxy, realm, SIP and authorization identities, Contact, expiry, challenge and response. For peering, retain approved source and destination addresses, ports and provider confirmation. Registration, OPTIONS reachability and portal state are not proof of inbound and outbound call completion.
Prove number routing and identity per direction
2talk advertises number supply, toll-free and international options and porting, but the reviewed public pages do not define one inbound Request-URI or identity-header contract for all trunks. Confirm the exact number, availability or port result, activation window, portal route and PBX match.
For inbound calls, retain source, destination, Request-URI, asserted identity and final extension. For outbound calls, retain the authorized identity, presented calling number, privacy behavior and carrier response. Do not infer caller-ID authorization from registration, number ownership or inbound delivery.
Resolve media and protection on the actual call
The Lyra and Plus guides publish codec, DTMF, T.38 and port guidance, while Lyra additionally lists provider signaling and RTP addresses and TLS as a signaling option. Apply only values appropriate to the selected platform and PBX. Preserve offer and answer SDP, telephone-event mapping, RTP endpoints, decoded audio or fax result, and any signaling certificate evidence.
A TLS menu option or port does not prove certificate validation, negotiated TLS or protected media, and no reviewed source establishes SRTP for the selected trunk. Keep firewall policy, SIP authentication, signaling confidentiality, media confidentiality, management access and fraud controls as separate checks.
Test resilience and compromise response safely
The reviewed sources do not publish account-specific inbound failover behavior or timing. Map provider recovery, portal forwarding, PBX redundancy, access diversity and power backup separately, including trigger, alternate destination, capacity, identity, detection, restoration and return to primary. Prove new-call routing in an approved exercise and do not claim established-call survival unless observed.
2talk advises identifying whether compromise affects the account, number or device; limiting exposure; fixing the root cause; then rotating account and number credentials and re-registering devices. That order avoids treating a password change as remediation while the original exposure remains. Preserve call-history and control changes without publishing secrets.
Accept emergency, commercial and support limits
2talk warns that non-copper business voice may be unavailable for 111 calling during a power outage and is not suitable for vulnerable consumers under the cited code. Confirm normal 111 access, callback identity, address and nomadic policy, power and network dependencies, accessible alternatives and the provider-approved validation method for each site; do not place an uncoordinated emergency call.
Reconcile the selected plan, number types, trunk blocks, rate card, taxes, terms and support entitlement. Public pricing and an incident-history page do not prove a complete quote, present availability or an SLA. Record explicit concurrency and CPS limits plus a bounded acceptance matrix for registration or peering, inbound, outbound, identity, audio, DTMF, fax, protection, failover and rollback.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- 2talk Voice and SIP Trunks ↗
- 2talk Lyra SIP Settings ↗
- 2talk Plus Generic SIP Settings ↗
- 2talk VoIP Security Advisory ↗
- 2talk account-compromise response ↗
- 2talk vulnerable consumers and 111 during a power outage ↗
- 2talk Voice Pricing ↗
- 2talk incident and maintenance history ↗
- 2talk Faxmail ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.