Identify the exact trunk order and point of demarcation
IP Telecom presents SIP trunks for Irish businesses as connectivity between an existing IP PBX and the public network. Record the legal customer, sites, numbers, ordered channels, access circuits, PBX or SBC, service handoff, support entitlement and signed product schedule. Keep the SIP trunk separate from IP Telecom hosted PBX, broadband, Teams integration and adjacent products.
The product schedule measures availability at the provider point of demarcation and excludes customer Internet, network, equipment and third-party causes from its downtime calculation. Map that boundary physically and operationally: provider edge, access owner, firewall or SBC, PBX, LAN, power and endpoints need named monitoring and restoration owners.
Documented service facts
Reviewed 2026-10-15. Compare SIP trunk services →
SIP authentication
Not verifiedThe reviewed public pages do not identify whether a selected trunk uses registration credentials, source-address trust, mutual TLS or another account-specific control. Obtain the issued technical handoff and preserve the authentication identity, source policy, challenge behavior and secret owner without exposing credentials.
SIP registration
Not verifiedNo public registrar, proxy, expiry, Contact policy or registration failover sequence was verified. Do not invent an address from the provider domain or copy another customer profile. Record the supplied targets, DNS answers, loaded PBX objects and observed transaction for the exact order.
Numbers and inbound delivery
DocumentedIP Telecom describes SIP trunk connectivity to the public network and support for porting geographic, non-geographic, DDI and freephone numbers. Those statements do not establish current inventory, port eligibility, delivered Request-URI, identity headers, primary target or alternate delivery for a selected order. Preserve the port and routing handoff plus one authorized inbound trace.
Failover and continuity
DocumentedThe service page recommends resilient access such as primary plus backup broadband or 4G/5G and says resilience is designed around the customer risk profile. The product schedule measures provider availability at its point of demarcation and excludes customer access, network and equipment causes. Exact SIP target failover, detection, rerouting and restoration remain unverified.
Service area and number coverage
DocumentedThe reviewed service is presented to Irish businesses and says existing geographic, non-geographic, DDI and freephone numbers can be ported. Exact new-number inventory, rate centres, portability, service-address eligibility, activation timing and international service remain order specific.
Codecs, DTMF and call quality
Not verifiedIP Telecom describes fully IP service, HD-quality audio, QoS-aware routing and customer-side QoS, VLAN and SIP-ALG practices, while its product schedule makes voice quality dependent on the customer Internet connection. No public codec, packetization, DTMF or RTP-address profile was verified. Observe SDP, RTP and decoded results on the approved path.
Fax and analogue-dependent devices
Not verifiedThe copper-transition guidance tells businesses to inventory fax, alarm, lift, door-entry, payment and monitoring equipment, but it does not establish T.38, audio fax, modem, alarm or lift compatibility on the SIP trunk. Qualify every non-voice device with its supplier and a representative approved test before retiring the existing service.
Signaling and media protection
DocumentedThe service page says encrypted SIP using SIPS or TLS and SRTP can be offered where the PBX supports it. That is an option statement, not proof that a selected order enables it or that every hop is protected. Obtain the certificate, name-validation, trust, cipher, media-keying and intermediary profile and verify the negotiated path.
Channels and call-start limits
DocumentedIP Telecom defines one channel as one simultaneous call and describes flexible channel counts plus additional burst capacity during peaks. No account-specific concurrent-call pool, burst entitlement, calls-per-second limit, inbound/outbound sharing rule or overload response was verified. Use the signed order and controlled load evidence.
Emergency calling
Not verifiedThe migration guidance says businesses should consider emergency calling, power loss and Internet disruption, but the reviewed public sources do not define SIP-trunk emergency-number support, location registration, callback identity, nomadic restrictions or a provider-approved test process. Keep an accessible independent method until those controls are evidenced.
Pricing, terms and usage policy
Not verifiedThe service page describes a pay-as-you-use arrangement with a minute bundle and directs customers to an individual quote rather than publishing one complete price list. The fair-use page applies changing business-use and acceptable-use controls across IP Telecom services. Use the signed order, current tariff, taxes, term, limits and cancellation terms instead of reproducing a marketing amount.
Support and demarcation
DocumentedIP Telecom publishes separate sales, customer-service and technical-support contacts. Its SIP-trunk product schedule defines availability at the provider point of demarcation and assigns customer network and equipment beyond that point to the customer. Record the actual demarcation, monitoring, escalation, maintenance and restoration owners.
SMS and MMS
Not verifiedThe reviewed SIP-trunk, product-terms, fair-use and migration pages do not establish SMS or MMS eligibility, number support, API, webhook, throughput, retention, compliance workflow or pricing. Treat messaging as a separate product and qualify each number and use case independently.
Use the issued technical handoff without inventing defaults
The reviewed public material does not publish a complete registrar, outbound proxy, authentication, transport, port, DNS, codec, DTMF or RTP profile. Obtain the provider-issued handoff for the selected order and preserve its revision. Do not derive a registrar from the marketing domain, copy another customer configuration or treat general compatibility language as certification.
For acceptance, capture loaded PBX objects and one authorized inbound and outbound transaction: resolver answers, source and destination tuples, Request-URI, From, asserted identity, Contact, challenge and final response. Keep successful signaling separate from destination answer, negotiated media and user experience.
Design access resilience separately from SIP routing
IP Telecom recommends resilient connectivity such as a primary link plus backup broadband or 4G/5G and says continuity should be designed around the customer risk profile. Access failover, provider-side SIP target selection, alternate inbound delivery, PBX redundancy and endpoint mobility are different controls. A working backup link does not prove that signaling source policy, DNS, NAT or media will survive the transition.
Exercise one approved new call through each designed path and restoration sequence. Record detection, DNS and route changes, registration or peer state, inbound target, caller identity, delay, media, return to primary and an unrelated control call. Do not represent any mechanism as preserving an established call unless that behavior is separately documented and observed.
Qualify capacity, media and protection on the live design
The service page defines one channel as one simultaneous call and describes flexible counts and peak bursting. It also describes HD audio and optional encrypted signaling and media using SIPS or TLS and SRTP where the PBX supports them. These are service descriptions, not the selected account entitlement or negotiated result.
Obtain the concurrent-call pool, burst conditions, calls-per-second controls and overload response. For representative calls, retain SDP, codec, packetization, DTMF, RTP endpoints, QoS treatment, loss, jitter and decoded audio. Validate certificate names and trust, cipher selection and SRTP keying; a configured TLS port, firewall rule or lock icon is not end-to-end proof.
Port numbers without hiding emergency and analogue dependencies
IP Telecom says geographic, non-geographic, DDI and freephone numbers can be ported, subject to the customer migration. Preserve the exact inventory, losing-carrier record, authorization, accepted port date, temporary routing, rollback and inbound destination. A general portability statement does not guarantee eligibility, current inventory or a specific completion date.
The provider migration guidance tells businesses to consider emergency calling, power and Internet disruption, fax, alarms, lifts, door entry, payment terminals and monitoring equipment. The reviewed sources do not define SIP-trunk emergency routing or compatibility for those devices. Maintain an accessible independent emergency method and qualify each non-voice device before retiring its legacy path.
Accept the commercial and operational service actually ordered
The public page describes pay-as-you-use service with a minute bundle but directs customers to an individual quote. Preserve the signed tariff, included destinations, taxes, term, number and port charges, channel and burst rules, fair-use or acceptable-use controls, support entitlement and cancellation terms. Do not publish a marketing phrase as a durable account price.
Before cutover, verify numbers, routing, identity, inbound and outbound calls, DTMF, audio, protection, capacity within authorization, access failover, restoration and rollback. Store redacted evidence with the configuration export and provider case. No IP Telecom account, order, trunk, number, network, PBX, packet, media stream or call was tested for this guide.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- IP Telecom SIP Trunks ↗
- IP Telecom terms and SIP Trunking product schedule ↗
- IP Telecom Fair Use Policy ↗
- IP Telecom Ireland copper switch-off guidance ↗
- IP Telecom contact and support ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.