Bind the review to one SIP account and commercial scope
CommPeak documents password-based and IP-based SIP accounts. Identify the contracting entity, account ID, authentication method, approved source addresses, routes, DIDs, caller identities, channels, support entitlement and intended PBX or SBC. Keep termination, inbound numbers, messaging, Cloud PBX, Dialer and Softphone scope separate unless the signed order joins them.
Export the current portal record before change without exposing secrets. Preserve the SIP domain, credential owner or IP allowlist, access rules, caller-ID rules, route and budget controls, channel limits, alert destinations and responsible teams. A product-page capability is not proof that a control is enabled for the selected account.
Documented service facts
Reviewed 2026-10-15. Compare SIP trunk services →
SIP authentication
DocumentedCommPeak documents both password-based and IP-based SIP accounts. The reviewed pages do not establish which method, username, source addresses, challenge behavior, secret rotation or access rules apply to a selected account; preserve the portal-issued account type without publishing credentials.
Registrar, proxy and DNS
DocumentedThe current FreePBX and Asterisk guides identify sip.commpeak.com as the SIP domain for their examples. They do not document one universal DNS record set, target order, proxy policy, registration interval or Contact behavior for every account, so retain the portal-issued settings and observed DNS and registration state.
Numbers and inbound delivery
Not verifiedCommPeak publishes DID numbers as a separate network product, but the reviewed trunk pages do not establish inbound service, inventory, portability, delivered Request-URI or identity, or primary and alternate targets for a selected account. Treat inbound numbers and routing as separately accepted scope.
Routing and failover
DocumentedThe product page describes flexible routing, geo-redundant infrastructure and automatic failover to backup carriers. It does not define the selected account topology, trigger, target order, DNS dependency, established-dialog behavior or recovery. Obtain the current route design and observe only authorized failure tests.
Service and number coverage
DocumentedCommPeak markets A-Z termination and more than 190 calling destinations. Coverage, number availability, portability, restrictions and allowed use can change; qualify every source, destination and number type against the current portal, quote and compliance requirements.
Codecs, DTMF and RTP
DocumentedThe FreePBX guide selects ulaw and alaw, while the Asterisk example also lists g729 and rfc2833 DTMF. Those guide examples do not prove the accepted codec, licensing, packetization, DTMF, RTP range, transcoding or quality profile for a selected account. Preserve negotiated SDP, RTP tuples and decoded results.
Fax and analogue dependencies
Not verifiedNo current T.38, audio pass-through, fax-machine or analogue-adapter acceptance statement was verified in the reviewed pages. Inventory fax, alarms, lifts, door entry, payment and monitoring systems separately and retain the approved replacement or test result for each dependency.
Signaling and media protection
DocumentedCommPeak instructs third-party SIP clients to enable SRTP manually when using TLS. The product page also describes encryption and access controls, but neither source establishes the selected TLS versions, certificate names, trust model, media profile, keying, downgrade behavior or protection across every intermediary leg.
Channels and call starts
DocumentedThe product page says customers can add channels and adjust routing, and the FreePBX guide exposes a local Maximum Channels field. Neither proves the ordered simultaneous-call entitlement, direction sharing, calls-per-second limit, burst behavior or overload response; obtain account limits and test only within authorization.
Emergency calling
Not verifiedNo selected-account emergency-calling eligibility, registered location, callback identity, propagation time, failure behavior or approved test process was verified. Do not infer emergency service from ordinary termination or DID service; obtain written scope and keep an accessible independent emergency method until acceptance.
Pricing, SLA and contract
DocumentedCommPeak publishes usage-based voice pricing, separately billed SIP and DID services, country-specific compliance documents and custom high-volume quotes. The reviewed public pages do not establish the selected route rates, taxes, surcharges, deposits, SLA remedy, term, suspension or cancellation conditions; preserve the dated quote and contract.
Monitoring, support and demarcation
DocumentedThe product page describes dashboard monitoring, SIP and call error logs, text alerts and 24/7 support, while CommPeak publishes a status page. These channels do not prove current account health, restoration time or the PBX, SBC, access and provider demarcation. Record ownership, evidence retention and escalation for the selected account.
SMS and MMS
Not verifiedCommPeak offers messaging products, but the reviewed SIP-trunk material does not establish SMS or MMS on selected voice numbers. Treat messaging as separate until number eligibility, registration, consent, throughput, API or portal behavior, retention, filtering and price are documented.
Choose the PBX procedure by driver and version
The current FreePBX guide selects Add SIP (chan_pjsip) Trunk and supplies username, secret and SIP-domain fields. The current Asterisk guide instead edits sip.conf, uses sip reload and checks sip show peers, which is a chan_sip-style workflow. Do not merge the two examples or copy either into an unknown release.
Record the PBX and module versions, object owner and generated configuration before editing. For PJSIP, preserve endpoint, auth, AOR, registration and identify state as applicable. For any legacy chan_sip deployment, treat migration and support status as separate work. Compare the loaded runtime object with the portal-issued account rather than relying on labels in a GUI or sample file.
Separate account state from end-to-end call evidence
A reachable SIP domain, successful registration, responsive peer or online portal indicator proves only part of the path. For an authorized outbound call, retain DNS results, request URI, From and asserted identity, authentication exchange, final response, destination answer, SDP, RTP tuples and decoded media. For inbound scope, add number ownership, provider route, delivered identity, PBX match and final destination.
The FreePBX guide includes outbound-route patterns, and the Asterisk guide requires dialplan configuration. Verify normalization and authorization at the PBX boundary before changing provider settings. A local maximum-channel field is not evidence of the provider entitlement.
Verify media and protection as negotiated
CommPeak tells third-party SIP clients to enable SRTP manually when TLS is used. Treat that as a configuration warning, not proof that TLS or SRTP is active. Capture the signaling transport, certificate name and chain, protocol and cipher, SDP crypto or DTLS attributes where applicable, RTP endpoints and whether every intermediary leg meets the ordered policy.
The FreePBX and Asterisk examples mention codecs and DTMF choices, but the selected account and destination may differ. Preserve offer and answer, packetization, transcoding, DTMF result, loss, jitter and decoded audio. Keep fax and analogue devices outside ordinary voice acceptance until separately supported and tested.
Accept routing, monitoring, support and rollback
CommPeak publishes flexible routing, monitoring dashboards, SIP and call error logs, alerts, status information and round-the-clock support. Map each operational signal to an owner and retention period. Record which team controls PBX routing, firewall and NAT, access, provider routes, caller identity, DIDs, spend controls and escalation.
Before cutover, define expected inbound and outbound results, permitted load, failure triggers, alternate paths, recovery, rollback and stop conditions. Exercise only approved failures and preserve signaling, media and user outcome separately. Public claims about global reach, redundancy or uptime do not replace the selected route list, order, service schedule or observed acceptance evidence.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- CommPeak SIP trunking ↗
- CommPeak documentation and developer hub ↗
- CommPeak SIP account configuration ↗
- CommPeak FreePBX SIP trunk guide ↗
- CommPeak Asterisk PBX SIP trunk guide ↗
- CommPeak pricing overview ↗
- CommPeak service status ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.