CIPT2 – Multisite Dial Plan: PSTN Access – Handling Incoming and Outgoing Calls

Multisite Dial Plan: PSTN Access – Handling Incoming and Outgoing Calls

Outgoing Calls – DID/NON-DID
Incoming Calls – DID/NON-DID
Using ISDN ToN

FXO – Analog
T1/E1 – Digital

ANI – Caller ID/Calling Party
DNIS – Called Party
TON – Type of Number (Ways of identify of local, national, long distance etc…)

FXO has no bandwidth to report DNIS, only ANI. Analog phone is just attached to the FXS port.

Good practice is to add/prefix a 9 to any Calling Party for outbound calls. For return calls to the PSTN.

You can do this on the Gateway for Incoming Calling Party Settings with a 9 Prefix.

You can also reference a CSS + PT for Incoming PSTN Calls. TP in the PT that matches the Called Party 2xxx and prefixes the Calling Party with a 9. This is a Gateway level change in CUCM.


In a CCS world… We need to modify the Calling/Called Party information…

Some carriers permit any ANI digits…
Some carriers only permit your valid range via an ANI filter..

Best practice is to present your Caller ID or hide it

On your PSTN Route Pattern you can set a ‘Calling Party Transform Mask’


This can also be done on the Line using the Calling Party External Phone Number Mask’ and this will look at what is set under the Line External Phone Number Mask

You can also set the Calling Party as ‘Restricted’ via the Route Pattern.

Incoming Calls

Gateway sends calls to CUCM based on matching any ANI or DNIS information

CUCM has a Translation Pattern to maniuplate digits to your Dial Plan

Subscriber – Local

Detailed in the Q.931 signalling