Define the ordered service before copying a template
Peerless describes SIP Trunking within the Infobip Voice US product family and exposes ordering through the Peerless Portal. Preserve the legal service name, account owner, locations, ordered channels, numbers, access path, implementation worksheet and support boundary. A network or product-family statement is not an account entitlement, serviceability result or interoperability certificate.
The one-sheet lists static and registered trunks, PRI and analog delivery, and integrations with several PBX brands. Treat these as marketed service choices rather than one universal configuration. The current order and handover record must identify the exact Peerless edge, customer PBX or gateway, supported software release and owner of each change.
Documented service facts
Reviewed 2026-10-05. Compare SIP trunk services →
Outbound authentication
Not verifiedThe public one-sheet advertises static and registered trunks but does not define one order's source-address or digest-authentication contract, credential lifecycle, accepted outbound identities or whether the methods can be combined. Obtain the current implementation worksheet and keep secrets out of shared traces.
SIP registration
DocumentedPeerless advertises static trunks, registered trunks or a combination. The reviewed sources do not publish the registrar, username realm, refresh behavior, Contact handling, transport or inbound-binding rules for one account, so preserve those values from the order before interpreting REGISTER state.
Inbound delivery
DocumentedThe Peerless Portal can order telephone numbers and channels and manage services, routing, configuration and inventory. Keep number inventory, assignment, configured destination, arriving INVITE, PBX acceptance and final extension delivery as separate evidence; portal visibility is not proof of a completed call.
Inbound failover
DocumentedThe one-sheet advertises PSTN failsafe routing, traffic distribution through multiple IP addresses, geo-redundant routing, multiple SBCs and customer redundancy through multiple SIP or PRI trunks. It does not establish one account's triggers, priority, timers, response handling, restoration or established-call survival. Treat each mechanism as a separate new-call control until an authorized test proves its scope.
Number and regional availability
Not verifiedPeerless describes a broad geographic number inventory and multi-location ordering, but public marketing does not prove inventory, portability, address eligibility or serviceability for a particular number and site. Require a dated result for each deployment location.
Audio codecs
Not verifiedThe reviewed public sources do not establish one trunk's codecs, packetization, DTMF events, RTP addresses or transcoding boundary. Retain the actual SDP offer and answer, payload mapping, media endpoints and decoded application result.
T.38 fax
Not verifiedThe one-sheet mentions PRI and analog delivery, but that does not establish T.38 or voice-band fax behavior. Qualify the exact number, direction, gateway, document set, error correction, switchover and fallback separately.
Signaling and media encryption
Not verifiedBroad references to an IP network and security do not define TLS, certificate validation, SRTP, keying, allowed transports or downgrade behavior for one trunk. Obtain trunk-specific parameters and verify signaling and media protection on every relevant leg.
Concurrent calls and burst
DocumentedPeerless links the ordered channel count to simultaneous calls and says portal users can add or decrease channels in real time. This does not establish purchased concurrency, call-start rate, activation completion, burst treatment, rejection behavior or PBX capacity; keep those controls separate.
Emergency calling
DocumentedPeerless lists E911 among available inventory and SIP-trunk features. The reviewed sources do not define one account's address workflow, eligible outbound identity, callback route or approved test method. Confirm those values for every physical location without placing an uncoordinated emergency call.
Pricing model
Not verifiedPeerless publishes broad metered, unlimited, inbound-charge and flexible-billing claims, but those pages are not a current quote for a specific account. Obtain dated terms covering channels, activation, usage, numbers, E911, toll-free service, porting, support, taxes, commitments, renewal and cancellation.
Administration and support
DocumentedThe Peerless Portal is described as ordering and management control for channels, numbers, routing, configuration and inventory, with real-time usage, call-detail views, exportable records and service requests. Portal visibility does not establish record completeness, retention, alarm coverage, support response or service restoration.
SMS and MMS
Not verifiedPeerless links to separate Infobip messaging services, but the reviewed trunk sources do not establish SMS or MMS entitlement on trunk-assigned numbers. Verify number capability, sender registration, consent controls, application path, throughput, retention and fees independently.
Keep channel order, number routing and call delivery separate
The portal materials describe ordering and managing SIP channels and telephone numbers, then controlling routing, configuration and inventory. Record each transition independently: accepted order, activated channel, number inventory, assignment to the service, configured destination, arriving INVITE, PBX route, endpoint alerting, answer and usable media.
A channel is a commercial and concurrency input, not proof of a completed call or a PBX resource. Likewise, a number appearing in inventory does not prove port completion, inbound routing or emergency-address association. Preserve timestamps and identifiers from both the portal and PBX instead of reconciling them from memory.
Choose the static or registered identity model explicitly
Peerless advertises static trunks, registered trunks or a combination, but the reviewed sources do not define the source addresses, registrar, realm, Contact behavior, refresh policy, transport or credential lifecycle for an arbitrary account. Copy these only from the current implementation record.
For a static path, distinguish network source authorization from SIP identity and outbound caller-ID permission. For a registered path, distinguish a challenge and authenticated REGISTER from a stored binding, delivered inbound INVITE and permitted outbound call. Do not weaken firewall, password or certificate policy merely to make a generic PBX example register.
Decompose every resilience claim into one controlled path
The one-sheet lists PSTN failsafe routing, load balancing across multiple IP addresses, geo-redundant routing, redundant SBCs and customer redundancy through multiple SIP or PRI trunks. These are different controls with different owners. Map the normal destination, alternate, selection order, health input, response or timeout trigger, retry interval, restoration rule and failure domains for each enabled mechanism.
Treat the marketed features as new-call controls until account evidence proves more. They do not establish that two routes avoid the same power, internet, firewall, PBX, provider or downstream carrier dependency, and they do not prove survival of an established dialog. Run bounded authorized cases for rejected, unanswered and unreachable destinations and retain the resulting route and timestamps.
Separate capacity, visibility and emergency acceptance
Peerless associates the number of SIP channels with simultaneous calls and says users can change channel counts through the portal. Record the ordered and activated value separately from active calls, call-start rate, PBX channels, licences, bandwidth and observed rejection. A portal change request is not proof that new capacity is active.
Portal call-detail and DID-usage views can aid correlation, but they do not establish complete records, retention, billing accuracy, alerting or service restoration. E911 is listed as an available feature, not a documented address workflow. Keep service activation, number, physical address, accepted outbound identity, callback route and the provider-approved non-live test record together for every location.
Resolve technical and commercial unknowns in a dated order
Require the current worksheet to define signaling peers, authentication, registration, transports, certificates, media addresses, codecs, packetization, DTMF, fax, protected media, concurrency, call-start limits, number availability, emergency handling, records, alarms, support and rollback. Keep SMS and MMS separate unless number capability and an application path are explicitly ordered.
Obtain dated commercial terms for channels, activation, usage, numbers, E911, toll-free service, porting, support, taxes, commitments, renewal and cancellation. Public metered, unlimited, inbound-charge and flexible-billing language is not a quote. No account, order, number, trunk, portal role, PBX, route, call, media path, failover, emergency workflow, message, capacity, price, availability, compatibility or support response was tested for this guide.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Peerless Network SIP Trunking ↗
- Peerless Network SIP Trunking one-sheet ↗
- Peerless Portal Channel Partners brochure ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.