5.7 |
Central Busy Signaling with Attendant P |
| This section describes which steps are required to set up central busy signaling in connection with Attendant P. |
Sample configuration |
|
| • | No settings are needed in the HG 1500 cards because, among other things, the CAR tables in the HG 1500 cards are created automatically. |
| • | In this description, Attendant P is operated via an RS232 connection. |
| • | The subnode busy signaling of card tab 3-16 differs from that of the main node, which uses card tabs 1 and 2. Different colors can be set up in the Configuration Manager to indicate the states "internal busy", "external busy" and "station is ringing". In the case of the subnode card tab 3-16, the color selected for "internal busy" is the same as the color for "station is ringing". |
| • | Attendant P must also function when the server is shut down. In other words, none of the components associated with other servers such as the Feature Server, TAPI, etc., affect the functionality of Attendant P. |
Setting up the PABX number in the node |
| Every node in a networked system has its own unique PABX number. |
| 1. | Select the menu item Settings | Lines/networking. |
| 2. | Select the Routes tab. |
| 3. | In the Routes list, select Trk Grp. 16 for HiPath 3000 and Trk Grp. 64 for HiPath 5000. |
| 4. | Enter the name of the route, e.g., LAN, in the Route Name field. |
| 5. | In the PABX Number Incoming area, enter the unique call number of the PABX in the PABX number field. |
| 6. | Repeat steps 1-5 for each node. |
Setting up the call number of the destination system |
| The call number of the target system need not be set up for the node at which Attendant P is to be operated (in the sample configuration, Attendant P is operated at node 1). In all other nodes (2-4), the call number must be set up. |
| 1. | Select the menu item Settings | Lines/networking. |
| 2. | Then select the QSIG features tab. |
| 3. | In the Inter-system busy signaling area, enter the value of node 1 in the System no. target system (here 1) and Call no. target system (here 9781) fields. |
| 4. | Repeat steps 1-3 for the other nodes. |
Setting up the time parameter to delay central busy signaling messages |
| The time parameter for the "delay of busy signaling messages" need not be set up for the node at which Attendant P is to be operated (in the sample configuration, Attendant P is operated at node 1). For all other nodes (2-4), this time parameter should be set to 100ms. |
| 1. | Select the menu item Settings | System Parameters. |
| 2. | Select the Time parameters tab. |
| 3. | In the table for the Delay of busy signaling messages, select the value 100ms as the base value. |
| 4. | Repeat steps 1-3 for the other nodes. |
Setting up the station flag for central busy signaling at stations |
| The station flag for "central busy signaling" need not be set up for the node at which Attendant P is to be operated (in the sample configuration, Attendant P is operated at node 1). This flag must be set for every station of the other nodes (2-4) to be signaled at Attendant P. |
| 1. | Select the Station view. |
| 2. | Set the flag for Central busy signaling on the Station flags tab. |
| 3. | Set the flag for every station to be signaled at Attendant P. |
| 4. | Repeat steps 1-5 for the other nodes. |
Configuring and adapting LCR |
| In order use the central busy signaling functionality, you will need to first configure or adapt LCR (least cost routing). |
| For the node at which Attendant P is to be operated (in the sample configuration, this is node 1), every other node (2-4) must be additionally configured in the LCR under "Dialed digits". |
| 1. | Select the menu item Settings | Least Cost Routing. |
| 2. | Select the Dial plan tab. |
| 3. | In the Dialed digits column of the table, enter the station numbers of the other nodes (2-4) and assign a Route table to them. |
| 4. | Select the Dialing rules table tab. |
| 5. | In the Rule name column of the table, enter a rule name for the other nodes (2-4), then assign the Rule format "E1A" to them, and then select the Procedure "Corporate Network". |
| 6. | Select the Route table tab. |
| 7. | From the Selection list, select the route table that you assigned to the other nodes in step 3. |
| 8. | In the route table, select in the Route column Trk Grp. 16 for HiPath 3000 and Trk Grp. 64 for HiPath 5000, and assign the Dial rule configured during step 5. |
| 9. | Repeat steps 7-8 for the other nodes. |
| In the other nodes (2-4), only the target node needs to be evaluated in the LCR. |
| 10. | To do this, create an entry for node1 in the dial plans of each of the other nodes (2-4) by proceeding as described earlier in steps 1-8. |
Configuring Attendant P |
| 1. | For each node (2-4), create a separate BLF file (a *.txt file) containing all stations to be signaled at Attendant P. The file names must be unique and must correspond to the name of the node (e.g., BLF_NODE_2.txt, etc.). |
| 2. | Copy the BLF files you created to the directory of Attendant P. |
| 3. | Assign the BLF files to the cards. The BLF card tabs 1 and 2 are always assigned to the node at which Attendant P is operated (in the sample configuration, this is node 1). All other card tabs (3 through 16) can be assigned to the other nodes (2-4). |
| Example: assigning node 2 to card tab 3: |
| - | Start Attendant P |
| - | Select the menu item File | Settings |
| - | Select the BLF tab |
| - | Click the Set Network BLF button |
| - | Select the BLF file BLF_NODE_2.txt |
| - | Select card 3 |
| HiPath 3000/5000 V9, Manager E, Administrator Documentation, Issue 10 | up ![]() |
|
![]() |
||
| Disclaimer & Copyright | ID: P31003H3590M1000176A9 | 2014-03-03 |