Bind authentication and registration to the selected country
Allstream’s quick-start says signaling is matched to customer IP addresses. Its signaling table identifies IP Match for U.S. and Canadian services, while registration with Digest Authentication and the associated outbound 401 challenge are described as mandatory for U.S. service. Do not transfer the U.S. registration path to a Canadian order or infer that a portal login is a SIP credential. Preserve the country, service option, ordered static addresses, FQDN, peer direction, challenge sequence and accepted handoff.
The guide also documents OPTIONS on SIP trunks and lists Native SIP and PRI-SIP portal options. OPTIONS reachability, a SIP registration, an IP match, a portal session and an accepted call are different states.
Documented service facts
Reviewed 2026-10-25. Compare SIP trunk services →
SIP authentication
DocumentedThe quick-start documents customer-address IP Match for U.S. and Canadian service, and separately limits mandatory digest credentials and the outbound 401 challenge to U.S. service. Preserve country, service option, static addresses, peer direction and current handoff.
SIP registration
DocumentedRegistration with Digest Authentication is documented as mandatory for the U.S. path, while IP Match applies in the U.S. and Canada. OPTIONS, portal login, registration, IP match and accepted calls remain different states.
Inbound delivery and identity
DocumentedThe quick-start lists extended DIDs and P-Asserted-Identity behavior; portal pages expose group- and individual-DID controls. Number inventory, port completion, provider selection, delivered identity, edge receipt and PBX route remain separate.
Forwarding and continuity
DocumentedPortal controls include Immediate, Busy/No Answer, Unavailable and Selected Callers forwarding. The quick-start separately lists trunk overflow to a telephone number, multi-endpoint failover and load sharing across at most two endpoints. The selected order and portal object govern.
Number and regional availability
Not verifiedThe reviewed first-party records do not establish current serviceability, number inventory, portability, lead time or regulatory eligibility for a requested address and number block. Retain a dated qualification and port result.
Codecs, DTMF and RTP
DocumentedThe quick-start lists G.711, G.722 and G.729 profiles, in-band and RFC 2833 DTMF combinations, RTP or SRTP UDP 10000–65535 and no network transcoding. The ordered profile and negotiated call remain authoritative.
Fax
DocumentedThe quick-start describes G.711 pass-through and T.38 with G.711 fallback, while warning that T.38 depends on end-to-end compatibility. Entitlement, gateway behavior, switchover and completed pages remain unverified.
Signaling and media protection
DocumentedThe guide lists TCP 5061 and RTP or SRTP plus public, NAT and private-VPN topologies. These do not prove TLS identity, client certificates, SRTP negotiation or protected intermediary legs. Current provider-issued peer ranges and observed negotiation govern.
Concurrent calls and call starts
Not verifiedThe quick-start recommends a G.711 planning allowance per simultaneous call and rejects excessive attempts and short-duration traffic, but it does not publish one selected order’s sessions, calls per second, burst or PBX limit. Keep those quantities separate.
Canadian 911
DocumentedThe Canadian advisory distinguishes fixed native, fixed non-native and nomadic service, requires a current Registered Location and records power, broadband and update-delay boundaries. Private switches must send a correct ten-digit caller number, with the BTN described as the trunk-group default when identity is missing or invalid.
Pricing and contract
Not verifiedNo complete selected-account price was established. Bind access, trunks, DIDs, continuity features, PBX or SBC work, usage, support, taxes, term, renewal and termination to the dated order, contract and bill.
Portal, certification and support
DocumentedAllstream publishes SIP portal access, PBX certification rows, vendor setup guides and 24/7 Canadian repair contact information. Portal state, historic certification row, installed release, current acceptance, trouble ticket and response target remain separate evidence.
SMS and MMS
Not verifiedThe reviewed SIP-trunk records do not establish SMS or MMS entitlement on trunk numbers, sender registration, API access, throughput, webhook security, retention or price. Treat messaging as a separate service unless the current order says otherwise.
Record the exact Internet, NAT or private topology
The quick-start presents public-IP without NAT, NAT with an application-layer gateway, NAT without an ALG and private-IP VPN patterns. For an Internet order, the static public address is part of the handoff; the NAT-without-ALG example also records the customer PBX private address. Private SIP uses dedicated VRF or VLAN separation toward the Allstream SBC.
These are documented design patterns, not interchangeable templates. Preserve the ordered access, public and private addresses, NAT owner, ALG state, Allstream SBC FQDN and current source ranges. A reachable firewall port does not establish identity, routing or media.
Keep signaling, codec, DTMF, fax and media evidence separate
The quick-start lists UDP 5060, TCP 5061, RTP or SRTP UDP 10000–65535, G.711, G.722 and G.729 profiles, in-band or RFC 2833 DTMF combinations, and T.38 with G.711 fallback. It says G.729 and T.38 depend on end-to-end compatibility and states that network transcoding is not provided. Those rows do not prove the selected transport, certificate, media protection, codec, digit delivery or fax result.
For an authorized call, preserve both SDP bodies, final payload mapping, packetization, DTMF method, RTP tuples, protection profile and decoded result. Treat published port ranges as a provider boundary, not permission to expose a PBX broadly.
Separate portal forwarding from trunk continuity
Allstream’s portal pages document Immediate, Busy/No Answer, Unavailable and Selected Callers forwarding. They also distinguish group-level and individual-DID scope, with Unavailable Call Forwarding described as an exception to individual-DID configuration. The quick-start separately lists trunk overflow to a telephone number, multi-endpoint failover and load sharing across at most two endpoints.
Unavailable Call Forwarding, a DID forward, trunk overflow, multi-endpoint failover, SIP pooling, customer WAN failover and a PBX route are distinct controls. Record the service family, object scope, destination, effective time, provider attempt and restoration owner before changing any layer.
Treat certification and setup guides as bounded records
Allstream publishes a certified IP PBX table and vendor setup guides, including Asterisk and FreePBX material. Many rows name specific historic releases. A listed vendor or release is evidence of that published certification row, not proof that a current product, later release, custom module or selected configuration is supported.
Preserve the installed PBX, release, SIP driver, loaded endpoint, generated and runtime state, exact Allstream service option and current acceptance statement. A vendor guide can seed comparison, but the observed exchange and completed call govern the deployed result.
Keep Canadian 911 location and acceptance independent
Allstream’s Canadian advisory distinguishes fixed native, fixed non-native and nomadic VoIP, requires a current Registered Location, records outage, broadband and power dependencies, and warns that updates are not immediate. For a private switch it requires a correct ten-digit calling-party number and describes the billing telephone number as the trunk-group default when the switch receives no valid calling-party number.
Do not use an uncoordinated emergency call to test forwarding or failover. Keep registered location, effective update, outbound identity, default BTN, PBX route, callback, alternate means and provider-approved validation separate. No Allstream account, portal, PBX, packet, call, media, failover or emergency result was tested for this guide.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- Allstream SIP Trunking Quick Start Guide ↗
- Allstream SIP Portal Overview — Native SIP and PRI-SIP ↗
- Allstream SIP Portal Overview — SIP Extreme and SIP Gateway ↗
- Allstream SIP Portal User Guide ↗
- Allstream SIP Portal — Logging In ↗
- Allstream Certified IP PBX List ↗
- Allstream SIP Trunking IP-PBX Vendor Setup Guides ↗
- Allstream toll-fraud protection guidance ↗
- Allstream advisory for 911 access using VoIP services in Canada ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.