Aastra Ascotel IntelliGate 2025 - 6.1.9.2 Identification of calls to the public network

Ascotel IntelliGate 2025/2045/2065
680 Planning a private network Part 3
6.1.9.2 Identification of calls to the public network
If a transit PINX or a gateway PINX is to recognize whether or not it should for-
ward an incoming call to the public network, the call number must be an external
number. As such it must
• either comply with numbering plan identifier (NPI) E.164 or
• be preceded by an exchange access prefix.
Fig. 3.67: Call number attributes for outgoing calls to the public network
(2 variants)
In the system both attributes are set in the route configuration. This means that a
separate route is always reserved for calls to the public network.
The page 687 contains an implementation example.
haz0802aaena0
A
A calls
0-012 345 67 89
Transit route
B
012 345 67 89
0012 345 67 89
NPI = unknown
Route configuration:
NPI = unknown
Send access code = 0
A
A calls
0-012 345 67 89
Transit route
012 345 67 89
NPI = E.164
Route configuration:
NPI = E.164
Send access code = -