Articles in this section

SIP Trunk Ordering

Published:

πŸ›°οΈ SIP Trunk Onboarding – Information Required

πŸ“˜ Overview

This article outlines the details required by CommsChannel to provision and onboard a new SIP Trunk service for your business. Providing complete information helps ensure that your SIP service is configured correctly, operates reliably, and complies with Australian call routing standards.

πŸ“‹ Step 1: Information Required for New SIP Trunk Setup

When requesting a new SIP Trunk, please provide the following details:

Information Needed

Description / Example

Company Name

Your business or customer name.

Primary Contact

Name, email, and contact number for setup communication.

Number of Channels Required

Specify how many simultaneous calls (in/out) are needed.

Authentication Type

Choose one of the following:
β€’ Registration-based – PBX registers using username & password.
β€’ IP-based – Calls are routed via static IP without registration.

Number of DIDs Required

How many phone numbers should be assigned to the SIP Trunk?

Existing or New DIDs

Indicate whether you need new DIDs or want to migrate/port existing ones.

Preferred DID Type

GEO DIDs (local area numbers) or Virtual Mobile Numbers (if SMS is required).

Preferred Area Code

NSW (02), VIC (03), QLD (07), SA (08), etc.

Sequential Numbers

Do you require consecutive numbers (e.g., 101–105)?

Destination Device/Service

Specify where the SIP Trunk will connect:
β€’ Existing PBX (brand & model)
β€’ New Yeastar PBX (Cloud or On-prem)
β€’ SIP Gateway or ATA

Site Public IP Address (for IP-based trunks)

Required for whitelisting and inbound routing.

Test or Production Service

Indicate if this is for testing or live production deployment.

πŸ’‘ Tip: Providing your PBX type and firmware version helps us pre-test compatibility before activation.

βš™οΈ Step 2: Required SIP Endpoint Settings

Please ensure that your endpoint (PBX, SBC, or ATA) is configured as follows for correct SIP operation:

Codec Settings

Preferred Codec: G.711A (A-law)

Number Format

Use E.164 format without the β€œ+” symbol.
Example: for Melbourne, send 613XXXXXXX.

Caller Line Identification (CLI)

Present a valid geographic number in one of the following formats:
β€’ E.164 Format: e.g., 613XXXXXXXX
β€’ Standard Australian STD Format: e.g., 03XXXXXXXX

The CLI number must be from DIDs associated with your SIP Trunk.
CLI can be placed in:
β€’ PAI (P-Asserted Identity) – RFC3325 (with Privacy field)
β€’ Remote-Party-ID
β€’ From field in the SIP INVITE

Calls may be blocked if invalid or unregistered CLI numbers are used.
If you are using temporary DIDs during number porting, please ensure you display your permanent DID as the CLI.

πŸ“₯ Inbound Calls

All inbound SIP INVITEs will have the Request URI (RURI) formatted as E.164 without the β€œ+” prefix.
Example: 613XXXXXXX
Please configure your PBX inbound routing rules accordingly.

🧱 Firewall and Network Configuration

Ensure the following ports and protocols are allowed to and from your PBX:

Protocol

Direction

Port(s)

Notes

SIP

UDP/TCP

5060

Main signaling port

RTP

UDP

16000–65000

Media stream (voice)

ICMP

Bidirectional

β€”

For monitoring and troubleshooting

Allowed IP

β€”

139.99.135.216

CommsChannel SIP gateway

Supported Standards

β€’ SIP 2.0 via UDP or TCP
β€’ RTP via UDP
β€’ DTMF RFC2833

πŸ“ž Temporary DIDs and Call Forwarding During Porting

If you are assigned temporary DIDs while number porting is in progress:
1. Arrange a call forward from your existing carrier to the temporary DID.
2. Any charges applied by the existing carrier for call forwarding are the customer’s responsibility.
3. Your SIP Trunk will be configured with both temporary and permanent DIDs.
4. Once porting is complete, permanent DIDs will become active automatically.
5. It is the customer’s responsibility to cancel existing services with the current provider after successful porting.

βœ… Post-Onboarding Checklist

Before going live, verify:
β€’ SIP Trunk is registered or reachable by IP.
β€’ Calls can be made and received using correct CLI.
β€’ RTP audio is working both ways.
β€’ Firewall and NAT settings are properly configured.
β€’ PBX time zone and codec settings are correct.

πŸ†˜ Support

If you need assistance or clarification, please contact:

πŸ“§ Helpdesk@commschannel.com.au

🌐 www.commschannel.com.au

Access denied
Access denied