User`s guide

15(59)
Datum/Date Rev
Dokumentnr/DocumentnrUppgjord/Prepared
Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Tillhör/Referens-File/Reference
99-07-15 A
365/155 34-ASB 150 02 Uen
FACILITY DESCRIPTION
Faktaansvarig - Subject responsible
Causes which force the PNR to perform alternative
routing
• Busy route
All trunks included in the route are occupied or
blocked.
• Travelling Class Mark (TCM) mismatch
The TCM value of the originator is lower than that
requested from the route.
• Network failures
Network failures will normally be detected after
seizure of a route and call set-up will be released
by the network, before any alerting or before con-
nection to the desired party can be
established.
The following network problems will be detected.
- (2) No route to specific transit network
- (3) No route to destination
- (21) Call rejected
- (27) Destination out of service
- (34) No circuit/channel available
- (38) Network out of order
- (41) Temporary failure
- (42) Switching equipment congestion
- (44) Requested circuit/channel not available
- (47) Resource unavailable, unspecified
- (58) Bearer capability presently not available
- (81) Invalid call reference value
- (82) Identified channel does not exist
After release of the trunk, a new call set-up will
be established automatically. Every call set-up
will be logged in a CIL record.
Operation
This PNR facility can be accessed by:
• the user dialling the PNR number
• a re-routed call from another router, e.g. LCR
(routing from PNR back to LCR is not allowed
due to the fact that it is not logical and in order to
avoid possible looping).
• a dialled-in number from network,
i.e. continues as gateway / transit call
Capacity
A maximum of 1000; 1-4 digit private network directory
numbers can be defined