9.4.8 |
Routes |
| Routes can be configured via Routes. A route is assigned to every line (in the case of ISDN BRI, 2 B-channels). A line cannot be assigned to more than one route. The standard configuration for all lines is Route 1. The CO call privileges assigned to the B-channel determine the access rights available to even or uneven B-channels which have been set up. Non-switched MSI lines must be deleted via system administration. |
| In an LCR environment, this code is only used for display; seizure codes are programmed in the Dial plan. In the case of networking, the input is to be entered or deleted in accordance with the configuration of the remote system. |
| In an HiPath 3000/5000 IP network, route 16 must always be used. The Feature server (HiPath 5000) uses this route to generate its call number tables automatically. Note that rerouting should not be enabled for route 16. |
Configuring different routes for simplified dialing |
| Even if simplified dialing (Prime Line) is activated, trunks can be configured for different routes. In other words, the collision check is no longer performed. A fax line can now be accessed via direct trunk access code or via a trunk key for the line in question. |
| The redial function is implemented based on the line/route seized. If the fax line was seized originally, the redial function will access the fax line as well. If simplified dialing is activated, redial is performed for the route 1 trunks. |
Routes for OpenScape Office |
| The routes for OpenScape Office can also be configured in this window. The Route 1 and the Routes 10 - 16 are not used for OpenScape Office. |
9.4.8.1 |
Routes list |
| The Routes list contains a list of available routes. |
9.4.8.2 |
Area: Route, Name |
| To assign a name to a route, type a name in the Route Name text box. The entered name replaces the default route number in the Routes list. |
| Route names appear on the system telephone display when: |
| - | the user presses or programs a call key, and |
| - | during incoming calls where the call number or name of the caller is not available. |
| If you do not assign a name to the route, the route number will normally appear in the display. What appears depends on what you enter in the Route type field in the Routing parameters mask. |
9.4.8.3 |
Area: CO code (2 nd. CO code) |
| You only define the second trunk code if the communication system is a subsystem of another communication system (e.g., a HiPath 3000 switch as a subsystem of a 9006 switch), or if it is networked with several other communication systems. In this case, the second trunk code is the seizure code for the main system. With this code, the subsystem can access the CO trunks of the main system. |
| The second CO code is the code used for seizing a CO line in the remote station. With MSI lines, in accordance with the entry in the Trunk call pause field of the Routing parameters mask, the dial tone is monitored again when a second CO code is dialed. The digits are requested after a timeout. The second CO code is only evaluated if PABX is selected in the Route type field under routing parameters. |
| In a digital network this field is only used to provide the correct display and callback information (Missed Calls List). The second CO code (trunk seizure in the other node) is configured in the LCR Dial Plan in this case. |
| To route trunk seizure of a HiPath 4000 station via HiPath 3000 in LCR, a second trunk seizure code XX must be configured for both switches. This prevents conflict between trunk seizure and the attendant code. |
| Procedure: |
| HiPath 4000 Stn: "0..." |
| LCR HiPath 4000: "0..." -> "XX..." |
| LCR HiPath 3000: "XX..." -> Trunk seizure |
| Warning: In this case, the flag "External traffic transit" must be carefully verified as otherwise transit traffic may also be possible with the new CO code. |
9.4.8.4 |
Areas: PABX number incoming and PABX number outgoing |
| The "CLIP no screening" feature is implemented by splitting the PABX number field into "PABX number incoming" and "PABX number outgoing". If no "PABX number outgoing" is entered, the data from the "PABX number incoming" is always used. |
| Under PABX number you can define which numbers are transferred to callers: |
| - | the first field is used to enter the country code (e.g., 1 in the USA, 49 in Germany) |
| - | the second field is used to enter your own local area code (e.g., 89 for Munich) |
| - | the final field is used to enter the PABX number (i.e., your company's primary telephone number) |
| The No. and type, outgoing field in the Routing parameters mask determines how many digits will be sent. The actual digits are specified in the PABX number mask. Depending on the PABX number entered under "PABX number outgoing", either the outgoing PABX number data or the incoming PABX number data is used. When the outgoing data is sent, the CO is signaled that no screening is to be performed. |
| As of HiPath 3000/5000 V5.0, the node number is no longer placed before the DID automatically, regardless of whether the recipient is a local CO or tie trunk. The node number must therefore be entered as the PABX number. There are two ways to do this: |
| 1. | By entering the complete ISDN call no. (local area code+PABX number+node number) as the PABX number-outgoing and setting the call number type to local area code. |
| 2. | By entering only the node number as the PABX number-outgoing and setting the call number type to unknown. |
| PABX number |
| For an incoming call on an ISDN line, the PABX number is blanked out to the left of the incoming call number. The remaining portion of the call number is interpreted by the communication system as a DID number. When call numbers are transferred to the ISDN system, the PABX call number is automatically used as the leading portion of the call number. This does not apply to dialing information (destination address). |
| In Germany, the PABX call number programmed for the PRI or Basic BRI must omit the area code and the extension number. |
| For example: |
| Call number of the ISDN PRI interface: 0221-4711-0. The PABX call number that must be programmed for this is 4711. |
|
|
Country code, Local area code |
| Callback in the CO will not work unless the call number is entered with the area code and country code. The zero must be omitted for the country code. |
| For example: |
| |
Location number current |
| Here, the route for the current location number (main station) selected in the Routes list can be defined. |
Suppress Stn. Call No. |
| In order to enable flexible customization for various customer applications, this routing parameter can be used in combination with the outgoing PABX number to set whether the internal extension included in the OAD (=originating address) on the trunk (OAD = <outgoing PABX number> + <station DID>) or whether only the configured outgoing PABX number is sent in the OAD. |
| For example, let us assume that a service employee who can be reached centrally via a general service number should not be directly accessible to his or her customer. In such a case, the DID number of the service employee could be suppressed by entering the general service number as the outgoing PABX number and enabling the "Suppress Stn-Call-No" flag. All called subscribers would then only see the service number as the CLIP (calling party information presentation). |
| In a Centrex environment, by contrast, it may be meaningful to enter the call number of the Centrex group as the outgoing PABX number and to leave the Suppress Stn-Call-No disabled. All called subscribers would then see the Centrex call number plus the station DID as the CLIP |
| This flag works as a toggle with the flag outreach call number transparent under Display. |
9.4.8.5 |
Area: Seizure code |
Input |
| The assignment codes for each route are entered here. See also the Routing parameters tab and the Routing flags and Digit repetition fields for the meaning of the seizure codes for closed numbering. |
| The IVM needs all seizure codes. These are set up as before and loaded into the communication system. |
| After the loading procedure, a download of the seizure codes to the IVM is automatically triggered. |
| The routing codes entered must be collision free, both mutually and within the communication system's entire call number plan. Use the Check button to test for collisions. |
Seizure code, Change, Delete, Check |
| The seizure code is the code that causes the switching system to provide a line to the station that dialed the code. An example of a commonly used seizure code is the number 9 to get an outside line. You can assign up to ten different seizure codes for each route. |
| The Seizure code list box displays the default seizure code for each of the routes listed in the Routes list. |
|
| In the case of a digital network, the LCR dial plan should be used to define the access codes. |
| To ensure that you have not assigned the same seizure code to two or more routes, click the Check button. If any duplicates are found, you will see an error message. |
|
9.4.8.6 |
Direction Prefix area |
| This input field is used for the incoming Direction Prefix when LCR is activated.All routes can have the same prefix. |
9.4.8.7 |
Area: Overflow route |
| Overflow is traffic that is beyond the capacity of a specific trunk group and is therefore offered to another trunk group or line. The Overflow route field allows you to assign an overflow route for each route. For example, if all BRI trunks are busy, you can choose to route calls to analog lines. You select an overflow route from the drop-down list box. |
| If all trunks in the overflow route are also busy, no further overflow takes place (no cascading). If LCR is active, the overflow must be programmed in the Dial plan. |
|
| The default settings depend on the country. |
9.4.8.8 |
Area: Numbering plan |
Called Party Number |
| Setting of the parameter "Numbering Plan Identification" in the information element "Called Party Number" of the D-channel protocol. |
| Default value in Germany: System check |
All others |
| Setting of the parameter "Numbering Plan Identification" in all address information elements except "Called Party Number" of the D-channel protocol. |
| Default value in Germany: System check |
9.4.8.9 |
Area: Site |
| Setting of the "Location" parameter in the information elements "Cause" and "Progress indicator". |
| Default value in Germany: System check |
9.4.8.10 |
Area: Switch |
COLP (Connected Line Identification Presentation) |
| If this flag is set, the number of the called party will be shown to the caller in the case of an external incoming CO connection. The calling party can see if the call has been forwarded or picked up by somebody else. This feature needs to be turned on by the central office as well. This feature is only available on digital Lines (BRI or PRI). |
| If the flag is set and an external incoming call is forwarded or intercepted, the updated call number is signaled to the CO in the connect message output by the communication system. If the COLP feature is activated in the CO, the updated call number is also displayed for the caller. |
| If an external outgoing call is forwarded or queried at the CO in the communication system, then the incoming connect message with the updated call number has no impact on the display of the caller, regardless of the "COLP" switch setting. |
Without CLIP (Netherlands only) |
| If this flag is set, the communication system will not transfer the calling party information to the public network on a BRI or PRI line. This flag can be activated or deactivated on a per route basis. In addition, the station has the option to suppress the called party information on a per call basis via an access code or the system telephone menu. |
| This switch can be used to suppress the calling party number of station A in the outgoing SETUP message. |
No Div. Leg. Info |
| If this flag is set, the standard diverting LEG information signal is not sent to the CO. The DIV. LEG info contains the call number of the A user. The DIV. LEG info should be suppressed if problems occur in the case of external call forwarding (CF ext.). |
Always use DSP |
| If this flag is set, a connection to the Internet telephony service provider is only possible via a DSP (digital signal processor). If this flag is not set, then there is a Direct Payload connection to the Internet telephony service provider. |
| This flag may not be set in the case of fax transmissions (T.38) via an external device (AP 1120). |
Intern call like extern |
| If this flag is set, network-internal calls are acoustically signaled in the same way as external calls. |
Notify send |
| This message is used for notification of the ring status. The message can be sent from the network as well as the subscriber side to notify the other party (network or subscriber) about an interrupted connection, for example, or that call forwarding is active. |
| If the notify feature is not supported by the CO, the notify message can be suppressed by resetting this flag. |
| If this option is activated, a "Notify" message is transmitted if a call is e.g., on hold or parked. |
|
Non Setup ACK. (Singapore only) |
| If requested by the central office, the 'Setup Acknowledgement' message can be suppressed by the communication system. |
| Some COs do not recognize the setup acknowledge message. In such cases, transmission of the 'setup acknowledge' message must be suppressed. Example: Fujitsu's Fetex150 COs. |
Without CCNR |
| If this flag is set, an incoming ISDN call with CCNR (Call Completion on No Reply) is signaled so that the system can accept a callback request. This means the caller can initiate a callback if the HiPath station does not reply. In some cases the message is not supported by the ISDN provider In this case the switch must be activated to prevent the system from sending CCNR. |
With sending complete |
| If this flag is set, the optional message "All digits sent" is ouput by the system when all dialed digits are transmitted via the ISDN primary multiplex access. This flag is always set for the New Zealand country code. |
9.4.8.11 |
Digit Transmission area (from HiPath 3000/5000 V8, HiPath OpenOffice EE V1 R2) |
| The type of digit transmission is determined here for the selected route and is displayed as static (e.g. route table 6: en-bloc sending) text under Settings | Least Cost Routing | Dial plan after selecting the route table (see Route table drop-down list). |
Digit-by-digit |
| The digits are transmitted in sync with dialing. |
En-bloc sending |
| During en-block digit transmission (block dialing per route), the dialed digits are buffered by the communication system. Dialing only takes place when a timer has elapsed after the last digit has been dialed, when the end-of-dial code # has been entered or if an exact match in the dial rule is found. In the case of PRI in the USA block dialing to the central office is mandatory. |
| LCR must be activated to be able to select en-bloc digit transmission. |
| The type of digit transmission is automatically set to en-bloc digit transmission in the route table if at least one route of the LCR route table is configured with en-bloc digit transmission. |
| |
| HiPath 3000/5000 V8, Manager E, Administrator Documentation, Issue 11 | up  |
|
 |
||
| Disclaimer & Copyright | ID: P31003H3580M1000176A9 | 2011-03-18 |
