peoplefone SIP Trunk: registration, fallback and security boundaries

Identify the country account, line and ordered service

peoplefone operates country-specific account contexts and presents SIP lines, SIP-TRUNK, hosted PBX, app, fax, Teams and other services as adjacent offerings. Record the legal account, country, ordered line type, numbers, PBX or SBC, locations, access, support path and current portal values. This profile is scoped to the reviewed Swiss trunk material; it is not a promise that another country uses identical routing, emergency or commercial rules.

A generic claim that a VoIP-capable PBX can connect is not certification of an exact release, module set or deployment. The published certified-PBX list contains dated software versions, so retain the exact platform and the provider or vendor evidence that applies to it.

Keep portal login, SIP credentials and registration separate

Each SIP line has its own proxy, SIP username and SIP password, distinct from the customer-account login. Preserve the proxy and DNS result, transport, user, authentication identity, Contact, expiry, challenge and response without copying secrets into a ticket. Record every authorized registering device and the provider contact set.

peoplefone allows several registrations but recommends one device per line. Multiple contacts may therefore be permitted, yet they can alter call forking and failure behavior. A successful REGISTER proves a contact transaction, not SIP-TRUNK activation, number assignment, inbound delivery, outbound identity, media or emergency routing.

Prove trunk activation, number routing and identity

The SIP-TRUNK line type is a portal control for PBX-oriented inbound information. Number blocks or individual numbers are then assigned to a SIP line, and displayed-number or CLI Open controls govern a separate outbound identity path. Record each layer independently.

For inbound calls, retain the called number as delivered, Request-URI, identity headers, selected PBX route and destination. For outbound calls, retain the authorized presented identity, privacy handling and carrier response. Ownership of a number, inbound assignment and permission to present it are not interchangeable.

Resolve media, firewall and protection on the call

The network guidance publishes PCMA, PCMU, G.722 and G.729a, while the firewall page lists Swiss signaling and media inputs and recommends limiting rules to peoplefone. Apply current provider values to the selected account and validate the actual SIP and RTP tuple. Preserve SDP, codec, DTMF representation, RTP directions, packet loss and decoded audio.

TLS signaling and SRTP media remain separate. SRTP requires provider activation on the SIP line as well as device policy, and peoplefone limits its encryption statement to calls that remain within its network. A TLS port, a configured SRTP switch or a lock icon is not proof of certificate validation, media keying or end-to-end protection.

Treat fallback forwarding as a new-call path

peoplefone documents an offline role that can forward exact numbers or prefixes after the SIP line becomes offline. Map the registration timer, provider state, filter, alternate destination, number presentation, call cost, capacity and recovery path. Do not represent this as survival of an established call or preservation of PBX features.

In an approved exercise, observe loss detection, one new inbound call through the alternate path, restoration, return to primary and a nearby number that should not match the filter. Keep provider forwarding, access diversity, PBX redundancy and endpoint failover as separate controls.

Accept emergency, commercial and support boundaries

For Switzerland, verified location information must be associated with the relevant SIP line and number, and country boundaries remain explicit. Confirm the service address, callback number, nomadic-use rule, power and Internet dependencies, accessible alternative and provider-approved validation process at every site. Do not place an uncoordinated emergency call.

Before acceptance, obtain current number availability, port result, capacity and CPS terms, fax position, quote, rates, taxes, support entitlement and escalation path. Test registration, inbound and outbound calls, identity, audio, DTMF, protection, fallback and rollback on the exact approved PBX release. No such account or call was tested for this guide.

Diagnose fallback that never takes the new call

When an offline SIP line does not forward a new inbound call, use the peoplefone fallback diagnostic. It separates PBX registration loss, provider offline state, rule ownership, exact or prefix matching, the alternate call leg and restoration.