NT-IP. Enhanced ISDN Network Termination with one RS-232 and two analog ports. Finnish Edition. NT-IP Finnet Technical Reference Manual Rev. 4.

Transcription

1 NT-IP Enhanced ISDN Network Termination with one RS-232 and two analog ports Finnish Edition Technical Reference Manual SW REVISION 4.0 DATE: January /97

2

3 safety rules The electrical supply used for this equipment involves LETHAL voltage levels. If objects or liquids penetrate inside the workstation, immediately disconnect the supply cable. Before using the equipment again, have it checked by qualified personnel. DO NOT ACCESS INTERNAL PARTS WHICH ARE NORMALLY PROTECTED WITH PANELS FIXED WITH SETSCREWS. BEFORE ANY OPERATION ALWAYS CHECK THAT THE ELECTRICAL SUPPLY HAS BEEN COMPLETELY AND EFFICIENTLY DISCONNECTED. If the user is not able to restore the regular functioning, he must refer to qualified service personnel. In case of fire, avoid by all means using water to extinguish it. Warnings Handling of devices which are subject to static electricity Many of the components used in the workstation are subject to damage by electrostatic discharge. When handling connectors between different devices, disconnect the electrical supply using the switch located in the back part of the system. Failure to do so could cause permanent damage to the equipment. this product complies with the EEC Directive 89/336 relating to Electromagnetic compatibility and to the EEC Directive 73/23 (Low Voltage) concerning safety standards. 3/97

4

5 1 Introduction The NT-IP adds to the features of a standard ISDN network termination (NT1) for the basic rate access, two standard telephone ports and one RS232 interface to provide a fully digital, fast and reliable connection to a PPP terminal server, such as an Internet Service Provider (ISP), a remote access, an access server, etc. The NT-IP also supports server-side operation (e.g. when connected to a Microsoft Windows NT 4.0 RAS Server. When connecting to the ISDN through a NT-IP, you can use ISDN basic telephony services without any need to purchase additional equipment (digital phones and/or terminal adapters), and you can keep using standard devices, such as standard phone sets, cordless phones, analogue modems, group 3 fax machines, automatic answering machines, analogue micro PBX s etc. The NT-IP supports lifeline operation either through an analog phone set connected to one of the a/b ports or through an ISDN phone connected to the S-bus. A full range of supplementary telephony services is also supported (call hold, call waiting, 3-party conferencing, call forwarding, etc.). A fully digital data service is provided by the NT-IP straight to the COM port of a PC with unrivalled performance compared to analogue modems, including sub-second call set-up times and a virtually error free data channel to the service provider at a guaranteed bit rate. No additional hardware or software need to be installed to operate the service. Additionally, you can connect native ISDN terminals, such as videotelephony terminals, group 4 fax machines, etc., directly on the S-bus. 5/97

6 Figure 1 NT-IP Finnet Technical Reference Manual Rev Glossary The following terms will be used throughout this document: ISDN PSTN or POTS basic rate access (BRA) user bus, "S" or "S/T" bus multipoint access point-to-point access ISDN terminal analog terminal, POTS terminal POTS port or a/b port normal conditions emergency conditions local loop 1.2 Feature Summary Standard NT1 the Integrated Service Digital Network the standard analog phone network (Plain Old Telephone System) the standard ISDN access, with one signalling and two user channels a four wire bus used to connect user terminals to the NT1 an ISDN basic access configured to provide support for up to 8 terminals on the user bus an ISDN basic access configured to provide support for a single terminal on the user bus a generic terminal designed for connection to the S bus such as an ISDN phone, a videophone, a terminal adapter, a group 4 fax, a PC equipped with an ISDN board, etc. a generic terminal designed for the connection to the PSTN such as a phone, a modem, a fax, a key system, an answering machine, etc. one of the two interfaces provided by the NT-IP for connection to analog terminals the a.c. supply is available and adequate power is provided to the NT-IP the a.c. supply is not available and the NT-IP uses the remote power from the exchange to guarantee a (restricted) service to the user the telephone line, consisting of a copper pair that connects the NT-IP to the ISDN exchange 2-wire interface on the U reference point 4-wire user bus on the S/T reference point POTS ports pulse and/or tone dialling, ringing signal, metering pulse generation PCM speech coder/decoder, according to G.711, A-law generation of Calling Line ID messages available in emergency conditions (mains off) RS232 dataport Internet Access on a single or on both B-channels using the multilink PPP (MP) protocol Microsoft RAS connections (server side and client side) Bandwidth on Demand (BOD) Bandwidth Allocation Protocol and Bandwidth Allocation Control Protocol (BAP/BACP) Peer to peer communication according to ITU-T V.120 and V.110 recommendations Enhanced AT command automatic bit rate recognition Maintenance local system and port configuration and diagnostics local and remote download of firmware upgrades 6/97

7 2 System operation 2.1 Power Supply The NT-IP has no batteries and is powered from the 230 V a.c. mains power. When this power is not available, the NT-IP uses the power supplied by the ISDN exchange through the local loop to provide two switch-selectable restricted power modes: basic lifeline phone service through one of the a/b ports basic lifeline phone service through an ISDN phone connected to the S-bus When the restricted power mode on the a/b ports is selected: incoming calls are offered to both ports, provided that the call is compatible with the profile assigned to each port, but only one port can be active at a time, i.e., going off-hook on one port automatically disables the other one. regular operation of the S-bus (i.e. activation, communications, etc.) is guaranteed and a phantom voltage with limited power supply (25 mw) is provided across the S-bus to operate terminals that require voltage on the S-bus to detect connection. In both restricted power modes, the RS232 data port is not active. 2.2 The S 0 interface On the S 0 interface the NT-IP provides the same quality of service of a standard NT1, allowing for the connection of up to 8 external native ISDN Terminals (TE) in any bus configuration (short, extended) and a complete transparency to test procedures from the exchange. Normal PS1 phantom power is provided to the S 0 bus when local ac power is available. If the S 0 bus restricted power mode is selected the NT-IP provides reversed polarity phantom power up to 420 mw when ac power is not available. If the a/b mode is selected, the NT-IP only provides a limited power (25 mw) voltage for terminals that use a connect detect feature. Nevertheless, transmission functions on the S bus are fully operational. 2.3 The RS-232 Data Port The NT-IP has a DB9 female connector for straight connection to a PC COM port, equipped with the following circuits: 103 (TXD), 104 (RXD), 105 (RTS), 106 (CTS), 107 (DSR), 108 (DTR), 109 (DCD) and C125 (RI). The RS-232 port operates up to kb/s with automatic bit rate detection (auto-baud). To guarantee a safe and proper operation in any environment, the RS-232 port is optically insulated from any other port of the NT-IP. This avoids any risk of coupling electrical noise or dangerous voltages from the PC onto the phone sets or the telephone line. Port configuration and operation (such as call control) are carried out through an advanced ATcommand set compatible with any standard communication software. The NT-IP supports the standard Point-to-Point Protocol (PPP), the Multilink Point-to-point Protocol (MP) as well as the V.120 and the V.110 rate adaption protocols. When operating in the single channel PPP mode, the main function of the NT-IP is to operate as a format converter between the asynchronous format on the PC side at various speeds and the synchronous format at a fixed speed of 64 kb/s used on the ISDN channel. When operating the Multi-link PPP (MP) protocol, the NT-IP also provides for all the operations required to establish an additional link, to split and recombine the traffic between the channels and makes it completely transparent to the user s PC the use of two B-channels. 7/97

8 The V.120 operating mode provides for a error-protected, high-speed transmission channel over a single B-channel. V.120 mode can be used for many applications, such as remote access (RAS) to a corporate server. V.110 rate adaptation for low speed asynchronous applications up to 38.4 kb/s is also supported. 2.4 The a/b ports The NT-IP provides for PCM A-law speech coding and decoding and signalling functions as necessary to operate any analog device, such as phones, modems, group 2/3 fax machines, automatic answering devices, small analog PBX, etc. Signalling functions include: hook status detection ringing support for both pulse and DTMF dialling, support for register recall or hook-flash key to operate supplementary services generation of metering pulses, generation of the display of calling line ID (CLID), Local tones are generated when required (e.g. dial tone, congestion and call waiting). 2.5 The Supplementary Services Supplementary services offered by the NT-IP fall into two broad categories: services that rely upon network provided supplementary services (e.g. call hold, call forwarding, three party conference, etc.) locally implemented services that do not imply a direct interaction with the network The ISDN Supplementary services Most ISDN supplementary services are related to the deployment of advanced telephony services (e.g. call waiting, call forwarding, calling line indication, etc.) and, from the user's perspective, are very similar to the corresponding services provided by the analog networks. The NT-IP supports a large number of such services: number identification services multiple subscriber number MSN calling line identification presentation CLIP calling line identification restriction CLIR connected number presentation COLP connected number restriction COLR malicious call identification MCID call completion services call hold HOLD call waiting CW call offering services terminal portability TP call forwarding unconditional CFU call forwarding on busy subscriber CFB call forwarding on no reply CFNR explicit call transfer ECT call completion on busy subscriber CCBS multiparty services three party conference 3PTY community of interest services closed user group CUG charging services advice of charge AOC 8/97

9 For these services, the NT-IP supports the ETSI Generic Functional Protocol (ETS ) and the relevant service specific signalling ETS, and it provides for the necessary mapping between these protocols that describes user-network signalling and the various procedures available to the user in order to activate, deactivate, interrogate or invoke the service Support for the Keypad Protocol The NT-IP also supports the Generic Keypad Protocol, according to ETS , to access supplementary services based on stimulus procedures. These procedures are often used to implement supplementary services according to national specifications. This protocol is much simpler and it basically results in the keys pressed being transparently transmitted as "keypad information" to the switch, where all the processing takes place. The NT-IP makes it completely transparent to the user what kind of protocol has to be used to obtain a specific supplementary service. The user only presses the same "key sequence" required when connected to the POTS. NOTE: Based on customer specifications a specific Supplementary Service can be implemented using of the Functional Protocol or the Keypad Protocol Support for the Feature Key Management Protocol The NT-IP can be programmed to provide a limited support to supplementary services based on the Feature Key Management Protocol according to ITU-T Q.932. See for further details The Local Services A number of additional services is provided via the a/b ports, such as generation of Calling Line Identification (CLI) display services based on on-hook (ETS ) and off-hook (ETS ) data transmission protocols The NT1-Plus can provide CLI services based on using FSK or DTMF signalling generation of charging pulses, based on AOC (either currency of charging units) or Charge Advice information element distinctive ringing patterns, in order to discriminate incoming calls based on the called party number incoming call pick-up (i.e. the possibility to answer an incoming call ringing on the other a/b port. timed fixed destination calls, using a pre-registered number (e.g. emergency or telco helpdesk calls) 2.6 Configuration and diagnostic Features The NT-IP allows for local and remote configuration of most of its operating features. Local configuration can be carried out using a DTMF phone connected to one of the a/b ports or connecting a PC to the RS232 data port of the NT-IP. Remote configuration can be carried out from a basic rate access; the phone number of this access must have been registered in the NT-IP to be configured. Aethra provides an application program running on any 32 bit Windows platform. This program makes use of another NT-IP and of a specific driver to connect to the target NT-IP through the ISDN. Diagnostic features include monitoring of microphone current and the ringing voltage, as well as the detection of permanent short circuit condition and measure of the capacity at the a/b ports. 9/97

10

11 3 ISDN Operation and Signalling Procedures 3.1 Standard NT-1 operation NT-IP operates as a full service NT1 for the external native ISDN terminals (TE) connected to the S 0 bus. To such TE s the NT-IP provides the following service: support to up to 8 physical TE s "short bus" or "extended bus" configuration handling of S0 activation and deactivation procedures at the physical layer handling of the access collisions on the D-channel between the terminals connected to the S- bus and the internal terminal adapter controller functions. 3.2 Layer One Activation Procedures When in normal power mode, downstream and upstream activations on the U interface are completed by the internal terminal adapter controller functions irrespective of the presence of external TEs. When activation is complete, the NT-IP sends the INFO2 signal on the S 0 bus. This allows for immediate activation of a TE plugged into the S 0 bus when the U interface has already been activated. The NT-IP also supports partial activation of the link using the UOA and SAI bits. In restricted power mode on the S 0 bus, the NT-IP does not complete a downstream activation if there is no TE is connected to the S 0 bus (i.e. the ACT bit is not returned to the LT until INFO3 is received on the S 0 bus) Layer one initialization When the remote power supply is removed for more than 2 seconds, the U-interface controller is reset. No activity is started at the U-interface during this state. The "full reset" state (including reinitializing the coefficients of the echo canceller) is entered after 4 seconds of removal of line power D-channel access control The NT-IP has the following operational states to control the access to the D-channel on the part of terminals connected to the S-bus and the internal a/b ports: STATE 1: (transparent) STATE 2: (blocked) 3.3 Layer Two TEI Assignment the NT-IP transmits to the LT the D bits as received from the S-bus; D bits received from the S-bus are also echoed downwards on the E-channel. When the D-channel is in IDLE mode (MARK state for at least 8 consecutive bits), the internal D-channel controller can access the D-channel if there is some data to transmit by making a transition to state 2. the NT-IP transmits to the LT the D bits as received from the internal D-channel controller; the E channel is kept to the SPACE logical level, to inform the terminals connected to the S-bus that the D-channel is not available. Upon finishing transmission of every frame generated by the internal controller, the NT-IP reverts to state 1 for a time sufficient to allow external TEs to receive at least 10 ECHO at "mark" and therefore to gain access to the D-channel (see ETS ). The NT-IP can be used on basic accesses configured for point-to-point or multi-point operation. 11/97

12 In the point-to-point mode, signalling procedures use a single fixed value TEI for all ports, programmed in the range 0 to In the multi-point mode, each port uses a separate TEI value. TEI values are assigned by the network on-demand. Configuration calls are answered based using a TEI value from those assigned to a port. NOTE: When configured to operate for point-to-point operation on TEI 0, the NT1Plus assumes the "line doubler" operation mode (i.e. the S bus is disabled) TEI removal Automatic TEI values assigned by the network are invalidated when the line interface is disconnected for more than 2 sec. After such an event the NT-IP will request the network to assign new TEI values when signalling procedures require activation of layer two. 3.4 Layer Three A/b port profiles The NT-IP allows to define a port profile for either a/b port. This profile affects both outgoing calls (the BC and HLC i.e. in the SETUP message used to start the call) and incoming calls (compatibility checks on incoming BC and HLC are performed according to the port profile): Inactive Speech/Audio Telephony Group 2/3 fax outgoing only inactive this profile is used when no device is connected to the port. When the user goes off-hook an a port configured with this profile, a congestion tone is generated for 30 seconds. No layer 2 and layer 3 activity is started when the user goes off-hook or in response to an incoming call. speech/audio telephony fax outgoing only this is a general purpose profile and it operates correctly independently on the type of device connected to the a/b port. It is therefore strongly recommended to program port profile to this value, unless some special requirements exist. this profile is used when only phones are connected to the port. this profile is used when only faxes are connected to the port. This mode prevents any activity in response to incoming calls (including TEI activation, layer two establishment, etc). In any case, a device connected to the port is still able to place outgoing calls: this can be used to establish calls from an inactive port without the need to reconfigure it. NOTE: even when both a/b ports are configured with the inactive profile, incoming remote configuration calls are normally answered. The following table illustrates the coding of the BC and HLC i.e. included in the outgoing SETUP message for every profile: BC Speech BC 3.1 khz HLC Telephony HLC Fax 2/3 Progress Indicator Inactive x x speech/audio x x telephony x x fax x x 1 in the current version of the PC control program, only a fixed TEI value of 0 can be programmed 12/97

13 Octet 3 and 4 of the Progress indicator (PI) i.e. are coded as 0x80 0x83, corresponding to coding standard location description CCITT User origination address not ISDN For incoming calls, the profile affects compatibility checks performed on the incoming SETUP. Specifically: Calls compatible with the SPEECH/AUDIO profile: BC = "SPEECH" BC = "3.1 khz Audio", PI = ignored, HLC = ignored Calls compatible with the TELEPHONY profile: BC = "SPEECH", PI = ignored, HLC = absent or, if present, coded as "Telephony" BC = "3.1 khz Audio", PI = present, HLC = ignored or, if present, coded as "Telephony" Calls compatible with the FAX profile: BC = "3.1 khz Audio", PI = ignored, HLC = void or, if present, coded as "Gr.2/3 Fax" Data Port Profile The data port is always configured as for the unrestricted digital basic service. In PPP and V.120 modes outgoing calls use a BC coded as unrestricted digital information and no LLC is included. Incoming calls are accepted if the indicated BC is unrestricted digital information. In the V.110 mode, calls include rate adaption information (V.110/X.30 at a specific data rate) in the BC and the LLC: Octet 5a Octet 5b Octet 5c asynchronous, no negotiation, selected V.110 rate intermediate rate (not used), no NIC, flow control not used/required 1 stop bit, 8 data bits, no parity Incoming calls are accepted if V.110 rate adaption information is contained either in the LLC information element or in octets 5, 5a and 5b of the BC information element in the received SETUP.. 13/97

14

15 4 Basic Voice Call Procedures This section describes the basic call control procedures applicable to voice calls. Refer to 7.4 for information on calls originated or answered by the RS232 data port. Some references to the call hold and the call waiting supplementary services are included in this chapter due to the close relationship with basic call control procedures. 4.1 Timers The following timers are used in these procedures T701 wait for the first digit after R key pressed 6 sec T702 guard time 4 sec T703 delayed clear-forward 60 sec (def) T704 hold/retrieve request timer 4 sec NOTE: The T703 can be programmed for either port via the configuration registers 65 and 66N (see 6.7.3) 4.2 Placing Outgoing Calls Upon detecting an off-hook condition, the NT-IP activates layer one and two (if not already active) and transmits a SETUP message using BC and possibly HLC as described in If layer one and two do not activate in the proper time or if the network rejects the cal attempt with a with a RELEASE or RELEASE COMPLETE message, then the NT-IP sends a congestion tone and waits for the user to hang-up. The user can however start a local service (such as CW activation) or the RESUME request. Upon receiving a positive acknowledge (SETUP ACK), NT-IP connects to the indicated B-channel, so that the user may receive the dial-tone provided by the exchange. If the first digit dialled is a number between 0 and 9, then NT-IP enters in the overlap sending state and it sends INFO MESSAGES, with one or more digits included in the CALLED PARTY NUMBER i.e, coded with "type of number: unknown " and "numbering plan: unknown". When the NT-IP exits the overlap sending state (e.g. due to a CALL PROCEEDING or an ALERTING or a CONNECT message received from the network), no further digit information is sent to the network. DTMF tones are instead simply transmitted on the B-channel to make it possible to operate DTMF activated services. If the first digit dialled is either a * or a #, the NT-IP assumes that the user is starting a procedure connected to a supplementary service. Subsequent operations are described in Accepting Incoming Calls The NT-IP perform compatibility checks on the Bearer Capability (BC), High Layer Compatibility (HLC) and Called Party Number information elements 2 of the incoming SETUP, as described in As a general rule, the NT-IP provides: distinct responses for either port when in automatic TEI mode (e.g. separate ALERTING messages are sent on the different TEIs associated with either a/b ports) a single response for both ports when in fixed TEI mode 2 the compatibilty check on the Called Party Number is automatically disabled when the NT-IP operates in restricted power mode. 15/97

16 4.3.1 Fixed TEI mode Upon receiving a SETUP with indication of the B-channel, the NT-IP acts as follows: if neither port profile is compatible with the call, then it ignores the call (if a broadcast SETUP is received) or it replies with a RELEASE COMPLETE, cause 88 incompatible destination if the SETUP is received on a point-to-point link (i.e. on an assigned TEI) if at least one port profile is compatible with the call and that port is either free or busy and allowed to process waiting calls, the NT-IP sends an ALERTING message, and generates the ringing current, or a waiting call tone if the port is off-hook if all compatible ports are busy and not allowed to process waiting calls, then the NT-IP replies with a RELEASE COMPLETE with cause 17 user busy Upon receiving a SETUP with a "no channel" indication, the NT-IP process the call as a waiting call (see ETS ) and: if neither port is compatible, then it ignores the call if a broadcast SETUP is received or it replies with a RELEASE COMPLETE, cause 88 incompatible destination if the SETUP is received on a point-to-point link it replies with ALERTING if the at least one port is compatible with the call and that port is busy and allowed to process waiting calls it replies with RELEASE COMPLETE with cause 17 "user busy", if all compatible ports are busy but not allowed to process waiting calls it replies with RELEASE COMPLETE with cause 34 "no channel available", if all compatible ports are not busy Automatic TEI mode Upon receiving a SETUP with indication of the B-channel, separate processing occurs for either port: if the port is not compatible, then it ignores the call or it sends a RELEASE COMPLETE, cause 88 incompatible destination if the SETUP is received on a point-to-point link if the port is compatible with the call and it is either free or it is busy but allowed to process waiting calls, the NT-IP sends an ALERTING, and generates the ringing current, or a waiting call tone if the port is off-hook if the port is busy and not allowed to process waiting calls, then the NT-IP replies with a RELEASE COMPLETE with cause 17 user busy Upon receiving a SETUP with a "no channel" indication, the NT-IP process the call as a waiting call (see ETS ) and: if the port is not compatible, then the NT-IP ignores the call if the port is compatible, then: if that port is busy and enabled to process waiting calls, the NT-IP replies with ALERTING if that port is busy but not allowed to process waiting calls, the NT-IP replies with a RELEASE COMPLETE with cause 17 user busy if that port is on-hook, then the NT-IP replies with a RELEASE COMPLETE with cause 34 no channel available 4.4 Clearing Procedures Locally Originated Disconnection (Clear Forward) When detecting an on-hook condition, the NT-IP transmits a DISCONNECT message with cause 16, normal clearing. However, if the delayed clear forward features is enabled and if the call is an incoming one, then the NT-IP starts the delayed clear forward timer and it only transmits the DISCONNECT when this timer expires. The current call remains active and if the user goes off-hook she/he will be again connected to the previous party. See also for clearing procedures when calls on hold are involved. 16/97

17 4.4.2 Remote Disconnection Upon receiving a clearing message for an active call: if the clearing message is a DISCONNECT message containing a "Progress Indicator" i.e., then the NT-IP maintains the connection on the B-channel used for the call, and it will complete the clearing procedure: by sending a RELEASE when the user goes on-hook by sending a RELEASE COMPLETE if a RELEASE message is received from the network. if the clearing message is a DISCONNECT without the "Progress Indicator" i.e., then the NT-IP sends a RELEASE message and releases the B-channel; if the clearing message is a RELEASE, then the NT-IP replies with a RELEASE COMPLETE and releases the B-channel if the clearing message is a RELEASE COMPLETE, then the NT-IP releases the B-channel. For the last three cases, the NT-IP also sends a local congestion tone until the user hangs up or a timer of 30" elapses. 17/97

18

19 5 Procedures for supplementary services This section describes user and network procedures used to deploy supplementary services (see 2.5). From the point of view of these procedures: some supplementary services, such as MSN, CLIP and COLP, do not require any user procedure to activate, deactivate or invoke the service. some services (e.g. call forwarding, CF) must be explicitly activated and deactivated by the user and then they are automatically operated when needed (e.g. when an incoming call meets the conditions for being forwarded). These services also usually support a status interrogation using interrogation procedure. some services (e.g. 3 party conference, MCID) require instead an explicit invocation by the user to operate. To execute these procedures when using NT-IP, the user usually presses a sequence of keys starting with * or # on the phone keypad, and in some cases precedes this sequence by the action of the register recall (RR) key (see 5.2). These procedures usually mimic those used in POTS networks for the equivalent services. 5.1 Operating supplementary services When the user goes off-hook, the NT-IP immediately sends a SETUP and then connects the indicated channel to allow the user to receive the dial tone generated by the switch. If the first digit dialled after going off-hook is a numeric digit, then normal outgoing call establishment occurs If the first digit dialled is either a * or a # the NT-IP assumes the user is starting a procedure related to some supplementary service and immediately clears the initiated call. Subsequent digits dialled by the user are then stored and analysed as a keypad sequence. The NT-IP assumes that the sequence has one of the following formats: to activate or to invoke a service, or to deactivate a service, or *<service code># or *<service code>*<parameters># #<service code># or #<service code>*<parameters># *#<service code># or *#<service code>*<parameters># to interrogate about the status of the service. When the complete sequence has been entered, then the following cases apply: if the service code is recognised as one related to a supplementary service provided by the network using the functional protocol, then the NT-IP acts according to the mapping procedures defined for that service; if the service code relates to a "local service" (e.g. CLI enable) then a local procedure is performed, with no further action usually taken towards the network; if the service code is neither recognised as one related to a supplementary service provided by the network using the functional protocol, nor as a "local service", then the complete keypad sequence is transmitted "en-bloc" in the KEYPAD i.e. of a new SETUP message, according to the "stimulus" procedure described in ETS In some cases, the keypad sequence can be collected and analysed after pressing the R key. This is for example the case when, during an active call, the user presses R*79# to activate the suspend/resume supplementary services. NOTE: As an exception to the above rules and for compatibility reasons with existing POTS procedures, keypad sequences using the service code 31 can also be terminated by using * instead of #: i.e. *31* and #31* are considered as complete keypad sequences as fully equivalent to *31# and #31#. 19/97

20 As a programmable option, the NT-IP can provide locally generated voice announcements to notify users with information returned from the network as a result of activation, deactivation, interrogation and invocation procedures. 5.2 Using the R key Some of the user procedures involving supplementary service require the use of the register recall (R) key. This clause describes the use of this R key in general terms. When a call A is in its active phase, and the user presses the R key, then the NT-IP interrupts the speech channel to the party connected in call A, generates a local dial tone and starts the T701 timer. When T701 elapses, and no other key has been pressed, the NT-IP removes the dial tone and restores speech channel to the party connected in call A. If the user presses any key before the timer expires, the local dial tone is removed, and, depending on the actual call state and on the key pressed, the NT-IP takes the appropriate actions as described below. The R key is also used the retrieve a held call A if the new call B has not reached the active state. 5.3 Service codes The following service codes are recognised to start local or network related procedures using keypad sequences: service code supplementary service type of procedure applies after R during a call 00 suspend/resume functional NO 01 closed user group functional YES 21 call forwarding unconditional functional/stimulus NO programmable 31 caller ID restriction functional YES 37 call complet. on busy subscr. functional NO 41 read back charges for last call local NO 43 call waiting local YES 53 hot line local YES 61 call forwarding no reply functional/stimulus NO programmable 65 caller ID local YES 67 call forwarding busy functional/stimulus NO programmable 82 call pick-up local NO All other service codes are treated as "unknown" and keypad sequences using such service codes are transparently passed to the network. 5.4 Multiple Subscriber Numbers (MSN) Description This service allows for multiple telephone numbers (MSN's or directory numbers DNs) to be assigned to an ISDN access. This basically permits the user to allocate distinct numbers to different terminals and/or services. The maximum number of MSN's per access is a network option Procedures Up to three MSN can be programmed into either port, using registers N1, N2 and N3. The MSN contained in N1 has a special significance, because it is included as the "calling party number" or as the "connected party number" in outgoing SETUP or CONNECT messages. These number are always coded as "type of number: unknown" and "numbering plan: unknown". note 20/97

21 If no number has been programmed for a port, incoming speech and audio calls will be offered to that port independently of the called party number. If one or more MSN have instead been programmed, then only the calls directed to one of the these numbers will be offered. It may be sufficient to program any number of digits as required to identify the number among those assigned to the access. To allows for such partial programming of the MSN, the NT-IP aligns the received Called Party Number and the programmed MSN to the right and then it verifies that the populated digit positions coincide. As a general rule, it is however safer to enter the whole MSN as some networks may not properly process such abbreviated MSNs. When in restricted power mode, no MSN compatibility check is performed. Incoming calls are offered to a port based on the port profile and on the incoming call management parameter (global parameter 05). This behaviour complies with ETS Calling Line Identification Presentation (CLIP) Description This service allows the called subscriber to receive information regarding the identity (telephone number and possibly subaddress) of the calling party. The calling user may either provide the calling number (in this case the number is screened, verified and formatted by the network), or the network itself uses the default accesses number. No checks are performed instead on the user-provided subaddress, which is transparently passed to the called user. The service is activated or deactivated by the network operator and therefore no user procedures related to the service deployment Procedures At the calling site, the NT-IP includes in the outgoing call set-up message the first programmed MSN associated with the port that originated the call. If the first MSN is not programmed, then no information is included. CLIP information received on incoming calls is also used to generate CLI display messages on the analog ports (see 5.16) 5.6 Call Hold and Retrieve (HOLD) This service enables a user to place an existing call into a stand-by state and, subsequently, to retrieve the call. When the call is in the held state, the associated channel becomes available for use with other calls by the same user (e.g. to start a new call or to accept a waiting call). The HOLD service may available on a subscription basis or on a general basis. The HOLD service is commonly used to start a new call or to accept a waiting call without releasing the currently active one. When one call is active and another one is held, the user can then switch between calls or activate other supplementary services such as Three Party or Explicit Call Transfer Procedures As a general rule, a maximum of two calls can be queued at a single a/b port: as an example, if a port already has an active and a held call, then that port is not allowed to start a third call and will not receive indication of incoming calls. 21/97

22 Placing a second call To start a second call when call A is established, the user presses the R key and starts dialling the number of the remote party. The NT-IP issues a HOLD request as soon as the user starts dialling the new call. As an exception, if call A is incoming, and the first digit dialled is 9, and no other key is pressed within T702 seconds, the NT-IP takes this as a request for the MCID supplementary service and acts accordingly). If the network rejects the request or if no response is received within T704 (e.g. due to the HOLD service not being supported or available), then the NT-IP aborts the HOLD requests and restores the speech channel to the party connected in call A. If a positive acknowledge is received (HOLD ACK message) the NT-IP sends a new SETUP message, including any digits dialled so far. Upon receiving the SETUP ACK reply message with indication of the channel assigned to the new call, the NT-IP connects the a/b port to the indicated channel. Subsequent digits are then sent in overlap mode. During the establishment phase for call B (i.e. the call is in the dialling or the ringing phase), pressing R again causes call B to be cleared and call A to be retrieved and reconnected. Once the new call B is established (i.e. the CONNECT message is received), then the user can alternate between the two calls assigned to the port or activate other supplementary services such as the three party conference (3PTY) or the explicit call transfer (ECT). When the user presses the R key after call B has reached the active state, only a limited numbers of actions are allowed. After R, the user can dial: 0 to disconnect the hold call 1 to clear the active call B and retrieve the held call A 2 to place B on hold and retrieve A (alternate call) 3 to place the calls in conference (3PTY) 4 to activate the ECT service 9 to invoke the MCID service on the active call (provided it is an incoming call) Every other digit will be ignored and the speech channel to the currently active call will be reconnected Alternating calls (Broker s call) When the user presses R 2, the NT-IP first sends a HOLD request for call B. If the request is rejected or if no answer is provided, then call B is reconnected. If call B is successfully placed on hold, then the NT-IP starts retrieving call A. If the retrieve request for call A is rejected or no answer is received to the retrieve request, then the NT-IP alerts the user with a short tone. Retrieving of call B is then started when the user presses the R key or automatically after 5 sec. If the retrieve request is for call A acknowledged, the NT-IP reconnects the port to the B-channel included in the retrieve confirmation message for call A Clearing procedures Remote clearing of the held call Upon receiving a clearing message for the held call A, then the NT-IP completes the clearing procedures by sending a RELEASE message and it sends a short local tone to alert the user of the call being cleared. 22/97

23 Remote clearing of the active call NT-IP Finnet Technical Reference Manual Rev. 4.0 Upon receiving a DISCONNECT or a RELEASE message for call B in the active or in the establishing phase (the called party does not answer or is busy) with call A in the held state, then the NT-IP acts as follows: if the clearing message is a DISCONNECT with PI, it keeps the connection to the B-channel to receive any call progress signal sent by the network (clear-forward tone) and it starts retrieving the held call either when the user presses the R key or automatically after 5". Upon retrieving call A, the release procedure for call B is completed. if the clearing message is a RELEASE then the NT-IP sends a RELEASE COMPLETE and it immediately retrieves the held call Locally originated disconnection When the user goes on-hook and an active call and a held call exist, then if the "reminder ringing for held call" facility is deactivated, then both calls are immediately disconnected if the "reminder ringing for held call" facility is activated, then: the currently active call B is disconnected and the NT-IP starts ringing the port to remind the user that call A still is in the held state; when the user goes off-hook, then call A is retrieved and the speech channel is reconnected. The reminder ringing has a maximum duration of 60 sec. After this time, if the port remains in the onhook state, then call A too is disconnected. If a waiting call exists when the user goes on-hook, the a/b port rings to alert the user (see 5.7.3) 5.7 Call Waiting (CW) Description This service allows the user to be notified of an incoming call, even when both channels on the user's access are busy, and therefore no channel is available for the call. Were the CW service not available at that access, then the call would be cleared with cause "user busy". Standard calls are offered with indications of the associated channel, while call set-up messages for waiting calls bear the indication "no channel available". Upon receiving this notification, the user can take appropriate actions to make one channel available (such as clearing or placing one of the existing calls on hold) and then answer the call. The maximum number of waiting calls is a network option. The CW supplementary service is available by prior arrangement with the network operator Procedures The NT-IP uses audible tones (CW tones) to inform the busy user of a "waiting call". As an extension to the standard service, the NT-IP also generates CW tones in the case that a "standard" (i.e. non-waiting) call is being offered but the compatible port is busy. Call waiting must be enabled by setting configuration register N9 position 2 to 1. Once enabled, the user can dynamically activate, deactivate the CW service or interrogate on the activation status. In order to activate, deactivate the CW service or to interrogate on the activation status, the following key sequences can be used: procedure short format activation *43# deactivation #43# interrogation *#43# Position 3 of register 4N holds the current status of the CW activation. 23/97

24 ! disabling CW tones may be necessary to avoid interference with operation of modem or fax devices Handling Waiting Calls The user willing to take a waiting call C must disconnect or place the currently active call A on hold. Call waiting (CW) tones are generated until the NT-IP receives an indication that call C is being released (e.g. by expiry of a network implemented CW-timer or due to a disconnection originated by calling party or when call is answered by another TE). The SETUP message for this new call C may either contain the indication of the associated channel or it may indicate "no channel available". The CW tones have the following pattern: 150 ON, 150 OFF, 150 ON, 8000 OFF Once alerted of the waiting call, the user can: ignore the tones and continue call A press R 0 to release the waiting call 3 and any subsequent call on wait until the user goes on-hook press R 1 to release call A and accept call C press R 2 to place call A on hold and accept call C press R 9 to invoke the MCID supplementary service (this applies to the call A, provided it is an incoming one, and it has no effect on the waiting call C) If the user goes off-hook and a waiting call is queued, the NT-IP rings the port. If a digit different from 0, 1, 2 or 9, follows the R key, the NT-IP sends a 5 sec congestion tone to the port to alert the user of the incorrect operation and then restores the previous situation. The user can interrupt the tone by pressing R again Rejecting the waiting call (R 0) The NT-IP disconnects the call on wait by sending a RELEASE COMPLETE with cause "call rejected". Any subsequent call on wait is also immediately RELEASed using the same cause Hold and answer (R 2) The NT-IP first sends a HOLD request for call A. If the request is rejected or if no answer is provided, then call A is reconnected, but call C remains queued to the port and call waiting tones are still generated. If call A is cleared while this HOLD request is pending, a congestion tone is sent to the port and then the user must then go on-hook to receive ringing for call C. If call A is successfully placed on hold, then the NT-IP sends a CONNECT for the offered call. If the network does not assign the call to the port (e.g. due to the call being assigned to another terminal on the access), the NT-IP sends a congestion tone for 5 seconds (or until the R key is pressed) before retrieving call A. If the network assigns call C to the port, the NT-IP connects the port to the channel indicated in the CONNECT ACK message received from the network. 3 this is only possible with dual TEI operation, where either port has its own TEI and therefore handles the call as if it were a distinct terminal. If single TEI operation is programmed, this sequence has no effect. 24/97

25 5.8 Restriction of caller's ID (CLIR) Description NT-IP Finnet Technical Reference Manual Rev. 4.0 This service allows the calling user to request that her/his party s number (and subaddress) is not presented to the called party. If the calling party has subscribed to the CLIR supplementary service in the permanent mode, then the network automatically invokes the CLIR supplementary service for each outgoing call. If the calling party has subscribed to the CLIR supplementary service in the temporary mode with default value "presentation restricted", then the network automatically invokes the CLIR supplementary service for each outgoing call unless the default value is overridden by subscriber request at the time of call request. If the calling party has subscribed to the CLIR supplementary service in the temporary mode with default value "presentation not restricted", then the network only invokes the CLIR supplementary service if requested by the subscriber at the time of call request". NOTE: The CLIR service may not be available on a general basis Procedures The CLIR parameter in the NT-IP operates like this: where: CLIR register no prefix *31# #31# 0 NO INDICATION RESTRICTED ALLOWED 1 RESTRICTED RESTRICTED ALLOWED 2 (default) ALLOWED RESTRICTED ALLOWED 3 RESTRICTED RESTRICTED RESTRICTED NO INDICATION means that octet 3a is NOT included., RESTRICTED means that octet 3a is included and set to RESTRICTED ALLOWED means that octet 3a is included and set to ALLOWED Therefore Setting the CLIR parameter to 0 does not actually restrict or request presentation of the calls, but it simply instructs the network to use the "default" presentation value, which may be either "allowed" or "restricted", depending on a subscription option. Setting the CLIR parameter to 1 includes the request to restrict presentation for all calls, unless the user prefixes *31# the presentation indicator is set to "allowed" for that call. Setting the CLIR parameter to 2 includes the request to request presentation for all calls, unless the user prefixes *31#, as in this case the presentation indicator is set to "restricted" for that call. For all cases, the final result depends on the network: for example, if the network does not offer the CLIR service on a general basis, and the user has not subscribed to the service, the number is presented anyway. If the user wants a permanent restriction, he/she can select one of the following options: subscribe to the "permanent restriction". In this case the CLIR parameter can be set to any value, as the call will be restricted anyway. subscribe to the "on a per-call basis, default restricted" and set the CLIR parameter to 0, 1 (this still allow the user to request presentation on a per-call basis by prefixing #31#). subscribe to the "on a per-call basis, default allowed " and set the CLIR parameter to 1 (this still allow the user to request presentation on a per-call basis by prefixing #31#). If the user wants to restrict presentation on a per-call basis, he/she can: subscribe to the "on a per-call basis, default allowed " and set the CLIR parameter to 0 or to 2. He/she can request restriction on a per-call basis allow presentation by prefixing *31#. 25/97

26 5.9 Connected Line Identification Presentation (COLP) Description The COLP service allows the calling subscriber to receive information regarding the identity (telephone number and possibly subaddress) of the party answering the call (due to possible call diversions, this number may be different from the called one) Procedures The NT-IP uses the first MSN for the relevant port and it includes this information (if present) in the CONNECT message. This service is only supported in the outgoing direction: display of the connected party number is not available on a/b ports 5.10 Connected Line Identification Restriction (COLR) Description The COLR service allows the answering user to request that the number (and subaddress) be not presented to the calling party. NOTE: the COLR service may not be available on a general basis COLR procedures Depending on the value assumed by the COLR parameter (register 4N, position 6), the outgoing CONNECT message contains the CONNECTED PARTY NUMBER information element with a presentation indicator set as shown in the following table: 5.11 Malicious caller ID (MCID) Description COLR Presentation register indicator 0 (default) NOT INCLUDED 1 RESTRICTED 2 ALLOWED Upon invocation of this service during an incoming call, the network registers and stores under control of the network operator critical information regarding the call, such as calling and called party number, time and date of the call. A subscription option allows for automatic registering of all unanswered calls. The MCID supplementary service is available by arrangement with the service provider. Cancellation is at the request of the subscriber or for service provider reasons Procedures The NT-IP allows the user to invoke the MCID service by pressing R 9 during the active phase of the call or immediately after the caller has disconnected. 26/97

27 5.12 Terminal Portability Description This service allows a user to suspend a call and subsequently to resume it at the same terminal and at the same socket, or after moving the terminal to a different socket, or at a different terminal on a different socket. When the call is suspended, the network maintains the connection to the remote user and it stores relevant information for the call (B channel), to allow the call to be re-established at a later time. When suspending a call, the user may specify a "call identity", which has to be indicated when the call is being resumed Procedures The TP service is used in the NT-IP to "transfer" active calls from one a/b port to the other. When a call is active on one port (say, port 1), the user suspends the call by pressing: if no call ID is entered, or R * 00 # R * 00 * # if a call ID (e.g. "1234") is desired. The user then goes on-hook. To resume the call at the other port (or on the same port), the user goes off-hook and dials or, if a call ID has been associated with the call: * 00 # * 00 * # Note that the suspended call can also be resumed from the same port Party Conference (3-Pty) Description This service enables the user with two ongoing calls (one active and one in the held state) to bridge the two calls into a three-way conference, so that a three-way conversation is possible among the promoting user and the two remote parties. The promoting user has complete control over the conference, as he/she can disconnect or temporarily exclude either remote party from the conference, or terminate the conference Procedures The 3-party conference can be entered when one active call (A) and one held call (H) exist. The user presses to join call H into the conference. Subsequently the user can: R 3 release the connection added on conference (H) R 1 resume private conversation with A (H returns to the held state) R 2 request explicit call transfer R 4 27/97

28 5.14 Closed User Group Description This service allows a user to be a member of one or more closed user groups. When such a membership is established, the network performs special access checks over calls originated or received by the user. Members of the same CUG are usually allowed to communicate among themselves, but calls leaving or entering the group are usually restricted. Nevertheless, as subscription options, a CUG member can be granted the right to place (Outgoing Access) and/or to receive (Incoming Access) calls outside the CUG (non-cug calls). Some additional restrictions can be placed on CUG members to prevent them from placing (outgoing calls barred) or receiving calls (incoming calls barred) within the CUG. The CUG service is available on a prior arrangement with the network provider. As a subscription option, the user can subscribe to a preferential closed user group. In this case, outgoing calls are by default treated as CUG calls, and no action is required on the part of the user's terminals to place CUG calls. If no preferential closed group has been subscribed to, then the user must explicitly indicate a CUG index when placing a CUG call Procedures In the NT-IP, a user with a preferential CUG places a call outside the CUG4 by dialling * 0 1 # in front of the called number. Calls within the CUG do not require any prefix. Users without preferential CUG need to explicitly indicate a CUG index (in the example, ) to place CUG calls by dialling: * 0 1 * # in front of the called number. Non-CUG calls do not require any prefix Advice of Charge (AOC) Description This service allows the served user to receive charging information related to calls and to the invocation or activation of supplementary services. The AOC supplementary service is usually activated on a general basis, i.e. the served user receives charging information at every call, but activation of the service may be required on a per-call basis. The AOC service actually consists of three services: the AOC-S provides information on charging rates at call set-up time and when charging rates change during a call. The AOC-S can also be used to charge call attempts (i.e unanswered calls) the AOC-D service provides cumulative charging information during the active cycle of a call. the AOC-E service provides recorded charging information at the end of a call. A network operator may choose to provide charging information either in "charging units" or in as a currency amount. 4 the user must have subscribed to the Outgoing Access (OA) option 28/97

29 Procedures The NT-IP is able to process the received charging information and to generate "charging pulses" on the a/b port that originated the call. Generation of charging pulses is enabled for either port by setting the relevant configuration parameter (registers N9, position 3) to 1. Additionally, when charging information is provided as currency amount, the general configuration parameter 08 contains the amount of currency equivalent to a charging pulse. This register contains 4 significant digits and an additional multiplier digit that specifies the number of digits after the decimal point. For example, if 6.05 units of local currency correspond to a charging pulse, the register shall be programmed either with "60503" or "06052".5! charging pulses may adversely affect operation of modem or fax devices Call Forwarding Services (CF) Description of the service based on the ETSI functional protocol NOTE: This section applies to call forwarding services using the ETSI functional protocol specified in ETS These services are used to instruct the network to divert incoming calls to a different number. Three different types of service are provided: call forwarding unconditional (CFU) : all incoming calls are diverted call forwarding busy (CFB): calls are diverted if they meet busy call forwarding no reply (CFNR): calls are diverted if no reply is obtained from the called user If the user's access has the MSN service, then these services can be activated on a "served number" basis rather than for the "whole access". This feature may not be available on a general basis: i.e. it may require a specific subscription by the served user, or it may not be offered by the network provider. Additionally, separate requests can be issued for different basic services (e.g. audio 3.1kHz, speech, 3.1 khz telephony, unrestricted data, etc). This feature may not be available on a general basis. In any case, the user can submit a request for diverting calls for "all services". As each activation can specify a different "diverted-to" number, the user has the possibility to specify different target numbers for each different service and for each different number on the access. The CF supplementary services are offered on a subscription basis, with several notification options: to the served user notification of forwarding notification of service being active 6 to the calling user notification of forwarding to the forwarded-to user presentation of the "served user" number when the diverted call is offered Activation, deactivation and interrogation procedures are available. 5 Placing the correct value in this parameter is required to guarantee proper operation of the charging pulses, it the AOC indication is based on the currency. 6 this notification occurs when the served user places an outgoing call 29/97

30 Procedures using the ETSI functional protocol NT-IP Finnet Technical Reference Manual Rev. 4.0 The CF functional protocol allows the user to request activation, deactivation of the service and to interrogate the status of the service. The "served user number" can be: implicitly set to the first MSN assigned to the port originating the request by using the "short format" sequences, or explicitly contained in the "long sequence" format If the first MSN assigned to the port is empty and the "short" sequence format is used, then the "all number" version of the request is used 7. All activation, deactivation or interrogation requests are issued for "all services". This is summarised in the table below: service procedure short format long format activation *21*<dtn># *21*< dtn >*< sun ># CFU deactivation #21# #21*<sun># interrogation *#21* *#21*<sun># activation *67*<dtn># *67*< dtn >*< sun ># CFB deactivation #67# #67*<sun># interrogation *#67# *#67*<sun># activation *61*<dtn># *61*< dtn >*< sun ># CFNR deactivation #61# #61*<sun># interrogation *#61# *#61*<sun># where <sun> stands for "served user number" and <dtn> stands for "diverted-to number". This sequences are mapped into the proper FACILITY messages to the network to activate/deactivate or interrogate the CF service. Information on the outcome of these requests is provided via voice messages. Upon interrogation the user receives information on the status of the service, and if the service is activated, about the served user number and the diverted-to number Procedures using the stimulus protocol The NT-IP also provides for support to the CF services using the stimulus procedures. Parameter 07 position 1 allows to select between support to functional or stimulus protocol. In this case the activation, deactivation and interrogation sequences (i.e. with service codes 21, 67 and 61) are simply passed over to the network as stimulus keypad sequences and no special processing is required on the part of the NT-IP. Information on the outcome of these requests are usually provided by the network using voice announcements or confirmation tones. 7 if the network does not support the "per served user number" option, it will however process the request as if contained "all number". 8 the activation, deactivation and interrogation requests may come out to be invalid in the case that the following conditions occur: the network option "activation, deactivation and interrogation for all numbers" has the value "NO", the MSN service is provided to the access, the "all number" version of the request is used, due to the first MSN not being programmed. In this case the first MSN MUST be programmed for the service to operate properly. 30/97

31 5.17 Call Completion on Busy Subscriber Description NT-IP Finnet Technical Reference Manual Rev. 4.0 The CCBS supplementary service enables user A, encountering a busy destination B, to have the call automatically completed when the destination B becomes free without any further call attempts: user A requests ( books ) the CCBS supplementary service the network: monitors destination B for access resources (e.g. one B-channel) to become available waits for a short time left for user B to possibly reuse the resources for originating a call, then indicates to user A that user B is free (recall) user A accepts the CCBS recall and transmit a SETUP message the network routes the call to user B. The network may provide a subscription option which applies to the whole access: Option Value Meaning Recall Global recall is offered to all compatible terminals. mode Specific recall is only offered to the specific terminal that activated the CCBS service. If the subscription option is not offered, one of the two values is chosen by the network provider Procedures If the CCBS service is available at the user s access, the original call that meets busy is cleared with a clearing message with cause 17 ("user busy") or 34 ("no channel available"), and including a piece of information indicating that CCBS requests are allowed (CallInfoRetain). When this happens and there is no call on hold for the a/b port 9, the NT-IP first couples any tone sent by the network (typically a busy tone) and, after a 3 second delay it generates a a voice announcement that invites the user to dial R5 10 to book a CCBS recall. Based on the network response to the CCBS invocation, a voice message informs the user on the outcome of the request. When the network ascertains that the called user is no more busy and the calling user is free, then it sends the calling user a specific message indicating that the remote user has become free. This message indicates whether the Global or the Specific Recall mode is in use and it also includes the BC/HLC and the called party address of the original call: if the Specific Recall Mode is specified, then only the port originating the CCBS Request can proceed in this CCBS transaction. if the Global Recall Mode is specified and register 43 (see Virhe. Viitteen lähdettä ei löytynyt.) is set to 1, then either port can process the CCBS recall (even if the CCBS has been booked by a terminal on the S-bus), provided that its BC/HLC port profile and one of the MSNs assigned to that port are compatible with the original call The NT-IP rings "CCBS-compatible" ports using a special CCBS ringing pattern: 300 ms ON, 300 ms OFF, 1400 ms ON, 3000 ms OFF If none of the CCBS compatible ports goes off hook within a certain (network dependent) time, the CCBS request is cancelled by the network and the NT-IP stops ringing the ports. When a CCBS compatible port goes off hook, the NT-IP sends a SETUP message containing the BC (and possibly HLC) i.e. of the original call, and another piece of information indicating that this is a CCBS recall. This SETUP message does not contain the called address. 9 otherwise, as the active call is in the disconnection phase, the R key will immediately retrieve the call on hold 10 using DTMF dialling 31/97

32 Upon receiving this SETUP, the network notifies all other terminals on the access that the CCBS-recall has been assigned. This causes the NT-IP to cease ringing any port still involved in this CCBS transaction. The call then proceeds as a standard outgoing call. The user may also: cancel the CCBS booking by going off-hook and pressing #37# interrogate the status of the CCBS by going off-hook and pressing *#37# 5.18 Explicit Call Transfer (ECT) Description This service enables the user with two ongoing calls (one active call to A and one held call to B) to request the network to join user A and user B in a single call. If the request is successful, the requesting user is then disconnected while user A and user B remain connected Procedures In the NT-IP, the ECT is requested by pressing R 4 when a call is active and another call is on hold (this also includes when the 3-PTY service is active) Calling Line ID services This service allows a user to be informed of the number of the calling party before answering a call. The service is also known as "call line identification" (CLID) or "CLASS" services. To this purpose, a specific display device must be connected to the a/b port or, alternatively, the display may be integrated in the phone. The NT-IP provides Calling Line Identification (CLI) display services for normal calls and for waiting calls. Both the FSK and the DTMF-based CLI signalling are supported. NOTE: CLI services for waiting calls are only available in FSK mode On-hook transmission The procedure meets the requirements of ETS , for the "associated to ringing, during ringing" method ( 6.1.1). CLI services are available for both ports in normal and in restricted power mode and in every situation: e.g. simultaneous occurrence of call offering to both a/b, or when the other a/b port is already ringing, etc. The first ringing pulse is not delayed compared to the occurrence of the incoming call Off-hook transmission The procedure meets the requirements of ETS When a waiting call occurs, the NT-IP cuts the speech path from the network and sends a specially coded Dual Tone Alerting Signal (DT-AS) to the a/b port. The NT-IP then waits for the display device to reply with a DTMF tone corresponding to the digit "D" or "A". After receiving this tone, the NT-IP sends the CLI message, and then reconnects the speech channel. 32/97

33 Configuration The NT1+ can select between FSK or DTMF signalling via the global parameter 44 (see Virhe. Viitteen lähdettä ei löytynyt.). enable the CLI service for either port by setting parameter N9, positions 6 and 7. select if a ring pulse or if no ring pulse is sent before the CLI message via parameter 4N pos 7 NOTE: if the DTMF mode has been selected, the off-hook CLI mode cannot be enabled. When reverting the FSK mode, the off-hook CLI must be enabled if needed. Once enabled via configuration, the user can "activate" or "deactivate" the CLI on the a/b port by going off-hook and dialling *65# or respectively, #65#. Interrogation of the activation status of the service is also possible by dialling *#65#. NOTE: After enabling the service via configuration register N9, the service must activated by dialling the *65# sequence. If the user attempts to activate the service when it is not enabled via register N9 results in a "service rejected" message Date and Time information Some networks provide a date and time information element in the CONNECT or in other messages. The NT-IP uses this information to update an internal clock. After reset, the content of the internal clock is invalidated and are therefore not used. When a message is received including this information, the internal clock is updated to the value indicated by the network and is then kept running. When this date and time information is available, it is included in the CLI message to be visualised by the CLI display device. NOTE: Date and time information is included in the CLI Message only in FSK signalling mode Message structure for FSK signalling mode When the FSK mode is active, the CLI data message consists of a call setup type message, followed by a date and time parameter (when this information is provided by the network) and then by either an ASCII coded calling party number, or a reason for no calling party number parameter. The Reason for no calling party number is visualised as: P O if the presentation indicator in the received calling party number i.e. is set to "restricted" if the SETUP does not contain a calling party number i.e. or digits are otherwise unavailable Message structure for DTMF messages When the DTMF mode is active the CLI message format is the following: <A><A-number><C> <B><0><0><C> <B><1><0><C> for standard CLI indication for number non available for number restricted where <A-number> is the calling party number. The same rules as in the case of FSK signalling apply for the representation of the number in DTMF digits Number representation The representation of the calling party number depends on the received "type of number": type of number display 33/97

34 national international unkown NT-IP Finnet Technical Reference Manual Rev <digits in calling party number i.e.> 00 <digits in calling party number i.e.> <digits in calling party number i.e.> NOTE: If configuration register 07 position 3 is set to 0, then the initial 0 is not prefixed to the digits contained in the national type of number format. This can be used for countries where the national type of number already includes an initial Additional services The following services do not strictly rely on network provided supplementary services, but they are instead "local services" Delayed clear-forward This service allows a user with an incoming call active to go on-hook and to resume the call form another phone connected to the same a/b port. When this feature is enabled by setting position 4 of register N9 to the value 1, the NT-IP postpones the clearing of incoming calls for 60 sec after the user going on-hook, so that the user is allowed to move the phone to another socket or to resume the call from another phone Distinctive Ringing This service allows the user to receive different ringing patterns for incoming calls based on the called MSN contained in the call-set message. This service allows the user to receive different ringing patterns for incoming calls based on the called MSN contained in the call-setup message. For either port, the user associates a specific ringing pattern to each of the three available MSN's. Distinctive ringing is enabled by placing 1 in position 4 of configuration register 4N. The user selects the pattern to associate with every MSN by programming register 95. The following patterns are provided: id pattern ON -4.0 OFF ON OFF 0.3 ON OFF ON OFF 0.3 ON 0.3 OFF 0.3 ON 3.5 OFF ON OFF 0.6 ON OFF ON OFF 0.2 ON -4.0 OFF ON OFF 0.7 ON -4.0 OFF Retrieving charging information for the last call The user may retrieve charging information for the last (outgoing) call by going off-hook after the call has been cleared by going off-hook and dialling *41#. A voice message indicates accumulated charges for that call, including any call attempt charges for unanswered calls. If the user with an active outgoing call places a second call using the HOLD service, cumulative charges for both calls are maintained Fixed Destination Calls ("Hot-Line" Calls) This service allows a user to place a call to a selected number without any dialling. If the user goes off-hook but does not dial any digit within a certain time, then the NT-IP automatically calls the selected number. This service must be enabled using position A of register 9N. 34/97

35 Configuration register 3N is user acccessible and it holds the required parameters for either port. The first two positions are set to 0 to disable the service. If not set to zero, these digit contains a value (1 to 30) which represents the timer duration in seconds. Subsequent digits are used to hold the fixed destination number. The user can program the fixed destination number 11 by going off-hook and dialling: * 5 3 * # where represents the new fixed destination number. Interrogation of the actual value of this number is possible by dialling The user can deactivate the service by dialling: * # 5 3 # # 5 3 # NOTE: the selected delay time must not interfere with timer T302. This timer is in the range 10 to 15 seconds and it is used by the switch to clear calls originated by the local user if no sufficient dialling inform is provided Call Pick-up When a call is ringing on one a/b port, the user can "capture" on his/her phone connected to the other a call ringing on the other a/b port. This service must be enabled using position 2 of register 9N. To capture the call when the other a/b port is ringing, the user goes off-hook and then dials: 5.21 Feature Key Protocol If the Feature Key Protocol is enabled: * 8 2 # when sending user digits, the NT-IP always uses Keypad information elements in place of the Called Party Number i.e., this also includes when the user dials * or # as the first digit during an active call, in response to the user pressing the R/flash key, the NT-IP: sends an INFORMATION message on the call reference of the active call; this message includes a Feature Key Activation information element with the Feature ID Number set to 0 if the network replies with an INFOrmation REQuest iinformation element, included in an INFORMATION message, with the Information Request Indicator set to "Prompt for additional information" and the "Type of information" set to "address digits", then any further digits dialled by the user are sent using the Keypad i.e. in INFORMATION messages. digits are sent until the network sends an Information Request information element with the Information Request Indicator set to "Information request completed". NOTE: Programming the NT-IP for the support of the Feature key protocol automatically disables all the supplementary services based on the stimulus or the functional protocols. 11 the value of the FDC timer can only be modified in configuration mode. 35/97

36

37 6 Configuration 6.1 General Information on Configuration Modes Local and remote configuration procedures are provided to access and modify configuration and diagnostics registers and to download the operating firmware. NOTE: Most of the operating features of the RS232 data port are however controlled using the AT command set at the RS232 interface. Generally speaking, configuration parameters are divided in two broad categories: global parameters affect the general operation of the NT-IP port specific parameters only refer to the operation of an individual a/b or data port To prevent users from tampering with critical parameter, two local configuration modes are provided: a user configuration mode allows for modifying non-critical parameters an operator configuration allows for complete control over all the operating parameters After downloading, the new firmware is stored on a secondary permanent read-only memory. This firmware can be activated either immediately or at a later time using a separate activation command Local configuration Two types of local configuration are possible: tone based PC based using key sequences from a DTMF phone connected to an a/b port, with voice announcements guiding the configuration process from a local PC connected to the data port of the NT-IP. The PC runs MS- Windows 95 or Windows NT 4.0 (or later). To prevent users from tampering with critical parameter, two local configuration modes are provided: a user configuration mode allows for modifying non-critical parameters an operator configuration allows for complete control over all the operating parameters Remote configuration Remote configuration can also be accomplished in two ways: tone based PC based using key sequences from a DTMF phone connected over the ISDN, with voice announcements guiding the configuration process from a remote PC port running MS-Windows 95 - Windows NT 4.0 (or later). The PC connects to the NT-IP over the ISDN via another NT-IP configured with the proper driver (async to sync HDLC) 6.2 Accepting remote configuration calls Remote configuration calls are accepted based on the calling party number and the called party subaddress. Up two 20 distinct remote configuration numbers/subaddress pairs and one default subaddress can be registered in the NT-IP. Numbers/subaddress pairs can have up to 21 digits and are stored in one of the following formats: [1] <number> [2] <number>/ [3] <number>/<subaddress> When an incoming data call is offered, the NT-IP verifies if the Calling Party Number contained in the call set-up message matches one of the registered configuration numbers. 37/97

38 If a match occurs: NT-IP Finnet Technical Reference Manual Rev. 4.0 if the matching number is stored in the format [1] (no "/"), than a called subaddress must be included in the call set-up message and it must match the default subaddress. If no default subaddress is registered, then the call is accepted independently on the received called subaddress. if the matching number is stored in the format [2] ("/" and no indicated subaddress), than no called subaddress is required in the call set-up and no check is performed on such element if present if the matching number is stored in the format [3] ("/" followed by a subaddress), then the called subaddress contained in the call set-up message must match the indicated subaddress Numbers/subaddress pairs are contained in configuration registers 70 to 89. The default subaddress is contained in configuration register 90. The proper remote configuration process (tone or PC based) is started according to the bearer service indicated in the call set-up message: the tone-based mode is activated through speech or audio calls, while the PC based process is activated through data calls. A call meeting the required conditions (bearer service, calling party number / called subaddress) is automatically answered by the NT-IP, provided that both a/b ports are in the idle state (on-hook, not ringing). 6.3 Downloading firmware upgrades Local and remote PC-based configuration modes support software upgrades. The downloaded software is automatically stored in a secondary non-volatile memory, and it can be activated at any later time after download is complete. The firmware is comprised of two main blocks: the code and the voice messages. A complete download (code + voice messages) as well as a separate download for code of for message only is possible. NOTE: Special care has been taken to preserve any existing configuration across upgrades. At compile time, every configuration parameter can be flagged as "keep existing value" or "return to default ". At activation time, each configuration parameters is acted upon based on the value of its flag. 6.4 Tone-based configuration procedures Local configuration Connect a DTMF phone to one a/b port. To enter the operator configuration mode: disconnect any existing POTS or RS-232 call disconnect the line pair connect a DTMF phone to one of the a/b port and lift the handset dial the access command sequence according to To enter the user configuration mode: disconnect any existing POTS or RS-232 call connect a DTMF phone to one of the a/b port and lift the handset dial the access command sequence Remote Configuration use a phone connected to an ISDN access whose number has been registered within the target NT-IP confirm that the Calling Line Id Presentation supplementary service is available at the target access dial the number of the target access once connected, dial the access command sequence according to Please refer to 0 for the read parameter status command. 38/97

39 6.4.3 Access command The access command sequence is the following: # * # # * # When entering the command, keep pauses between digits to less than one second Structure of Commands Each command specifies a "parameter index". Some parameters can be read and modified. Some other can be read, but not modified. The following commands are used: modify commands, used for parameter configuration read commands, used to read the current value of a configuration parameter reset commands are used to restore configuration values to the factory default Modify commands have the following structure: * < index> * <value> # Read and reset commands have the following structure Entering commands * <index> # When the NT-IP enters the configuration mode the device emits an audible tone. When the initial * key is operated, the NT-IP stops the generation of the tone and prompts the user with the message: "enter the parameter index": The user enters a two digit code representing the parameter index and: terminated by the * key for modify commands, or the # key for a read command. Only the last two digits entered are considered, so in case of an error the user simply re-enters the correct digits and then press * or #. If the entered index is not valid, a: "wrong entry" message is generated, followed by the audible tone indicating the ready state. If the entered index is a valid one, then the user is prompted with a message: Modify commands "enter the parameter value". The new value can now be entered, followed by the # key. Valid operations are confirmed via the message: "the parameter value <x> is <y>" where <x> and <y> represent the address and the assigned value. If the assigned value is incorrect, the following message is given: "wrong entry" The configuration mode can be interrupted at any time by going on-hook Read Commands The current value of the requested parameter is indicated via the message: "the parameter value <x> is <y>" 39/97

40 6.5 Description of configuration parameters NT-IP Finnet Technical Reference Manual Rev. 4.0 The NT-IP has a number of user programmable configuration parameters, contained in a non volatile memory. Some parameters (such as operating mode, access configuration, remote configuration numbers, etc.) are global parameters as they refer to the system as a whole. Other parameters (such as assignment of network numbers, port profile, call waiting enable, generation of metering impulses, level setting, etc.) are port specific for each a/b port. Parameters indicated as "O" can only be accessed in the operator configuration mode. 6.6 Global parameters register user/ operator default TEI assignment *02*XX# O XX = 0 63 fixed TEI (point-to-point) XX=64 XX = 64 automatic TEI (multi-point) operating mode (line doubler) *04*X# O X=0 S bus enabled (NT-IP) 0 X=1 S bus disabled (line doubler) Incoming call management X = 0 broadcast, *05*X# U X = 1 alternate, 0 X = 2 a/b 1 preferred, X = 3 a/b 2 preferred *07*XYZ# U support mode for supplementary services: X = 0 CFx stimulus, X = 1 CFx functional, Y = 1 HOLD & 3PTY according to ETSI (fixed) Z =1 0 is prefixed to the number representation (Calling Number, XYZ=011 ServedUserNr, ForwToNumber) when the Type of Number is National. This is used for CLI and other services *08* XXXXX# O Amount of currency per charging unit. Four digits followed by an additional digit indicating the number of decimal digits Disable local configuration 12 *30*X# O X=1 local configuration disabled enabled X=0 local configuration enabled CCBS mode X=0 either port only processes own CCBS requests *43*X# U X=1 either port also processes CCBS originated by other terminals 0 or by the other port (only significant if the GlobalMode option is used by the network). Select CLI mode: *44*X# U X=0 FSK mode 1 X=1 DTMF mode *7Y*n n# O Remote configuration numbers. These numbers are not altered when a new version is downloaded. n n: up to 20 digits. empty Y = 0 to 9 *8Y*n n# O Remote configuration numbers These numbers are not always reset to their default values when a new version is downloaded. n n: up to 20 digits. empty Y = 0 to 9 *90*nnnn# O Remote configuration "called subaddress". Up to 4 digits empty Note: "U" = user access, "O" operator only access Table A Global parameters 12 this command is only active in remote configuration mode 40/97

41 6.6.1 TEI assignment If the access has a multi-point configuration, the NT-IP must be configured for "automatic TEI assignment", by assigning the value 64 in the TEI assignment parameter (index 02). If the access has a point-to-point configuration, the TEI must be programmed with a value ranging from 00 to 63, according to the value of the TEI assigned by the ISDN service provider (usually the value 0 is used). NOTE: when programmed for fixed TEI operation, the "line doubler" operating mode is assumed. Therefore the S bus is automatically disabled Operating mode (register 04) The NT-IP can be used as described above or simply as a pair gain (line doubler) by deactivating the S bus. NOTE: when programmed for fixed TEI operation, the "line doubler" operating mode is assumed. Therefore the S bus is automatically disabled Management of Incoming Calls (register 05) When an incoming call is compatible with both a/b ports (i.e. matching MSN and port profile), four different options can be specified: mode operation value broadcast simultaneously offered to both a/b 0 (default) alternate alternatively offered to either a/b 1 or a/b 2 1 a/b 1 preferred offered to a/b1 (when both ports are free) 2 a/b 2 preferred offered to a/b2 (when both ports are free) 3 This parameter only applies to calls compatìble with both ports and when both ports are free. As an example, if port 1 is busy and CW-enabled, then the call will be offered to port 2 independently of the setting of this parameter and port 1 will receive the CW tones. The "alternate" or the "a/b x preferred" mode are useful for example if a small analog PABX is connected to the a/b ports of the NT-IP: in this case calls are never routed to both ports but every call is instead offered to one and only one port, thus simulating the behaviour of a small hunt group Support mode for supplementary services (register 07) This register allows to select: whether CF services are implemented using the ETSI functional protocol (1) or the stimulus (0) protocol whether HOLD and 3PTY services are implemented using the ETSI functional protocol (1) or the stimulus (0) protocol whether a leading 0 is added to the digits in the calling party number i.e. when the type of number is coded as "national" Amount of currency per charging unit (register 08) This parameter contains information required to generate charging pulses when the network provides currency based charging information. The parameter is comprised of four digits and an additional digit that specifies the position of the decimal point Enable local configuration (register 30) This parameter can only be accessed via remote configuration and it can be used to disable local configuration. 41/97

42 6.6.7 Enable support to the Feature Key Management Protocol This register enabled the NT-IP to support the Feature Key Management Protocol. See also CCBS operating mode (register 43) This register defines whether the NT-IP allows a port to: only process CCBS requests originated from that same port (value = 0), or also process CCBS requests originated by other terminals on the S bus or by the other port (value = 1). This mode is only significant if the GlobalMode option is used by the network CLI operating mode (register 44) This register configures the CLI service for use of FSK (0) or DTMF (1) signalling Remote configuration numbers and subaddress (registers 70 to 89 and 90) Remote configuration numbers and subaddress are used to recognize remote configuration calls. Up to 20 remote configuration numbers/subaddress pair and one subaddress can be programmed into the NT-IP. These number can only be assigned via remote configuration. Refer to 6.2 for details on use of these registers. NOTE: when using DTMF commands, no specific subaddress can be entered (i.e. in the "number/subaddress" format). This operation can only be carried out using the PC based configuration program. 6.7 a/b port Specific Parameters Separate commands are used for each a/b port: N = 1 holds for the 1 st a/b port, N = 2 for the 2 nd a/b port. The value of some port specific parameters contains a sequence of digits. Each digit holds the value of a specific sub-parameter. When entering a new value, use 9 to skip a digit position without altering the current value of the subparameter. It is not necessary to update all digit positions in the dialling mode and a/b port service parameters: e.g. if only digit position 1 and 2 have to be modified, then press # after entering the two digits to terminate the command. *N1*XXX...X# user 1 MSN (in Line Doubler mode operator ). Up to 28 digits. empty *N2*XXX...X# user 2 MSN. Up to 28 digits. empty *N3*XXX...X# user 3 MSN. Up to 28 digits. empty POTS register 1 (dialling mode). *N7*XY# user X = 0 pulse and tone, 1 tone only XY = 00 Y = 0 Recall/flash key enabled, 1 disabled Keypad Control Register. X= 0~9 (delay in 100ms increments before starting recognition of *N8*XYZ# user pulse dialling after going off-hook. (max recommended value is 3) XYZ = 302 Y = 0 (reserved, keep at zero) ; Z = 0~9 (minimum duration of R key set to [25 + (z*5)] ms). *N9*ABCDEFGHI # user Port Profile A = 0 outgoing only, A = 1 speech/audio, A = 2 telephony, A = 3 gr 2/3 fax A = 4 inactive 1 42/97

43 *3N*AANNNN# *4N*ABCDEFG# *64+N*X# *9N*ABC# user user user Register N Port Profile NT-IP Finnet Technical Reference Manual Rev. 4.0 call waiting B=0 disabled, 2 B=1 type 1 only, B=2 both type one and two generation of metering pulses C=0 disabled, 0 C=1 enabled delayed clear back D=0 disabled, 1 D=1 enabled select audio levels E=0 high levels (0,-7 dbr), 0 E=1 low levels (+4,-11 dbr) CLI on-hook (for standard calls) F=0 disabled, 1 F=1 enabled CLI off-hook (for waiting calls) G=0 disabled (fixed if the DTMF mode is selected) 0 G=1 enabled reserved 0 voice or tone to confirm CF and CW services I = 0 tones 0 I = 1 voice announcements FDC register AA = 00 FDC disactivated 00 AA = delay before starting the FDC call NNNNNN = target number reminder ringing for notification of held calls 0 A=0 disabled, 1 enabled CLI services activation (this is affected by the *65# keypad sequence) 1 B=0 deactivated, 1 activated CW activation (this is affected by the *43# keypad sequence) 0 C= 0 deactivated, 1 activated Distinctive ringing 1 D=0 disabled, 1 enabled CLIR E=0 pres. ind. is not included (unless *31# or #31#), 2 E=1 pres. ind. included and set to restricted (unless #31#) E=2 pres. ind. included and set to allowed (unless *31#) COLR F=0 pres. ind. is not included 0 F=1 pres. ind. included and set to restricted F=2 pres. ind. included and set to allowed Ring prior to CLI message G = 0 a ring pulse is sent before the CLI message 1 G = 1 NO ring pulse is sent before the CLI message Delayed Clear forward timer (65 for port 1 and 66 for port 2) 60 X=0 value in seconds (1 120) Fixed Destination calls 0 A=0 disabled, 1 enabled Call Pick-up 1 B=0 deactivated, 1 activated Wake up alarm 1 C=0 deactivated, 1 activated Each a/b port can be set according to the type of analog terminals connected (see 3.4.1). This settings use certain signalling features of the ISDN. For example, if the port profile of an a/b port is set 43/97

44 to "fax", then that port will not be offered calls coming from an ISDN phone or another NT-IP a/b ports set as "telephone" Audio level selection The NT-IP provides for two sets of reference audio levels for each a/b port. Higher levels meet reference levels values specified by most network providers and are suited for modems and fax devices. Lower levels provide for greater echo attenuation and better acoustic comfort CLI presentation Two separate parameters are used to respectively enable the CLI presentation on normal calls (onhook transmission) and the CLI on waiting calls (off-hook transmission) Voice or tone to confirm services This parameter allows the user to choose between audible tones or voice announcements to confirm activation and deactivation of Call Forwarding and Call Waiting services. Audible tones may be required when using special phone sets that decode the confirmation or rejection tones, usually provided on POTS networks when requesting CF activation or deactivation. A dial tone or a busy tone are provided to indicate the successful or unsuccessful outcome of the request POTS register 4 (4N) Reminder ringing of held calls If a call on hold exists when the user goes on-hook and this feature is enabled, the a/b port will ring to remind the user of the held call Activation of waiting calls This parameter is affected by the keypad sequences *43# and #43#. Using this sequences, the user activated or deactivates reception of CW tones when a call is waiting, or when a compatible call is received but the relevant a/b port is busy. In order to process waiting call, parameter N9 position 2 must be set to 1 or Activation of CLI services This parameter is affected by the keypad sequences *65# and #65#. Using this sequences, the user activated or deactivates CLI services on incoming calls. In order to generate CLI messages, parameter N9 position 6 (off-hook CLI) and/or 7 (on-hook CLI) must be set to Select CLI timing mode This parameter specifies whether a (first) short ring pulse is sent just before the CLI message Delayed clear forward timers (65 and 66) These registers specify the delayed clear timers respectively for the a/b port 1 (register 65) and the a/b port 2 (register 66). The default value for the timers is 60 seconds Special Service Enables (9N) This register can only be accessed via local and remote configuration through the PC running the AETHRA configuration software. It is not intended for the user. 44/97

45 Using this register, the operator can selectively enable the relevant special services (Fixed Destination Calls, Call Capture) 6.8 Read Commands code access announcement * 00 # U hardware and software revision * 0A # U read activation status of parameters * 16 # U status of a/b port 1: 0 = OK, 1 = NOK * 26 # U status of a/b port 2: 0 = OK, 1 = NOK * 67 # U current power status: 0 = emergency, 1 = normal * 60 # U current S bus configuration: 0 = short, 1 = extended (2B1Q only) * 93 # U read date and time * 94 # U read calling number of the last configuration call * 98 # U reset all user configuration parameters to their default values. * 99 # O reset all user and operator configuration parameters to their default values Table B - Direct Commands Port Status (commands 16 and 26) The following values are read back when the read port status command is issued *N6# user a/b port status 0 IDLE 1 error/status 2 outgoing call 3 active call 4 off-hook ringing Read activation status of port specific and global parameters (command 0A) This command is used to check if some parameters have been changed via a remote configuration call, but are still waiting to be activated. Four digits are read back, according to the following table: *0A# user Read date and time a/b1 specific parameters A=0 activated, 1 waiting for activation a/b2 specific parameters B=0 activated, 1 waiting for activation global parameters C=0 activated, 1 waiting for activation data port parameters D=0 activated, 1 waiting for activation This command allows to read date and time as maintained by the NT-IP. The NT-IP uses date and time information contained in some messages from the network to update its internal clock. After reset, this information is invalid until the internal clock synchronizes to the date and time provided by the network Default reset commands These commands are used to reset all configuration parameters to the factory default values. NOTE: remote configuration numbers are not affected by these commands. n.a n.a n.a n.a n.a 45/97

46

47 7 Data Port Operation The data port of the NT-IP is configured and operated via AT commands. 7.1 AT commands The NT-IP data port accepts AT commands in the 8N1 (8 bit, no parity, one stop bit) format. AT command processing varies according to the current NT-IP status. the command mode is entered after power-on or at the end of a connection. Data from the PC are interpreted as commands the online mode is entered after an incoming or outgoing connection has been successfully established. Any data received from the PC are used for transmission. the online command mode is entered when an escape sequence (usually with certain timing constraints) is received in the online mode: subsequent data from the PC are processed as commands, although the ongoing connection is still active Some AT commands can only be accepted if no connection is established or in progress. An AT string consists of the upper case AT or lower case at prefix followed by one or more commands possibly separated by a space and terminated by terminating character (usually C R, hex 0D). A reply is provided at every AT string. If all commands are correct a positive reply is sent (OK C R L F), otherwise the first occurrence of an invalid or incompatible command a negative acknowledge is sent (ERROR C R L F) and the rest of the string is ignored. The special A\ or a\ commands can be used to repeat the last AT command. Some internal registers are used to assign values to some parameters. These registers are identified by the letter S followed by a number : e.g. the character used as a command terminator is contained in S3 (default C R), whilst S5 (default backspace B S) indicates an editing character, which is interpreted as a command to cancel the last entered character in a command. If the AT string contains more than one interrogation, a reply is provided for each request with a final OK or ERROR Automatic Speed Detection In the command and in the online command phase, the NT-IP automatically detects the PC speed, and immediately upgrades its own speed to reflect the detected speed. Supported PC speeds are: 2400, 4800, 9600, 14400, 19200, 28800, 38400, 57600, and b/s. The last speed detected before entering the online state is then used throughout the call AT command list The description of every command is provided according to the following template: Ex F P V R Controls Local echo of received commands x = 0/1 local echo disabled /enabled command and online command mode OK o ERROR if 'x' is out of range This scheme indicates that: the command ATE1 or ATE0 has the function (F) to control the local echo to the AT commands received, the command requires specification of one configuration parameter (P), the command is valid (V) in the command or in the online command mode, a positive (OK) o negative (ERROR) reply (R) is provided by the NT-IP. 47/97

48 7.1.3 Basic commands A D [P T] [nnnnn] [/ssss] Ex H Ix O Qx Sn? Sn=v Vx Xn F P V R F P V R F P V R F P V R F P V R F P V R F P V R F Immediately answer the incoming call None When an incoming call exists Start a new call to the indicated number/subaddress P o T ignored, nnnn/ssss called number/subaddress (max.20/19 digits) Also supports the ATDnnnn 1[/ssss 1]+nnnn 2[/ssss 2] format for dual numbers. Command new state of connection (CONNECT, NO CARRIER,..), ERROR (incompatible) Controls echo of received commands to the PC x = 0/1 local echo disabled /enabled Command and online command mode OK o ERROR if 'x' is out of range Release current call None Online OK Query device status x = 0,2,4,5,7 Product code "AETHRA NT-IP" x = 1 ROM checksum "XXXX" 4 hex digits x = 3 firmware version "Vx.y" x = 6 report link status on the last call Command or online command See parameters Switch back to online mode None online command CONNECT o ERROR if send in an incompatible state Display response codes X = 0/1 display of response codes enabled /disabled Command and online command modes None if x = 1, if x = 0, either OK, ERROR if 'x' is out-of-range Read Sn register P n = 0, 2, 3, 4, 5, 7, 18, 21, 23, 25, 27, 29, 31, 32, 82, 83, 85, 87, 117, 125, 126, 127 V R F Command mode Current value of register Sn, ERROR if n invalid. Assign the value v to register Sn P n = 0, 2, 3, 4, 5, 7, 18, 21, 23, 25, 27, 29, 31, 32, 82, 83, 85, 87, 117, 125, 126, 127 V R F P V R F Command mode OK, ERROR if n invalid Set verbose mode x = 0/1 response in abbreviated/extended format Command and online command modes OK ifx = 1, 0 if x = 0, ERROR otherwise Defines the format of the CONNECT message P n (0~7) V R Command and online command modes OK, ERROR if n out of range 48/97

49 Z F P V R Reset all parameters to the values in the non-volatile memory None Command mode OK, ERROR if status invalid Extended "AT&" commands &Cx &Dx &F &Hx &Sx &W &Zm= <nnnn>/ <ssss> &Z? &ZO= <nnnn>/ <ssss> &ZO? *Dm F P V R F P V R C109 management x = 0/1 C109 always ON/connection status Command mode OK, ERROR if status incompatible C108 Management x = 0 simulated C108 (always ON), C108/1, C108/2) x = 1 use as C108.2: clear call when C108.2 goes off x = 2 use as C108.1: start a call using stored number when C108.1 goes ON Command mode OK, ERROR if status incompatible. F Resets all parameters to default values P None or 0 V Command mode R OK, ERROR if status incompatible. F P V R flow control management x = 0 flow control disabled x = 3 hardware flow control (RTS/CTS), default x = 4 software (XON-XOFF) flow control Command mode OK, ERROR if status incompatible F C107 management P x = 0/1 C107 always ON/ follows C108 V Command mode R OK, ERROR if status incompatible F Save current settings in non-volatile memory P None V Command and online command mode R OK F Assign the phone/subaddress nnnn/ssss to position m in Non Volatile memory P <nnnn>/<ssss> = assigned MSN / subaddress (max. 28/19 digits); 0 m 7 V Command and online command mode R list of phone number in Non Volatile memory F Display all phone numbers stored in Non Volatile memory P None V Command and online command mode R list of phone number in NV memory F P V R Assign MSN and subaddress <nnnn>/<ssss> = MSN / subaddress assigned to the data port (max. 28/19 digits) Command mode OK, ERROR if status incompatible F Readback the MSN/subaddress assigned to the data port P none V Command and online command mode R nnnn/ssss Select one of the phone numbers programmed in Non Volatile memory as the default F number P 0 m 7 V Command and online command mode R list of phone number in NV memory 49/97

50 7.1.5 Enhanced AT commands Bnn BPn CEn JAn JSn KAMn KASn KSMn KSSn &Jn EPDxx EPD? F Set the protocol in use for B-channel communication 10 through 18 = V.110 P 20 = V = PPP async to sync V command R OK or ERROR if n is out of range or if current status is not compatible F Enable/Disable BACP/BAP P 0 = disable, 1 = enable (default) V command R OK or ERROR if n is out of range or if current status is not compatible F P V R Enable/Disable Call Bumping 0 = disable, 1 = enable (default) command OK or ERROR if n is out of range or if current status is not compatible F add traffic threshold (S126) P n kb/s, default 48 V command R OK or ERROR if n is out of range or if current status is not compatible F subtract traffic threshold (S127) P n kb/s, default 32 V command R OK or ERROR if n is out of range or if current status is not compatible F add persist time in minutes (S85, bit 1 6) P 0 to 63 (default 0) V command R OK or ERROR if n is out of range or if current status is not compatible F add persist time in seconds (S85, bit 1 6) P 0 to 63 (default 0) V command R OK or ERROR if n is out of range or if current status is not compatible F subtract persist time in minutes (S125, bit 1 6) P 0 to 63 (default 0) V command R OK or ERROR if n is out of range or if current status is not compatible F subtract persist time in seconds (S125, bit 1 6) P 0 to 63 (default 0) V command R OK or ERROR if n is out of range or if current status is not compatible F P V R F P V R F P V R enable/disable Multilink PPP 0 = MP disabled (default) 3 = MP enabled (both originate and answer) command OK or ERROR if n is out of range or if current status is not compatible define endpoint discriminator to be used in MP configuration OFF (no EPD in use, default) c = < Octet_1 Octet_2 Octet_3.. Octet_n > c = [0 5] c = ascii_string command OK or ERROR if n is out of range or if current status is not compatible return endpoint discriminator none command returns current EPD 50/97

51 7.1.6 Storing and retrieving parameter settings NT-IP Finnet Technical Reference Manual Rev. 4.0 Current settings can be stored in non-volatile memory with the AT&W command. The ATZ command restores all settings to the values contained in the non-volatile memory. The AT&F command is used to reset all parameters to the factory default values: parameter value parameter value TEI AUTOMATIC Verbose (S23 bit 6) ON (1) MSN EMPTY Result code (S23 bit ON (1) 7) Subaddress EMPTY XON char (S31) (17) Auto Answer (S0) OFF (0) XOFF char (S32) (19) Escape char (S2) '+' (43) Max. frame size 2048 CR char (S3) (13) Multilink Protocol disabled LF char (S4) (10) Endpoint Discriminator none BS char (S5) (8) call bumping enabled DTE speed (S18) (9) BAP/BACP enabled C107 (S21 bit 3) Follows C108 (1) Add persist time 0 C109 (S21 bit 4) Line status (1) Add threshold 48 kb/s C108 (S21 bit 5) From DTE (1) Sub threshold 32 kb/s Echo (S23 bit 0) ON (1) Response to the ATI6 command The following information is given as a response to the ATI6 command: "DTE Async-HDLC statistics Rx Good Frames : 0 Rx Bad Frames : 0 Rx Overflow : 0 Rx Aborted Frames : 0 Rx Frames too long : 0 Rx Discard Frames : 0 Tx Frames : 0 Tx Underrun : 0 B-Channel HDLC statistics Rx Good Frames : 0 Rx Bad Frames : 0 Rx FIFO Overflow : 0 Rx Overflow : 0 Rx Aborted Frames : 0 Rx Frames too long : 0 Rx Discard Frames : 0 Tx Frames : 0 Tx Underrun : 0" "ATXn" result code Option Table CONNECT messages issued by the NT-IP at call establishment can have different format, as indicated by the following table. As an example, if ATX5 is active and a V120 call is established using the B-channel, the NT-IP sends a CONNECT /V /LAPF message to the DTE. ATV0 ATV1 X0 X1 X2 X3 X4 X5 X6 X7 0 OK V V V V V V V V 2 RING V V V V V V V V 3 NO CARRIER V V V V V V V V 4 ERROR V V V V V V V V 51/97

52 Symbol reference 6 NO DIAL TONE V V V V V 7 BUSY V V V V V 8 NO ANSWER V V V V V 1 CONNECT V 10 CONNECT 2400 % % % 11 CONNECT 4800 % % % 12 CONNECT 9600 % % % 17 CONNECT % % % 14 CONNECT % % % 39 CONNECT % % % 19 CONNECT % % % 20 CONNECT % % % 21 CONNECT $ # 22 CONNECT % % % 23 CONNECT % % % 47 CONNECT $ # symbol operation example V SUPPORTED -- % reports DTE speed CONNECT reports DTE speed/protocol DCE speed/error control CONNECT /V /LAPF $ reports the DCE speed/error code CONNECT 64000/NONE # reports the DCE speed/error code/error control CONNECT 64000/NONE/LAPF where Protocol V120, V110, PPP DCE speed (in PPP mode, if MP is disabled or in V.120) (in PPP mode, if MP is enabled) 2400, 4800, 9600, 19200, (in V.110 mode, depending on the user rate) DTE speed 2400, 4800, 9600, 14400, 19200, 28800, 38400, 57600, , Error code ARQ (used for V.120 connections), NONE Error control LAPF (used for V.120 connections) 7.2 RS-232 control signals DCD/C109 can be programmed to indicate connection status (AT&C1) or it can be set permanently ON (AT&C0). When DTR is programmed for DTR drop dial operation (AT&D1), the NT-IP attempts to establish a connection when the DTR goes ON, using one of the phone numbers stored in non volatile memory using the AT&Zm=ssss/nnnn. DTR transition to OFF causes the current call to be cleared if the AT&D1 or the AT&D2 commands have been issued. If hardware flow control mode is active (AT&H3), the CTS/C106 is used to flow control the local DTE. DSR/C107 can also be set to be permanently ON (AT&S0) or to follow DTR/C108 status (AT&S1). 7.3 Flow control Flow control on the interface to the local DTE can be configured using the AT&H3 command: AT&H0 AT&H3 AT&H4 Flow control disabled Hardware (CTS/RTS) flow control (default) Software (XON/XOFF) flow control With hardware flow control enabled (AT&H3), the NT-IP stops forwarding data received from the line if the local DTE sets RTS to OFF. Depending on the protocol in use, this may in turn translate into the NT-IP exercising flow control mechanisms on the link (e.g. by sending RNR frames or withholding acknowledgement of received frames) to slow down the remote device. 52/97

53 Similarly, the NT-IP uses the CTS signal to instruct the local DTE not to send more data to avoid overflow of its internal transmit buffer (e.g. when the DTE speed is greater than the link speed or due to back pressure from the remote site). Software flow control (AT&H4) is based on two control characters used to stop and resume traffic in the opposite direction. Character codes used for this purpose are contained in register S31(default 0x11, XON) and register S32 (default 0x13, XOFF). 7.4 Handling data calls Receiving calls In order to allow NT-IP to answer incoming data calls, the S0 register must be set to a value different from 0. If no MSN/subaddress has been programmed, incoming data calls will be offered to the data port independently of the called party number or subaddress contained in the incoming call SETUP message. If instead a MSN and/or a subaddress are configured, then only calls directed to that MSN/subaddress are answered. The programmed MSN/subaddress is also included as COLP information in CONNECT messages. When the V.110 mode is selected, the NT-IP also checks for V.110 rate adaptation information to be included in the incoming call SETUP message Placing calls Calls are placed using the standard sequence ATD<number> or, optionally, ATD <number>/ <subaddress> sequence. The programmed MSN/subaddress is used for the CLIP service in outgoing calls Using DTR-drop mode (direct call) The NT-IP can be programmed to automatically establish a data call when C108.1 has an OFF to ON transition. To this purpose, the NT-IP maintains a small phonebook of 8 numbers/subaddresses in non volatile memory. Numbers are entered in the phonebook via the AT&Zm=nnnn/ssss command. The phonebook can be read-back using the AT&Z? command. To enable the DTR-drop feature, use the AT&D1 command. When a transition of C108.1 from the OFF state to the ON state is sensed, the NT-IP will then start call establishment using the number selected in the phonebook via the AT*Dm command Terminating calls Calls are cleared by exiting the online state using the escape sequence and then disconnecting the call using the ATH command. Alternatively, if the AT&D1 or the AT&D2 commands are in force, calls are cleared with DTR/C108 going OFF. 53/97

54

55 8 PPP operation The Point-to-Point Protocol (PPP) defines procedures to configure, maintain and terminate a link between two peers. This link is used for the transport of higher layer network protocols such as the Internet Protocol. Additionally, the PPP defines a framework for multiple peer-to-peer signalling protocols (such as authentication protocols, multilink protocol and bandwidth allocation protocol). Multilink PPP (MP) is a protocol that allows two end-systems to use multiple physical channels to achieve a greater transmission speed. When using MP, the separate logical links existing on each physical connection are connected in a bundle. For ISDN applications, separate calls are established on the two B-channels resulting in a transmission speed of 128 kb/s. The main purpose of MP is to distribute transmitted PPP packets over the channels in the bundle and to recombine received packets into a single logical flow. The NT-IP makes the use of MP transparent to the user's PC: i.e., the user's PC is unaware of all the operations required to establish and release additional calls and to co-ordinate packet flows on the channels. Basically, from the PC point of view a single link exists with a higher throughput than if a single B-channel were in use. PPP is described in RFC The CHAP authentication protocol is described in RFC MP is described in RFC BACP/BAP are described in RFC Asynchronous HDLC to synchronous HDLC conversion Personal computers use the asynchronous serial interface to exchange PPP packets. These packets are contained in character-oriented HDLC frames. The NT-IP provides for conversion between such frames and bit-oriented, synchronous HDLC frames suitable for transmission over the B-channel to communicate to access routers at the ISP. 8.2 PPP operations Configuring PPP operations The AT command used to enable PPP operation is the following: ATB40 enable async to sync PPP In order to use PPP, the proper modem driver must be installed and the destination you are calling (e.g. an access server at an Internet Service Provider) must also support PPP Placing a single link PPP call The PC instructs the NT-IP to place a call using the ATD command. A link configuration phase is started as soon as the physical link is established. The NT-IP intervenes in the initial configuration process to locally negotiate the Asynchronous Control Character Map (ACCM) configuration option. This option is locally negotiated with the PC in order to increase the throughput on the B-channel by avoiding transmission of unnecessary escape codes on the B-channel Authentication When the link has been configured, an authentication procedure is started, using a protocol negotiated during the link establishment phase. The NT-IP provides two modes for handling authentication: 13 The PC only requires some characters (e.g. X-ON and X-OFF) to be control-escaped when sent by the peer. If the ACCM option is not negotiated locally, the PC assumes the default condition is in force and all 32 control characters (codes 0x00 to 0x1F) are control-escaped before being transmitted to the NT-IP. 55/97

56 mode mode 1 S87.2=1 default protocol required by the access server CHAP PAP or Shiva-PAP operation PAP is locally negotiated between the NT-IP to the local DTE. The username/password included in the PAP authenticate request from the local DTE are cached by the NT-IP and then used to handshake CHAP/MD5. The PAP (or S-PAP) authenticate request on the initial link is passed to the access server. mode 2 S87.2=0 PAP or Shiva-PAP CHAP The PAP (or S-PAP) authenticate request on the initial link is passed to the access server. Authenticate-request, response and success/failure packets are transparently passed between the local DTE and the access server. Protocols other than PAP and CHAP must be handled in transparent mode. This may not guarantee proper authentication in all configurations. 8.3 MP operations Configuring for MP In order to use MP, the proper modem driver must be installed and the destination access server must also support MP. An attempt to place an MP call to a device that does not support it, results in a single B-channel PPP connection. Once the PPP protocol as been selected using ATB40, the AT&Jn command is used to enable or disable MP operation: AT&J0 AT&J3 NOTE: AT&J1 and AT&J2 commands are rejected Placing an MP call Disable MP Enable MP in answer and originate modes IF MP is enabled the NT-IP includes an MRRU configuration option and possibly the EID configuration option (see 8.3.6) when configuring the initial link. If MP operation is rejected by the server, the additional channel is not established and the session continues on the initial link Establishing the additional channel After successful negotiation of MP, the NT-IP establishes the second call to the server. By default, the same telephone number is used for both MP connections. If required, two different numbers may be specified by using the ATD<DN_1>+<DN_2> command, where <DN_1> and <DN_2> represent the phone numbers of the destination. The DTE will not be notified of this additional call. If Bandwidth-On-Demand (see 8.4.1) is enabled, the NT-IP will not start the call immediately after negotiation of MP, but it will rather postpone the call until the conditions for establishing the second channel are met. If this second call fails due to network reasons (e.g. network congestion, or the access server being busy, or the second B-channel being not available), the NT-IP will repeat the call at intervals of 60 seconds. If the call fails because one analog call or a configuration call is active, and the call bumping feature is enabled (see 8.4.2), the NT-IP will automatically retry when that call is cleared Configuring the additional link Once the call is established, the NT-IP autonomously negotiates configuration parameters for the additional link, using the same option values negotiated for the first link. 56/97

57 If LCP cannot be properly configured or the authentication procedure does not complete, the B-channel is disconnected and single channel operation continues Authenticating the additional link If the default non-transparent authentication mode is selected (S87.2=1), see 8.2.3, PAP or CHAP authentication are completely handled by the NT-IP using the username/password cached when establishing the initial link. If the transparent authentication mode is selected (S87.2=0), then: if PAP authentication has been negotiated on the initial link, the NT-IP sends the PAP authentication request using the same username/password as in the first authentication if CHAP authentication has been negotiated on the initial link, the NT-IP transparently passes any CHAP authenticate-request, response and success/failure packets between the PC and the access server. It is recommended to use the default mode, as some software implementations on the PC do not properly handle multiple CHAP authentication cycles during a PPP session. This would prevent additional connections to be authenticated. However, transparent CHAP authentication is the most secure method, as the user's password is not cached within the NT-IP MP data phase If LCP configuration and authenticated on the additional link are successful, the NT-IP distributes outgoing traffic from the DTE between the two channels, and sequences the packets received on either channel in a single packet flow before handing them over to the DTE. Should the connection on either channel be cleared for reasons other than "call bumping" (see 8.4.1), the NT-IP will not re-attempt to establish the connection Endpoint Discriminator The Endpoint Discriminator (EID) consists of a Class Field and a user defined Address Field. When this EID is configured into the NT-IP, it will be used during the PPP negotiations that occurs on the initial and the additional channels. The access server uses this EID to associate a PPP link to a specific endpoint and therefore either creates a new bundle or adds this link to the bundle to the same end-point. The use of EID is optional, but it may be required by some MP implementations at the server side. Class values are assigned as follows: Class Length Comments 0 Null Class 0 the default value if the option is not indicated 1 Locally Assigned up to 20 a local assignment (e.g. a device serial number) 2 IP Address 4 an IP host address 3 MAC Address 6 an IEEE MAC address 4 Magic-Number block up to 20 1 to 5 concatenated 32 bit PPP Magic-Numbers 5 Directory Number up to 15 an octet sequence representing an E.164 DN Use of class 1 and class 4 is "deprecated" by the MP standards and should be avoided. The EID Address field can be assigned by the ATEPD command: ATEPD OFF indicates that no EID has to be included in the configuration. This is the default value. ATEPDc = <Octet_1, Octet_2, Octet_3,.., Octet_n>, where c indicates the selected class (0 to 5) and each Octet_i is in the range from 0 to 255. The angle brackets "<" and ">" are part of the this command. 14 A subsequent call is attempted after 60 seconds. 57/97

58 ATEPDc = ascii_string, where c indicates the selected class (0 to 5) and ascii_string is a string of ASCII coded character, which are transparently passed to the EID. The first character in this ascii_string must be not be an opening angle brackets ("<"). The command ATEPD? can be used to view current setting of the Endpoint Discriminator Address. 8.4 Call Management Procedures The NT-IP implements call management procedures in order to optimise the usage of the B-channels and minimise costs: call bumping, traffic based bandwidth on demand (with and without bandwidth allocation protocol) Traffic based Bandwidth-On-Demand Bandwidth-On-Demand (BOD) or Dynamic Bandwidth Allocation (DBA) refers to the ability of a system to dynamically change the bandwidth of a multilink bundle by establishing and removing links. BOD decisions are based on link utilisation. The decision to add a channel is based on either the transmit or the receive traffic on the existing channel staying above an "add threshold" for a defined "add-persist" amount of time. The additional channel is removed when the both the transmit and the receive traffic on that channel stays below a "subtract threshold" for a defined "subtract-persist" amount of time. Add and subtract threshold and persist time are specified in the following AT commands: ATJAn add traffic threshold for n kbps, (default, n = 48). S126 ATJSn subtract traffic threshold for n kbps, (default, n = 32). S127 ATKAMn or ATKASn add-persist time for n period in min/sec, n = 0-63 S85 Bit 1 7 ATKSMn or ATKSSn subtract-persist time for n period in min/sec, n = 0-63 S125 bit 1 7 If the add-persist time is 0, then BOD is disabled (default). BOD is only effective if calls originate from the NT-IP Adding bandwidth The NT-IP calculates the averages of transmit and receive traffic on the initial link in the last seconds (or minutes) as indicated by the ATKA command. The NT-IP then continuously compares these averages to the programmed add threshold. When either the transmit or the receive average passes this threshold, the NT-IP attempts to establish a call for the additional link according to Removing bandwidth The NT-IP calculates the averages of transmit and receive traffic on the bundle in the last seconds (or minutes) as indicated by the ATKS command. The NT-IP then continuously compares these averages to the programmed subtract threshold. When this threshold is passed, the NT-IP stops sending data packets on the additional link and it transmits a LCP Terminate-Request to the access server on that link. After receipt of the Terminate-Ack the NT-IP disconnects the B-channel supporting that link. If no Terminate-Ack is received within 3 sec, the Terminate-Request is sent again. In case of no response, the link is assumed to be terminated anyway and the NT-IP disconnects the channel Call Bumping "Call Bumping" refers to the capability of the NT-IP to drop the channel supporting the additional MP link and to use that channel when the user wants to place or to answer a voice call through a phone connected to one of the two a/b ports. The following command are related to Call Bumping: ATCE0 ATCE1 Disable call bumping Enable call bumping (default) 58/97

59 The Call bumping enable status is also reflected in bit 0 of register S Outgoing calls NT-IP Finnet Technical Reference Manual Rev. 4.0 If the user goes off-hook to start a voice call, the NT-IP stops sending packets on the additional channel and then requests link termination on the "additional channel". When the server acknowledges the termination request (indicating that no more packets are being transmitted on that link), the NT-IP clears the call, and then sends the call set-up message for the voice call. NOTE: due to the time required to properly terminate the additional link, some delay may occur before getting the dial tone for the analog call Incoming calls An incoming voice call is offered by the network as a waiting call15 when both B-channels are in use. If Call Bumping is enabled, the NT-IP transmits an ALERTING message, it rings the a/b port(s) and it then waits for the user to go off-hook to start the link termination procedure on the additional channel. NOTE: this avoids slowing down the data traffic until the call is actually answered; nevertheless the user may experience some delay before being connected to the calling party. When the speech call has been cleared, the NT-IP attempts to re-establish the additional link, it therefore places an additional call, re-using the same phone number as for the first establishment: if BOD is enabled (add-persist value is not zero): the additional call is placed based on traffic statistics being collected during and after the speech call; nevertheless, a minimum of 10 seconds since the speech call has been cleared must elapse before the additional data call is placed when BOD is disabled (the add-persist value is zero): the additional call is started 10 seconds after the speech call has been cleared. For the duration of the voice calls, the NT-IP does not process any other incoming call, unless the connection to the access server on the original channel is terminated. Call Bumping does not obviously apply to a second voice call (i.e. the user on the other a/b port is not allowed to place calls) Diagnostic calls Call bumping also applies to remote diagnostic calls occurring during MP operation. Such a call takes precedence over PPP calls and therefore it is answered after the additional link has been terminated and the supporting physical connection has been disconnected. After the diagnostic call has been disconnected, the NT-IP attempts to re-establish the additional link. NOTE: Diagnostic calls are always processed independently of Call Bumping being enabled or not THE BANDWIDTH ALLOCATION PROTOCOL When using BOD as described in 8.4.1, bandwidth is added or removed based on some user-defined traffic thresholds internal to the NT-IP (or to the PPP server on the other side). Furthermore the NT-IP must know in advance the telephone number of the additional channel. The Bandwidth Allocation Protocol (BAP) allows the two endpoints (i.e. the NT-IP and the PPP server) to gracefully negotiate when adding and dropping the additional bandwidth, and therefore it makes more likely that BOD decisions are better suited to the real traffic. BAP also provides a means to indicate the telephone number that has to be dialled to place the additional call. The Bandwidth Allocation Control Protocol (BACP) is a control protocol for BAP, and it is mainly used to determine if the peer supports BAP. 15 If the waiting call supplementary service is offered by the network, and subscribed to by the user. 59/97

60 BACP/BAP can be enabled as follows: ATBP0 Disable BACP/BAP function ATBP1 Enable BACP/BAP function (by default) NT-IP Finnet Technical Reference Manual Rev. 4.0 BACP/BAP is transparent to the user. When the BACP/BAP function is enabled and the MP has been successfully negotiated, the NT-IP uses BACP to determine whether the peer supports BAP and to agree upon link discriminators. If the access server agrees to use BAP, this is used to negotiate addition and removal of the second B channel with the peer equipment based on user-defined traffic thresholds. When BACP/BAP is enabled, the NT-IP includes the Link Discriminator option in LCP configuration for every link. If, during configuration of the first link in the bundle, either the Link-Discriminator option is code-rejected or the remote peer does not include the Link Discriminator option in its Configure- Request, then the NT-IP then assumes the BACP/BAP is not supported at the server, and no further BACP/BAP activity is taken. If the Link-Discriminator option is acknowledged in both directions, then the NT-IP attempts to negotiate BACP on the first established link, (i.e. it sends a BACP Configure-Request, including the Favoured-Peer option with a Magic Number of 1). If the BACP/BAP is not enabled, the NT-IP code-rejects the Link Discriminator option if this is offered in the LCP configuration Adding bandwidth using BAP When BAP has been successfully negotiated and the traffic conditions for adding a channel to the bundle are met, the NT-IP sends a Call-Request BAP packet, including the link type option set to "ISDN". If the Call-Response indicates Nak, the NT-IP will not retry to establish the call until the conditions to add a channel are newly satisfied (i.e. the add-persist timer is restarted). If the Call-Response indicates Rej or Full Nak, no more attempts will be retried for the entire duration of the bundle. If the server replies with a Call-Response indicating Ack, the NT-IP starts the new call, possibly using any Phone-Delta information included. The NT-IP does not implement the server side of BAP, i.e. when receiving a Call-Request, the NT-IP always responds with a Call-response indicating Rej. The request to add bandwidth may also come from the server, as a Callback-Request. Upon receiving this packet, the NT-IP replies with an Ack response if resources are available (i.e. the NT-IP is not already using two B-channels), and attempts to establish the call using any Phone Delta information included in the request packet. In either case, when the call attempt is completed, the NT-IP transmits a Call-Status-Indication packet, indicating the result of the call attempt (either successful or reporting the Q.931 cause in case of failure). The NT-IP does not include the retry action and will not retry to establish the call until the conditions to add a channel are newly satisfied (i.e. the add-persist timer is restarted) Removing a link using BAP When the traffic conditions for removing the additional channel, the NT-IP transmits a Link-Drop- Query-Request indicating the link discriminator of the link deemed to be dropped. If the Link-Drop-Query-Response indicates Nak or Full-Nak the NT-IP restarts the subtract persist timer and does not take any further action. If the Link-Drop-Query-Response indicates Ack the NT-IP starts the link termination procedure as described in Upon receiving a Link-Drop-Query-Request, the NT-IP transmits an Ack response if its transmit traffic has been below the add-threshold for at least half the add-persist time. If the transmit traffic 60/97

61 has exceeded the add-threshold during half the add-persist time, the NT-IP responds with Nak. No immediate action is taken by the NT-IP, which keeps the link in use until the reception of a LCP Terminate-Req. 61/97

62

63 9 V.120 Communications V.120 is an international standard that defines a protocol for peer-to-peer communications over ISDN. The V.120 protocol allows two endpoints to exchange error-protected, flow controlled traffic. V.120 implements a variant of HDLC based Link Access Procedure known as LAP-F and described in the ITU-T recommendation V.120 and Q.922. The NT-IP does not allow for link parameter negotiation or for establishment of multiple logical links on the same physical channel. Only the single default link (LLI = 265) is used. 9.1 Configuring the V.120 mode In order to use V.120, the proper modem driver must be installed and the called destination must also support V.120. The ATB20 command is used to select V.120 operation: ATB20 Select V.120 protocol 9.2 Placing V.120 mode calls The standard sequence ATD<number> or, optionally, ATD<number>/<subaddress> is used to place a V.120 call. The call SETUP message includes the Bearer Capability (BC) information element set to "unrestricted digital information". When V.120 is configured, this is the expected B-channel protocol independently of any LLC information being included in the incoming call SETUP message. 9.3 V.120 operation As soon as the connection is established, an initialisation procedure takes place. Should this initialisation fail, then the call is cleared. Once that the logical link has been established, characters received from the DTE are assembled into V.120 frames. Frames are then forwarded either when the maximum frame length is reached (as set in the ATCL command), or when a 100 msec timer since the last received character has expired. The default maximum transmit frame size for V.120 is 256 octets, not including any FLAG, transparency bit and octets and FCS. The ATCLn command (n = 1~2048) can be used to select a different value. The maximum receive frame size is always set at 2048 octets. The NT-IP always uses a window size of 7. The NT-IP assumes that the local DTE uses a character format of 8 bit data, no parity, 1 stop bit (8N1). 63/97

64 10 V.110 Communications The NT-IP supports the V.110 rate adaption for asynchronous data at various speeds. Supported data rates are: 2400, 4800, 9600, 19200, and b/s. These rates define the adaption scheme used on the B-channel. Data rates at the local interface with the DTE can be selected independently of this V.110 rate. Flow control must be enabled via the AT&H3 or the AT&H4 command to cope with any speed mismatch between the local DTE and the adaption rate and the local and the remote DTE. The NT-IP supports the 8 bit/char, no parity, one stop bit format (8N1) Configuring the V.110 mode The following AT commands are used to select V.110 operation: adaption rate (b/s) ATB10 follows DTE ATB ATB ATB ATB ATB When the ATB10 command is in force, the NT-IP uses an adaption rate from the above list that matches the DTE speed or it uses is the next lower value16. This is true for outgoing calls, as incoming calls are always accepted independently on the line speed indicated in the incoming call setup message Handling V.110 mode calls In order to use V.110, the proper modem driver must be installed and the called destination must also support V Outgoing calls The call is started either via an ATD <number> command or using the DTR-drop mode (see 7.4.3). The call SETUP message always includes the Bearer Capability (BC) information element set to "unrestricted digital information" and a Low Layer Compatibility (LLC) information element indicating that the call will use V.110/X.30 rate adaption for asynchronous characters at the data rate selected according tho the ATB1x command currently in force Incoming calls Incoming calls are accepted if V.110 rate adaption information is contained either in the LLC information element or in octets 5, 5a and 5b of the BC information element in the received SETUP. If both elements are included in the incoming SETUP message, the LLC element takes precedence The NT-IP accepts V.110 incoming calls independently on the adaption rate indicated in the incoming call SETUP. This rate is however reported in the CONNECT message, e.g. CONNECT /V /NONE if the ATX5 command is in force Rate Adaption The V.110 rate adaption protocol is based on three adaption steps: 16 e.g. with the PC operating at 28.8 kb/s, the selected rate adaption is 19.2 kb/s 64/97

65 RA0 RA1 RA2 NT-IP Finnet Technical Reference Manual Rev. 4.0 async to synch: data is padded with stop elements to fit the nearest 2 N x 600 bit/s adaptation of resulting data to the closest intermediate rate of 8, 16, 32 or 64 kbps (RA1) adaptation of intermediate rates to the bearer rate of 64 kbps Rate Adaption Steps Step 0 (RA0) This step consists in padding the incoming bit patterns with additional stop bits to fit the closest 2 N x 600 bit/s rate (i.e.: 600, 1200, 4800, 9600, and bps). If the incoming character rate exceeds the nominal rate, stop bits can be deleted by RA0 up to a maximum of 1 stop bit every 8 characters. Deleted stop bits are reconstructed before passing characters to the DTE (if the bit following the 8 th bit in a character is not a mark, a stop bit must be inserted). Step 1 (RA1) V.110 uses a data frame of 80 bits. Each data frame carries 48 user data bits from RA0 in the positions marked D1 to D48. The frame synchronisation pattern consists of a 0x00 octet repeating every 10 octets, with all octets in between having the B1 set to 1. Depending on the RA0 rate, multiple positions are used for every RA0 bit (e.g. to transmit 1200 bps each RA0 bit uses 4 D positions). octet B1 B2 B3 B4 B5 B6 B7 B D01 D02 D03 D04 D05 D06 S1 3 1 D07 D08 D09 D10 D11 D12 X 4 1 D13 D14 D15 D16 D17 D18 S3 5 1 D19 D20 D21 D22 D23 D24 S 6 1 E1 E2 E3 E4 E5 E6 E7 7 1 D25 D26 D27 D28 D29 D30 S6 8 1 D31 D32 D33 D34 D35 D36 X 9 1 D37 D38 D39 D40 D41 D42 S D43 D44 D45 D46 D47 D48 S9 The E bits represent signalling information, including the structure of user data bits, the S bits are used to carry synchronisation and status information, X bits are used for end-to-end flow control. The RA1 frame is used to adapt the RA0 rate to the closest intermediate rate of 8, 16, 32 or 64 kb/s rate. As an example: if the user rate is 4.8 kb/s it uses all the 48 D bits in the frame at an intermediate rate of 8 kb/s if the user rate is 2.4 kb/s, then user data bits are repeated twice, thus resulting in 24 user data bits contained in the RA1 frame. E bits indicate the "repetition rate" of user bits inside the RA1 frame: Step 2 (RA2) input interm. repetition rate rate rate E1 E2 E Depending on the intermediate rate, the whole RA1 structure is contained in 1, 2,4 or 8 bit positions in the B-channel. This intermediate rate is known from the LLC information element. user intermediate b1 b2 b3 b4 b5 b6 b7 b8 rate rate X 65/97

66 Operating sequences X X X X X X X X X X X X X X RA1 Frame synchronisation and signalling At least 2 consecutive frame pattern must be met to achieve synchronisation. Loss of frame sync is assumed when errors in the framing pattern is detected in three consecutive frames. Establishment Upon B-channel establishment, the RA1 frame is transmitted with S = OFF, X = OFF, D = 1)17. The receiver starts a timer T1 (1 sec) and searches for the RA1 frame in the incoming B-channel, according to the intermediate rate. If no frame synch is achieved before T1 expiry, then the call is cleared. When the receiver synchronises to the incoming frame, it stops timer T1, starts sending the "connect" RA1 frame (S = ON, X = ON, D = 1), connects C104 to the received data, and, with a delay of 24 bits, starts transmitting data received from the DTE on C103. Data phase and flow control During the data phase, S bits are set to ON, and D bits carry user data. Flow control may be required if the DTE s have different speeds. The line rate will be that of the calling side. Case 1) DTE "A" is calling and is has a higher speed. The line rate will match the speed of DTE "A". TA "B" flow controls TA "A", using the X bit. TA-A will in turn flow control DTE-A using C106. It is also possible that DTE "B" flow controls TA "B" by using C105. DTE "A" TA "A" line rate 9600 TA "B" DTE "B" C106 OFF X = OFF C105 OFF Case 2) DTE A is called. The line rate will match the speed of DTE B. DTE "A" TA "A" line rate 1200 TA "B" DTE "B" C106 OFF The TA "A" flow controls DTE "A". No end-to-end flow control occurs. Locally originated disconnection When a logical disconnection is initiated by the local host18, the NT-IP starts sending the "disconnect" RA1 frame with (S = OFF, X = ON, D = 0) after having transmitted all characters so far received from the DTE. 17 ON is represented by 0, OFF by 1 66/97

67 Upon receiving a "disconnect confirmation" RA1 frame with (S = OFF, X = ON, D = 0) or losing the RA1 frame synch, the NT-IP indicates C104 to mark and then disconnects the B-channel. If no disconnect confirmation is received, the call is released after 3 seconds. Remotely originated disconnection Upon receiving the "disconnect" RA1 frame with (S = OFF, X = ON, D = 0), the NT-IP responds by sending the same RA1 frame and then it waits for the remote peer to clear the B-channel, otherwise the disconnection will be originated locally after a 3 second timeout. If enabled by the AT&C1 command, the NT-IP sets C109 OFF to indicate that the physical connection has been released. Loss of frame sync Upon detecting frame loss, the NT-IP first sets C104 to mark and transmits X = OFF. The NT-IP then attempts to resynchronise. If synchronisation is not achieved in 3 seconds, the NT-IP starts the disconnection procedure as in 0. If resynchronisation is achieved the NT-IP sends X = ON and resumes transmission of used data after a delay of 24 bits. 18 either by C108 going OFF if the AT&D1 or the AT&D2 commands are in force or in any case by exiting the online state using the escape sequence and then disconnecting using the ATH command 67/97

68

69 11 Installation Guide This guide will assist you to install and use the NT-IP. Appendix A also describes the installation of the Remote Access (which is necessary to establish the connection to the Internet) on the platform used by the PC. Three steps are required to install the NT-IP and to use it: physical installation installation of the NT-IP as a new device creation of a dial-up connection 11.1 Unpacking the NT-IP Packing List 1. An NT-IP 2. A power adapter RJ-45 (polarised) to RJ11 cable to connect to the telephone line RJ-45 to RJ-45 cable 5. 1 RS pin to 9-pin cable RS pin to 9-pin adapter " driver disk User's Manual. The diskette includes the following drivers (.INF files) for the Windows 95/98 and the Windows NT 4.0 environment: PPP (64K) : this only allows for 64 kb/s single link PPP operation ML-PPP (128K): this allows for 128 kb/s PPP operation, and, depending on specific AT commands, bandwidth-on-demand, call bumping and use of BAP/BACP V.120 rate adaption V.110 rate adaption async to sync HDLC Back Panel The following connectors are available on the back panel of the NT-IP: 1. one RJ-45 jack with key to connects to the telephone line 2. one input connector for the power adapter. 3. two RJ-45 jacks to connect to ISDN terminals (S 0 bus) 4. one DB9 female port for connection to the serial port of a DTE 5. two RJ-11 terminal jacks and two spring terminal block for connecting analog equipment (phone, fax, modem, answering machine, etc.) 19 this mode is only used when the NT-IP is used to remote configure another NT-IP 69/97

70 LED's The following status monitoring LED's are located near the front panel: PWR U DTR DCD CTS TD RD B1 B RS-232 Connector AC power supplied Line interface connected (remote power sensed) Data Terminal Ready (C108) Line status or Carrier detect (C109) Clear to Send (C106) Transmit Data (C103) Receive Data (C104) B1 channel in use by the NT-IP B1 channel in use by the NT-IP The following connections are provided on the RS-232 DB-9 female connector. signal i/o pin C103 TXD in 3 C104 RXD out 2 C105 RTS in 7 C106 CTS out 8 C107 DSR out 6 C102 GND - 5 C109 DCD out 1 C108 DTR in 4 C125 RI out 9 The DB-9M to DB-25F adapter cable is provided with the following connections: Switches DB-9M DTE DB-25F DCE 3 C C C C C C C C C Two dip switches are located on the bottom side of the device. They are used to: select between a/b or S 0 restricted power modes select the S 0 bus configuration (short passive / extended) include terminating resistors for the S 0 bus (100 Ω / 50 Ω / off) SETTINGS Switches OFF ON SW2.1 Emergency a/b emergency S0 SW2.2 Extend. bus Short bus SW1.1 Open Rx 100Ω Rx SW1.2 Open Tx 100Ω Tx 70/97

71 11.2 Hardware Installation To install the NT-IP you also need: an ISDN basic rate access (U interface) the supplied RJ-45 to RJ-11 cable (or equivalent) to connect the NT-IP to the telephone line the supplied DB9-to-DB9 cable to connect the NT-IP to the serial port of your PC. If you are connecting the NT-IP to a computer with a different serial interface, you may also need to use the supplied D9/D25 adapter. To make installation easier, the NT-IP supports: automatic recognition of the PC speed up to kb/s during the command phase of the AT command. Plug&Play operation To connect the NT-IP to your PC: power down your computer connect the a.c. adapter to the NT-IP and verify that the PWR LED on the NT-IP is ON use the supplied DB9-DB9 cable to connect the RS-232 port of the NT-IP (4) to the serial port of your PC start your PC: you may immediately use the Hyper-Terminal program supplied with Windows 95 to exercise the NT-IP with AT-commands. Now you can connect the NT-IP to the line: use the RJ-45 to RJ-11 cable to connect the NT-IP to the wall socket of the telephone line (1) and verify that the red LED is ON: this indicates that the ISDN line is powered connect any ISDN terminal to the NT-IP using the supplied RJ-45 to RJ-45 cable (3). connect the NT-IP to the ac /dc adapter (2) and then plug the adapter. connect analog terminals (phone sets, modems, etc.) to the ports 1 and 2 of the NT-IP termination (5). Now you can proceed to install the NT-IP as a new hardware device into your PC 11.3 Installing the NT-IP as a new hardware device Based on the PC platform you are using, you need to follow a different procedure, as shown in the table below: if your computer is running: follow the procedure described in Windows Windows Windows NT Keep the diskette contained in the NT-IP package at hand during installation Installation for Windows 95 The NT-IP is a Plug-&-Play device. Just shut down and restart your PC with the NT-IP properly powered and connected to the COM port of your PC. Your PC will automatically detect the NT-IP being connected: 71/97

72 click on Next insert the INF FILE FOR WIN95/NT 4.0 diskette contained in the NT-IP package into the floppy disk drive click on Next when the next window appears, click on Finish Installation for Windows 98 The NT-IP is a Plug-&-Play device. Just shut down and restart your PC with the NT-IP properly powered and connected to the COM port of your PC. Your PC will automatically detect the NT-IP being connected: click on Next 72/97

73 click on Next Check on Floppy disk drives click on Next Insert the INF FILE FOR WIN95/NT 4.0 floppy disk supplied with the NT-IP. Click on Next (this will install the recommended driver) 73/97

74 Click on Next Click on Finish Installation for Windows NT 4.0. Windows NT 4.0 does not support the Plug-&-Play feature of the NT-IP. The NT-IP is not automatically detected when the computer is turned on. Press START in the application bar, go to SETTINGS and click on CONTROL PANEL. 74/97

75 Double click on the MODEM icon, Click on ADD Select Don t Detect My Modem click on Next 75/97

76 Select Have Disk Insert the INF FILE FOR WIN95/NT 4.0 floppy disk supplied with the NT-IP click on OK select one of the proposed drivers 20 click on Next if requested to do so by the system, select the desired COM and click on Next. 20 Appropriate drivers for Internet access are: 1) Aethra ISDN NT-IP (Multilink PPP 128K), 2) Aethra ISDN NT-IP (PPP 64K). Refer to the user manual for further details. 76/97

77 Click on Finish to complete the installation procedure 11.4 Setting up a Remote Access Connection if your computer is running: follow the procedure described in Windows Windows Windows NT Once your NT-IP has been installed in your PC, you must configure a dial-up connection. You must have the following information from your service provider: User name and Password phone number(s) one or more addresses of name servers. Alternatively your service provider may provide automatically provide this information to your PC at connect time: in this case you do not need this information. Note: the procedure assumes that your ISP uses a dynamic IP addressing scheme (which is true in most cases). If you ISP uses instead a static addressing scheme, you should be assigned an IP address and you should enter it when required Using Windows 95 select Start Accessories Remote Access double click on the Make New Connection This step is automatically skipped if no previous connections are present. 77/97

78 enter a name for the new connection (as an example, you may use the name of your ISP) select the Aethra ISDN NT-IP (PPP 64K) or the Aethra ISDN NT-IP (Multilink PPP 128K) modem in the drop-down list click on Next enter the phone number of your service provider click on Next Click on Finish 78/97

79 right click on the icon for the new connection contained in the Dial-Up Networking window and select PROPERTIES Select the SERVER TYPES tab make sure that TCP/IP is checked click on TCP/IP Settings check on Server assigned IP address, unless your ISP uses a static IP addressing scheme. In this case you must check on Specify an IP Address and enter the IP address assigned by your ISP enter the address of at least one name server (DNS) as provided by your ISP, or check on Server assigned name server address. click on OK. Now your PC is ready to connect to the Internet. 79/97

80 Double click on the new connection icon. Enter the User Name and the Password assigned by your ISP check on Save Password. After saving the password, you will not be required to enter your password in subsequent connection to your ISP. click on Connect to access the Internet Using Windows 98 Select on Start Programs Accessories Communications Remote Access Double click on the Make New Connection icon 80/97

81 enter a name for the new connection (as an example, you may use the name of your ISP) select the Aethra ISDN NT-IP (PPP 64K) or the Aethra ISDN NT-IP (Multilink PPP 128K) modem in the drop-down list click on Next Enter the phone number of your provider click on Next Click on Finish To use the new connection, select REMOTE ACCESS, 81/97

82 double click on the connection you have just created follow the same procedure as for Windows Using Windows NT 4.0 The following paragraphs describe the procedure used to make a connection in Windows NT 4. Click on Start Programs Accessories Remote Access. If no modem has been installed, the message below appears. Click on OK. enter a name for the new connection (as an example, you may use the name of your ISP) click on Next In the next window indicate that you are creating a connection to the Internet (by click on the relevant box) and click on Next. Select the modem to be used and click on Next. Enter the provider number and click on Next. Click on Finish. 82/97

83 click on More and select Modify Modem Voice and Properties. select the Server tab, check on the TCP/IP protocol click on TCP/IP Settings check on Server assigned IP address, unless your ISP uses a static IP addressing scheme. In this case you must check on Specify an IP Address and enter the IP address assigned by your ISP enter the address of at least one name server (DNS) as provided by your ISP, or check on Server assigned name server address. click on OK. To start the connection, double click on the Connection you have just created: 83/97

84 Enter the User Name and the Password assigned by your ISP check on Save Password. After saving the password, you will not be required to enter your password in subsequent connection to your ISP Appendix A: installing the Remote Access Component This clause describes how to install the Remote Access component. Remote Access is a component of the Windows Operating system. You need this component to be installed in order to support the communication functions required to establish a connection to the Internet. NOTE: It may be necessary to have the Windows 95/98/NT floppy or CD-Rom installation disk(s) Using Windows 95/98 To install the REMOTE ACCESS follow this procedure: Select Start Settings and click on Control Panel Double click on the Application Installation In the next dialogue box go to Windows 95 Installation or Windows Installation in Windows 98 Windows displays the list of the installed components: Select Communications and click on Details. check on the Remote Access component It may be necessary to insert the Windows installation disks (floppy disk or CD-Rom). Click on OK in the two next windows Using WINDOWS NT To install the REMOTE ACCESS follow this procedure: Select Start Settings and click on Control Panel Double click on the Network icon In the next window select Services window and then click on Add. In the next window select Remote Access Service (RAS) from the list, insert the Windows NT CD installation disk and click on Have Disk. If other peripheral units are installed in the PC, a window appears asking whether to add them (if so, click on OK). In the next two windows click on Continue and Close. 84/97