Grandstream UCM6300 Technical Guide

How to Configure Enterprise SIP Trunks on Grandstream UCM6300 in Pakistan

A practical, provider-neutral guide to configuring a SIP trunk on a Grandstream UCM6300 series IP PBX, including Register and Peer trunks, inbound and outbound routes, DID handling, caller ID, NAT, codecs, security and troubleshooting.

Reviewed 31 August 2026 Beginner to administrator UCM6300 and UCM6300 Audio families

Start configuration Discuss your SIP trunk

Typical production call flow SIP

Telecom provider / ITSPSIP signaling, DID numbers and voice channels

Carrier

↓

Firewall / routerACL, NAT and RTP handling according to provider design

Secure

↓

Grandstream UCM6300Register or Peer SIP trunk with inbound and outbound routes

PBX

↓

IVR, queue or extensionRoute each DID to the correct business destination

Users

Quick answer

On a Grandstream UCM6300, open Extension / Trunk → VoIP Trunks, select Add SIP Trunk, and choose Register SIP Trunk or Peer SIP Trunk according to your telecom provider. Enter only the server, authentication, transport, codec, DID and caller ID parameters supplied or approved by the provider. Then create separate Inbound Routes and Outbound Routes, test incoming and outgoing calls, and secure the trunk before production use.

In this guide

Configure the trunk from carrier handoff to live calls

Use the sections below as a deployment checklist or jump directly to the problem you are solving.

The foundation

What is a SIP trunk on a Grandstream UCM6300?

A SIP trunk connects the UCM6300 to an external SIP service or another SIP PBX. The trunk carries calls between your internal extensions and the outside network, while the UCM controls routing, permissions, IVR, queues, recordings and caller treatment.

Inbound calls

The provider delivers a DID, UAN or pilot number to the UCM. An inbound route then sends the call to an extension, IVR, queue, ring group or another approved destination.

OUT

Outbound calls

An outbound route matches the dialled number, checks extension privileges and sends the call through the selected trunk in the number format expected by the provider.

DID and caller ID

Inbound DID matching and outbound CLI presentation are separate tasks. They must match the number format and caller ID policy of the telecom provider.

Important design principle: a SIP trunk is not the same thing as an extension. A 100 user office may need only a limited number of simultaneous external channels, while a contact centre may need a much higher channel count. Size the trunk for peak concurrent external calls and business continuity.

Before you log in

Get the SIP provider information first

Do not guess carrier settings. Ask the provider for a written SIP configuration sheet and record the items below before changing the PBX.

Information to obtain	Why it matters	Typical possibilities
Trunk type	Determines whether the UCM authenticates by registration or by peer/IP relationship.	RegisterPeer
SIP server / proxy	The carrier address to which SIP signalling is sent.	FQDN or IP address, sometimes with primary and backup servers.
Authentication details	Required for Register trunks and some carrier designs.	Username, Auth ID, password, realm or domain.
SIP transport and port	Must match the provider handoff.	UDPTCPTLS if supported
RTP / media information	Needed for firewall rules and one way audio troubleshooting.	Provider media IP ranges plus UCM RTP port range.
Allowed codecs	The call can fail with incompatible SDP or codec negotiation.	Use the provider approved list and order.
DTMF method	Needed for IVR key presses and external systems.	RTP events, SIP INFO or another provider specified method.
DID / UAN delivery format	Your inbound route must match the exact digits the carrier sends.	E.164, national format, local format or provider specific DID string.
Outbound number format	Determines your outbound route dial pattern and digit manipulation.	E.164, national or another carrier specified format.
Caller ID policy	Prevents rejected or rewritten outbound CLI.	Pilot CLI, assigned DID, DOD mapping or provider controlled presentation.
Channel count and failover	Defines concurrent external call capacity and resilience.	Primary channels, overflow, secondary SBC or alternate trunk.

Back up first: create a current UCM configuration backup before changing a production trunk, inbound route or outbound route. Also note the installed UCM model and firmware because menu labels and advanced options can change between firmware branches.

Choose the correct trunk type

Register SIP Trunk vs Peer SIP Trunk

Grandstream currently exposes both trunk types in the UCM6300 interface. The correct choice is determined by the service provider or the PBX interconnection design.

Register SIP Trunk

The UCM sends a SIP registration to the provider using credentials supplied for the service.

Common for ITSP or carrier services that use account registration
Usually needs username, authentication information and password
Registration state provides a useful first health indicator
Do not invent From User, domain or proxy values unless the provider requires them

Peer SIP Trunk

The UCM exchanges calls with a known SIP peer, commonly by IP address or an agreed network relationship.

Useful for IP PBX to IP PBX interconnection and some carrier handoffs
Often relies on trusted source addresses, ACLs or managed connectivity
A peer trunk may not show a normal registered state because it does not register
Verify reachability and actual call flow instead of judging it by registration alone

Do not convert a provider supplied Peer trunk into a Register trunk, or vice versa, just to make the status look familiar. Build the trunk exactly around the carrier handoff and authentication model.

Pakistan deployment note

SIP trunk availability and settings are provider specific

Business SIP trunk services are currently marketed in Pakistan by providers including Jazz Business and Nayatel, while PTCL also lists SIP Trunks in its SME communications portfolio. This confirms that enterprise SIP connectivity is commercially available, but it does not mean all providers use the same registration, IP addressing, codec, DID or caller ID settings.

Ask your provider for the exact technical handoff and use the credentials, IP ranges and number formats issued for your own account. Commercial availability, service areas, KYC requirements, DID options and tariffs can change.

Jazz Business SIP Trunks Nayatel SIP Trunk PTCL SME Communications

Hands on configuration

Step by step: configure a SIP trunk on Grandstream UCM6300

The workflow below follows the current UCM6300 family approach. Exact labels can vary slightly with firmware, so always compare the screen with the provider sheet and the manual for the installed firmware.

Back up the UCM and confirm the network design

Maintenance → Backup

Create and download a current configuration backup.
Record the UCM model, firmware version, LAN IP, default gateway and DNS settings.
Confirm whether the carrier is delivered over public internet, a managed private circuit, VPN or another controlled network.
Confirm whether the UCM is behind NAT and which firewall owns the public address, if a public address is used.

A static public IP is not universally required. Some services register through NAT, some carrier handoffs use private or managed connectivity, and some designs use fixed public addresses. Follow the provider handoff rather than forcing one network model onto every SIP trunk.

Prepare firewall, NAT and QoS deliberately

Permit SIP signalling and RTP media only as required by the approved design. Where the provider publishes fixed signalling or media IP ranges, restrict access to those sources wherever practical.

Do not expose the UCM web administration interface directly to the public internet.
Avoid broad inbound rules such as “any source to SIP” when provider IP ranges can be used.
Apply voice QoS consistently across the LAN and WAN if the network carries competing data traffic.
Keep NAT mappings stable for internet delivered trunks and verify the UCM sees the correct external address.
Treat SIP ALG as a firewall specific feature. If it rewrites SIP incorrectly or causes failed registrations, broken SDP or one way audio, disable it and retest. Do not change it blindly on a working provider design.

Create the VoIP trunk

Extension / Trunk → VoIP Trunks → Add SIP Trunk

Select Register SIP Trunk or Peer SIP Trunk exactly as specified by the carrier.
Enter a clear Provider Name, for example Primary SIP Carrier.
Enter the provider Host Name / SIP Server as supplied.
For a Register trunk, enter the username and authentication information supplied for the account.
Save the trunk, then edit its advanced settings only where the provider requires additional parameters.

Do not copy SIP credentials from screenshots or online examples. Authentication IDs, realms, domains, From User values, outbound proxies and ports are carrier and account specific.

Set transport, codecs and DTMF to the carrier profile

Use the provider approved transport and codec list. Do not enable every codec simply because the UCM supports it. A controlled codec order produces more predictable negotiation and makes troubleshooting easier.

Transport

Use UDP, TCP or TLS only as supported by the carrier. TLS also requires the correct certificate and trust design.

Codecs

Match the provider. G.711 is commonly used where bandwidth permits, but the carrier profile takes priority.

DTMF

Match the provider DTMF method so IVR key presses and external systems work reliably.

If the carrier supports media encryption, configure SRTP only as part of a mutually supported end to end profile. Enabling encryption on one side alone will not make the call secure.

Verify the trunk before building call routes

For a Register trunk, confirm that registration succeeds. If it fails, inspect the SIP response rather than repeatedly changing unrelated settings. A 401 challenge can be normal during authentication, while a persistent 403 usually needs the account details or provider policy checked.

For a Peer trunk, remember that “Registered” may not be a meaningful health state. Confirm network reachability, source IP expectations, SIP OPTIONS behavior if used, and actual inbound and outbound call attempts.

Create the inbound route

Extension / Trunk → Inbound Routes

Select the new SIP trunk.
Enter a DID pattern that matches the exact called number format delivered by the provider.
Choose the destination: IVR, call queue, ring group, extension, voicemail or another approved call flow.
Add time conditions where office hours and after hours need different destinations.
Save and apply, then test from an external mobile number.

Most “incoming call reaches the UCM but not the destination” problems are route matching problems. Compare the DID actually received in the SIP INVITE with the pattern configured in the inbound route.

Create the outbound route

Extension / Trunk → Outbound Routes

Create a descriptive route name, such as Pakistan National via SIP.
Build dial patterns around how users dial and how the provider expects to receive numbers.
Select the SIP trunk and apply the correct privilege level or source restrictions.
Use strip, prepend or digit manipulation only where it is required to convert the user dialling format into the carrier format.
Test mobile, landline, UAN and international destinations according to the customer's permitted calling policy.

Do not create an unrestricted international route for every extension. Restrict high cost destinations to authorized users and apply the least privilege principle to outbound calling.

Configure outbound caller ID and DOD only as the carrier permits

Grandstream UCM supports Direct Outward Dialing mappings for SIP trunks. Use DOD when you need selected extensions to present approved external numbers and the provider supports that presentation.

Use only caller IDs assigned or approved for the customer account.
Confirm whether the provider expects the CLI in From, P Asserted Identity or another supported header profile.
If the provider always forces the pilot number, local UCM DOD changes may not alter the public caller ID.
Test each required CLI from an external receiving phone.

Test a complete acceptance matrix before go live

Inbound

DID to extension, IVR, queue and after hours route.

Outbound

Mobile, landline and every permitted destination category.

Media

Two way audio, DTMF, hold, transfer and conference behavior.

Identity

Inbound CLI, outbound CLI, DOD and DID presentation.

Also test concurrent call capacity, failover, voicemail, call recording policy, emergency procedures, CDR visibility and recovery after an internet or carrier interruption where applicable.

Production hardening

SIP trunk security checklist for UCM6300

SIP fraud is a configuration and access control problem as much as a password problem. Secure the carrier path, UCM administration and outbound permissions together.

Restrict exposure

Whitelist provider signalling IPs where practical
Limit RTP to the required media paths
Do not publish the admin portal directly to the internet

Protect credentials

Use unique strong UCM administrator passwords
Protect SIP trunk passwords and backups
Use role based administrative access

Limit dialling

Apply extension privilege levels
Restrict international and premium destinations
Review unexpected high volume calling promptly

Patch and back up

Keep to a supported firmware release
Review release notes before production upgrades
Keep recoverable configuration backups

Use encryption correctly

Use TLS and SRTP when the provider supports them
Validate certificates and trust configuration
Do not assume signalling encryption also encrypts media

Monitor behavior

Review CDRs and failed call patterns
Enable relevant system alerts
Investigate repeated authentication or routing failures

Fast diagnosis

Grandstream UCM6300 SIP trunk troubleshooting

Change one variable at a time. Check SIP responses, the DID actually received, the number actually sent, and whether RTP flows in both directions.

Symptom	Likely area	What to check first
Register trunk stays offline	Authentication, DNS, transport or firewall	Server address, Auth ID, password, realm/domain if required, SIP port, DNS resolution and provider source restrictions.
Peer trunk does not show Registered	Normal peer behavior may be misunderstood	Confirm whether the peer is supposed to register at all. Test reachability and call flow instead.
Inbound call reaches PBX but not user	DID matching or inbound route	Compare the called number in the SIP INVITE with the inbound route pattern and destination.
Outbound call gets 404 or 484	Number format or dial pattern	Check the digits sent to the provider, strip/prepend rules and the required national or E.164 format.
Persistent 403 Forbidden	Provider authorization or identity	Verify account state, source IP, Auth ID, From User/domain and caller ID policy with the provider.
488 Not Acceptable Here	SDP or codec mismatch	Reduce the codec list to the carrier supported codecs and verify media/security negotiation.
One way audio	NAT, RTP or firewall	Check SDP addresses, NAT settings, RTP rules, provider media IPs and whether SIP ALG is rewriting traffic.
DTMF does not work in IVR	DTMF method mismatch	Match the UCM and provider DTMF method and retest through the actual carrier path.
Wrong outbound caller ID	DOD, From/PAI or carrier policy	Confirm the number is assigned to the account and the provider accepts the required presentation method.
Calls drop after a fixed interval	NAT state, session timers or firewall	Check firewall UDP/TCP timers, re INVITE/session handling and RTP continuity.
503 Service Unavailable	Carrier, channel or resource condition	Check channel exhaustion, provider service state, alternate SBC/failover and whether the response comes from the UCM or carrier.

When the problem is unclear: capture a single failed call using the UCM troubleshooting or packet capture tools, note the exact time, calling number and called number, and inspect the SIP ladder. This is much faster than changing multiple advanced settings by trial and error.

Quick answers

Frequently asked questions about UCM6300 SIP trunks

These answers are written for readers. They are intentionally visible on the page even though FAQ rich result schema is not required for Google Search.

Can Grandstream UCM6300 connect directly to a SIP trunk?

Yes. The UCM6300 family includes VoIP trunk configuration in the web interface. Create a Register or Peer SIP trunk according to the provider handoff, then add inbound and outbound routes.

Do I need a static public IP for a SIP trunk on UCM6300?

Not always. The requirement depends on how the telecom provider delivers the service. Some trunks register through NAT, some use fixed public addressing, and some are delivered over managed private connectivity. Follow the carrier design.

What is the difference between a Register SIP Trunk and a Peer SIP Trunk?

A Register trunk normally authenticates by sending SIP registration credentials to the provider. A Peer trunk commonly exchanges calls with a known SIP peer or trusted network relationship and may not register in the same way.

Which codec should I use for a Pakistan SIP trunk?

Use the codec list supplied or approved by your provider. G.711 is commonly suitable where bandwidth permits, but the carrier profile is more important than a generic recommendation.

Can I use Jazz Business or Nayatel SIP trunk with Grandstream UCM6300?

Both companies currently publish business SIP trunk services. Compatibility depends on the technical handoff they issue for your account. Obtain their SIP server, authentication or peer details, DID format, codecs, DTMF, media IPs and caller ID rules, then configure the UCM to match.

How many SIP channels do I need?

Size channels around peak simultaneous external calls, not simply the number of employees or extensions. Include inbound and outbound concurrency, call centre peaks, growth and any redundancy requirement.

Can incoming SIP calls go directly to an IVR or call queue?

Yes. The inbound route can send calls to an IVR, queue, ring group, extension or other supported destination. Build and test the destination first, then point the DID route to it.

Can UCM6300 record calls made through a SIP trunk?

Yes. UCM6300 recording can be applied at appropriate trunks, routes, extensions, queues and other call handling objects according to the required recording policy. Storage, access and legal requirements should be planned separately.

Should I enable TLS and SRTP on every SIP trunk?

Enable them when the provider supports the same security profile and the certificate, transport and media settings are configured correctly on both sides. Enabling encryption only on the PBX cannot force an incompatible carrier connection to become encrypted.

Reviewed by TekkPak Technologies

TekkPak Technologies is a Grandstream Authorized Reseller and business communications solution provider in Pakistan. This implementation guide was reviewed against current Grandstream UCM6300 documentation available in August 2026 and current public SIP trunk offerings in Pakistan.

Primary technical sources

Grandstream and UCM are trademarks of their respective owner. Provider services and settings can change. Always verify the configuration sheet issued for the customer's own SIP trunk before production deployment.

Grandstream Authorized Reseller in Pakistan

Need TekkPak to configure or troubleshoot your SIP trunk?

Share your UCM model, provider name, number of SIP channels, DID or UAN requirement, number of users and the problem you are facing. TekkPak can help with trunk configuration, inbound and outbound routing, IVR, queues, call recording, endpoint provisioning and acceptance testing.

WhatsApp TekkPak Explore Grandstream solutions

W WhatsApp TekkPak

Discover more from TekkPak Technologies

Subscribe to get the latest posts sent to your email.