7.2.11 |
Correlation With Other Features |
| This section describes how the least cost routing application interacts with other system features. |
7.2.11.1 |
Station-Related Features |
| • | System speed-dialing call numbers must be prefixed with the LCR access codes for proper operation. |
| • | Station redial will insert the access code used for the original call. |
| • | Repertory dial keys to external destinations must have the LCR access code for proper operation. |
| • | General call keys will be activated when the route is selected by the system. |
| • | Call keys will be activated when the route is selected by the system. |
| • | MUSAP keys may be used for external calling using the LCR access code. |
| • | DTMF tones may be input manually when answer supervision is received. |
| • | Toll restriction class of service is checked as part of the LCR analysis. |
7.2.11.2 |
Trunk-Related Features |
| • | Basic rate ISDN trunks may be accessed by stations assigned CACH values or PDID values. |
| • | Verified forced account codes may be requested before a selected route group is accessed. |
| • | DTMF or rotary pulse dialing may be selected based on the outdial rule. |
Additional Information Concerning the Setup of Public Network Trunks |
| • | The class of service configured is valid on a locked terminal (lock code). |
| • | It is possible to send speed-dialing numbers after selecting the network. |
| • | If speed-dialing numbers are used without first selecting the network, the default network is used (carrier-select override). |
| • | If LCR is activated, there is no trunk group overflow. An alternative route can be determined using the route table. |
| • | When LCR is activated, no digit repetition is performed; the routing tables are followed instead. |
| • | Message waiting and automatic callback follow the rules for LCR. |
| • | An account code entered by the user is valid for the whole connection, even if more than one route over different trunk groups was tried during connection setup. |
| • | In the case of connections via other network providers or carriers, the provider or carrier may not transmit the actual connection costs, i.e., it may send the HiPath 3000only the charges to the dial-in node (such as a dial-in control server [Europe only]). |
| HiPath 3000/5000 V8, Feature Description, Issue 10 | up ![]() |
|
![]() |
||
| Disclaimer & Copyright | ID: P31003H3580F100017618 | 2011-02-07 |