How Do I? | Part 1 IP Connectivity - Page 73 |
Section Two –IPNC Configuration
This section details the configuration of the IPNC1 and IPNC2.
|
| Task |
|
|
|
|
| Description |
| ||
|
|
|
|
|
|
|
|
|
|
|
|
| Step 1 |
|
|
|
|
|
|
|
|
|
|
| Configure INDEX environment using the (T) |
|
| See INDeX Environment for IPNC Data call (page 70). |
| ||||||
| type interface option |
|
|
|
|
|
|
|
|
| |
| Step 2 |
|
|
|
|
|
|
|
| Use the Monitor application, select Call and enable Call |
|
| Test INDeX configuration for both Units. |
|
|
| |||||||
|
|
|
|
|
|
|
|
|
| events. Point the Monitor application to the local IPNC |
|
|
|
|
|
|
|
|
|
|
| and dial the ARS routed number configured in Step 1 |
|
|
|
|
|
|
|
|
|
|
| from an |
|
|
|
|
|
|
|
|
|
|
| Monitor Application must indicate the call is presented to |
|
|
|
|
|
|
|
|
|
|
| the local IPNC. The resultant tone returned by the on- |
|
|
|
|
|
|
|
|
|
|
| switch extension (i.e. engaged or busy) is NOT |
|
|
|
|
|
|
|
|
|
|
| significant at this stage. It is only important that the call is |
|
|
|
|
|
|
|
|
|
|
| presented to the IPNC. |
|
| Step 3 |
|
|
|
|
|
|
|
| For quick |
|
| Obtain the configuration files for IPNC1 and |
|
|
| |||||||
| IPNC2. Create an Intranet Service type |
|
| and outgoing account names. Use a common Service |
| ||||||
| using the Service parameters set out below. |
|
| Name and Service Account Name. |
| ||||||
| Services Parameter |
| IPNC1 |
|
| IPNC2 |
|
| For example, on the IPNC1 set both the Name and |
| |
| Name |
|
| IPNC2 |
|
| IPNC1 |
|
|
| |
|
|
|
|
|
|
| Account Name to ISDN_link and set both the Service |
| |||
| Account Name |
| IPNC1 |
|
| IPNC2 |
|
|
| ||
|
|
|
|
|
| Password and Service Incoming Password to a unique |
| ||||
| Password |
| password1 |
|
| password2 |
|
|
| ||
|
|
|
|
|
| password that is common to both sites. Then configure |
| ||||
| Incoming Password |
| password2 |
|
| password1 |
|
| IPNC2 using these identical parameters. |
| |
| Step 4 |
|
|
|
|
|
|
|
|
|
|
| On the IPNC1 Service form, configure the |
|
| The <called number> is dependant on whether T type or |
| ||||||
| Telephone number to access the IPNC2. |
|
| the S type IPNC interface option is used. |
| ||||||
|
|
|
|
|
|
|
|
|
| • For S type see Step 2- INDeX Environment S type (page 72) |
|
| • Service/Number = <called number> |
|
| • For T type see Steps 4& 5 - INDeX Environment T type (page 70) |
| ||||||
|
|
|
|
|
|
|
|
|
| It is good practice to initially configure dial up operation |
|
|
|
|
|
|
|
|
|
|
| in one direction only. |
|
| Step 5 |
|
|
|
|
|
|
|
| The <called number> is dependant on whether T type or |
|
| In the Extension field of the default RAS |
|
|
| |||||||
| (Dial In) on the IPNC2 add the number to |
|
| the S type IPNC interface option is used. |
| ||||||
| match the Incoming call. |
|
|
|
|
| • For S type see Step 2- INDeX Environment S type (page 72) |
| |||
|
|
|
|
|
|
|
|
|
| • For T type see Step 1 - INDeX Environment T type (page 70) |
|
| (See Step 3 INDeX T type configuration as |
|
| The RAS allows the IPNC router to identify which |
| ||||||
| detailed on page 70) |
|
|
|
|
|
|
| incoming number are to be associated to data routing. |
| |
|
|
|
|
|
|
|
|
|
| The RAS Extension field is use for this purpose and by |
|
|
|
|
|
|
|
|
|
|
| default the match is made from right to left. |
|
| Step 6 |
|
|
|
|
|
|
|
| The Multilink protocol is imperative for the correct |
|
| For the IPNC1 and the IPNC2 apply the |
|
|
| |||||||
| parameters on the PPP tab of Intranet |
|
| operation of bundled channels over digital services and |
| ||||||
| service type (created previously) as |
|
| VoIP. IPHC is mandatory for the support of QoS for |
| ||||||
| described in the table below |
|
|
|
|
| VOIP. |
| |||
| Parameter |
| IPNC1 |
|
| IPNC2 |
|
| (See The RAS Tab on page 55) |
| |
| Service/PPP |
| Yes |
|
| Yes |
|
|
| ||
| 1. | Multilink |
|
|
|
|
|
|
|
|
|
| 2. | IPHC |
|
|
|
|
|
|
|
|
|
| RAS/PPP |
| Yes |
|
| Yes |
|
|
|
| |
| 1. | Multilink |
|
|
|
|
|
|
|
|
|
INDeX IPNC Cassette Administration Manual | How Do I? - Page 73 |
38DHB0002UKDD – Issue 7 (22/11/02) | Part 1 IP Connectivity |