Simwood Hosted SIP Trunks: inbound registration and routing evidence

Keep Hosted and carrier service scopes separate

Simwood publishes Hosted SIP Trunks alongside Carrier Services, Wholesale, Partner and Direct material. Start with the ordered product, account portal, assigned server and authentication model. Do not use a Carrier Services or Wholesale template to relax the boundary for a Hosted trunk, and do not copy Partner or Direct firewall data into another service without current confirmation.

The Hosted overview describes per-trunk credentials and allocated Trunk Channels. These public properties do not establish one account's current credentials, number assignment, concurrency, price or availability.

Outbound success does not prove an inbound binding

The hosted interop guide documents outbound INVITE authorization through a 401 digest challenge without requiring registration. The same guide says registration is required for inbound calls. Preserve the outbound challenge and result as a bounded control, then separately capture the assigned registrar, REGISTER challenge, authenticated REGISTER, accepted expiry, Contact and current binding.

A working outbound call proves neither that the provider has a current inbound Contact nor that the called number selects the expected trunk. Use the paired diagnostic to locate the first missing boundary.

Separate Contact-user addressing from the called number

For Hosted trunks, the interop guide says the registered Contact user can shape the user in the inbound INVITE Request-URI. It separately says the To user carries the callee number that should be used for routing. Record Request-URI, To, source, transport, endpoint identification, context and the first matching FreePBX or Asterisk route.

Do not broaden source trust or create a catch-all route simply because the two user values differ. First prove whether the mismatch belongs to the registration Contact, provider number route, PJSIP endpoint, context or dialplan normalization.

Treat the Asterisk 16 sample as version-scoped evidence

Simwood labels its sample as an Asterisk 16 PJSIP example, provides it as-is and says it does not support Asterisk. Its registration, auth, AoR, endpoint, identify and header-parsing pattern can explain object ownership, but it is not a current universal recipe for Asterisk or FreePBX. Compare it with the installed branch, generated configuration and loaded objects before adapting anything.

The sample contains an older, short source-address list. Simwood's current whitelisting page, updated October 31, 2025, lists substantially more ranges, limits itself to Partner and Direct, excludes Wholesale and says the ports are not all-inclusive. Neither page establishes a complete Hosted firewall policy; obtain current service-specific values.

Keep signaling, media and failover evidence distinct

The hosted secure-calling article documents TLS on 5061 and SRTP settings using SDES. Confirm the assigned host, certificate identity and chain, peer validation, negotiated transport, SDP crypto result, RTP endpoints and fallback policy. An open TLS port or configured SRTP option is not proof that a completed call protected both signaling and media.

The current product page advertises ring timeouts, time-of-day routing, failover options and forwarding. The reviewed public material does not establish one universal response-code matrix, timer, destination order, restoration interval or established-call survival result. Freeze the portal rule and test only an authorized new-call condition.

Run one bounded acceptance trace

For one authorized number and time window, record product scope, portal route, registrar and binding, provider attempt, customer-edge receipt, Request-URI, To, endpoint identification, context, route match, answer, SDP and each media direction. Preserve timestamps and redacted correlation identifiers rather than credentials or call content.

Confirm current number eligibility, portability, emergency workflow, messaging, fax, codecs, DTMF, channel allocation, call-start rate, pricing and support for the exact order. No account, PBX, registration, packet, media stream or live call was inspected for this guide.

Diagnose outbound success with missing inbound delivery

Use the Simwood inbound diagnostic to join Hosted registration, Contact-user addressing, called-number routing and loaded PBX state.