5.1.6  
Transit traffic 
 
Implementing features, see also Manager E Transit Traffic

Definition  
Transit traffic refers to calls that are handled by the communication system with two external stations. External connections can be set up to either the central office or to a networked system.
It is possible to handle transit traffic both manually and automatically over digital trunks and analog lines with a backward release criterion. Transit traffic can also be processed on analog trunks without a backward release criterion (loop start) by using timeout control followed by automatic release (maximum time is 42 minutes). Transit traffic is needed in the following situations:
 •   Networked systems
 •   Trunk-to-trunk connections (including DISA)
 •   Transition from a private network to the public network and vice versa
Transit traffic is used in conjunction with the following features:
 •   Call forwarding
 •   Transfer
 •   Callback (CorNet and QSig networks; if supported on the trunk side, transit traffic can be used externally as well)
 •   Message waiting for central voice mail servers in CorNet and QSig (not for U.S.) networks
External access from a remote node is not possible over HiPath 3550 or
HiPath 3500 BRI trunks. Such calls are intercepted to the HiPath 3550 or HiPath 3500 intercept position.  
In the case of IP/IP E2E payload via enterprise proxy for Internet telephony, some of the features listed are only supported if the RTP proxy is activated in the HG 1500.  
Definition of Features Associated with Transit Traffic
 •   Call forwarding: A trunk-to-trunk connection is possible using call forwarding - no answer (CFNA) or call forwarding (CF) to an external destination. Care should be taken concerning the release capability of the trunks. Using LCR, an incoming call can also be forwarded (CF or CNA) to a CorNet-N link to a station in the remote node, to the Attendant in the remote node, to a voice mail system in the remote node, or rerouted to an external destination by the remote node. When calls from a HiPath 3000 are routed through a CorNet-N link to internal and external destinations, the CorNet-N channels must be split between these functions. In the case of a transfer to a remote voice mail system, the HiPath 3000 sends the originally called destination's station number to the voice mail to activate the proper answer message.
Always refer to the latest CorNet Configuration Note or the CorNet Sales Positioning Guide for the latest information.  
 •   Transfer: It is possible for the user to transfer calls (screened and un-screened) to an external destination or to a remote node, via a CorNet link.
The transfer can also be initiated by a voice mail call processing feature or by an IVR which automatically transfers, unscreened, a call to an external or CorNet destination.
 •   Callback: If Callback was activated by the user to a CorNet user in a remote node, the Callback will be activated in the same way as an internal callback activation (this feature is not available with connections to a ROLM 9005).
 •   Message waiting for central voice mail servers in CorNet networks: Message Waiting notification is possible from a remote voicemail system connected via CorNet links. In the case of PhoneMail, the SW version must be 6.3 or higher.

Model-Specific Data  

 Subject  
 HiPath 3800  
 HiPath 3550  
 HiPath 3500  
 HiPath 3350  
 HiPath 3300  
Feature available in  
 x  
 x  
 x  
Hardware requirements  
 S0-/S2M board / HG 1500 board  
 TLA board  
Software requirements  
 V5.0 or later  
 V1.0 or later  
 V1.0 or later  

Dependencies/Restrictions  

 Subject  
 Dependency/Restriction  
Analog trunk  
MSI  
MSI trunks are automatically released after a programmable period (default: 310 seconds. A tone sounds 10 seconds before release). The time parameters only can be changed by using HiPath 3000/5000 Manager E.  
IP/IP e2e payload via enterprise proxy for Internet telephony  
The following features are only supported in the HG 1500 when the RTP proxy is activated:  
 •   Call forwarding to external stations
 •   Transfer
 •   Call forwarding
With administration via Manager E, it is possible to have trunk-to-trunk transit connections with transit flags as well as transit connections from trunks to tie trunks in the case of networks.
When the flag is set, toll fraud is possible if outgoing selection is enabled as a result of additional system configuration parameters.
Transit traffic is used in conjunction with the following features:
 •   Direct inward dialing
 •   Call forwarding
 •   Transfer
 •   Conference
 •   LCR

HiPath 3000/5000 V9, Feature Description, Issue 10   up Top
Disclaimer & Copyright   ID: P31003H3590F100017618   2014-02-27