Bulk Solutions SIP trunking: direction-specific identity and route evidence

Model inbound and outbound as separate provider relationships

Record the account, DID, inbound trunk group, customer destination, outbound trunk group, authentication method, service hostname, caller identity and PBX objects for each direction. Bulk Solutions publishes workflows where inbound delivery uses an IP-authenticated destination while outbound calls use registration credentials. That is evidence that the directions can have different owners, not a guarantee that every account or PBX should copy the same combination.

A successful outbound call proves neither DID assignment nor inbound destination reachability. An inbound INVITE proves neither outbound authorization nor the caller identity accepted for termination.

Treat source-IP authorization and registration as different controls

For IP-authenticated outbound calling, preserve the portal host entry, translated public source address, propagation time and request sent to the provider service hostname. For credential mode, preserve the trunk-group username, challenge, authenticated retry and any required registration state without exposing the secret.

The current registration workflow notes that some accounts can require an active registration before digest-authenticated INVITEs are accepted. Keep REGISTER, an OPTIONS-style connection test, INVITE challenge and completed call as separate evidence; none substitutes for the others.

Trace inbound delivery from DID assignment to the first PBX match

Confirm the DID is assigned to the intended inbound trunk group and retain the exact provider destination. Bulk Solutions documents 11-digit request-URI delivery by default for the IP path. Capture the INVITE and compare its source, destination, Request-URI, To and asserted identity with the loaded Asterisk endpoint identification, context and first FreePBX inbound-route match.

Do not enable anonymous SIP as a discovery shortcut or trust every packet that presents the DID. Restrict the signaling boundary to the current provider sources and prove the request was matched by the intended trunk object.

Use the provider hostname without flattening DNS and firewall evidence

Bulk Solutions recommends sip.bulkvs.com and publishes SRV-oriented redundancy guidance. Preserve the query type, current answers, TTL, chosen target, transport, provider source and customer-edge receipt. A hostname in configuration does not prove the resolver returned every current target or that the firewall admits the source used for one call.

Provider-network diversity is not a customer failover contract. The reviewed material does not establish one universal set of customer-destination priorities, advancement responses, timers, retry counts, restoration intervals or established-call survival behavior.

Keep the legacy FreePBX template inside its version boundary

The public Bulk Solutions PDF identifies FreePBX 14.0.4.5 and configures a chan_sip trunk. Preserve it only as provider terminology and legacy screen context. Do not copy its driver, fields, ports, dial strings or trust settings into FreePBX 17 PJSIP without mapping them to the installed release and current generated objects.

On FreePBX 17, make durable changes through the supported trunk, Asterisk SIP Settings and inbound or outbound route owners. Then inspect generated and loaded PJSIP endpoint, identify, AOR, registration and transport state before testing a call.

Accept voice, media and emergency paths independently

For one authorized inbound and outbound voice call, retain the first provider attempt, PBX route, SIP response, negotiated SDP, RTP direction, decoded audio and hangup. The published codec or DTMF list does not establish every downstream route, and an answered call does not prove two-way media.

Keep 911 routing and caller identity outside the general voice acceptance result. Use the Bulk Solutions emergency diagnostic and the documented 922 verification path before any authorized live test. No availability, compatibility, capacity, pricing or laboratory result is claimed.

Diagnose the inbound path without changing working outbound identity

Use the Bulk Solutions inbound diagnostic to trace DID assignment, trunk group, destination, edge receipt, PJSIP identification, route and media.