IP Enabling - Customer Engineer Manual1580194569

AMENDMENTS ................................................................................................
2
PREFACE ...........................................................................................................3
1. THE CONCEPT ................................................................................................4
2. THE EXTENSIONS ..........................................................................................6
3. INSTALLATION ..............................................................................................7
3.1. CONFIGURATION CONSIDERATIONS ................................................................. 7
3.1.1. Defining media access code(s) to IP gateway(s) ............................................ 7
3.1.2. Installing the signalling group(s) ...................................................................... 8
3.1.3. Installing the virtual PM(s) ............................................................................ 10
3.1.4. LAN Configuration ...................................................................................... 10
3.2. iS3000 ....................................................................................................................... 15
3.3. IN-SYSTEM GATEWAY (ISG) .................................................................................. 17
3.3.1. Projecting the ISG in the iS3000 .................................................................. 17
3.3.2. Configuration ............................................................................................... 23
3.3.3. Installation .................................................................................................... 24
3.4. iTMP DRIVER ........................................................................................................... 25
3.5. ErgoLine@Net ......................................................................................................... 27
3.5.1. Configuration ............................................................................................... 27
3.5.2. Installation .................................................................................................... 28
3.6. DHCP / TFTP SERVER ............................................................................................. 31
3.6.1. DHCP Server ............................................................................................... 31
3.6.2. TFTP Server ................................................................................................ 40
3.6.3. ErgoLine@Net operation without DHCP and TFTP server ....................... 45
3.6.4. ISG operation without DHCP and TFTP server .......................................... 47
3.6.5. Multiple TFTP servers in the VoIP Network ............................................... 49
3.6.6. How to configure multiple TFTP server access .......................................... 50
3.7. QUALITY OF SERVICE ASPECTS (QoS) ................................................................ 56
3.7.1. ErgoLine@Net QoS - OM command CHIPPD ........................................... 56
3.7.2. ISG QOS ...................................................................................................... 59
4. IP-TRUNKING USING ISG ...........................................................................61
4.1. INTRODUCTION ................................................................................................... 61
4.2. EXAMPLE OF A NETWORK CONFIGURATION ................................................. 62
4.3. OVERFLOW WITH MULTIPLE ISG BOARDS (since SIP@Net 4.0) ...................... 66
4.4. T.38 FAX SUPPORT ................................................................................................ 68
4.5. IP 21 CONNECTIVITY ............................................................................................ 71
4.5.1. IP21 without SMA functionality ................................................................... 73
4.5.2. IP21 with SMA functionality ......................................................................... 74
Table of Contents
4.6. IP400 CONNECTIVITY ........................................................................................... 76
i
4.7. IP3000 CONNECTIVITY .........................................................................................78
4.8. IPK CONNECTIVITY ...............................................................................................82
4.9. CONNECTIVITY OF PABX’S OVER H.323 ............................................................83
5. MAINTENANCE ............................................................................................ 84
5.1. GENERAL .................................................................................................................84
5.2. ErgoLine@Net .........................................................................................................84
5.2.1. Loading a different Boot Package .................................................................84
5.2.2. Upgrading of SW Application Package .........................................................84
5.2.3. Running without DHCP or TFTP Server .....................................................85
5.2.4. Installation with more than one VoIP-Vlan ...................................................85
5.2.5. Service Menu ................................................................................................86
5.3. ISG MAINTENANCE ...............................................................................................88
5.4. ISG BOOT PACKAGE UPGRADE ...........................................................................89
5.5. DEBUG TOOLS .......................................................................................................90
5.5.1. CAT Tool .....................................................................................................91
5.6. DIAGNOSTICS / TROUBLESHOOTING / FAQ .....................................................96
5.6.1. Startup Items ................................................................................................96
5.6.2. Operational Items ........................................................................................98
5.6.3. Voice Quality Items ......................................................................................98
5.6.4. Miscellaneous Items ...................................................................................100
A. EXAMPLES OF CONFIGURATION FILES .................................................102
A.1. Configuration prebisg<mac-address>.txt examples for the ISG ...........................102
A.2. Config file dhcpsrv.ini 'Uwe Ruttkamp' DHCP server ............................................104
A.3. Configuration file dhcpd.conf for the 'www.isc.org' DHCP server ........................105
A.4. Windows DHCP server ..........................................................................................106
B. PROTOCOLS AND PORT NUMBERS .......................................................108
Table of Contents
ii
iS3000 Series (SIP@Net)
IP Enabling
Release date : 01/Jan/2013
1
AMENDMENTS
The items that follow are incorporated in the update of this manual from issue 0506 to 0609:
CHAPTER/SECTION DESCRIPTION
All Troughout the manual various sections and subsection are
re-arranged and updated to the latest ISG release
fa2010v1.305.
3.4. "iTMP DRIVER" iTMP driver can handle 1024 extensions when installed on
a dedicated ISG board.
4.3. "OVERFLOW WITH Added.
MULTIPLE ISG BOARDS (since
SIP@Net 4.0)"
4.4. "T.38 FAX SUPPORT" New mechanism of T.38 Fax handling is added.
4.9. "CONNECTIVITY OF Added.
PABX’S OVER H.323"
2
PREFACE
This manual is valid for SIP@Net (previously known as Call@Net), running on all ISPBX
models of the iS3000 Series. It contains all relevant aspects related to IP enabling.
The contents of this manual is based on the following releases :
- iS3000 SIP@Net 4.0

- ISG application package FA2010V1.305
- with boot package F39A20V1.102
- ErgoLine@Net application package FEC010V1.108
- with boot package FEC030V1.603
- iTMP Driver version 1.1.4
3
1. THE CONCEPT
This manual describes how to add IP-phones to an existing, converged, iS3000 installation.
System management of IP-telephony is done via the existing tools, used for the iS3000.
The technology behind IP-enabling is the re-usage of the Terminal Message Protocol (TMP) in
order to transport control and feature information between the ErgoLine@Net IP-phone and
the iS3000. TMP is an iS3000 proprietary protocol that brings all the features to our standard
digital terminal range. This protocol is "tunnelled" over IP and made available on the
ErgoLine@Net.
ErgoLine@Net
iS3000
ISG
IP Network
CIE or DHCP server

CPU3000 TFTP server
iTMP driver
Figure 1-1 TMP configuration using the In-System Gateway (ISG).
In both configurations it is vital that the Ergoline@Net extension can reach the IP address of
the iTMP driver to establish a signalling channel and can reach the IP address of the gateway
to establish a media path (speech channel). The iTMP driver should be able to reach the CIE
or CPU3000 on one Ethernet-card and the ErgoLine@Net on the other Ethernet-card.
The ErgoLine@Net and ISG get the IP network settings via the DHCP/TFTP server.
The InnovaPhone gateway/gatekeeper IP network settings are defined via its configuration
program.
Only the ErgoLine@Net can work with dynamic IP addresses. The other mentioned
equipment requires fixed IP addresses.
The iTMP driver, DHCP server and TFTP server can be installed on the same PC, however it
is advised to use a separate PC for the iTMP driver. Reason for this is to divide the LAN
network into two parts : namely PBX-subnet and customer-subnet.
4
A combination with the BIM is only allowed, when there is always enough processor-power
available. For example do not combine, when the BIM has to handle a lot of FDCR-records.
Note that the ISG can only cooperate with :
- SIP@Net 4.0/Call@Net 3.1 (or higher)

- CIE firmware package FA0000.901 (or higher), for a iS3070/3090 system
- ErgoLine@Net package version FEC010V1.101 (or higher)
- iTMP driver 1.1.0 (or higher).
The contents of this manual is based on the following releases :
- iS3000 SIP@Net 4.0

- ISG application package FA2010V1.305
- with boot package F39A20V1.102
- ErgoLine@Net application package FEC010V1.108
- with boot package FEC030V1.603
- iTMP Driver version 1.1.4
Before installing the ISG board, keep in mind that the ISG can also be used for other
applications :
- CCIS over IP : networking between an iS3000 and 2000 IPS/SV7000. More details can be
found in the "CCIS over IP" Customer Engineer Manual.
- Mobile@Net IP DECT : interface between the iS3000 and the DECT Access Points
(DAP). More details can be found in the "Mobile@Net IP DECT (iS3000)" Customer
Engineer Manual.
- SIP Trunks and Extensions : More details can be found in the "SIP Trunks and Extensions"
Customer Engineer Manual.
5
2. THE EXTENSIONS
The ErgoLine@Net is an IP phone and (in combination with the iS3000 SIP@Net) offers all
the features of the ErgoLine D325. Additionally it offers :
- Assignment of dynamic IP addresses.

- Assignment of 802.1Q QoS-setting (VLAN-identifier).
- Assignment of 802.1p QoS-setting (User Priority).
- Assignment of DSCP QoS-setting (Differentiated Service Code Point).
- Acoustical echo cancellation.
- Codec support (G.711 and G.729).
The ErgoLine@Net includes a 10/100 Mbps repeater. This repeater makes it possible to
connect a desktop PC to the ErgoLine@Net PC port, while the ErgoLine@Net LAN port is
connected to the LAN, using the PC's former wall socket.
To ensure the ErgoLine@Net operates without problems when installed on the customers'
network take the following considerations into account :
- The wall socket must support half duplex mode.

- The ErgoLine@Net needs an Ethernet wall socket to connect it to the IP network. To
avoid rework on the existing IP network, the ErgoLine@Net includes a 10/100 Mbps
repeater. This repeater makes it possible to connect a desktop PC to the ErgoLine@Net
PC port, while the ErgoLine@Net LAN port is connected to the IP network, using the
PC's former wall socket. When The ErgoLine@Net is down (not powered), the repeater
is down as well and the PC is then disconnected from the IP network.
By using 802.1Q QoS-setting PC and ErgoLine@Net traffic can be separated. See chapter
LAN configuration for more details.
- The desktop PC's network card must support the negotiated speed between LAN switch
and the ErgoLine@Net LAN port.
How to use the ErgoLine@Net concerning user features, see the end user documentation.
6
3. INSTALLATION
3.1. CONFIGURATION CONSIDERATIONS
It is not likely that all ErgoLine@Net terminals will use the same settings. It is possible to define
the settings per sub-signalling group for each distinctive group of terminals. Per sub-signalling
group of the circuits of ErgoLine@Net terminals the following data can be determined :
- VoIP data, like codec settings and gatekeeper address.

- Media access code, determining the routing of the media connection via a gateway.
- Language.
For a specific ErgoLine@Net terminal, the (sub-)signalling group and the MAC-address are
assigned to a circuit by means of CHPCTB.
When different groups (islands of terminals) are required, then different signalling groups have
to be defined and the defaults can not be used.
Examples of islands are :
- Group of terminals with different language.

In this case the language indication in the signalling groups are different.
- Group of terminals using Innovaphone Gateway and other terminals using ISG.
In this case the signalling group data of the first group contains the IP address of the
gatekeeper, while the signalling group data of the second group contain the IP address
0.0.0.0.
- Group of terminals with less congestion chance to the ISG/Innovaphone Gateway.
In this case the media access codes in the signalling groups are different and the media
access codes are assigned to different destinations. One of the destinations has less
congestion chance.
3.1.1. Defining media access code(s) to IP gateway(s)
On behalf of the media paths for the terminals, gateways to the IP network need to be present.
To reach these gateways the iS3000 will perform number analysis on a media access code. The
media access code can lead to either :
- a trunk access code (TAC)

- an abbreviated number (ABNR)
- a network access code followed by a trunk access code (NAC+TAC)
Note that the iS3000 will analyze the media access code in tree 0.
7
Number analysis must eventually reach an (outgoing) analysis tree, in which the digits 0 ... 9
are all specified as external number, with MIN length = 1 and MAX length = 20 (OM
command ASEXTN).
3.1.2. Installing the signalling group(s)
Before you continue installation of the iS3000 you need to take the following questions into
account :
- Which gateway will the terminals use for their media paths ?
- Will all terminals be using the same gateway ?
- and the same media access code, leading to the gateway(s) ?
- Which H.323 gatekeeper will the terminals use ?
- and what is its IP address ?
- Are all terminals going to use the same gatekeeper ?
- Will all terminals be using the same language ?
- Will all terminals use the same VoIP settings ?
The answers to these questions have to be recorded in the signalling group data for the
ErgoLine@Net terminals.
If you notice that not all terminals will have the same settings, then you will need to define
signalling groups for each distinctive group of terminals. Signalling data for the ErgoLine@Net
terminals will have the signalling group number 01xx.
1. Check boundary NEBOUND 047 (number of iTMP signalling groups). NEBOUND 047
determines the number of signalling groups you can project in your system. It also
determines the highest signalling group number, so in the resulting signalling group number
01xx: xx can never be larger than (NEBOUND 047 - 1).
2. Check boundary NEBOUND 077 (average number of IP data lines per iTMP signalling
group).
NEBOUND 077 determines the average number of data lines the VoIP file in the signalling
data can contain. Refer to the ErgoLine@Net section for a relevant value for this
boundary. This boundary is an average, meaning that when it is set to 100, you can have a
group using 90 lines and a group using 110 lines. As long as the average usage is no more
than 100 lines.
3. Assign the correct media access code to the signalling group(s), for example signalling
group "0101" and media access code "75".
CHIPPD:0101,0,75;
8
4. Assign the correct gatekeeper IP address to the signalling group(s).
Note that when you use the ISG and no gatekeeper is used, then you should assign gatekeeper
0.0.0.0 to the signalling group(s).
CHIPPD:0101,2,0.0.0.0;
5. Assign a language to the signalling group(s), for example "English".

CHIPPD:0101,1,0;
6. The ErgoLine@Net terminal needs a set of VoIP data to operate correctly.

This data needs to be assigned to the signalling group(s), for example :
CHIPPD:0101,3;
Enter tag : Codecs;
Enter data: Preferred1=G729A;
Enter data: ;
An overview of the possible tags and data which can be specified is given in subsection
3.7.1. "ErgoLine@Net QoS - OM command CHIPPD".
7. Check the changed signalling group data :

DIIPPD:0101;
Response of the data entered in step 3 ... 6 is as follows :
<DIIPPD:0101;
SIGN.GROUP LANGUAGE MEDIA ACCESS CODE GATEKEEPER
0101 0 75 0.0.0.0
VoIP DATA
[Codecs]
Preferred1=G729A
<EXECUTED
See subsection 3.7.1. "ErgoLine@Net QoS - OM command CHIPPD" for the meaning of
the displayed data.
8. Activate the changed signalling group data :

ACIPPD:;
9. Download signalling group data to the terminal :

DOWNLD:2730; (in this example 2730 is the DNR)
Downloading can also be performed by :
SETOUT:13,1,1;
SETINS:13,1,1;
9
In this example circuit 1 of the (virtual) board in position 1 in the (virtual) third PM shelf is
used.
3.1.3. Installing the virtual PM(s)
Also the following questions need to be taken into account :
- Are there more than 512 ErgoLine@Net terminals ?

One virtual PM can contain up to 512 terminals, so when answering positive to the
question you need to install more than 1 virtual PM.
- Are there more than 1 signalling group for ErgoLine@Net terminals ?

If so, how will the signalling groups be distributed over the boards in the virtual PM ?
Of course, you can project all ports individually with a different signalling group number.
But since the ports reside on a virtual PM, it makes no operational difference on which
board they reside, or even on which virtual PM. So assign signalling group numbers per
board.
- Will all terminals be assigned to a fixed (virtual) place ?

Or should the terminals automatically be assigned to a (virtual) place ?
In case of automatic assignment the iS3000 will start assigning from circuit 0 on board 1 in
the first virtual PM. So the terminal will use the signalling group data that is assigned to that
position !
Now proceed with the installation steps as described in the following sections.
3.1.4. LAN Configuration
Before you continue installation of IP-enabling on the network you need to take the following
questions into account :
- Does the customer wants to use the repeater functionality of the ErgoLine@Net?
- Does the customer wants to have a separate (virtual) LAN for ErgoLine@Net terminals,
separating the Voice-over-IP (VoIP) traffic from the data traffic of the customer's PC ?
When separate VLANs are used, it is advised to set the VLAN identifier (VID) for the
ErgoLine@Net terminal too. In that case the ErgoLine@Net will not start-up when it is
connected to the wrong LAN switch (incompatible VID).
In case the answer to the first question is "no", it is not necessary to use the 802.1Q QoS-
settings on the ErgoLine@Net. The customer can separate the VoIP traffic by connecting the
ErgoLine@Net terminal and the PC to different ports of the LAN switch.
10
In most LAN switches the ports can be configured with different VIDs : see figure below.
Data VLAN
VoIP VLAN
LAN switch
Customer PC ErgoLine@Net
In case the answer to the first question is "yes" and the answer to the second question is "no",
it also is not necessary to use the 802.1Q QoS-settings on the ErgoLine@Net. In this case the
customer does not want to separate the VoIP traffic and the data traffic : see figure below.
Data VLAN Data VLAN
ErgoLine@Net LAN switch
Customer PC
In case the answers to both questions are "yes", it is necessary to use the 802.1Q QoS-setting
on the ErgoLine@Net or to use the MAC-source address based VLAN mechanism.
In the first two cases, each port of the LAN switch belongs to only one VLAN and the VoIP
traffic is separated from other IP traffic because ErgoLine@Net terminals and PCs are
physically (and logically) connected to different LANs.
In the situation that an ErgoLine@Net and a customer PC are connected to the same port of
a LAN switch and the customer wants to separate the VoIP traffic from other IP traffic, this
port should be able to handle the IP traffic of two different VLANs. The different VLANs are
(in this case) :
- VoIP VLAN for the (VoIP) traffic of the ErgoLine@Net and

- Data VLAN for the (non-VoIP) traffic of the customer's PC.
11
Data messages and VoIP
messages to be routed
via different VLANs
Data VLAN
Data VLAN
VoIP VLAN
ErgoLine@Net LAN switch
Customer PC
The reason for having two VLANs is to be able to use the advantages related to different
VLANs. Manufacturers of Ethernet switches have the following mechanisms to make it
possible :
• MAC-source address based VLAN mechanism

The MAC-address of the ErgoLine@Net has to be configured in the LAN switch. The
LAN switch will then take care that all traffic with the configured MAC-address will be
routed to the specific VoIP VLAN. This means that no special action is required in the
ErgoLine@Net terminal.
• Auxiliary VLAN-mechanism (Cisco) , by using 802.1Q QoS-setting of ErgoLine@Net.

The port of the LAN switch can be configured with :
- a Native VID (VLAN-IDs)
This is a VID that is configurable on a per port basis and used for traffic that does not
belong to the Auxiliary VLAN.
- an Auxiliary VID
This is a second VID that is also configurable on a per port basis, in addition to a Native
VID, and used for traffic belonging to the Auxiliary VLAN. The Auxiliary VLAN is used
for VoIP traffic.
The (VoIP) equipment that wants to use the auxiliary VLAN has to support 802.1Q, also
called VLAN-tagging. In principle, VLAN-tagging adds a tag, containing a VID, to the
Ethernet-frame. This tag is used by the LAN switch to distinguish between the two virtual
LANs (native/auxiliary) on the same port of the network-switch. Note that the equipment
on the native VLAN uses normal Ethernet frames, so that VoIP traffic is in fact
distinguished from other traffic by a different type of Ethernet frame (802.1Q). This means
that when the ErgoLine@Net adds the VID with the value configured for the auxiliary
VLAN, the LAN switch will send the message to the correct virtual LAN.
Note that in principle each LAN and therefore each virtual LAN, will have its own DHCP
12
server, which allocates IP addresses and provides configuration parameters (e.g. IP addresses)
to equipment in its LAN.
Example
A B
ErgoLine@Net A iS3000
A B B
ISG
ErgoLine@Net
A B B
CPU/CIE
A B B
ErgoLine@Net
A = Data VLAN
B = VoIP VLAN
DHCP/TFTP DHCP/TFTP iTMP driver
VLAN A VLAN B
Figure 3-1 Configuration using different VLANs
In the configuration above, the customer PCs (laptops) operate in VLAN A, together with
VLAN A's DHCP, TFTP and other servers.
In VLAN B, the ErgoLine@Net terminals, the gateway (e.g. ISG), the iTMP driver and VLAN
B's DHCP and TFTP servers exists.
The ErgoLine@Net terminals forward the "PC-traffic" to the port of LAN switch that, on its
turn, forwards this IP-traffic to VLAN A.
The ErgoLine@Net terminals add VLAN tags containing the VID for VLAN B to their own
Ethernet frames. The port of the LAN switch recognizes these tagged frames and forwards
them to VLAN B.
The question is how the ErgoLine@Net terminals get their information about the VIDs they
should use in their tagged frames.
The following steps realize this :
13
1. The ErgoLine@Net is powered up and the internal boot package is activated.
2. On VLAN A, the ErgoLine@Net issues a DHCP request for an IP address on the VLAN
A. This is so, because it is done with an untagged message. The reason for this is that the
VID for the Voice VLAN is not yet known at this point in time.
3. The DHCP server on VLAN A supplies an IP address and the address of the TFTP server.
4. The ErgoLine@Net issues a request to the TFTP server and asks for the file preb325.txt.
5. The file preb325.txt is sent to the ErgoLine@Net, which reads the following information :
- the package-id of the application package, e.g. fec010v1.108.
- the VID, in this example the value for VLAN B.
- the iTMP driver data : IP address and port number (normally 2600).
6. The ErgoLine@Net checks if the received package-id of the application package differs
from the currently loaded application package. If not so the package is upgraded with the
application package present on the TFTP server.
7. The application package is activated and it will further tag all the Ethernet messages, with
the VID obtained in step 5.
8. The ErgoLine@Net issues a DHCP request for an (new) IP address on VLAN B.
9. The ErgoLine@Net will apply the stored iTMP driver IP Address and iTMP driver port and
will make a connection to the iTMP driver.
10. Via the iTMP driver the other items of the QoS-settings (DSCP, User Priority) are given
to the application package.
The above means, that the ErgoLine@Net will not access the TFTP server in VLAN B. In case
a new application package has to be loaded in the ErgoLine@Net, the preb325.txt has to be
adapted and a reboot action must be forced. This can be realized by means of :
- power-down/up of the ErgoLine@Net, or

- by downloading a new application package-id by means of CHIPPD.
Note: The iTMP driver on the ErgoLine@Net side and the ISG should be directly connected via
VLAN B.
The TFTP server on VLAN B will be used by the ISG.
14
3.2. iS3000
1. Check boundaries LOBOUND083 (maximum number of PMs) and NEBOUND372

(maximum number of virtual PMs in a unit). The total number of PMs (the sum of these
two boundaries) in a unit may never exceed 31.
2. Assign a PM-shelf number 5, with shelf-type 16 virtual PM in cabinet 1 (cabinet where the
CPU3000/CCS boards reside).
ASSHLF:15,16;
When you need more than 512 PCTs, use the next virtual PM-shelf number 6.
Note that the shelf number depends on the system configuration.
In an iS3050, BOUND154 (system limited number of shelves per cabinet) must be set to 4.
In case of an iS3010 or iS3030 with LOBOUND 083 set on 2, the virtual PM-shelf number
will be 3.
When you need more than 512 PCTs, use the next virtual PM-shelf number 4.
Note: When one expects a system expansion of an iS3030 to an iS3030E (installing a second
cabinet), one must assign PM 21 and PM 22 (in the future second cabinet) on forehand,
before assigning the virtual PM in cabinet 1. Set the future PM 21 and 22 to "not installed".
When PM 21 and 22 are not assigned and the iS3030 system is expanded to an iS3030E,
the virtual PM will not work anymore.
3. Assign a PMC-board on position 17, with board-type 90 (CCS) or 91 (CPU3000), signalling

group : 0101, hw-type : 255, as-pcts : 0.
ASBRDS:15,17,90,0101,255,0;
4. Set the PMC-board in service.

SETINS:15,17;
Note that the PMC-board will not be in service yet : it goes to INS after the "iTMP" service
is up and running (after installing the iTMP driver).
5. Assign PCT-boards with board-type : 37, signalling group : 0101, hw-type : 255, as-pcts : 1.
The result is that there are empty virtual-circuits. Up to 16 boards with 32 circuits can be
assigned.
ASBRDS:15,1,37,0101,255,1;
6. Set the PCT-boards/circuits in service.

SETINS:15,1;
SETINS:15,1,0&&31;
15
7. Assign the service "iTMP" to a service client profile (CHPROF). It is advised not to use the
default profile.
CHPROF:1,4,1;
8. Assign the IP address of the PC running the iTMP driver to a profile (CHIPPR). The
communication with the iTMP driver should now be established, check with DIIPSE.
CHIPPR:"IP-ADDRESS iTMP driver PC",1;
9. One of the next procedures makes an ErgoLine@Net in TMP mode operational :
- Manual MAC assignment and no user interaction

Set NESYSOP135 to false (= 0) : disable automatic assignment of virtual circuits.
Find a free virtual-circuit on a PCT-board in the virtual shelf (DIBRDS).
Assign the MAC-address (12 hexadecimals) to a virtual circuit, with signalling group :
0101, hw-type : 255 (CHPCTB). (You can use the OM command DIMACA to display the
EHWA and related DNRs of the LCT that is related to a given MAC-address.)
Assign a DNR to the virtual-circuit, with BSPT 95 (CHDNRC).
Set the virtual circuit in service.
The circuit comes in the status ABL-fail.
Connect the ErgoLine@Net.
The circuit comes in service automatically. The ErgoLine@Net will be operational and
the user can see the DNR.
Note: If you want to remove a MAC address, specify an empty MAC address. It is not possible to
delete a virtual circuit using DEPCTB. ASPCTB is not required.
- Automatic MAC assignment and no user interaction

Set NESYSOP135 to true (= 1) : enable automatic assignment of virtual circuits.
Assign a DNR to the first free virtual circuit.
Set the virtual circuit in service (status ABL-fail).
The MAC address of the ErgoLine@Net will automatically be assigned to the first free
virtual circuit.
The circuit will come in service automatically. The ErgoLine@Net will be operational
and the user can see the DNR.
Note: The terminal will use the signalling group that is projected for the circuit it is assigned to.
If this is not correct, then assign the MAC address manually to the selected circuit using
the correct signalling group number.
In contrast with "manual MAC assignment", "automatic MAC assignment" is not journalled.
So the assignment of the MAC address to a circuit, will get lost in a cold start, unless you
16
generate a MIS file. It is advised to retrieve the projecting data after (a session of)
"automatic MAC assignment" (RTRIEV) and to create new projecting files with the
"automatic MAC assignment" results.
- Manual MAC assignment with user interaction for DNR (based on desksharing)
Find a free virtual-circuit on a PCT-board in shelf-number 5 (DIBRDS).
Assign the MAC-address (12 hexadecimals) to a virtual circuit, with signalling group :
0101, hw-type : 255 (CHPCTB).
Assign a basic DNR (CHBDNR).
Set the virtual circuit in service.
The circuit comes in the status ABL-fail.
The circuit comes in service automatically. The ErgoLine@Net is operational and the
user can see the basic DNR.
The user performs the desk-sharing action or the installation prefix action to assign the
DNR to the ErgoLine@Net.
When the ErgoLine@Net has to be replaced, then the MAC-address of the broken
ErgoLine@Net has to be removed and replaced by another MAC-address. This can be done
with CHPCTB.
Note: The gateway used for the media connection with the ErgoLine@Net is seen as a number
of trunk/tie-lines. This implies that by projecting gateways for ErgoLine@Net, the number
of trunks increases. Each gateway-B-channel is one trunk-line. The number of trunks is
limited to 600 for CPU3000 and 3000 for CCS systems.
3.3. IN-SYSTEM GATEWAY (ISG)
The In-System Gateway (ISG) is a PCT board in the iS3000 that performs the media
connection function between the iS3000 Switching Network and the ErgoLine@Net
terminals in TMP mode. For the ISG, no gatekeeper is needed : this function is performed by
the iTMP driver and iS3000 CPU. The ISG can handle speeds of 10 and 100 Mbps : it adapts
the speed autonomously.
On every ISG board the first 10 B-channels can be used without a license. For every additional
10 channels, iS3000 license 59 is required.
3.3.1. Projecting the ISG in the iS3000
1. Install an ISG in a PM shelf with a PMC with PMC package 410.10.01 / 510.10.01 /
810.01.01 or later. Allowed is a maximum of 10 ISGs per iS3000 system.
Note that the ISG can also be installed in a PM2500 shelf with the latest PPU package.
17
ASBRDS:11,5,18,5D21,255;
2. Assign the correct media access code to the signalling group(s), for example signalling
group "0101" and media access code "75".
CHIPPD:0101,0,75;
3. Assign an analysis tree related to "DIAL TYPE 11" for example tree 11.
ASTREE:11,11;
4. Assign the media access code (trunk access code to the destination ISG) in the tree related
to "DIAL TYPE 11". In this example destination '75' is used.
ASINTN:11,75,2,21,75;
5. Set the destination characteristics.

CHDSTC:75,75,00,75,,1;
Note: Set "delayed seizure" on because of "en-block sending".

A fax can not be transported, when the codec selection for a destination is not fixed to
G.711. To make fax traffic possible in case other codecs than G.711 are used, it is advisable
to add an additional ISG-destination code with codec type G.711 for fax traffic.
6. Create a QSIG route.

CRROUT:75;
7. Enter the route in the route table.

CHROTA:75;
Enter route table data :75,1,2;
Enter route table data :;
8. Set the route characteristics.

CHRTCG:75,01100100001,543543;
CHRTCI:75,10100000000,000699999,33;
CHRTCO:75,000100,0;
9. Set the bundle characteristics.

CHBNDC:75,22,0000000000010001,420;
Note that when the ISG is used for IP-trunking as well, parameter DIR-AND-NEG must
be set to 22, instead of 12.
The CON-AND-SIG-TYPE of the “ISG bundle” is always 420 : QSIG-A.
In case of IP trunking the CON-AND-SIG-TYPE of the “ISG bundle” of the opposite site is
also 420 : QSIG-A !!!.
18
The B-channel negotiation rule in parameter DIR-AND-NEG is not relevant.
For uniformity reasons it is recommended to put this on 2, meaning "preferred B-channel".
The sequence of assigning the B-channels is not relevant and has no impact on the
occurrence of collision or congestion. Recommended for uniformity reasons : assign in
natural order, so start with the lowest circuit number : see step 10.
10. Assign the bundle to the route.

ASBNDL:75,75;
11. Assign 10, 20 or 30 lines (depending on the ISG license) to the bundle.
ASLINE:75,0101,11,5,0,1;
|
ASLINE:75,0115,11,5,0,15;
ASLINE:75,0117,11,5,0,17;
|
ASLINE:75,0131,11,5,0,31;
12. Set the outgoing numbering scheme.

In the external numbering scheme the first digit of the IP address must be specified. Keep
in mind that IP addresses in the iS3000 are always represented as 4 digit blocks with
exactly 3 digits each. This means that IP address 10.12.193.55 is represented as
010.012.193.055.
By assigning digits 0, 1 and 2 in the external numbering scheme related to the media access
code, all possible IP addresses are covered.
ASEXTN:75,0,7,1,20,0;
Give [<ROUTE-TABLE>]:;
ASEXTN:75,1,7,1,20,0;
ASEXTN:75,2,7,1,20,0;
13. Make sure that on the TFTP server a prebisg.txt (or prebisg<mac-address>.txt in
case only one specific ISG should be loaded) file is present. This file contains the name of
the used ISG software package (e.g. fa2010v1.305) and configuration data like :
- Codec settings.
- QoS settings.
- Test settings (optional).
14. Make sure that on the TFTP server the software package fa2010v1.305 (or higher) is
present.
19
15. Make sure that on the TFTP server an isg_trunk.sdp file is present, in case 'IP trunking'
is required too. This is the file with the configuration data for determining the IP address
of the opposite ISG : see chapter 4. "IP-TRUNKING USING ISG".
16. Set the ISG board and circuit 0 into service : now the isg<mac-address>.sdp and
isg_trunk.sdp files are loaded.
SETINS:11,5; (11, 5 is the ISG board position given in step 1)
SETINS:11,5,0;
17. To check the settings on the ISG, start up a browser and fill in the IP address of the ISG.
To login, use "isgadmin" for both the Username and Password (case sensitive and fixed).
Keep in mind that the browser output is mainly for test/check-purpose. This means that
the layout might be enhanced in the future release of the ISG. Furthermore not all data is
valid e.g. when the data is "unknown", then it means default value.
In the 'Channel Status Overview', the second column indicates the status of the channels.
This can be :
- Free : B-channel is not used.

- Busy IO : B-channel is used for an 'Internal Outgoing' call (call from/to IP phone).
- Busy TO : B-channel is used for a 'Trunk Outgoing' call (call between ISGs).
- Busy TI : B-channel is used for a 'Trunk Incoming' call (call between ISGs).
- Busy C : B-channel is used for a 'CCIS' call.
- Busy CN : B-channel is used for a 'CCIS' call, but no RTP channel is assigned.
- Busy EI : B-channel is used for an Incoming call to an Extension connected to an
IP21.
- Busy EO : B-channel is used for an Outgoing call from an Extension connected to
an IP21.
Note that for a CCIS call it is not possible to discriminate between an incoming or outgoing
call.
20
Figure 3-2 ISG Configuration Data Overview
21
Figure 3-3 ISG Channel Status Overview
22
3.3.2. Configuration
The following files must be available in the 'TFTP server root directory' of the TFTP server
(for instance C:\TFTP\DATA) to ensure the ISG will be able to do an auto configure :
• prebisg.txt or prebisg<mac-address>.txt
A text file containing the name of the used ISG software package fa2xxxv1.yyy, for
example : fa2010v1.305.
• fa2xxxv1.yyy
The current ISG software package. This file name is also in the contents of the prebisg.txt
file.
• isg_trunk.sdp
The 'IP-Trunking' configuration file containing the number plan information of the network
and the various IP addresses of the destination ISGs (see chapter 4. "IP-TRUNKING
USING ISG"). This file is optional : it is only required for ISG-trunking.
How to obtain these files :
• The file prebisg.txt is located on the iS3000 Series Software CD-ROM. The file can also be
modified with a text editor. The text file may not contain strange control characters. Note
that the name of the software package must always be the same as its file name on the
TFTP server (case sensitive). First check the QoS capabilities of the customer network
switches before the Quality of Service settings are changed. For full usage of these settings
the customer network switches shall support Layer 2 UP (802.1Q) or Layer 3 DSCP.
• The file fa2xxxv1.yyy is located on the iS3000 Series Software CD-ROM.
• An example of the isg_trunk.sdp is also located on the iS3000 Series Software CD-ROM.
This file has to be modified with a text editor, for the correct routing to the opposite ISG.
Note: The strings in the prebisg.txt file should be terminated with a CrLf. The editor used to
modify this file should be an editor using a CrLf to terminate strings, for example the
Microsoft Notepad editor. The text file may not contain strange control characters.
The ISG is configured during start-up. The DHCP client in the ISG will send out a DHCP
request. The following network parameters are obtained via DHCP :
- Own IP address
- Own net mask
- IP address of the default gateway
23
- IP address of the TFTP server
This is done by the boot program and stored in FEPROM.
The operational ISG package polls the TFTP server when the layer 1 is taken in service
(SETINS) and stores the data in FEPROM. This operational ISG package is responsible for
retrieving the configuration files from a configuration server. The configuration server is a
TFTP server with configuration files.
When the connection with the TFTP server is lost or not available during start-up, the
persistent settings (stored in FEPROM) of previous sessions will be used : alarm code 061,
QLF 062 (IP TFTP Warning) is generated.
When in that case there are no persistent settings (ISG starts up for the first time) the ISG
operational program will continuously try to establish connection with the TFTP server.
During this time no calls are possible. alarm code 063, QLF 003 (Invalid TFTP Data) is
generated.
3.3.3. Installation
The following procedure is executed :
1. The ISG is powered up and the internal boot package is activated.
2. The ISG issues a DHCP request for an IP address on the network. If the DHCP server fails,
then go to step 7.
3. The DHCP server should supply the (fixed) IP address info together with the address of
the TFTP server, if it fails then go to step 7.
4. The ISG issues a request to the TFTP server and asks for the file prebisg.txt. When found
the file prebisg.txt is sent to the ISG, which reads the file name of the application package.
If it fails, then go to step 7.
5. The ISG checks if the received file name of the application package differs from the current
loaded application package, if so continue at the next step, else continue at step 7.
6. The ISG issues a request to the TFTP server and asks for the file of the SW application
package. The file with the compressed SW application (=operational) package is loaded.
7. The ISG checks if a compressed SW application is stored in its memory if it is the case the
ISG decompresses the SW application package and loads it into the working memory. If it
24
is not present then reboot.
8. The ISG will start the SW application (= operational) package.
9. The ISG reports a "board present" signal to the iS3000.
10. The ISG will wait for the "in service" command sent by the iS3000 via the PMC.
11. The ISG issues a request to the TFTP server and asks for the file isg_trunk.sdp.
12. The isg_trunk.sdp is sent to the ISG, which reads the information and stores in its memory.
If the TFTP server fails, the (existing) data is used.
13. From this moment on the ISG will apply the settings found in the isg_trunk.sdp.
14. The ISG is ready to make/receive calls.
3.4. iTMP DRIVER
The iTMP driver is necessary for the TMP configuration. It is possible to have the iTMP driver
software, for a limited number of extensions, running on the ISG. The amount of extensions
that can be handled by an iTMP driver on the ISG is limited to :
- 50 extensions for a call rate of 1 call/sec.

- 100 extensions for a call rate of 0,5 call/sec.
- >100 ... max.1024 extensions in case the ISG is only applied as iTMP driver.
To enable the iTMP driver, put the following information in the configuration file
(prebisg<mac-address>.txt) :
- [PabxIp]
Ip=192.168.116.200
Port=2600
MaxNrOfExt=50
The IP address and port number that is given above represent the PABX to which the iTMP
driver has to communicate. The last parameter represents the maximum number of
extensions that are allowed to register with the iTMP driver. Notice that there can only be
one iTMP driver present on a system so for this reason it's better to apply prebisg<mac-
address>.txt instead of prebisg.txt.
25
Be aware to specify the IP address of the ISG in a “Client Service Profile” for the iTMP driver
using OM command CHIPPR.
Configuration limitations in the iS3000 environment :
- An iS3000 unit can handle only one iTMP driver;

- An iTMP driver can handle only one iS3000 unit.
Information related to the iTMP driver has been added in the web browser, see Figure 3-4
"iTMP driver settings" , second table part "iTMP driver settings". In case this information is not
(properly) present in the configuration file this information is not displayed.
Figure 3-4 iTMP driver settings
Optional, the iTMP driver can run on a dedicated Windows/PC platform (only one iTMP driver
can be installed).The iTMP driver files are released on the iS3000 Series Software CD-ROM.
Installing the iTMP driver is very straightforward. Follow the instructions of the iTMP driver's
readme file that was delivered with it. Start the installation procedure by double clicking on
the executable iTMP driver file and follow the instructions on the screen. Do not change the
default port number 2600 (only in exceptional cases).
26
Note that the PC of the iTMP driver must have a fixed IP address. It is vital that the
Ergoline@Net extension can reach the IP address of the iTMP driver to establish a signalling
channel and can reach the IP address of the gateway to establish a media path (speech
channel). The iTMP driver should be able to reach the CIE or CPU3000.
To check if the iTMP driver can connect to the CIE or CPU3000, run the "ping" command on
the PC, using the IP address of the CIE or CPU3000.
Note: The PC running the iTMP driver should not use any Power Options for energy reduction. For
example never turn off the hard disks, never go over to system standby mode.
3.5. ErgoLine@Net
3.5.1. Configuration
The related files on the TFTP server and the information present in the related signalling group
determine the configuration of the ErgoLine@Net terminals.
The following files must be available in the 'TFTP server root directory' of the TFTP server
(for instance C:\TFTP\DATA) to ensure the ErgoLine@Net terminals will be able to do an
auto configure :
• preb325.txt
A text file containing configuration data for the ErgoLine@Net (or the preb<mac-
address>.txt, in case the data is only valid for one specific terminal).
An example of the file preb325.txt is located on the iS3000 Series Software CD-ROM. The
file must be modified with a text editor. The text file may not contain strange control
characters.
• fecxxxv1.yyy
The current ErgoLine@Net software package. This file name should be present in the
contents of the preb325.txt file. For example : fec010v1.108.
The file fecxxxv1.xxx is located on the iS3000 Series Software CD-ROM.
The preb325.txt file contains the items listed in the first column (the Italic items are added for
explanation purpose only) :
27
fec010v1.108 Application file name
[iTMPDriver] iTMP driver tag
Ip=0.0.0.0 iTMP driver IP address
Port=2600 iTMP driver port number
[Vlan] (optional) Vlan tag
ID=0 The 802.1Q VLAN identifier
UP=0 The 802.1p User Priority
Note: The lines (inclusive the last line) in the preb325.txt file should be terminated with a CrLf.
The editor used to modify these files should be an editor using a CrLf to terminate strings,
for example the Microsoft Notepad editor. The text file may not contain strange control
characters.
The first main item is the application file name. The file name must be exactly the same as the
file name on the TFTP server (case sensitive).
The second main item is the IP address and port number (normally 2600) for the iTMP driver.
Take special care for the iTMP driver IP address and port number. A failure in the iTMP data
may cause a failing ErgoLine@Net which can only be solved by interrupting its power supply
cord.
The last main item, which is optional, is the VLAN. Optional means that the complete string
([Vlan], ID=x, UP=x) is not present in the file. It is not allowed to have only a part of the data
e.g. only UP.
The ID (VLAN identifier) has a value between 0 and 4094. The value 0 is the default value.
The User Priority (UP) in the string has value between 0 and 7. The value 0 is default. In case
another value for the User Priority is required, then it should be changed by means of signalling
group data (CHIPPD).
It is advised to apply 802.1Q QoS-settings in the network, when the LAN switches are
configured for it. In this way an extra check on the IP connection can be realized.
3.5.2. Installation
When the described preparations have been executed properly, the actual installation of the
ErgoLine@Net phones is an easy job. In fact, the ErgoLine@Net phones install themselves
until they are operational.
• Make sure the DHCP server, the TFTP server, the iTMP Driver, the gateway(s) and the
28
gatekeeper (if required) are operational and active on the network, to which the
ErgoLine@Net phones are connected.
• Connect the ErgoLine@Net phones to the network with an Ethernet cable.
• Connect the power supply of the ErgoLine@Net phones.
The following automatic procedure is executed :
1. The ErgoLine@Net is powered up and the internal boot package is activated. The
maximum lease time request for the DHCP server is 1 hour for the boot.
2. The ErgoLine@Net issues a DHCP request for an IP address on the network. The
maximum lease time request for the DHCP server is 4 hours. It is assumed that loading
the application package is started within this time.
3. The DHCP server supplies an IP address together with the address of the TFTP server,
the IP netmask and the IP address of the default gateway. If the DHCP server fails then go
to step 9.
4. The ErgoLine@Net issues a request to the TFTP server and asks for the file preb<mac-
address>.txt.
- If the preb<mac-address>.txt is present, then this file will be used by the
ErgoLine@Net as preb325.txt
- If the preb<mac-address>.txt is absent, then the file preb325.txt is asked.
If the TFTP server fails then go to step 9.
5. The file preb325.txt (or preb<mac-address>.txt) is sent to the ErgoLine@Net, which

reads :
- the file name of the application package,
- the iTMP driver IP address and iTMP driver port number data, and
- the optional VLAN data of VID (Vlan-IDentifier) and UP (User Priority).
If TFTP file transfer fails, go to step 9.
6. Store the iTMP driver IP address and iTMP driver port number data and the optional
VLAN data in non-volatile (FLASH) memory. The ErgoLine@Net checks if the received
the file name of the application package differs from the current loaded application
package, if so continue at step 7 else continue at step 9.
7. The ErgoLine@Net issues a request to the TFTP server and asks for the file of the SW
application package.
8. The SW application package is sent to the ErgoLine@Net, which stores it in non-volatile
29
(FLASH) memory. If this fails then go to step 1.
9. The ErgoLine@Net decompresses the stored package, loads it into working memory and
starts the application. If no (valid) package exists, reboot (start at step 1).
10. The application package is activated and it will further tag all the Ethernet messages, with
the VID obtained in step 5. If no VID was given in step 5, then no tag will added.
11. The ErgoLine@Net issues a DHCP request for an (new) IP address. The DHCP server
supplies an IP address together with the IP netmask and the IP address of the default
gateway. The IP address of the TFTP server (if present) will also be given by the DHCP
server. If the DHCP server fails then go to step 1.
12. The ErgoLine@Net will apply the stored iTMP driver IP Address and iTMP driver port and
will make a connection to the iTMP driver.
13. The ErgoLine@Net sends its MAC address to the iS3000.
14. The iS3000 sends the H323-DNR and the IP address of the gatekeeper to the
ErgoLine@Net.
15. The ErgoLine@Net registers itself at the gatekeeper (if applicable). In case of the ISG then
no gatekeeper registration.
16. The gatekeeper confirms the registration (if applicable).
17. The ErgoLine@Net sends this confirmation to the iS3000.
18. The iS3000 checks if the related virtual circuit has the status INS, when this is true, the
iS3000 continues terminal activation and sends iS3000 information like QoS-settings, date
and time, LED statuses, own DNR, etc.
19. The ErgoLine@Net is ready to make/receive calls when the text "Non operational" is no
longer displayed. The text "Non operational" will stay on the display when the virtual
circuit is not INS. There are four different meanings of the text "Non operational" :
Non operational : terminal is taken out of service.

Non operational (1) : terminal cannot establish connection with iTMP driver.
Non operational (2) : terminal cannot register at the gatekeeper.
Non operational (3) : terminal has detected that the Ethernet is disconnected.
30
3.6. DHCP / TFTP SERVER
3.6.1. DHCP Server
The DHCP server can be installed on the same or on another PC, which runs the TFTP server.
Recommended DHCP servers, which can be used :
- Microsoft DHCP server (W2000).

It can be found on Microsoft's W2000 (server) CD-ROM package.
Note that this is no freeware !
- The Weird Solutions DHCP server (version 1.5).

A copy can be obtained from http://www.weird-solutions.com/download.
Note that this is no freeware !
- The ISC DHCP server version 3.0 (or higher).

A copy can be obtained from http://www.isc.org.
Note that this is freeware !
- HeHa's DHCP / BOOTP server version 2.0.

A copy can be obtained from http://www.heha.cjb.net.
Note that this is a shareware product !
- DHCP server, which can be found http://tftpd32.jounin.net.

Note that this is a freeware product !
- Any other DHCP server may work as well but this has not been verified.
The DHCP Server that comes with "MS Windows 2000/2003 Server" is recommended,
however, other types of DHCP servers (freeware, shareware, or licensed) can be used.
The DHCP Server must provide the following data :
- IP Address
- Subnet Mask
- Default Gateway IP address
- Next Boot Server IP address: this is the IP address of the TFTP Server (DHCP option 066).
- Configuration file name preb325.txt available via the TFTP server (DHCP option 067).
Setting up a DHCP Server requires some knowledge about DHCP and differs per type of
server. Therefore this is not described here. Consult the documentation that comes with the
31
DHCP server that you are using.
Setting up DHCP Server under Windows 2000/2003 Server
The DHCP server can be installed on the same server or on another PC, which runs the TFTP
server. The Microsoft DHCP server (Windows 2000/2003) can be found on Microsoft
Windows 2000/2003 Server CD-ROM package. Note that this is no freeware!
The following procedures give an example of setting up the DHCP Server under Windows
2003 Server. This procedure is also applicable for Windows 2000 DHCP server, but there are
some minor differences.
PROCEDURE: Installing the DHCP Server under Windows 2003 Server
Actions
1. From the Start (via Settings in Windows 2000) menu, open the Control Panel in
Windows.
2. Open Add/Remove Programs.
3. Click on Add/Remove Windows Components.
4. Select "Networking Services" and click Details.
5. In the Components window, check the check box Dynamic Host Configuration
Protocol (DHCP). See following screen capture.
32
6. Click OK and Next.
7. Insert the Windows 2003 CD-ROM when the system asks for it.
8. Finish the procedure via the instructions on the screen.
9. Close the Add/Remove Programs window and close the Control panel window.
PROCEDURE: Setting up the Settings for IP-Enabling
Actions
1. Start the DHCP manager: Start -> Programs -> Administrative Tools -> DHCP.
The window as show in the following screen capture is displayed.
33
2. Select the active DHCP server and create a new scope: Menu-bar -> Actions -> New
Scope. The "New Scope Wizard" is started.
3. Clicking Next in the first screen of this wizard results in a screen that offers the possibility
to enter a name and description for the new scope, for instance : IP-Enabling.
4. Clicking Next in the naming screen of this wizard results in the next screen for the IP
address range.
Define a range of IP addresses for the ErgoLine@Net terminals to be used, for instance:
192.168.4.20 ... 192.168.4.60.
Define the associated subnet mask, for instance: 255.255.255.0.
34
5. Click Next. Now the screen for exclusion of an IP address range is opened.
This screen offers the possibility to define IP address ranges which must be excluded, for
example IP addresses of DHCP server, TFTP server. This is only necessary, if the IP
address(es) of equipment with a fixed IP address is within the DHCP address range. If not,
you can leave this blank.
If you have filled in something, click "Add" to save the exclusion list.
35
6. Click Next. The window "Lease Duration" is now opened.
Set the desired lease duration of the granted IP addresses to the desired value.
36
7. Click Next. The "Configure DHCP options" window is opened.
Select yes and click Next.
37
8. Enter the Router (Default Gateway) address in option 3. After entering the Router IP
address, click Add the save the entered information in the list. See the following screen
capture.
Click Next and click Next again. The Window that is displayed now, asks you for the
WINS settings: click Next again.
38
9. You are now in the "Activate Scope" window. Click Next and then Finish.
10. You see the newly created scope. Under the newly created scope, you see a sub line
"Scope Options". Right mouse click the "Scope Options" and select Configure Options.
11. Check the check box "Option 066" and enter the IP address of the TFTP server.
12. Check the option 067 for the boot file name. You must enter preb325.txt.
Click Apply to save the changes and OK to leave the screen. Now your DHCP Server is
setup correctly.
39
13. Close the DHCP window.
3.6.2. TFTP Server
There are many types of TFTP Servers available (shareware, freeware). The TFTP server is
used to supply files to iS3000 IP equipment (e.g. ErgoLine@Net, ISG) and to all other kind of
IP equipment. From experience it came clear that some TFTP servers could not handle more
than 25 ErgoLine@Net terminals simultaneously. With the Windows 2000 TFTP server no
restrictions are experienced. For this reason we recommend this server for larger installations
of ErgoLine@Net terminals and ISGs.
Recommended TFTP servers, which can be used :
- Windows 2000 TFTP server.

Note that this server is recommended for installations larger than 25 ErgoLine@Net
terminals. The number of 25 is based on experience.
40
- Cisco TFTP server.
- Solarwinds TFTP server.

A copy can be obtained from: http:// solarwinds.net/Tools/Free_tools/TFTP_Server/
index.htm.
- Linux TFTP server (versions 0.17-14) from RedHat.

A copy can be obtained from : http://www.redhat.com.
- 3Com TFTP server.

A copy can be obtained from http:// support.3com.com/software/
utilities_for_windows_32_bit.htm.
- TFTP server, which is part of HeHa's DHCP / BOOTP server version 2.0.
A copy can be obtained from http:// www.heha.cjb.net.
Note that this is shareware !
- TFTP server, which can be found http://tftpd32.jounin.net.

NEC Unified Solutions strongly recommends the Windows 2000/2003 TFTP Server.
TFTP Server for ISG
The ISG requires a TFTP server as well. You can use one TFTP Server for both types of
equipment simultaneously : the ErgoLine@Net terminals and the ISG. It requires that you put
the files for the ISG in the same directory as the files for the ErgoLine@Net terminals.
Setting up the Windows 2000/2003 TFTP Server
Setting up the Windows 2000/2003 TFTP Server, comprises three parts: Installing the Server,
Starting the Server and copying files to the right directory.
Note: TFTP Server is only available under Windows 2000/2003 Server.
PROCEDURE: Installing the TFTP Server
Actions
1. Go to Start -> (in case of Windows 2000 via Settings ->) Control Panel in Windows.
41
2. Open Add/Remove Programs.
3. Click on the Add/Remove Windows Components.
4. In the Components window, check the check box "Remote Installation Services".
5. Click Next.
6. Insert the Windows 2000/2003 CD-ROM when the system asks for it.
7. Finish the procedure via the instructions on the screen.
8. Close the "Add/Remove Programs' window and close the Control panel window.
9. When Windows asks you to restart the computer. Click Yes.
PROCEDURE: Starting the TFTP Server
Actions
1. Go to Start (in Windows 2000 via -> Settings ) -> Control Panel in Windows.
2. Open Administrative Tools
3. Open Services
4. Select Trivial FTP Deamon. See following screen capture.
42
5. Right Mouse Click the "Trivial FTP Deamon" and select Start.
6. Again, Right Mouse Click the "Trivial FTP Deamon" and select Properties.
7. Change the "Startup Type" setting to Automatic.
8. When TFTP has been successfully installed under Windows 2000, a folder named
tftpdroot has been created.
Note that under Windows 2003, this folder is not automatically created, you must create this
folder yourself in drive C : see the following screen capture.
43
REMARK
In the related iTMP driver and in the related ErgoLine@Net software the chance on
congestion on the TFTP server is minimized. The actions in the ErgoLine@Net are :
- Only the boot package (fe0000.601 or newer) of the ErgoLine@Net will access the TFTP
server.
- If due to circumstances the boot program is not able to read the preb325.txt file, the boot
program will wait a certain (random) period of time before a retry is done.
- If due to circumstances the boot program is not able to read the file, with the application
program, the boot program will wait a certain (random) period of time before a retry is
done.
To inform the user an indication is given on the display about the status of the retries, if
present.
In case no Windows 2000 TFTP server is used, the engineer who takes care for upgrading the
44
ErgoLine@Net and/or ISG, should take care that no TFTP overload situation should occur :
see chapter 5. "MAINTENANCE".
3.6.3. ErgoLine@Net operation without DHCP and TFTP server
The ErgoLine@Net terminals have the possibility to operate without DHCP and TFTP. For
DHCP the ErgoLine@Net terminal makes use of the so-called infinite lease mechanism. The
procedure is as follows :
1. Make sure that the ErgoLine@Net terminal is not assigned an IP address via one of the
DHCP servers in the network. If there are DHCP servers on the network make sure that
the ErgoLine@Net terminal is in the so-called exclusive list. This implies that the server
will not reply to DHCP requests from the terminal.
2. Make sure that a PC is available on the network that has the 'Uwe Ruttkamp' DHCP server
running. This DHCP server will assign infinite leases (or static leases as they are also called
sometimes) to clients. You need at least version 1.6.0. An example of a configuration file
for this server is given in A.2. "Config file dhcpsrv.ini 'Uwe Ruttkamp' DHCP server".
It is also allowed to use the DHCP server on http://www.isc.org/. An example of the
configuration file is given in A.3. "Configuration file dhcpd.conf for the 'www.isc.org'
DHCP server".
Also the Microsoft servers may be applied, in this case the 'unlimited' option needs to be
applied. An example of the screen layout is given in A.4. "Windows DHCP server".
3. Make sure that the PC mentioned in the previous step also has a TFTP server running that
contains the preb325.txt file and the application package for the ErgoLine@Net
terminal. Take care that the DHCP server is configured such that as "next server" the IP
address of the PC mentioned in step 2 is given. Make sure that the preb325.txt file
contains the proper control section as indicated below. Besides the application package,
the preb325.txt file contains the IP address of the iTMP driver. In case you would like to
operate without DHCP server the option to select in the [Control] section of the
preb325.txt file would be Reuse. Be aware that the tags in the preb325.txt file are case
sensitive and that the preb325.txt file should be ended with a CR/LF.
• The [Control] tag in preb325.txt

To make it possible to operate without the use of DHCP in a controlled manner the
following tag [Control] and one of the four DhcpLease possibilities have to included in
the preb325.txt file :
[Control]
DhcpLease=Reuse or,
DhcpLease=Replace or,
45
DhcpLease=Erase or,
DhcpLease=Ignore
Reuse
In case no lease is available in flash yet, a lease will be obtained and stored in flash (provided
it is an infinite lease). In case a lease is available in flash already, no DHCP access will be
done and the lease from flash is used. This is ‘the option’ for operation without DHCP
server.
Replace
Replace the DHCP lease in flash by the infinite lease that was just obtained and continue
with the obtained DHCP lease. No DHCP parameters will be stored if no infinite lease is
obtained. When there are no DHCP parameters available from flash and no DHCP is
received, the terminal will reboot.
Erase
Always erase the DHCP lease from flash, do not save the DHCP lease that was just
obtained and continue with the obtained DHCP lease. When no DHCP parameters are
obtained the terminal will reboot.
Ignore
Keep the DHCP lease that is currently in flash, but continue with the newly obtained
DHCP lease or, when no lease is obtained continue with the DHCP lease from flash.
• Example of preb325.txt file

An example of a basic configuration file for the ErgoLine@Net terminal is given below. In
case settings are not given in the file defaults will be applied, that are correct for most of
the situations.
fec010v1.108
[iTMPDriver]
Ip=192.168.116.65
Port=2600
[Control]
DhcpLease=Reuse
When the infinite DHCP settings are found in flash these settings are used when the
application package of the terminal starts up and no negotiation will take place with the
DHCP server.
When the infinite DHCP settings cannot be found in flash the application package of the
terminal will start DHCP negotiation with the DHCP server. If the received DHCP lease
is infinite the terminal will save these parameters to flash.
Reset the terminal to save the Control tag 'DhcpLease=Reuse'. The terminal will go to
'operational' or 'non-operational' depending on whether the PABX and iTMP driver are
46
installed. Now the settings are saved and the ErgoLine@Net terminal can be used in a
DHCP and TFTP-less environment.
3.6.4. ISG operation without DHCP and TFTP server
The ISG has the possibility to operate without DHCP and TFTP. For DHCP the ISG makes
use of the so-called infinite lease mechanism. There are 2 mechanisms to assign fixed IP
address. A LAN based procedure and a peer-to-peer procedure.
The LAN based procedure is as follows :
1. Make sure that the ISG is not assigned an IP address via one of the DHCP servers in the
network. If there are DHCP servers on the network make sure that the ISG is in the so-
called exclusive list. This implies that the server will not reply to DHCP requests from the
ISG.
2. Make sure that a PC is available on the network that has the 'Uwe Ruttkamp' DHCP server
running. This DHCP server will assign infinite leases (or static leases as they are also called
sometimes) to clients. You need at least version 1.6.0. An example of a configuration file
for this server is given in A.2. "Config file dhcpsrv.ini 'Uwe Ruttkamp' DHCP server".
It is also allowed to use the DHCP server on http://www.isc.org/. An example of the
configuration file is given in A.3. "Configuration file dhcpd.conf for the 'www.isc.org'
DHCP server".
Also the Microsoft servers may be applied, in this case the 'unlimited' option needs to be
applied. An example of the screen layout is given in A.4. "Windows DHCP server".
3. Make sure that the PC mentioned in the previous step also has a TFTP server running that
contains the configuration data and trunk files (if required) for the ISG. Take care that the
DHCP server is configured such that as "next server" the IP address of the PC mentioned
in step 2 is given. Make sure that the configuration file (prebisg<mac-address>.txt)
contains the proper control section as indicated below. In case you want to operate
without DHCP server the option to select in the [Control] section of the prebisg.txt file
would be Reuse.
4. Take the ISG into service. Wait about one minute, to allow the ISG to save all information
(IP related information, as well as trunk files and configuration data) in flash. The ISG will
re-use this information the next time a restart of the board is done.
5. Now remove the PC from the network.
6. Take the ISG out of service and put it into service again. Notice that some extra delay is
required to re-start the ISG.
47
REMARKS
• In case VLAN tagging is applied notice that in that case the PC that is referred to in step 3
needs to be equipped with 2 network interfaces. This interface has to be able to deal with
802.1Q-tagged Ethernet frames. The OS has to pass VLAN identifiers to the DHCP/TFTP
server.
• All settings (IP settings, configuration items and trunk table) are stored in flash. So a TFTP
server is no longer required to guarantee a proper operation of the ISG.
• To make it possible to operate without the use of DHCP in a controlled manner the
following tag [Control] and one of the four DhcpLease possibilities have to included
in the prebisg.txt configuration file :
[Control]
DhcpLease=Reuse or,
DhcpLease=Replace or,
DhcpLease=Erase or,
DhcpLease=Ignore
Reuse
In case no lease is available in flash yet, a lease will be obtained and stored in flash (provided
it is an infinite lease). In case a lease is available in flash already, no DHCP access will be
done and the lease from flash is used. This is ’the option’ for operation without DHCP
server.
Replace
Replace the DHCP lease in flash by the infinite lease that was just obtained and continue
with the obtained DHCP lease. No DHCP parameters will be stored if no infinite lease is
obtained.
Erase
Always erase the DHCP lease from flash, do not save the DHCP lease that was just
obtained and continue with the obtained DHCP lease.
Ignore
Keep the DHCP lease that is currently in flash, but continue with the newly obtained
DHCP lease or, when no lease is obtained continue with the DHCP lease from flash.
Peer-to-peer procedure
The peer-to-peer procedure can be used when you do not have a PC that is capable to handle
802.1Q-tagged Ethernet frames and you intend to make use of VLAN/Priority tagging.
The peer-to-peer procedure is as follows :
1. Take the ISG out of service (OM command SETOUT).
48
2. Connect the PC to the ISG with a UTP cross cable.
3. Make sure that the 'Uwe Ruttkamp' DHCP server is running and configure the server such
that the IP address that needs to be applied in the VLAN, so the IP address that is used by
the operational package, is assigned to the ISG.
4. Make sure that a TFTP server is also available on the PC and check that as next server also
the PC in step 1 is specified.
5. Make sure the configuration file contains a control section with re-use. Also make sure that
VLAN/Priority tagging is off. Make the trunk tables available as well.
6. Now make the ISG operational (OM command SETINS).
7. Check with the browser that an infinite lease has been assigned with the IP address that
needs to be applied.
8. Remove the PC with the cross cable from the ISG.
9. Connect the PC and the ISG to the LAN (with normal UTP cables!).
10. Make sure that the DHCP server is configured such that you assign an IP address in the
default VLAN. The boot package always accesses the default VLAN and will never apply
VLAN/Priority tagging.
11. Prepare the configuration file and set the VLAN/Priority tag to the proper value.
12. Now take the ISG out of service again (SETOUT) and put the board into service again
(SETINS).
13. After the board has become in service, the PC may be removed from the network. The
ISG is now operational on the proper VLAN.
3.6.5. Multiple TFTP servers in the VoIP Network
The ErgoLine@Net terminal offers with the possibility to load an application package by
attempting several TFTP servers to prevent an overload situation and to make the TFTP
download more redundant. In the DHCP server a list with the IP addresses of TFTP servers
can be added. When the boot application attempts to load an application package and the
49
TFTP server is overloaded or crashes, another TFTP server is selected from the list.
The procedure is as follows :
1. Assign a Vendor Class Id "PBC-ELAN" in the DHCP server. The Vendor Class Id is case
sensitive. The DHCP server should support RFC2132.
2. Assign an option class 66 to this Vendor Class. Activate this Option and add the list of IP
addresses of the available TFTP servers. The maximum number of the list is 40. IP
addresses 0.0.0.0 and FF.FF.FF.FF are invalid.
3. Copy the application package and the configuration file (preb325.txt) to all TFTP servers
in the list. Be aware that the configuration file should be the same for all TFTP servers.
Make a script to make the copying easier.
In the DHCP boot request of the boot package, the ErgoLine@Net terminal will send its
Vendor Class Id to the DHCP server together with a request for option 43 (vendor class
string). The DHCP server will send a vendor class string containing the IP addresses of the
TFTP servers. The boot package of the ErgoLine@Net terminal will choose a TFTP IP address
randomly from the list and will try to load the configuration file from that TFTP server. When
failed the next TFTP server from the list is chosen. When the configuration file is successfully
loaded, the application package will be loaded (when the required version is different with the
one in the flash) from the same TFTP server where the configuration file is loaded. If
unsuccessful the next TFTP server from the list is selected. If all available TFTP servers have
been accessed and still no valid application file or application package is loaded the boot
package will wait a random time (max. 3 minutes) when the list is accessed again. When after
3 times trying the complete TFTP server list still no valid application package is loaded, the
boot package will reboot.
REMARK
If there are valid IP parameters with infinite lease are found in flash, the application package
will reduce the dhcp retry time to default. This means that the retry time is reduced from 2
minutes to about 50 secs.
3.6.6. How to configure multiple TFTP server access
Assign Vendor Class ID
1. In this example a windows DHCP server is used.

2. Right click on the applicable DHCP server to see the action menu.
3. Select "Define Vendor classes".
50
4. Click on the "Add" button to add a vendor class ID.
5. Fill in the fields as displayed below :
51
6. The ID should be in capital letters and written exactly as displayed above.
7. Click "OK" when finished and end the open window by clicking "OK".
8. Right click again on the applicable DHCP server to see the action menu.
9. Select "Set Predefined Options".
52
10. Click on the "Add" button to add the option.
11. Fill in the name.
12. Select "IP Address" for Data type and select "Array".
13. Fill the option 66 of the vendor class ID as follows :
14. Click "OK" when finished.

15. The result is :
53
16. Click "OK" to confirm the settings.
Assign Multiple TFTP server access to the Vendor Class
1. Right click on the "Scope Options" of the applicable DHCP server.

2. Select "Configure Options".
54
55
3. Select as Vendor Class "PBC-ELAN". Option 66 is displayed now.
4. Activate option 66.
5. Fill in the IP address in the IP address field.
6. Click on the "Add" button to put it in the list.
Copying the application package and the configuration file to all TFTP servers is done as
follows :
1. Create a script that will copy the files to all the TFTP directories.
2. Restart the terminal by unplugging the power of the ErgoLine@Net terminal or by setting
the signalling group parameters (OM command CHIPPD) with the new application
package.
3. Set the terminal out and in service (OM commands SETOUT/SETINS).
4. The Printf output shows that the package is loaded from the TFTP server 0.
3.7. QUALITY OF SERVICE ASPECTS (QoS)
3.7.1. ErgoLine@Net QoS - OM command CHIPPD
With OM command CHIPPD, Quality of Service (QoS) issues, VoIP tags and data can be
entered in the signalling groups. The following tags and associated data can be defined :
• Quality of Service (QoS) on layer 2 and 3

The Quality of Service on layer 2 and 3 can be configured. By default the Quality of Service
on both layers 2 and 3 are disabled.
First check the QoS capabilities of the customer network-switches network before the
Quality of Service settings are changed. For full usage of these settings the customer
network-switches shall support Layer 2 UP (802.1Q) or Layer 3 DSCP.
The related CHIPPD commands in case of a Cisco LAN switch are :
CHIPPD:0101,3;
Enter tag : QOSGlobal;
Enter data: DSCP=0;
Enter data: UP=3;
Enter data: ;
CHIPPD:0101,3;
Enter tag : QOSVoiceData;
Enter data: DSCP=46;
Enter data: UP=5;
56
Enter data: ;
The related CHIPPD command in case of a non-Cisco LAN switch is the same as above
except the UP in "QOSVoiceData" should have the value UP=6.
Additional QOSGlobal info

It is valid for all Ethernet frames, unless "QOSVoiceData" overrules it.
- DSCP (Differentiated Services Code Point)
It is a layer-3 value and it is always 0 (for future QoS settings).
- UP (User Priority)
It is a layer-2 value between 0 and 7. The recommended value is 3.
This value is transported by the 802.1Q-Ethernet frame-tag.
In case in preb325.text the VLAN-identifier is 0 and the UP is 255, then no 802.1Q-
Ethernet frame-tag will be sent to the LAN switch.
Additional QOSVoiceData info

It is only valid for H.225 RTP (voice/media) Ethernet-frames.
It is also only valid, when QOSGlobal-tag with UP between 0 and 7 is present.
It overrules the QOSGlobal values for RTP.
It is a value between 0 and 63 for RTP. The recommended value is 46.
It is a layer-2 value between 0 and 7. The recommended value is 5, when a Cisco LAN
switch is used. For other LAN switches the recommended value is 6.
Summary
If no 802.1Q-Ethernet frame-tagging (layer-2 Quality of Service) is required, then :
- In preb325.txt the Vlan-identifier and the User Priority should both be 0 or the
complete string with [Vlan] should be absent.
- The User Priority should be 255 in both the QOSGlobal and QOSVoiceData settings.
In this case it is still possible to apply DSCP (layer-3 Quality of Service). If this is required
then in QOSVoiceData setting the DSCP should have a value between 1 and 63.
If 802.1Q-Ethernet frame-tagging (layer-2 Quality of Service) is required (and advised),
then in preb325.txt the Vlan-identifier should have a value between 1 and 4096.
• Codec info
The codec applied between ISG and InnovaPhone Gateway is determined by this setting.
It is advised to project only one codec per signalling group.
The related CHIPPD command is :
57
CHIPPD:0101,3;
Enter tag : Codecs;
Enter data: Preferred1=G711aLaw;
Enter data: ;
Additional Codec info

It is used to transport the voice/media with Ethernet frames. The default value is
G711aLaw. The parameter is :
- Preferred1=
The recommended data values are :
- G711aLaw (should be used, when enough bandwidth is available)
- G729A (should be used, when only limited bandwidth is available)
- G729AB (performs silence suppression : this means another decrease of bandwidth,
however the quality decreases also)
• Application package
When large number of terminals has to be upgraded with a new application package and
to avoid a manual power down/power up, it is advised to specify the new application
package in the IP signalling group and to execute OM commands ACIPPD and DOWNLD
(or SETOUT/SETINS). Of course the new application package and new preb325.txt file
must be present on the TFTP server. The file name in command CHIPPD must be exactly
the same as the file name on the TFTP server (case sensitive). For further details see
section 5.2. "ErgoLine@Net".
The related CHIPPD command is :
CHIPPD:0101,3;
Enter tag : ApplPack;
Enter data: Name=fec010v1.108;
Enter data: ;
• General remarks on CHIPPD

- If a tag is defined once and the data is downloaded in the terminal, the values can only
be changed by redefining the tag values.
- Removing a "tag" by using CHIPPD (by entering the tag name without data) will only
removed the tag-data from the iS3000 memory. It will not reset the tag-data in the
terminal. If one wants to use the default values again, these default values must be
entered in the VoIP-data (by using CHIPPD) or the terminal must be rebooted.
- After entering the VoIP-data by using CHIPPD the data must be downloaded to the
ErgoLine@Net. The OM commands ACIPPD and DOWNLD perform this.
58
3.7.2. ISG QOS
The Quality of Service (QoS) issues, VoIP tags, etc. for the ISG are not defined using OM
command CHIPPD (like for the ErgoLine@Net terminals), but those items are specified in the
prebisg.txt file. The following items can be obtained from that prebisg.txt file :
• Codec information
The Codec information can be divided in :
- The sequence list
This is a list of supported codecs, which are used in the H.323-codec-negotiations. It
is not really a negotiation, because always the codec of the opposite equipment should
be used. This is the projected codec in the signalling group of the ErgoLine@Net
terminal and/or the projected codec in isg_trunk.sdp of the opposite ISG-trunk.
To take care that the projected codec is used the sequence in the list should be :
G729A, G729AB, G711aLaw (G711 should always be last).
The info in the file prebisg.txt is :

[Codecs]
Preferred1=G729A
Preferred2=G729AB
Preferred3=G711aLaw
- The codec parameters

This is information for further adjusting the codec e.g. jitter-buffer settings, levels. In
this manual these settings are not further explained. The test has shown, that the
default values are OK.
• Quality of Service (QoS) Setting

The Quality of Service parameters that are configurable are :
- DSCP setting (for voice only)
- User Priority settings
First check the QoS capabilities of the customer network-switches network before the
Quality of Service settings are changed. For full usage of these settings the customer
network-switches shall support Layer 2 UP (802.1Q) or Layer 3 DSCP.
- The info in the file prebisg.txt is :

[QOSGlobal]
DSCP=0
UP=3
[QOSVoiceData]
DSCP=46
59
UP=5
Additional QOSGlobal info

It is valid for all Ethernet frames, unless "QOSVoiceData" overrules it.
It is a value between 0 and 63. It applies for all IP messages, except for H.225 RTP. The
recommended value is 26. When set to 0, UP is not relevant.
It is a layer-2 value between 0 and 7. The recommended value is 3.
In case UP is 255, then no 802.1Q-Ethernet frame-tag will be sent to the LAN switch
and the QOSVoiceData UP setting is overruled.
Additional QOSVoiceData info

It is only valid for H.225 RTP (voice/media) Ethernet-frames.
It is also only valid, when QOSGlobal-tag with UP between 0 and 7 is present.
It overrules the QOSGlobal values for RTP.
It is a value between 0 and 63 for RTP. The recommended value is 46.
It is only valid, when the DSCP of QOSVoiceData has a value between 1 and 63. It is
a layer-2 value between 0 and 7. The recommended value is 5, when a Cisco LAN
switch is used. For other LAN switches the recommended value is 6.
Summary
If no 802.1Q-Ethernet frame-tagging (layer-2 Quality of Service) is required, then :
- The User Priority should be 255 in both the QOSGlobal and QOSVoiceData settings.
In this case it is still possible to apply DSCP (layer-3 Quality of Service). If this is required
then in QOSVoiceData setting the DSCP should have a value between 1 and 63.
Some differences of QOS settings between ISG and ErgoLine@Net and ISG are :
- In case of ISG the layer-2 User Priority setting for RTP depends of the layer-3 DSCP
setting. This is not the case for ErgoLine@Net.
- In case of ISG the Vlan-identifier setting is not explained, because it is not necessary.
The ISG becomes a fixed IP address and its own port on the LAN switch.
60
4. IP-TRUNKING USING ISG
4.1. INTRODUCTION
The ISG board can be used as a full replacement of the DTX-I/DTU-PH in combination with
the Innovaphone Gateway IP3000 for IP-trunking between iS3000 systems.
"IP-trunking” using the ISG is supported between iS3000 - iS3000 systems and also between
an iS3000 and other type of IP-equipment like the Innovaphone IP21, IP400 and IP3000.
The figure below shows an example of an IP-trunking configuration.
iS3000
ISG
iS3000
ISG
IP Network
iS3000
ISG
Figure 4-1 IP-trunking using ISG
For the iS3000 there is no difference. All kinds of intelligent routing based on time of day, or
on congestion can still be applied. Together with the (IP) Private Virtual Networking Protocol
over IP a complete QSIG/iSNet network is created.
One ISG board can realise a maximum of 30 media-connections at the same time. When more
simultaneous media-connections are required, a second ISG board can be installed : the
maximum number of ISG boards per iS3000 system is 10.
The ISG board supports :
- ECMA 333 protocol with on-demand-scenario.

- DTMF transparency.
- Selection of IP number and Codec by called party number.
61
On basis of IP address configuration file on TFTP server
- QSIG Basic call and "call related facility transport".
Call independent facility transport (QSIG Virtual calls for CCBS/CCNR, Message Waiting
Indication, Do Not Disturb activation/deactivation, Follow Me (primary and destination)
activation/deactivation, DECT mobility) is not possible via the ISG. When these functions
are required, one should project iPVN (for the virtual calls) additionally to trunking via
the ISG.
- Far end tone handling.
There is a media connection before the receipt of the connect from the opposite exchange
(fast start method).
For the "IP-trunking-ISG" concept the ISG must determine the IP address of the destination by
a translation of the called-party-number to an IP address via a configuration file on the TFTP
server. This configuration file is the isg_trunk.sdp file (or isg_trunk<mac-address>.sdp in
case the information is specific per ISG).
This isg_trunk.sdp file must be stored in the folder as defined in the 'TFTP server root
directory' (for instance C:\TFTP\DATA ). The file is activated after a SETOUT/SETINS of
circuit 0 on the ISG board.
Together with the Number Plan (NP), the Type of Number (TON) and a unique part of the
called party number (the so called "ISG-destination-code") the IP address and codec type are
given for that destination.
An example of this IP address configuration file (isg_trunk.sdp) is given in the following

section. Note that a trunk table can have a maximum of 200 entries.
4.2. EXAMPLE OF A NETWORK CONFIGURATION
A network of three iS3000 systems located in three different areas (Hilversum, Hoorn and
Eindhoven) are using IP-trunking. The number plan is as follows :
- Hilversum : 035689xxxx (with PNP level 1 regional number 019)

- Hoorn : 0229283xxx (with PNP level 1 regional number 059)
- Eindhoven : 04027xxxxx (with PNP level 1 regional number 319)
62
Hoorn
022 - 9283xxx
iS3000
Hilversum
035 - 689xxxx
ISG
iS3000
ISG
IP Network
iS3000
ISG
Eindhoven
040 - 27xxxxx
Figure 4-2 Example of IP-trunking using ISG
The lines in the "IP address configuration file" (isg_trunk.sdp) on the TFTP server must have
the following format :
<NP>,<TON>,<unique part of number>,<IP address>,<codec type>,<Payload>,

<Trunk or extension behaviour>,<Fast start usage>,<H.245 tunnelling>,
<H.245 in setup message>,<Relay setup ack>,<T.38 fax protocol>
<NP> Number Plan :

0 = unknown
1 = E.164 (ISDN)
2 = Private Number Plan (PNP)
<TON> Type Of Number :

0 = unknown
1 = subscriber / local number
2 = national / level 1 regional number
3 = international / level 2 regional number
63
<unique part of for example : 003135689.
number>
<IP address> the IP address of the ISG, including decimal points.
<codec type> this can be G711aLaw, G729A or G729AB.

<Payload> this can be 20, 30 and 40 msecs for G.729 and 30 and 40 for
G.711.
<Trunk or extension 'T' for trunk and 'E' for extension behaviour.
behaviour>
<Fast start usage> 'Y' for fast start behaviour, 'N' for no fast start.
<H.245 tunnelling> 'Y' for tunnelling and 'N' for no tunnelling.
<H.245 in setup 'Y' for H.245 in setup, 'N' for no H.245 in the setup message.
message>
<Relay setup ack> In case you want to connect the IP21 and don't use SMA put this
to 'Y'. Then dial tone generation is done locally on the IP21.
In case you use SMA on the IP21 put this parameter to 'N'. Then
you will receive the dial tone from the iS3000.
<T.38 fax protocol> ‘Y' to enable T.38 fax prtocol, 'N' to disable. Default the T.38 is
disabled to prevent unwanted "switchover" scenarios at normal
voice calls.
REMARKS
The last 6 items may be omitted from the trunking table. In case for example “Trunk or
extension behaviour” is not specified, trunk behaviour is assumed. Further in that case also the
proper defaults for the remainder of the settings are selected : Fast start enabled, tunnelling
and H.245 elements allowed in the Setup message) to 'Y'.
Be aware that T.38 needs to be enabled at both ISG's.
It is possible to read out these setting by means of the web browser. An example of the screen
layout is given below.
64
Figure 4-3 Example of ISG IP Trunking Data with T.38 item enabled
Depending on the number plan used, the next lines have to be in the isg_trunk.sdp file :
Unknown Number Plan (NP = 0)

0,0,689,<IP address ISG Hilversum>,<codec type>, etc.
0,0,035689,<IP address ISG Hilversum>,<codec type>
0,0,283,<IP address ISG Hoorn>,<codec type>
0,0,27,<IP address ISG Eindhoven>,<codec type>
65
E.164 Number Plan (NP = 1)
Private Number Plan (NP = 2)

The contents of the isg_trunk.sdp file (in this example the E.164 Number Plan) can be verified
on the "ISG IP Trunking Data" page on the http webserver.
4.3. OVERFLOW WITH MULTIPLE ISG BOARDS (since SIP@Net 4.0)
In case an iS3000 is coupled via IP to one or more other iS3000 systems and congestion occurs,
currently one ISG can not reroute a call to another ISG in the same opposite iS3000 or to
another opposite iS3000. This is because each ISG has it's own IP address. Such kind of
rerouting can also not be projected in the CPU with alternative routes, defined in the route
table. So for a given dialled destination, the ISG can only address the opposite iS3000 via one
IP-address. To achieve alternative routing some sort of rerouting with an alternative IP address
is required.
Example
66
Figure 4-4 Overflow with multiple ISG boards
When extension 1000 calls extension 2000 (in destination 2), ISG 1 only maintains one
opposite ISG IP address to reach extension 2000. Suppose that this is the IP address of ISG 2
and ISG 2 is congested. In that case no rerouting is possible via ISG 3. Since SIP@Net 4.0
rerouting via ISG 3 is possible as follows.
The ISG has a routing table, which determines the "opposite" IP address for each outgoing call,
depending on the dialled number. Suppose in ISG 1 is filled in that the IP address of ISG 2 is
used for extension 2000 (destination 2). In case congestion is met, e.g. all channels at ISG 2 are
in use, ISG 1 "tells" the CPU that congestion occurred and also that it supports the new
alternative routing function. The CPU will repeat the outgoing seizure, but now with an extra
information element in the set-up message. This information element is the "reroute digit
string", which is projectable : see boundary 427 (Second Line Maintenance Manual).
Suppose that with boundary 427 is defined that the "reroute digits" should be successively
*0*, *1*, *2* .... etc, such reroute digit string is added to the set-up message as separate
element. So when in the example the call to extension 2000 fails due to congestion, the CPU
will repeat the outgoing seizure, but now with the rerouting digits, being *0*. The IP address
will now be used, that is found for *0*2000. When this again results in fail the CPU will repeat
the seizure, and in the ISG will use the IP address that is found for *1*2000. In this way up to
10 alternative destinations can be defined. The CPU with stop to try rerouting after the
rerouting-digits *9* have been used.
67
Note that the rerouting digits must be unique and may not conflict with other existing Trunk
Access Codes (TAC). So in the previous example *0* ... *9* may not be in use as an TAC.
Suppose the following is filled in in the ISG trunk file (isg_trunk.sdp.file)
0,0,2,192.168.116.206,G711aLaw first choice for destination 2 (ISG 2)

0,0,*0*2,192.168.116.215,G711aLaw second choice for destination 2 (ISG 3)
0,0,*1*2,192.168.116.218,G711aLaw third choice for destination 2 (ISG 4)
0,0,*2*2,192.168.116.225,G711aLaw fourth choice for destination 2 (ISG 5)
etc.
This means that in case of congestion (suppose the dialled number starts with 2), the CPU will
cause the ISG to retry with IP-addresses 192.168.116.215, and when still congestion is
met, retry with 192.168.116.218 and 192.168.116.225. Note that the ISG will NOT
send the rerouting digits to the destination. These digits are merely used locally in the ISG to
perform alternative routing.
4.4. T.38 FAX SUPPORT
Support of the T.38 fax protocol is implemented on the ISG in order to transfer fax messages
in case of IP trunking over/via the iS3000 network only. It only applies for analogue G3 fax
equipment, not for G3 Super and/or G4 fax equipment.
Note that the T.38 fax protocol is not supported on "CCIS over IP" connections between an iS3000
and 2000 IPS.
68
Hoorn
022 - 9283xxx
Fax iS3000
Hilversum
035 - 689xxxx
ISG
iS3000 Fax
ISG
IP Network
iS3000
ISG
Eindhoven
040 - 27xxxxx
Figure 4-5 Fax over IP-trunking
Put the “T.38 fax protocol” element in the trunk table to ‘Y'.
Below an example of the contents of the trunking table is given :
0,0,20,192.168.116.142,G711aLaw,30,T,Y,Y,Y,Y,Y
0,0,25,192.168.116.142,G711aLaw
In this example ’20’ are the first two digits of the fax numbers; ’25’ are the first two digits
of the voice parties.
It is advised to put the most unique (longest) number as first enrty in the trunk table, for
example :
0,0,2723,192.168.116.142,G711aLaw,30,T,Y,Y,Y,Y,Y
0,0,267,192.168.116.142,G711aLaw
0,0,20,192.168.116.142,G711aLaw,30,T,Y,Y,Y,Y,Y
69
0,0,2,192.168.116.142,G711aLaw
Note that default the T.38 is disabled to prevent unwanted "switchover" scenarios at normal
voice calls. The extra item can be seen via the web browser, see example below. Be aware
that T.38 needs to be enabled at both ISG's.
Figure 4-6 IP Trunking Data with T.38 item enabled
• New mechanism of T.38 Fax handling

In the ISG firmware package fa2010.401 a new mechanism of T.38 fax handling has been
introduced for IP trunking. The mechanism is not compatible with the previous
mechanism for T.38 fax handling in older ISG firmware packages. This implies that fax
exchange using T.38 between an older ISG package and this release is not possible.
In case compatibility is required (due to a changeover of multiple nodes coupled via IP

trunking) the old mechanism can be enforced by adding a configuration item in the
prebisg<mac-address>.txt file as indicated below :
70
[Fax]
FaxSwitch=0
The default setting for this parameter is : FaxSwitch=1.

Notice that this default setting needs not to be added to the configuration file.
4.5. IP 21 CONNECTIVITY
It is possible to connect the IP21 with the ISG. This makes it possible to offer extension
behaviour on the ISG. Below an example of the contents of the trunking table is given :
0,0,18,192.168.116.201,G711aLaw,30,E,Y,Y,Y,Y
Note: Be aware that the options in the ISG trunking table only apply for outgoing calls.
For the IP21 make the following settings in VoIP interfaces :
- Enable fast start, tunnelling.

- Select mode Gateway (without registration).
- Fill in as remote gateway address the IP address of the ISG.
- Select the required codec and activate the exclusive check box.
Assume the configuration given in the figure below : the IP 21 is connected to the LAN and
two analogue terminals (1800 and 1801) are conencted to the IP 21.
ErgoLine@Net
iS3000
ISG
IP Network IP 21
CIE or
CPU3000
1800 1801
analogue terminals
Figure 4-7 IP 21 Configuration
In the Analogue interfaces section of the IP 21 enter the DNR in the section TEL1 calling party
number in. If required do the same (but apply a different DNR) for TEL2. In the example, 1800
and 1801 are the DNRs for TEL1 and TEL2. The IP address in the “Remote gateway address”
71
field (192.168.116.200) represents the IP address of the ISG.
Figure 4-8 IP21 VoIP Settings
In the routing table of the IP21 the two DNRs 1800 and 1801 have to be filled in.
72
Figure 4-9 IP21 Routing Table Settings
4.5.1. IP21 without SMA functionality
Note: Change the BSPT from 95 to 98 for all extensions in the PABX due to an imperfection at
the Innovaphone side. This applies for all Innovaphone products (IP21, IP400 and IP3000).
The terminals (1800 and 1801) connected to the IP21 can be reached by dialling a Trunk
Access Code , that leads to the route of the ISG. The terminal numbers 1800 and 1801 must
be projected as external numbers. This configuration only offers basic functionality.
1. Assign the Trunk Access Code to the destination (the IP21). In this example destination
'79' is used.
ASINTN:0,79,2,21,79;
2. Set the destination characteristics.
73
CHDSTC:79,79,00,79;
3. Enter the route in the route table.

CHROTA:79;
Enter route table data :75,1,2;
Enter route table data :;
Note that route 75 is the route to the ISG .
4. Assign the “external numbering” scheme : in this example 1800 and 1801.
ASEXTN:79,18,3,1,4,0;
5. Assign the internal number range in the incoming DDI tree of the ISG, for example tree 33.
ASBLCK:33,2,2,4,10;
6. Include the number range 18xx in the isg_trunk.sdp file :

0,0,18,192.168.116.201,G711aLaw,30,E,Y,Y,Y,Y
The IP address given is the IP address of the IP21.
4.5.2. IP21 with SMA functionality
Note: For software SMA, license number 66 is required.
In the iS3000 the two terminals connected to the IP21 have to be projected as software SMA
user, using OM command CHSMAR. This offers the analogue terminals connected to the IP21
the possibility to activate a large range of dialled features. Further these settings make it
possible to have the iS3000 generate all tone information like dial tone, ring back tone, busy
tone etc. For programming the Software SMA basics, refer to the Facility Implementation
Manual - Network and Routing.
For usage with software SMA, the following extra items have to be projected :
1. Assign the Trunk Access Code to the destination (the IP21) in the analysis tree used for
media dialling, for example tree 20.
ASINTN:20,79,2,21,79;
2. Assign the SMA users : virtual SMA shelf 15 is assumed, first board position and the first
two circuits.
CHSMAR:15,1,0,791800;
CHSMAR:15,1,1,791801;
3. Assign the two DNRs of the SMA users to the virtual hardware address, for example 1535
74
and 1536.
CHDNRC:1535,15,1,0;
CHDNRC:1536,15,1,1;
4. Assign the access code for SMA in the incoming DDI tree of the ISG.
ASINTN:33,1700,1,157;
5. Define the Local Domain which is used to define the TAC that must be inserted in front
of the CLI (line 10 of the additional parameters in CHLDOM) to offer the correct DDO-
number to the caller, for example :
CHLDOM:0,0;
1. Enter Country/Level 2 Code : 31
2. Enter Area/Level 1 Code : 35
3. Enter DDI Prefix : 689
4. Enter International/Level 2 Prefix : 00
5. Enter National/Level 1 Prefix : 0
6. Enter Special Services Prefix : 1
7. Enter Trunk Access Code : 79
8. Enter Preferred TON for Called Party Number : -
9. Enter Preferred TON for Calling/Connected Party Number : 1
10. Insert Trunk Access Code for CLI/COL with TON unknown : 1
11. Route defines call back Trunk Access Code for CLI/COL : 1
6. Assign FCM 32 (keytone postdialling allowed), FCM 58 (keytone dialling), FCM 60

(enquiry by keytone digit full) and FCM 62 (keytone enquiry entitled).
ASFACM:32&58&60&62,1535&1536;
7. Fill in 1700 (SMA access prefix) in the Routing table of the IP21, as illustrated in the
following figure. As soon as the IP21 SMA user goes “off hook”, 1700 is automatically sent
by the IP21.
75
Figure 4-10 SMA access number included in the IP21 Routing table
4.6. IP400 CONNECTIVITY
It is also possible to connect the IP400 with the ISG. For further details, just refer to the IP21
connectivity.
For the IP400 put fast start and tunnelling to Yes and H.245 setup in message to No
and select Extension behaviour.
Connect two ETSI Basic Rate trunks at the IP400 and calls from- and towards the trunk
interface (TEL1/TEL2 connections) can be made.
For a trunk connection at the IP400, the following figure illustrates how to configure a trunk
interface.
76
Figure 4-11 IP400 Trunk Configuration
Use a DTX-I ETSI trunk and connect it to the IP400. By using the trunk access code to select
the trunk line, the trunk line will be seized. Dialling an extension number situated in your own
PABX after that should be sufficient. The IP4000 Trunk Configuration figure shows a trunk
configuration. Furthermore only an extra line in the trunk table must be added that tells the
ISG that a specific outgoing trunk call must be directed towards the IP400. This entry must
also be projected as Extension since an ISG sees the IP400 always as an extension interface.
Making a call from the ETSI trunk, just dial the right trunk access code belonging to the trunk
and dial an arbitrary extension DNR in your own PABX. The other way around, dial the Trunk
77
Access Code that leads to the ISG followed by the number used in the trunk table plus the
extension DNR in your own PBX.
Note: Change the BSPT from 95 to 98 for all extensions in the PABX due to an imperfection at
the Innovaphone side. This applies for all Innovaphone products (IP21, IP400 and IP3000).
4.7. IP3000 CONNECTIVITY
It is also possible to connect the IP3000 with the ISG. For further details, just refer to the IP21-
and IP400 connectivity.
For the IP3000 put fast start and tunnelling to Yes and H.245 setup in message to
No and select Extension behaviour.
For the IP3000, the following connections can be made:
- Connect the primary rate interface of the DTU-PH to the PRI 1 connection. This offers
30 B-channels. The DTU-PH must be projected as network side connected to PRI 1.
- Connect the primary rate interface of the DTU-PH to the PRI 2 connection. This offers 30
B-channels. The DTU-PH must be projected as user side connected to PRI 2.
- Connect the Basic Rate trunk of the DTX-I to the S/T connection. This offers two basic
rate trunk lines.
The used signalling groups at the DTU-PH side are :
- 5D00 ETSI network side.

- 5D08 ETSI Netherlands user side.
The network side is used as default. Be aware to use a cross cable using the DTU-PH as user
side interface.
For the IP3000 trunk connections, the following figures illustrate how to configure the
different trunk interfaces.
78
Figure 4-12 IP3000 PRI 1 Configuration
79
Figure 4-13 IP3000 PRI 2 Configuration
80
Figure 4-14 ST Configuration
81
Figure 4-15 Gateway Configuration
4.8. IPK CONNECTIVITY
It is also possible to connect an IPK system with an iS3000 via the ISG.
The IPK system supports fast start as extra option.
For the IPK put fast start to Yes and H.245 setup in message and tunnelling to No
and select Extension behaviour.
For IPK details and projecting, refer to the appropriate IPK documentation. If the IPK is
82
projected in the right manner, dialling the Media Access Code followed by the number
corresponding in the trunking table allows calls towards the IPK.
The entry in the trunking table towards the IPK can be chosen as part of the extension range
in the IPK. For example when the number range in the IPK system is from 1000 ... 1999, a "1"
as unique number part is sufficient.
The other way around, dial a prefix from the IPK (Trunk Access Code) followed by a number
that is situated in the iS3000 where the ISG is located.
4.9. CONNECTIVITY OF PABX’S OVER H.323
To allow connectivity with a wide range of PABXs over H.323, an additional option is
introduced in the trunking table in ISG release fa2010v1.501. A connection type can now be
'T' (trunk) or 'E' (extension). Another flavor has been added 'S' that has the same behavior as
the 'E' possibility with the following exceptions :
- The H.323 SETUP that is generated by the iS3000 will be adjusted as follows:
- The bearer capability element is taken out and replaced by an H.221 H.242 bearer
capability.
- The sending complete element is removed.
- All codeset 4 and 5 elements are removed.
- The progress element is removed.
- For the received H.323 SETUP the following changes are made by the ISG:
- Ignore the received bearer capability and inject a 64 Kbps A-Law bearer capability.
- Inject a related progress element (which is required by the iS3000).
- In case the calling party number element indicates a private numbering plan, it is
change into ISDN numbering plan (added in ISG release fa2010v1.603).
- In the H.323 Call proceeding, Alert and Connect :
- The codeset 4 and 5 elements are taken out.
- The facility and progress elements are taken out (added in ISG release
fa2010v1.603).
An example how to program this option is given below :
0,0,2,192.168.116.206,G711aLaw,30,S
83
5. MAINTENANCE
5.1. GENERAL
For testing and perhaps future functions it is possible to tread one or more iS3000 items in a
special way. This is possible by means of dedicated files, containing the MAC address in the file
name. The MAC-address is persistent data and is not changeable by the application. Because
each ErgoLine@Net and each ISG has its own MAC address and thus it is possible to give each
apparatus its own file or group of files. In this way selectable ErgoLine@Net terminals and
ISGs can get specific data. This mechanism is present for all files.
Example
If the MAC address of the ISG is 08:00:3e:76:a0:17 then the special prebisg.txt file for this
board will have the name isg08003e76a017.sdp. Every time the ErgoLine@Net or ISG reads
a file of the TFTP server, it will first check for the file with the MAC address in the name. If it
is not found the general file will be used.
For the ErgoLine@Net it is valid for the preb325.txt and preb<mac-address>.txt file. Note
that 325 is replaced by <mac-address>. This is not the case for the ISG files.
For the ISG the following is valid :
- prebisg.txt and prebisg<mac-address>.txt.

- isg_trunk.sdp and isg_trunk<mac-address>.sdp.
5.2. ErgoLine@Net
5.2.1. Loading a different Boot Package
Replacement of a boot package is normally not necessary.
In the rare circumstances that a boot package upgrade is required, a Service Information will
be send including the location of the Boot Upgrade Application.
5.2.2. Upgrading of SW Application Package
- Copy the new application package to the TFTP server's working directory.
- Edit the existing preb325.txt file (or preb<mac-address>.txt, in case one specific
terminal has to be upgraded) with the new file name of the application package. The file
name must be exactly the same as the file name on the TFTP server (case sensitive) !!!
- Copy the updated file to the TFTP server's working directory.
- Force a reboot action of the ErgoLine@Net terminals.
84
This can be realized by means of :
- Power-down/up.
- By downloading a new file name of the application package by means of "[ApplPack]
Name=fec010v1.108" with OM commands CHIPPD, followed by ACIPPD and
DOWNLD. Putting the concerning circuits out of service for at least 4 seconds.
When the ErgoLine@Net is out of service for 4 seconds, then it will compare the file name
mentioned by [ApplPack] with the current application package name. If the ErgoLine@Net
notices a different application package, it will reboot.
With OM command DIEQID the software version of the application package and boot-
package can be checked.
Take care that after upgrading the file names in preb325.txt (or preb<mac-address>.txt) and
the file name mentioned in [ApplPack] of the related signalling group are the same. Is this is
not the case, then the ErgoLine@Net will reboot every time when it is out of service for 4
seconds and will load the package mentioned in preb325.txt.
Also take care that the TFTP server will not be overloaded. Putting only a limited number of
circuits out of service can do this.
5.2.3. Running without DHCP or TFTP Server
An ErgoLine@Net boot package stores its configuration (iTMP driver and Vlan) data and the
application package in its memory. When the DHCP or TFTP server goes down and the
ErgoLine@Net reboots, then it start the application package with the latest stored data.
The application package needs its DHCP server to become operational. When the DHCP
server temporary goes down, the ErgoLine@Net will stay operational as long as the DHCP
lease is valid. An adequate long DHCP lease period is required to cope with long DHCP down
periods.
5.2.4. Installation with more than one VoIP-Vlan
When the customer wants to install more than one VoIP-Vlan, then the realization depends on
the equipment. For the ISGs and InnovaPhone GWs this can be arranged in one of the
following ways :
- The ISGs (GWs) can be divided over the two or more VoIP-Vlans and by means of
signalling group data (media access code) the ErgoLine@Net terminals can give the right
relation to the ISG (GW).
- All ISGs (GWs) can be placed in one VoIP-Vlan and by means of Vlan routing the media is
85
handled.
In case of the "MAC-source address based VLAN mechanism", the MAC-address of the
ErgoLine@Net has to be configured in the LAN switch. The LAN switch will then take care
that all traffic with the configured MAC-address will be routed to the specific VoIP-Vlan. In
case of more than one VoIP-Vlan, then this information has to be configured in the equipment.
In case of the "Auxiliary VLAN-mechanism", the projecting of more than one VoIP-Vlan can be
arranged in the following way :
1. Configure in the DHCP server the MAC-addresses of the ErgoLine@Net terminals and
route the terminal of different VoIP-Vlans to different TFTP servers.
2. Place on the TFTP server the preb325.txt files, which are specific per terminal and which
contain the correct VLAN-identifier-value of the related VoIP-Vlan. The specific
preb325.txt files are preb<mac-address>.txt.
5.2.5. Service Menu
A read only menu can be accessed on the ErgoLine@Net using the Service mode (password
12687).
For a general explanation of the items in the Service Menu, see the ErgoLine D325/D330
Customer Engineer Manual. The following maintenance codes (accessible via option 'Do
Maintenance') are specific for the ErgoLine@Net :
86
CODE FUNCTION
11 Display test
12 Keyboard test
13 LED test 1
14 LED test 2
31 Erase the dynamic data (EEPROM) of a terminal
75 Own MAC (Hardware) Address
76 Own IP Address
77 Own IP Net Mask
78 Gateway IP Address
79 TFTP server IP Address
80 GateKeeper IP Address
81 GateKeeper Port Number
82 iTMP Driver IP Address
83 iTMP Driver Port Number
88 Application Package ID
89 Application Package 12NC
90 Boot Package ID
91 Boot Package 12NC
92 Own DNR
95 Hardware ID (Version)
96 Hardware 12NC
97 SB Number
98 Manufacture Date
101 Codec Preference number 1
120 QoS Global DSCP value
121 QoS Global UP value
122 Vlan identifier (read from preb325.txt)
87
CODE FUNCTION
123 DSCP value used in RTP Ethernet frames
124 UP value used in RTP Ethernet frames
125 DSCP value used in non RTP Ethernet frames
126 UP value used in non RTP Ethernet frames
Codes 130 ... 147 : Audio-settings microphone related.
Codes 150 ... 165 : Audio-setting speaker related.
Table 5-1 ErgoLine@Net D325 Maintenance Codes.
5.3. ISG MAINTENANCE
The IP-protocol used by ISG is according the H.323-standard. This means that the present
tools (e.g. Ethereal) can be used for tracing.
At the front of the ISG board LED indicators are present, indicating the status of the board.
Via the on-board web-server diagnostic data is available.
MEANING LEDS
GREEN RED
No system power or defect on-board power Off Off
PMC not operational or no operational Off On
package or Internal test active
Operational package running and waiting for On On
commands from PMC
Communication with PMC On Off
Software downloading via IP-connector Off Winking
Table 5-2 In-System Gateway (ISG)
Upgrading of SW application package
- Copy the new application package (which is available on the iS3000 Series Software CD
ROM) to the TFTP server's working directory.
- Copy (and rename if applicable to the prebisg.txt file) the example file prebisg.txt, which
is also present on the iS3000 Series Software CD ROM.
- Force a reboot action of the ISG.
88
This can be realized by means of :
- power-down/up of the ISG or,

- putting circuit 0 or the whole board out of service.
Then the application package will read the prebisg.txt file on the TFTP server for the file
name. This file name will be compared with the file name of the current application
package. If the ISG notices a different application package, then it will reboot.
With OM command DIEQID the software version of the application package and boot-
package can be checked.
Take care that the TFTP server will not be overloaded. Putting only the ISG out of service
when no other main actions are running on the TFTP server e.g. simultaneously upgrading of
ErgoLine@Net terminals.
5.4. ISG BOOT PACKAGE UPGRADE
Because of new functionality in the future it might be necessary to upgrade the boot package
of the ISG and to load a new application package. Before installing the new application package
first install a new boot package. This is mandatory, so do not install a new application program
without updating the boot program first, unless the latest boot program has already been
installed. Downloading a new boot package has as result that the current application package
will be lost.
WARNING: BOOT PACKAGE UPGRADING IS A CRITICAL PROCESS, NEVER

PULL THE ISG BOARD WHEN THE UPGRADE PROCESS OF THE
BOOT PACKAGE HAS BEEN STARTED, THIS MAY MAKE THE ISG
BOARD USELESS.
Boot package upgrade
1. Copy the new ISG boot package (if not already installed, use DIEQID) f39a20v1.102 to
the TFTP server's working directory.
2. Put the ISG boot package name in the prebisg.txt (or prebisg<mac-address>.txt file) on
the TFTP server at the first line of the file.
3. Force a reboot action (SETOUT/SETINS) of the ISG board. Notice that the boot package,
replace action will also remove the last installed application program, so this needs to be
re-installed.
4. When the RED led starts flashing, start with the upgrade of the application package.
89
Application package upgrade
1. Copy the new ISG package fa2010v1.305 to the TFTP server's working directory.
2. Change the ISG package name in the prebisg.txt (or prebisg<mac-address>.txt file) on
the TFTP server.
3. In case the ISG boot package replace action has been skipped, so the proper boot package
is already available, force a reboot action (SETOUT/SETINS) of the ISG board. In case the
boot package replace action is in progress, the application package will automatically be
activated.
Limitations Boot Upgrade Package
The boot upgrade package needs a DHCP server to operate properly. When network
switches are used which are supporting the Spanning Tree Algorithm, the forward delay timer
may not exceed the 10 seconds or set Spanning Tree to Fast. The switch port is blocked for
a certain time and no messages can be sent to the DHCP server. The boot upgrade package
does not have an IP address in this case and will reboot.
When the boot is upgraded the boot upgrade package will wait till the configuration file
(preb325.txt) is changed with an application package. The boot upgrade package does not
have an additional TFTP server list but will search at the TFTP server given by the basic DHCP
parameters (Own IP address, Gateway, Netmask, TFTP server).
5.5. DEBUG TOOLS
The following tools can be used for debugging :
- Check if the state of the extensions is "Up"
90
- Ethereal_0_9_xx.exe which is released on the CD-ROM : "SERVCD". Install WinPCap
first. This tool can be used to analyze the IP traffic. Remember to load the plug-in for the
iTMP protocol, present on the CD.
- TCPmonitor.exe which is released on the CD-ROM : "SERVCD". This tool can be used to
analyze the IP-traffic between an iS3000 and the iTMP driver. For more details, see
Second Line Maintenance Manual.
- WinPrintf or Printf for monitoring ErgoLine@Net terminals and ISG.
- CAT-tool : see following section.
5.5.1. CAT Tool
The iTMP driver requires no maintenance, but it can be necessary to monitor the driver and
change some configuration settings. This can be done using the Common Access Tool (CAT).
CAT can be found on the Service CD.
When starting CAT from the Start Menu, the following screen appears :
91
Figure 5-1 Start Menu
If there is no iTMP driver present in the left-pane, click on "Add Server" tab found at the left-
bottom to add a new server. Fill in the values as they appear in the Figure 5-2 "Add Server"
and click the "Add Server" button.
92
Figure 5-2 Add Server
The Server IP address is :
- the IP address of the PC running the iTMP driver (or ‘localhost' or '127.0.0.1' ), or
- the IP address of the ISG board, when the iTMP driver is installed on the ISG.
The 'port' is a fixed port (2601) on which the internal iTMP driver CAT-service is listening.
After adding the iTMP driver server, switch back to the 'Server' via by clicking op 'Server' tab.
Now Figure 5-1 "Start Menu" should be visible.
To initiate a connection with the iTMP driver, double-click on the "iTMP driver" entry. A login
dialog box appears : use "Demo" for both the 'User Name' and 'Password' and press OK.
Main-menu of iTMP driver CAT service
After the login procedure, Figure 5-3 "Main Menu" appears. These are the menu options
provided by iTMP driver via CAT.
93
Figure 5-3 Main Menu
Menu-item : Terminals
When selecting 'Terminals' all currently registered terminals (Ergoline@Net) are displayed.
The provided information is static, providing only information valid on the moment of the
'Terminals' request. By pressing 'Refresh' the information displayed is updated.
94
Figure 5-4 Terminals Menu
Menu-item : Debug
The 'Debug' opens the debugging facilities for iTMP driver.
It can be used to make detailed problem reports. The debug facilities are intended to Service
Engineer and LAB-users only. It is strongly advised not to use this during normal operation
since it will dramatically decrease the iTMP driver performance.
Menu-item : Config
The 'Config' displays the current configuration of iTMP driver.
During the iTMP driver installation process these IP address and port are initial filled in. It can
be used in case it is required to change the iS3000 to which the iTMP driver connects.
Menu-item : Version
Displays the iTMP driver version information.
95
5.6. DIAGNOSTICS / TROUBLESHOOTING / FAQ
5.6.1. Startup Items
PROBLEM DIAGNOSIS TROUBLESHOOTING

ISG/ErgoLine@Net DHCP scopes are not Check if the right scope has
continuously boots without properly configured. been projected.
receiving any IP address. Check if queries from the
ISG/ErgoLine@Net's MAC
addresses are received
anyway.
The DHCP server is not Ping the DHCP server to
reachable because it is check the reachability from
located on a different the ISG/ErgoLine@Net's
broadcast domain than the broadcast domain.
ISG/ErgoLine@Net.
The DHCP server is not Use the same VLAN id for
reachable because it is both the ISG/
located in a different VLAN. ErgoLine@Net's and DHCP
server.
The ISG/ErgoLine@Net is Set on Cisco switch FAST
connected to a Cisco switch spanning tree on.
with default spanning tree
algorithm enabled.
ISG/ErgoLine@Net The TFTP server is not Ping the TFTP server to
continuously boots without reachable because it is check the reachability from
loading any application located on a different the ISG/ErgoLine@Net's
package but it gets an IP broadcast domain than the broadcast domain.
address. ISG/ErgoLine@Net.
The TFTP server is not Use the same VLAN id for
reachable because it is both the ISG/
located in a different VLAN. ErgoLine@Net's and TFTP
server.
The TFTP server is not When you can not avoid
reachable because it is crossing a firewall, make
located on a network behind sure the TFTP traffic is
a firewall. properly tunneled.
The TFTP server has an Make sure the application
empty prebfile.txt. file is specified and loacted in
the TFTP root path.
96
ErgoLine@Net The iTMP driver is not Ping the iTMP driver to
continuously boots although reachable because it is check the reachability from
it has both the IP address located on a different the ErgoLine@Net's
and application package broadcast domain than the broadcast domain.
loaded. ErgoLine@Net.
The iTMP driver is not Use the same VLAN id for
reachable because it is both the ErgoLine@Net's
located in a different VLAN. and iTMP driver.
The iTMP driver is not Use the CAT tool to check
properly configured. the appropriate settings.
Not any iTMP driver Check the preb325.txt
registration attempt is done.content. Check if latest line
is terminated with a CRLF.
ISG continuously boots, ISG has communication The ethernet connector at
indicated by blinking red and problems with the local area the font of the ISG is not
green LED followed by a network. connected or has a bad
steady red LED on. connection.
The DHCP server cannot be
reached.
The TFTP server cannot be
reached.
The prebisg.txt file on the
TFTP server is not installed.
The operational package
referred to in the prebisg.txt
file is not present on the
TFTP server.
97
5.6.2. Operational Items

The ISG only accepts 10 or Licensing problems Check that the correct
20 calls at the same time. licenses are installed.
It is not possible to make IP-The isg_trunk.sdp file may Verify if the file
trunking calls with the ISG. not be present or correct. isg_trunk.sdp is present.
Verify that the <UNIQUE
PART OF NUMBER> is
available in the isg_trunk.sdp
file.
Verify that the syntax of the
isg_trunk.sdp file is as
described in section Figure
3-1 "Configuration using
different VLANs".
5.6.3. Voice Quality Items

Setup of call is successful but The signalling is routed Check the routing in the
no speech path is available. properly but not the media. gateway.
Use the trace panes to see if
the gateway can route a call
at all.
ISDN to IP and/or IP to Check that the relevant
ISDN roots in the gateway ISDN interfaces in the
may not be properly iS3000 are set into service.
configured.
Signalling and media may be Make sure you have the
treated in a different way in appropriate VLAN routing
the network because of a for both the signalling and
different VLAN. media.
Use the Ethereal tool to
check the QoS and VLAN
tagging in the VoIP packets.
98
Voice glitches during a This is mostly related to Reduce jitter and delays in
conversation. jitter/delay. Packets arriving the customer network. (I.e.
the ErgoLine@Net with better routing, VLAN and
more than xxx spacing QoS).
between each other causes Indication of jitter and delay
the ErgoLine@Net jitter can be obtained making use
buffer being emptied. No of the VoIP readiness
voice packets can be played assessment.
resulting in breaks in the
speech.
When the opposite party is a To isolate the problem,
DECT handset, this could be verify if the voice quality
a radio coverage problem degrades when the DECT
(weak signals). The problem party is connected to a 'non-
appear even when the user IP' telephone set.
is moving around different
DECT clusters.
Poor quality of the voice : Probably the used CODEC Change the CODEC to
general. does not match the G.711 (beware that more
customer expectation. Any bandwidth needed).
codec different from G.711,
introduces compression
affecting the voice quality.
Other factors like jitter, A VoIP assessment returns
delay, data loss, interference values of MOS based on
with other application simulated traffic.
traffic, are threats for your
VoIP media quality.QoS and
VLAN are not in use or not
properly configured.
Poor quality of the voice : It can be a hardware related Swap the suspected
specific. problem : especially when ErgoLine@Net set with
the voice quality is poor only another one that did not
in specific ErgoLine@Net manifest such a voice
sets. degradation.
99
During a conversation a In the gateway you are using Enable Send Comfort noise
remote party sounds as Silence compression but in the InnovaPhone
being disconnected Send Comfort Noise is not gateway.
between spoken words/ enabled.
sentences.
In the ErgoLine@Net the In the ISG (or other Move G729 CODEC to the
preferred CODEC is G729 gateway) the G711aLaw is first place in the preferred
but a call is established with preferred above the G729 CODEC list of the gateway.
CODEC G711aLaw. CODEC e.g. it is the first The ErgoLine@Net always
CODEC in the list. adds G711aLaw to the
preferred CODEC list.
5.6.4. Miscellaneous Items

PC connected to ErgoLine@Net is Check if PC adapter can
ErgoLine@Net PC port is operational. ErgoLine@Net work on 100 Mbit half
not able to establish a LAN speed is 100 Mbit (half duplex. If not (PC can only
connection. duplex). work at 10 Mbit) set the wall
adapter to 10 Mbit.
ErgoLine@Net is Change PC adapter settings
operational. ErgoLine@Net to automatic speed
LAN speed is 10 Mbit (half negotiation or to fixed 10
duplex). Mbit.
100
PC port connection ErgoLine@Net is The ErgoLine@Net
performance is bad. PC is connected to Cisco Catalist operating on 10 Mbit may
connected to 4000 series switch. add dribble bits to repeated
ErgoLine@Net and frames. It is known that a
ErgoLine@Net is particular Cisco interface
operational (and works board (WS-X4148-RJ) drops
fine). ErgoLine@Net LAN wrongly these frames. The
(and PC) speed is 10 Mbit problem can be solved by :
(half duplex). - Change speed to 100 Mbit.
-Use another interface
board e.g. WS-X4148-
RJ45V.
-Connect the PC direct to
the switch instead of via the
ErgoLine@Net repeater.
By using CHIPPD a new The new CHIPPD name is The new name is not
[ApplPack] Name is defined. different to the current downloaded to the terminal.
After OM command operational application After OM command
SETOUT the package. Check service CHIPPD the commands
ErgoLine@Net will not menu item 88. ACIPPD and DOWNLD (or
reboot. SETOUT/SETINS) should
be executed.
The terminal uses other IPPD VoIP-Data is removed Redefine the TAG with the
[QOSGlobal], by entering the Tag name default values. Download
[QOSVoiceData] or without data in the OM the net VoIP-Data by using
[Codecs] data than defined command CHIPPD. OM commands ACIPPD
in IPPD VoIP-Data (to be and DOWNLD or reboot
displayed using DIIPPD). the terminal. After a reboot
the terminal will use the
default values for not
defined VoIP-Data Tags.
IPPD VoIP-DATA is Check if data is downloaded
changed by using CHIPPD. to the terminal (e.g. by using
the service menu). If not
download the data by using
OM commands ACIPPD
and DOWNLD.
101
A. EXAMPLES OF CONFIGURATION FILES
A.1. Configuration prebisg<mac-address>.txt examples for the ISG
The file as it is given below is an example of a basic configuration file for the ISG. In case settings
are not given in the file defaults will be applied, that are correct for most of the situations.
• Example of a basic configuration file :

fa2010v1.305
• Example of a configuration file with differentiated services :

fa2010v1.305
[QOSGlobal]
DSCP=26
UP=255
VID=0
[QOSVoiceData]
DSCP=46
UP=255
[Codecs] (in case you want to change the order of codecs)
Preferred1=G711aLaw
Preferred2=G729AB
• Example of a configuration file with priority tagging :

fa2010v1.305
[QOSGlobal]
DSCP=26
UP=3
VID=0
[QOSVoiceData]
DSCP=46
UP=5
[Codecs]
Preferred1=G711aLaw
Preferred2=G729AB
• Example of a configuration file with VLAN tagging :

fa2010v1.305
[QOSGlobal]
DSCP=26
UP=3
102
VID=21
[QOSVoiceData]
DSCP=46
UP=5
[Codecs]
Preferred1=G711aLaw
Preferred2=G729AB
REMARK
Echo/Double Talk Distortion Settings (in exceptional cases)
Fine tuning between echo cancellation and protection against double talk distortion
(suppressing the volume of the opposite party when you start talking) is possible with the
’EcNlpAggr’ parameter. The value ranges from 0 to 65535. However the scale runs from
32767 (= max. echo protection) to 0 (zero) and then from 65535 to 32768 (= max. double
talk distortion). Below an indication is given how these values must be used.
32767 <----20000---10000----1--0--65535----50000---40000----> 32768

|| || ||
max. echo protection default less double talk distortion
Normally default value is 0 is used.
If maximum echo protection is required, the value used should be close to 32767. In this
case residue echo is removed maximally but there is a fair chance on double talk distortion.
If minimal double talk distortion is required, the value used should be close to 32768. In
this case residue echo is removed minimally but there is a very slight chance on double talk
distortion.
An optimum can be obtained by tuning the parameter based on the explanation above. So, if
the value of the parameter is set to 0 (zero) and you still have too much echo, you can e.g try
the value 10000 or 20000. If you have too much double talk distortion, you can e.g try the
value 50000 or 40000.
The parameters are entered in the prebisg.txt (or prebisg<mac_address>.txt) file as follows :
[G711]
EcNlpAggr=0
[G729]
EcNlpAggr=0
103
Instead of using the EcNlpAggr parameter it is also possible to use a fixed setting (which
should be equivalent to the settins in ISG package 201.01.03). The parameters to enter in the
prebisg.txt (or prebisg<mac_address>.txt) file are then :
[G711]
EcConfig=9
[G729]
EcConfig=9
Note that these EcConfig parameters overrule the EcNlpAggr parameters. Their value
is fixed to 9 (nine).
A.2. Config file dhcpsrv.ini 'Uwe Ruttkamp' DHCP server
• Example of dhcpsrv.ini file

[General]
SUBNETMASK=255.255.255.0
ROUTER_1=192.168.1.254
;ROUTER_1=161.218.28.66
;DNS_1=207.172.3.0
;DNS_2=207.172.3.9
;DNS_3=207.172.3.10
NODETYPE=8 ; Hybrid
NEXTSERVER=192.168.1.126 (IP address of the TFTP server)
[Settings]
Trace=0
;IPPOOL_1=192.168.1.40-50
; New in version 1.4
; IPBIND_0 ... IPBIND_9
; IPBIND_1=194.168.123.132
; 1 = just keep quiet on unknown clients

; 0 = decline requests from unknown clients
IgnoreUnknownClients=1
[08-00-6F-82-79-EB] (MAC address and
IPADDR=192.168.1.216 IP address for infinite leases)
AutoConfig=04/24/2004 09:20:46
104
A.3. Configuration file dhcpd.conf for the 'www.isc.org' DHCP server
• Example of dhcpd.conf file

This example is valid for DHCP-less operation of both the ISG and the ErgoLine@Net
terminals. Note that there is a class “ISG” and a class “ELAN” section. Depending on the
situation either the class “ISG”, the class “ELAN” or both sections have to be included in
this file.
# Command line activation

# dhcpd.exe -cf dhcpd.conf -lf dhcp.lease eth0
#
# dhcpd.conf
#
# Sample configuration file for ISC dhcpd
#
ddns-update-style none;
# option definitions common to all supported networks.

option domain-name "example.org";
option domain-name-servers ns1.example.org, ns2.example.org;
default-lease-time 36000;
max-lease-time 72000;
# No service will be given on this subnet, but declaring it helps the

# DHCP server to understand the network topology.
subnet 130.139.40.0 netmask 255.255.248.0 {

}
# Hosts which require special configuration options can be listed in

# host statements. If no address is specified, the address will be
# allocated dynamically (if possible), but the host-specific
# information will still come from the host declaration.
#host passacaglia {
# hardware ethernet 0:0:c0:5d:bd:95;
# filename "vmunix.passacaglia";
# server-name "toccata.fugue.com";
}
class "ISG" {
match if substring (option vendor-class-identifier,0,7)="PBC-ISG";
105
}
shared-network 192-168-1 {
subnet 192.168.1.0 netmask 255.255.255.0 {
option routers 192.168.1.254;
}
pool {
allow members of "ISG";
range 192.168.1.216 192.168.1.216;
next-server 192.168.1.251;
option vendor-class-identifier = "PBC-ISG";
default-lease-time INFINITE;
}
}
class "ELAN" {
match if substring (option vendor-class-identifier,0,7)="PBC-ELAN";
}
shared-network 192-168-1 {
subnet 192.168.1.0 netmask 255.255.255.0 {
option routers 192.168.1.254;
}
pool {
allow members of "ELAN";
range 192.168.1.100 192.168.1.215;
next-server 192.168.1.251;
option vendor-class-identifier = "PBC-ELAN";
default-lease-time INFINITE;
}
}
A.4. Windows DHCP server
Below is an example of the relevant screen section that shows how to assign an infinite lease
on a windows DHCP server. The unlimited box has to be applied to assign an infinite lease.
106
107
B. PROTOCOLS AND PORT NUMBERS
The table below lists which protocols are used by which devices and the destination port
numbers used by these protocols.
PROTOCOL INTERFACE/DEVICE LAYER 4 DEFAULT

PROTOCOL DESTINATION
PORT
DHCP DHCP Server UDP 67
TFTP TFTP Server UDP 69 (see note 1)
1024 - 65535
H.323 H.225.0 RAS not appl. not appl. not appl.
Extensions H.225.0 Call Signalling ISG / IPG TCP 1720
and Trunks
ErgoLine@Net TCP 1720
H.245 Media Control ISG / IPG TCP 1100 - 1299
Signalling ErgoLine@Net TCP 1024 - 65535
H.225.0 RTP / RTCP ISG UDP 49000 - 49199 2)
IPG UDP 49600 - 49979 2)
ErgoLine@Net UDP 49000 - 49199 2)
iTMP Aggregation CPU3000 TCP 2600
CIE TCP 2600
iTMP iTMP Server TCP 2600
CCIS Call Signalling CPU3000 / CPU4000 / CIE TCP 57000
Media Signalling (VPC) ISG / IPG UDP 4000 - 4031
RTP / RTCP ISG UDP 49200 - 49399 2)
IPG UDP 49200 - 49579 2
SIP Aggregation CPU3000 / CPU4000 / CIE TCP 2610
SIP SIP SIP@Net Server / ISG / UDP/TCP 5060
Extensions CPU4000 TLS 5061
and Trunks
RTP / RTCP ISG UDP 49200 - 49399 2)
IPG UDP 49200 - 49579 2)
Note 1 : Only the initial message is sent to port 69
Note 2 : Even numbered ports are used for RTP and odd numbered ports for RTCP.
Table B-1 Interfaces, Protocols and Port Numbers
108

IP Enabling - Customer Engineer Manual1580194569

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

IP Enabling - Customer Engineer Manual1580194569

Încărcat de

Drepturi de autor:

Formate disponibile

AMENDMENTS ................................................................................................

4.6. IP400 CONNECTIVITY ........................................................................................... 76

Release date : 01/Jan/2013

The contents of this manual is based on the following releases :

- iS3000 SIP@Net 4.0

CIE or DHCP server

Figure 1-1 TMP configuration using the In-System Gateway (ISG).

Note that the ISG can only cooperate with :

- SIP@Net 4.0/Call@Net 3.1 (or higher)

The contents of this manual is based on the following releases :

- iS3000 SIP@Net 4.0

- Assignment of dynamic IP addresses.

- The wall socket must support half duplex mode.

- VoIP data, like codec settings and gatekeeper address.

Examples of islands are :

- Group of terminals with different language.

3.1.1. Defining media access code(s) to IP gateway(s)

- a trunk access code (TAC)

3.1.2. Installing the signalling group(s)

5. Assign a language to the signalling group(s), for example "English".

6. The ErgoLine@Net terminal needs a set of VoIP data to operate correctly.

7. Check the changed signalling group data :

8. Activate the changed signalling group data :

9. Download signalling group data to the terminal :

3.1.3. Installing the virtual PM(s)

Also the following questions need to be taken into account :

- Are there more than 512 ErgoLine@Net terminals ?

- Are there more than 1 signalling group for ErgoLine@Net terminals ?

- Will all terminals be assigned to a fixed (virtual) place ?

3.1.4. LAN Configuration

Data VLAN Data VLAN

ErgoLine@Net LAN switch

- VoIP VLAN for the (VoIP) traffic of the ErgoLine@Net and

• MAC-source address based VLAN mechanism

• Auxiliary VLAN-mechanism (Cisco) , by using 802.1Q QoS-setting of ErgoLine@Net.

Figure 3-1 Configuration using different VLANs

The following steps realize this :

8. The ErgoLine@Net issues a DHCP request for an (new) IP address on VLAN B.

- power-down/up of the ErgoLine@Net, or

1. Check boundaries LOBOUND083 (maximum number of PMs) and NEBOUND372

3. Assign a PMC-board on position 17, with board-type 90 (CCS) or 91 (CPU3000), signalling

4. Set the PMC-board in service.

6. Set the PCT-boards/circuits in service.

9. One of the next procedures makes an ErgoLine@Net in TMP mode operational :

- Manual MAC assignment and no user interaction

- Automatic MAC assignment and no user interaction

3.3. IN-SYSTEM GATEWAY (ISG)

3.3.1. Projecting the ISG in the iS3000

5. Set the destination characteristics.

Note: Set "delayed seizure" on because of "en-block sending".

6. Create a QSIG route.

7. Enter the route in the route table.

8. Set the route characteristics.

9. Set the bundle characteristics.

10. Assign the bundle to the route.

12. Set the outgoing numbering scheme.

- Free : B-channel is not used.

How to obtain these files :

• The file fa2xxxv1.yyy is located on the iS3000 Series Software CD-ROM.

This is done by the boot program and stored in FEPROM.

The following procedure is executed :

1. The ISG is powered up and the internal boot package is activated.

8. The ISG will start the SW application (= operational) package.