Start with the ordered handoff
HKT presents the service as a way to connect enterprise communications through SIP, but the public page is not an implementation worksheet. Record the legal service name, site, access circuit, PBX or SBC owner, peer addresses, authentication method, number blocks and change contacts from the order.
Do not assume REGISTER, IP authentication, a registrar name or a particular dial-string format. Preserve the live signaling exchange and the provider-approved configuration for the exact service.
Documented service facts
Reviewed 2026-10-07. Compare SIP trunk services →
SIP authentication
Not verifiedHKT's public product page does not publish a universal registration, credential, certificate or source-address authentication profile. Obtain the implementation record for the ordered circuit and preserve the PBX or SBC object, peer addresses, credentials or certificates and observed authorization exchange.
SIP registration
Not verifiedThe reviewed public material does not establish SIP REGISTER as the connection model or publish a registrar, realm, Contact policy or expiry. Do not infer registration from the SIP Trunk name; retain the provider handoff and observed signaling for the installed service.
Inbound delivery
Not verifiedThe product is presented for enterprise calling, but the reviewed page does not publish one inbound number format, Request-URI rule, asserted identity policy or porting workflow. Capture the ordered number inventory, activated state, delivered identities and the exact PBX route that matched each acceptance call.
Routing and failover
DocumentedHKT describes built-in redundancy and disaster recovery. The public page does not define the topology, trigger, recovery objective, established-call behavior or customer-side dependency, so treat those as design and test questions. Record the ordered architecture and run an approved failure exercise before making a continuity claim.
Number and regional availability
Not verifiedThe reviewed product page is an HKT Enterprise Hong Kong offer, but it does not establish serviceability, number inventory, port eligibility or activation at a particular address. Obtain a dated order and written feasibility result for every site and number block.
Audio codecs and DTMF
Not verifiedThe public page does not publish a codec list, packetization, RTP address policy, DTMF method, transcoding boundary or media anchoring rule. Preserve both SDP bodies, the selected codec and telephone-event mapping, DTMF observations and decoded audio in each direction during acceptance.
T.38 fax
Not verifiedThe reviewed SIP Trunk material does not establish T.38, G.711 pass-through, redundancy, page limits or supported gateways. Treat fax as a separate workflow and acceptance plan tied to the exact gateway, codec path, access service and destination.
Signaling and media encryption
DocumentedHKT advertises encrypted communications, but the public page does not identify the signaling transport, TLS versions, certificate validation, SRTP profile, keying method or leg-by-leg boundary. Preserve the ordered security design and observed SIP, SDP and media negotiation rather than translating the marketing claim into a protocol guarantee.
Concurrent calls and call starts
Not verifiedHKT describes the ability to scale communication lines, including for peak contact-center demand, but does not publish a universal channel entitlement, call-start rate or access-bandwidth rule. Record ordered channels, burst controls, PBX and SBC ceilings and measured acceptance results separately.
Emergency calling
Not verifiedHong Kong Police documents 999 as a 24-hour emergency service, but the reviewed HKT SIP Trunk page does not define the trunk's emergency-call entitlement, location treatment or validation process. Obtain the provider's current procedure, maintain site and number records and an alternative calling method, and use only an approved test route.
Pricing model
Not verifiedThe public product page provides a sales enquiry rather than a complete dated rate card. Obtain a written quote that separates access, channels, numbers, usage, optional features, installation, support, taxes, term, reconfiguration and termination before comparison.
Administration and support
Not verifiedThe reviewed pages do not publish one SIP Trunk portal, support target, maintenance process or responsibility matrix. Preserve the named operational contacts, escalation path, monitoring boundary, maintenance notices, change process and acceptance record in the service documentation.
SMS and MMS
Not verifiedThe page discusses SIP as a technology used for multimedia and instant messaging, but it does not establish SMS or MMS entitlement on HKT trunk numbers, sender registration, API access, throughput, webhook security, retention or price. Do not convert the general description into a messaging feature claim.
Translate encryption into protocol evidence
HKT advertises encrypted communications. That does not identify the SIP transport, certificate validation rules, SRTP keying method or whether every leg is protected. Capture the ordered security boundary, the negotiated transport, both SDP bodies and the observed media profile.
Keep a distinction between provider-network protection, the PBX-facing handoff and any downstream recording, contact-center or remote-user leg. A high-level encryption claim is not proof of end-to-end confidentiality.
Treat redundancy and scale as testable design
The product page describes built-in redundancy, disaster recovery and flexible line scaling. Ask where redundant elements sit, what triggers recovery, which customer components remain single points of failure and whether established calls survive.
Capacity also needs an order-specific record: concurrent calls, call-start controls, access bandwidth, SBC and PBX ceilings and any peak-change lead time. Validate normal load and one approved failure case before reporting continuity or capacity.
Prove numbers, media and DTMF
Create an acceptance matrix for inbound and outbound calls, presented identity, number normalization, codec selection, RTP endpoints and DTMF. Store both offers and answers and note whether telephone events, in-band tones or SIP signaling carried each tested digit.
Fax, video and messaging need their own entitlement and test plans. A general explanation that SIP can carry multimedia or messaging does not establish T.38, video, SMS or MMS on a purchased trunk.
Bind emergency calling and price to current records
Hong Kong Police operates the 999 emergency-call service, but the public HKT SIP Trunk page does not state how this product presents location, which numbers are entitled or how a customer should validate the route. Obtain the current provider procedure, keep site and number records accurate and maintain an alternative calling method.
Use a dated quote for access, channels, numbers, usage, options, installation, support, taxes and term. The public page is not evidence of serviceability, compatibility, current price, availability or laboratory performance. No HKT account or live service was tested for this record.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- HKT Enterprise SIP Trunk product ↗
- HKT Enterprise voice solutions ↗
- Hong Kong Police 999 emergency-call service ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.