How to install the ISS

including ISS-2 and ISS-3

including upgrade

April 2017

www.nec-enterprice.com
A Publication of
NEC Nederland B.V.
HILVERSUM, THE NETHERLANDS

Date : April 2017

Great care has been taken to ensure that the information contained in this handbook
is accurate and complete. Should any errors or omissions be discovered or should
any users wish to make suggestions for improving this handbook, they are invited to
send the relevant details to:

NEC Nederland B.V.

P.O. BOX 32
1200 JD HILVERSUM
THE NETHERLANDS

© NEC Nederland B.V.

All rights are reserved. Reproduction in whole or in part is prohibited without the
written consent of the copyright owner.
All brand names and product names in this document are trademarks or registered
trademarks of their respective companies.
 CONTENTS

1. INTRODUCTION ...................................................................................... 6

2. FUNCTIONALITY .................................................................................... 14
2.1. ISS CHARACTERISTICS...................................................................................................................14
2.1.1. Memory........................................................................................................................................14
2.1.2. Clock .............................................................................................................................................14
2.1.3. ISS (XPE) Flash Storage Device Lifetime .......................................................................................14
2.2. LEDS..............................................................................................................................................14
2.3. ETHERNET PORTS .........................................................................................................................16
2.3.1. Ethernet Port for SIP ....................................................................................................................16
2.3.2. Ethernet Port for PMC-IP / PMC-SIC / SIC ....................................................................................17
2.3.3. Ethernet Port via USB interface ...................................................................................................17
2.4. PMC-IP / PMC-SIC / SIC BOARD....................................................................................................17
2.4.1. PMC-IP..........................................................................................................................................18
2.4.2. PMC-SIC ........................................................................................................................................22
2.4.3. SIC.................................................................................................................................................24
2.5. APPLICATIONS ..............................................................................................................................25
2.6. LICENSING ....................................................................................................................................27
2.7. SIP@Net SERVER CONFIGURATION .............................................................................................28
2.8. SECURITY ......................................................................................................................................28
2.9. Windows Embedded OS FOR THE ISS ..........................................................................................33
2.10. EXTERNAL ALARMING VIA V.24 ON USB ......................................................................................34
2.11. JOURNALLING OF DYNAMIC DATA...............................................................................................35
2.12. DIAGNOSTIC TOOLS .....................................................................................................................36
2.13. SIMPLE NETWORK MANAGEMENT PROTOCOL (SNMP) ..............................................................36
2.14. MULTI PARTY CONFERENCE ON THE ISS ......................................................................................36

3. INSTALLING THE ISS .............................................................................. 37

3.1. PREPARATION ..............................................................................................................................37
3.2. CONFIGURE REMOTE DESKTOP ...................................................................................................38
3.3. PASSWORD POLICY (optional)......................................................................................................41
3.4. INSTALLATION ..............................................................................................................................42
3.4.1. Installation of SIP@Net ................................................................................................................42
3.4.2. Installation of the SIP Driver ........................................................................................................50
3.4.3. Installation of the Media Server ..................................................................................................55
3.4.4. Installation of the Tools for the iS3000/SIP@Net Server.............................................................63
3.4.5. Maintenance Aspects...................................................................................................................66

4. HOW TO UPGRADE A CPU3000 TO ISS .................................................. 68

4.1. PRECONDITIONS...........................................................................................................................68
4.2. UPGRADING PROCEDURE ............................................................................................................68
4.3. ISS-2/ISS-3 IN iS3050 WITH CSN-BC BOARD ................................................................................70
4.4. CHANGE OVER TO FDCR OVER IP .................................................................................................71

5. HANDLING IMAGES OF THE ISS ............................................................. 72

5.1. RE-INSTALLATION OF EMBEDDED XP / WES2009 ........................................................................72
5.2. SELFIMAGE ON WINDOWS VISTA / WINDOWS 7 ........................................................................74
5.3. READ OUT THE VERSION OF AN ISS IMAGE .................................................................................75

6. HANDLING IMAGES OF THE ISS-2/ISS-3 ................................................. 76

-1-
6.1. CREATE A BOOTABLE WINPE USB MEMORY DEVICE ...................................................................76
6.2. CREATE AN IMAGE OF THE ISS-2/ISS-3 ........................................................................................78
6.3. RESTORE AN EXISTING IMAGE ON THE ISS-2/ISS-3......................................................................79
6.4. RESTORE A NEW (OR INITIAL) WES 7 IMAGE ON THE ISS-2/ISS-3 ...............................................79
6.5. READ OUT THE VERSION OF AN ISS-2/ISS-3 IMAGE ....................................................................80
6.6. WINDOWS UPDATE ......................................................................................................................81

7. INCOMING RAS CONNECTION FOR REMOTE MAINTENANCE................. 83

7.1. MODEM PREPARATION ON ISS/ISS-2/ISS-3 .................................................................................83
7.1.1. ISS with Windows XPE ..................................................................................................................83
7.1.2. ISS-2/ISS-3 with WES7 ..................................................................................................................89
7.2. MODEM PREPARATION ON THE HOST PC ...................................................................................94
7.3. SET UP A RAS CONNECTION TO THE ISS ......................................................................................98

A. PROTOCOLS AND PORT NUMBERS .......................................................100

-2-
PREFACE
This manual is valid for both SIP@Net platforms running on the In Skin Server (ISS).
Unless stated otherwise (in text and figures), the term ISS represents:

• the ISS with Windows XP embedded

• the ISS-2 or ISS-3 with Windows Embedded Standard 7 (WES7)

The new functionality, the installation aspects and an upgrade scenario are described in this manual. For
system specific details please refer to the installation manual of the system concerned.

IMPORTANT SAFETY INFORMATION

Protective earth
Before installation of an ISS, PMC-IP, PMC-SIC or SIC board or before replacement of any CPU by an ISS,
PMC-IP, PMC-SIC or SIC in a PM55/PM255/PM1100/19-inch PM shelf, make sure that the involved
hardware have a permanent connection to protective earth. Connection to so-called 'functional earth',
'signaling ground', or 'telecom earth' does not qualify as protective earth.
Parts of the iS3000 systems are provided with separate protective earth terminals. Each of these terminals
must be permanently connected to protective earth and the connection to protective earth must be
established before any other installation activity or connection is made, in particular connections to the
telecommunication network. Failure to follow these instructions may result in a safety hazard.
For details about the system specific earth connections, please refer to the installation manual of the
system concerned: issue date January 2009 (or later).

IMPORTANT EMC INFORMATION

All systems in which the ISS, PMC-IP, PMC-SIC or SIC can be used, meet the EN55022 Class B requirements
for radiated and conducted emission when installed conform the installation requirements.
When one of the below situations is applicable the warning below applies:

- If an ISS, PMC-IP, PMC-SIC or SIC is installed of which one or more USB ports are connected to
peripherals outside the system enclosure or,
- When Ethernet ports are connected with CAT-5 cables to peripherals outside the system or,
- When an ISS, PMC-IP, PMC-SIC or SIC is installed in a system (independent of the interfaces used).

Warning: This is a class A product.

In a domestic environment this product may cause radio interference in
which case the user may be required to take adequate measures.

-3-
USB EMC Measures

In this specific case a cable shall be used with three ferrite barrels. If such a cable is not available three
snap-on ferrite barrels of type ESD-SR-250 (also available as type number 9600 036 08000) shall be added
to a standard USB cable as given in the figure below.

Please note that the above warning and measures are NOT applicable if the USB port is ONLY connected to
peripherals that remain inside the system enclosure, for example in case of a USB license dongle or USB
memory stick.

Ethernet EMC Measures

In this specific case a cable shall be used with three ferrite barrels. If such a cable is not available three
snap-on ferrite barrels of type ESD-SR-250 (also available as type number 9600 036 08000) shall be added
to a standard Ethernet cable as given in the figure above.

Notice that due to the properties of the Ethernet physical layer, the use of CAT-5 Ethernet cables for
connection to peripherals outside the system will result in an EMC Class A system.

- For systems with an ISS, PMC-IP, PMC-SIC or SIC the EMC Class B emission limits can be maintained by
using a CAT-6 cable for the Ethernet ports that are connected to peripherals outside the system.

- For systems with a PMC-IP this method will improve the overall Class A emission properties.

-4-
PRODUCT DISPOSAL INFORMATION (EN)

For countries in the European Union

The symbol depicted here has been affixed to your product in order to inform you
that electrical and electronic products should not be disposed of as municipal waste.

Electrical and electronic products including the cables, plugs and accessories should
be disposed of separately in order to allow proper treatment, recovery and recycling.
These products should be taken to a designated facility where the best available
treatment, recovery and recycling techniques are available. Separate disposal has
significant advantages: valuable materials can be re-used and it prevents the
dispersion of unwanted substances into the municipal waste stream. This contributes
to the protection of human health and the environment.

Please be informed that a fine may be imposed for illegal disposal of electrical and electronic products via
the general municipal waste stream.
In order to facilitate separate disposal and environmentally sound recycling arrangements have been made
for local collection and recycling. In case your electrical and electronic products need to be disposed of
please refer to your supplier or the contractual agreements that your company has made upon acquisition
of these products.

At www.nec-enterprise.com you can find information about separate disposal and environmentally sound
recycling.

For countries outside the European Union

Disposal of electrical and electronic products in countries outside the European Union should be done in
line with the local regulations. If no arrangement has been made with your supplier, please contact the
local authorities for further information.
Battery Information

Defect or exhausted batteries should never be disposed of as municipal waste. Return

old batteries to the battery supplier, a licensed battery dealer or a designated
collection facility. Do not incinerate batteries.

The following cards of this product use batteries for memory backup and retention purposes:

CPU3000 : Vanadium Pentoxide Lithium 3V, 20 mAh VL2020

SIC : Vanadium Pentoxide Lithium 3V, 20 mAh VL2020
PMC-SIC : Vanadium Pentoxide Lithium 3V, 20 mAh VL2020
PMC-IP : Vanadium Pentoxide Lithium 3V, 20 mAh VL2020

-5-
1. INTRODUCTION
The In Skin Server (ISS/ISS-2/ISS-3) can be used as the Central Processing Unit for both the SIP@Net
platforms.
The SIP@Net platforms are:

• SIP@Net Server platform

Platform with an IP-based switching network.
Processors: External Server or In Skin Server (ISS, ISS-2 or ISS-3).
Optionally, this platform can handle IP-PMs.
System option 179 is set to "1".

• iS3000 platform
Platform with a TDM-based switching network.
The subtypes are:
- iS3000 Single processor: CPU3000, ISS, ISS-2 or external server
- iS3000 Fault Tolerant processor: CSM processor module
System option 179 is set to "0".

The ISS is a small PC board with Windows XP Embedded operating system.

Because of the fact that Windows XPE is declared "End of Service" at January 2016, the ISS-2 is introduced.
As a consequence, incidents related to the ISS with Windows XPE will be handled on "best effort" basis.
The ISS-2 is the successor of the ISS. However the OS of the ISS-2 or ISS-3 is Windows Embedded Standard
7.
The main differences between the ISS and ISS-2/ISS-3 are listed below:

ISS ISS-2/ISS-3
 Windows XP Embedded OS  Windows Embedded Standard 7 OS
 Single Core 500 MHz  Single Core, dual thread 1,6 GHz
 1 GB RAM memory  2 GB RAM memory
 4 GB Compact Flash (CF) disk  ISS-2: 8 GB Solid State Drive (SSD)
ISS-3: 16 GB Solid State Drive (SSD)
 limited write actions  Write ≈250 MB per day
 IPv4  IPv4 and (prepared for) IPv6
 physically occupies 1 board position  physically occupies 2 board positions
 5.5 Watt, flat heat-sink  8 Watt, heat-sink with fingers
 running SIP@Net 4.3 (or higher)  running SIP@Net 5.4 (or higher)

The ISS/ISS-2/ISS-3 is always mounted on either a:

• Server Interface Card (SIC)

or
• Peripheral Module Controller – Server Interface Card (PMC-SIC)
or
• Peripheral Module Controller – IP Gateway (PMC-IP)

In case of a SIC board the adjacent PMC board must be a PMC-G or PMC-MC.
The supported shelves are:

 PM55 (iS3010 cabinet) see note

 PM255 (iS3030 cabinet)
 PM1100 (iS3050 cabinet with 4 PM shelves)
 19-inch PM shelf

-6-
Note: Because of the fact that the ISS-2 or ISS-3 physically occupies 2 board positions, a SIC + ISS-2/ISS-3
cannot be placed in a PM55 shelf (iS3010 cabinet). Mount the ISS-2 or ISS-3 on either a PMC-SIC or
PMC-IP.
 The PMC-SIC is a combination (successor) of a PMC-G and a SIC card and therefore it fits in the
standard PMC board position.
• The PMC-IP is a combination (successor) of a PMC-SIC and an ISG card and therefore it fits in the
standard PMC board position.

The major difference with respect to the PMC-SIC is that the PMC-IP now also supports the IPG (ISG)-
function. The IPG functionality in the PMC-IP is enabled by assigning up to 4 "ISG boards" at virtual board
positions. When assigned it is possible to have up to 118 IPG channels.

WARNING: Because of power dissipation it is not allowed to install another board on the right-hand
side of the PMC-IP.
So positions respectively 18 (PM1100 (19 inch) Shelf), 8 (PM255) or 4 (PM55) must be left
empty. Even "parking" a board in those positions is not allowed.

iS3000 platform
The ISS/ISS-2/ISS-3 can be used as the successor of the CPU3000 single processor of the iS3000 platform.
On this platform the ISS/ISS-2/ISS-3 can control up to 4 PMs (not IP-PM). Note that instead of the ISS/ISS-
2/ISS-3, also an external server can be used, but it remains an iS3000 platform with maximum 4 PMs (not
IP-PM).

SIP@Net Server platform

The ISS/ISS-2/ISS-3 can also be as used a Central Processing Unit for the SIP@Net Server platform.
On this platform the ISS can control up to 2 IP-PMs (because of performance reasons of the ISS).
An IP-PM is an iS3000 PM Shelf with extension and/or trunk boards that act as a gateway between an IP-
infrastructure and a TDM-infrastructure.

For more details of projecting and installing the IP-PM, see the "SIP@Net Server CE Manual".
The maximum number of extensions that can be handled (with a call rate of 1 call/sec) is limited to:

 ISS ≈ 500 extensions (SIP and TDM)

 ISS-2/ISS-3 ≈ 1800 extensions (in SIP@Net 6.0)
 ISS-2/ISS-3 ≈ 2000 extensions (in SIP@Net 6.1 and higher)

Note that the above figures are relevant under the following conditions:

 TDM Trunks : can be a digital (or analogue) trunk in the IP-PM

 VoIP Trunks : must be Peer-to-Peer SIP trunks
 No SMA is used
 No Voice Logging/Voice Recording is used
 No Multi-party conference is used
 System option LOSYSOP218 (Use ISG/IPG instead of Media Server for DTMF detection, introduced in
SIP@Net 6.1) is set to "TRUE".

The main performance limitation of the ISS is the Media Server. The Media Server is needed for:

 Dial-tone and ring-tone for extensions in the IP-PM(s)

 For all extensions
 Busy tone with DTMF-recognition (Automatic Ring Back)
 MOH tone

-7-
  COB tone (for example waiting in queue)
 Confirmation tone
 Congestion tone
 Don’t disturb tone

 Three-party conference, when

 the three-party conference is setup by BCT
 the three-party conference leader is using a SIP-DECT terminal, Baseline Pro SIP terminal or a TDM
terminal in an IP-PM
 Multi-party conference
 Non Peer-to-Peer SIP trunks
 SMA-function
 Voice Logging/Voice Recording function

ISS with BIM

Instead of running SIP@Net, the ISS (with Windows XPE) can be used for the BIM functionality which is
used in a fault-tolerant CCS system. Also because of the fact that Windows XPE is declared "End of Service"
at January 2016, a BIM Upgrade Package is available to upgrade an existing ISS (with Windows XPE) to an
ISS with Windows Embedded Standard 2009 (WES2009).
Windows Embedded Standard 2009 is the next generation of Windows XPE.

Note that SIP@Net cannot be installed on the ISS with WES2009!!!

From the engineer point of view there is no real difference between Windows XPE and WES2009, with
respect to installing the BIM software and handling the XPE and WES2009 images.

For more BIM details, see the BIM Manual.

For completeness, see the overview below.

HARDWARE & OS
APPLICATIONS ISS with ISS with ISS-2/ISS-3 with
Windows XPE WES2009 WES 7
SIP@Net YES NO YES
BIM YES YES NO

Mounting the ISS

Remove the plastic seals of the PMC-IP, PMC-SIC or SIC board before mounting the ISS. Because of different
distances between the connectors, the ISS only fits in one way on the PMC-IP, PMC-SIC or SIC board.

-8-
Figure 1: Mounting the ISS

Figure 2: PMC-IP Board

-9-
Figure 3: PMC-SIC Board

Figure 4: SIC Board

- 10 -
 Figure 5: PMC-IP with ISS-2
INTERFACES
The PMC-IP / PMC-SIC / SIC has the following interfaces:

 3x 10/100 Ethernet ports mounted at the front.

 the top port represents the ISS and is mainly used to communicate between the ISS and the PMC-IP /
PMC-SIC / SIC. This can be direct cable connection or a connection via the LAN network.
 the port in the middle represents the ISG (only on the PMC-IP): on the PMC-SIC and SIC it is not used.
 the bottom port represents the PMC-IP / PMC-SIC / SIC and is applied to communicate between the
ISS and the PMC-IP / PMC-SIC / SIC and to control a maximum of 4 Peripheral Modules and one CSN-
BC board over an IP connection.
 4x USB interfaces for the ISS. One USB interface is used to connect the dongle. The remaining interfaces
can be used to connect other (memory) devices.
 2x Clock reference inputs (not on the SIC).
 In normal operation the VGA connector is not used. The VGA connector is only used to connect a local
monitor for handling of Windows images on an ISS-2/ISS-3, see chapter 6, HANDLING IMAGES OF THE
ISS-2/ISS-3 , or to set date and time to enable Remote Desktop, see below.

BATTERY
The on-board battery is the back-up battery for the Real-Time Clock (RTC) of the ISS.
The battery life-time is much more than 10 years.
During the first installation it is assumed that the battery is not (fully) charged.
After 12 hours operation in the system the battery is fully charged. From that moment the battery can run
the RTC of the ISS for weeks, while the board is out of the system.
Due to the fact that the battery is soldered on the board, the user cannot replace it.

- 11 -
WARNING:
Every time the ISS-2/ISS-3 is disconnected from the on-board battery on the SIC/PMC-SIC/PMC-IP (the
ISS-2/ISS-3 is removed from the board), the date & time of the ISS-2/ISS-3 is reset to a date in the past.
This old date & time give problems, in case a Remote Desktop connection is set up from a Windows
2008/2012 Server. An error message is given that there is a too large time discrepancy compared to the
actual date & time.
In this case first a local monitor/keyboard/mouse is needed, to set the actual date & time in the ISS-
2/ISS-3.
Setting up a Remote Desktop connection from a Windows 7 PC gives a warning, but the connection can
be made. So, the advice is to use a Windows 7 PC for the Remote Desktop connection.

See also section 3.2. CONFIGURE REMOTE DESKTOP.

STRAP

101 The strap on the SIC, PMC-SIC, PMC-IP and SIC-2 was meant for an alternative ISS that is
never introduced. Placing the strap in a wrong position will cause disturbance on the
103 ISS/ISS-2/ISS-3 Ethernet connection. Therefore: when present, park it on the bottom pins
or remove it.

ISS versus CPU3000

The major difference between the ISS and the CPU3000 is the fact that Peripheral Modules are controlled
via IP: tunnelling the traditional IMP protocol.
There are however a number of limitations/differences:

 There are no V.24 interfaces anymore. The consequences of this limitation are:
 No Alarm Unit (ALU) and Common Answering Night Service (CANS)
 No FDCR via V.24: use "FDCR over IP"
 Remote Maintenance via "V.24 modems" is not possible anymore.
An alternative is to use "USB modems" (see chapter 7. INCOMING RAS CONNECTION FOR REMOTE
MAINTENANCE) or to use the ComView IPs modem.

 There is no internal fingerprint, so a dongle has to be used via the USB interface. The USB interfaces may
also be applied for backup purposes, to make fire copies of the projecting files etc. Note that file
manipulation actions can also be done via the "Remote Desktop".

 Both PMC-G and PMC-MC can be used as PM controller. Note that the PMC-LU is not supported by a SIC
with ISS.

Comparing the ISS for the iS3000 platform and for the SIP@Net Server platform there are some differences
looking at the following components:

 The SIP driver

 On an iS3000 with CPU3000, the SIP driver normally runs on the ISG.
The SIP driver may be installed on the ISS and will function properly.
However in an upgrade scenario it is not sensible to take this approach, this would incorporate more
changes (for example the configuration files of the SIP terminals need to be changed, to access the
SIP driver on a different IP location).
Therefore the advice is not to install the SIP driver(s) on the ISS, but leave them on the ISG.

 On a SIP@Net Server the SIP driver will be installed on the same processor as the SIP@Net program.
This is advice to reduce the dependency to one hardware board instead of multiple boards ISS as well
as ISG hardware.

- 12 -
 The iTMP driver
 On iS3000 with CPU3000 the ITMP driver normally runs on the ISG, so in an upgrade scenario, leave
the iTMP driver on the ISG/PC.

 On a SIP@Net Server the iTMP functionality is not supported. So in an upgrade scenario from iS3000
to SIP@Net Server platform, change iTMP-DECT in to SIP-DECT.

 Licenses
New licenses are introduced: for details refer to section 2.6. LICENSING.

The ISS is backwards compatible with CPU3000, with the restriction mentioned in this document. For a
detailed description of the upgrade scenario, see chapter 4. HOW TO UPGRADE A CPU3000 TO ISS.

Note that iS3000 systems with a PMC-LU (in a PM250/PM1000 shelf), the CPU3000 can NOT be replaced
by the SIC with ISS !

- 13 -
2. FUNCTIONALITY
2.1. ISS CHARACTERISTICS

2.1.1. Memory

The ISS-2/ISS-3 is a small PC board running Windows Embedded Standard 7 OS.

The ISS-2 board contains 8 GB Solid State Drive (SSD) and is equipped with 2 GB of RAM memory.
The ISS-3 board contains 16 GB Solid State Drive (SSD) and is equipped with 2 GB of RAM memory.

The ISS is a small PC board running Windows XP Embedded OS.

The ISS board contains 4 GB Compact Flash (CF) disk and is equipped with 1 GB of RAM memory.

IMPORTANT REMARK:
Note that when a (used) CF card is used on the ISS of a different supplier (Kontron or MSC), always start
with a clean XPE image. Do not interchange CF cards that have been used in a different brand of ISS.

2.1.2. Clock

The ISS is equipped with an on board clock, which has a deviation of 1261 seconds per year, which is slightly
better than the CPU3000 (1320 seconds per year). The ISS synchronizes its date and time with the time of
the Operating System it is running on. This synchronization is done at least every minute. OM command
SEDATI is not supported on the ISS. Notice that it may be required to set the time properly on the ISS when
the board is started for the first time as is done on a normal PC.
The ISS can also synchronize to a time-server on the local network or in the internet, that uses the SNTP
protocol, see:

"Control Panel" -> "Date and Time" -> "Internet time".

Note that "ISDN date/time synchronisation" is disabled on the ISS.

2.1.3. ISS (XPE) Flash Storage Device Lifetime

The flash device can be written a limited amount of time (roughly 300.000 times). This implies that when
one flash location has been written the indicated amount of times the flash can no longer be written and
has to be replaced. Note that also techniques like 'wear levelling' will assure that flashes gradually degrade.
Measurements have shown that based on the figure above at least a lifetime of 12 years can be
guaranteed.

2.2. LEDS

The PMC-IP is equipped with 2 groups of 3 different LEDs (red, green and yellow). One group (located at the
top) represents the status of the PMC-SIC part and another group (underneath) represents the status of the
IPG part.
The PMC-SIC / SIC is equipped with 1 group of 3 different LEDs (red, green and yellow).
The color and possible rhythm determine the status of the PMC-IP / PMC-SIC / SIC board: see tables on the
following pages.
The RAM test indication will hardly be visible, only when the test fails it is steady for approximately 5
seconds before the PC-IP / PMC-SIC / SIC restarts.

- 14 -
The image updating indication occurring after download of a new package shows a flashing red LED. During
the erasure of the old package the led flashes in a fast rhythm. When the new package is copied to the old
package location the LED is flashing in a slower rhythm.
Finally when the new package is erased the LED is again flashing in the fast rhythm. After the update the
red LED is steady on indicating the start of the application.
Furthermore each Ethernet connector has 3 (on board) green LEDs associated that indicate Tx and Rx
activity, the Link status and applied speed.

LEDs on PMC-IP / PMC-SIC

MEANING
GREEN RED YELLOW
Power up Off On Off
RAM test (data lines) On On Off
RAM test (address lines) On On On
Copying program to RAM On Off On
Program started in BIST mode On Off On
Program started in normal mode Off On On
Downloading new package from TFTP server Off On Flashing
Waiting for communication with CPU On On Off
Operational On Off Off
Installing new package (see note 2) On Flashing Off
Downloading new package from CPU (INSTPK) On Off Flashing
Note 1 : One exception applies to this table in the situation where the PMC-IP is operating in Slave mode and the Ethernet
interface is used. The flashing state of the Yellow LED indicates that the board is downloading new software.

Note 2 : The last two statuses are only relevant for the PMC part when loading using OM command INSTPK.

LEDs on PMC-IP and PMC-SIC

LEDs on SIC
MEANING
GREEN RED YELLOW
Power up Off On Off
RAM test (data lines) On On Off
RAM test (address lines) On On On
Copy application to RAM On Off On
Application copied: BIST On Off On
Application copied: Application Off On On
SIC package download Off On Flashing
SIC Image updating Off Flashing On
SIC Application package start On On Off
Application package operational: communication with the On Off Off
SIP@Net Server is established

- 15 -
 LEDs on SIC

2.3. ETHERNET PORTS

2.3.1. Ethernet Port for SIP

The ISS has a 10/100 Ethernet port for SIP. This IP connector is the top connector and is used for:

 The SIP signalling towards the SIP driver and SIP@Net (provided the SIP driver is not running on the ISS)
 The signalling towards the SIC.
 OM, CSTA, FDCR, iPVN, SNMP, etc.

The ISS receives its IP address as indicated via the XP embedded setting. Default the ISS is configured such
that it obtains its IP address using a DHCP server. In situations where no DHCP server is available an
alternate IP address is assigned to the ISS as given below:

Alternate IP Configuration
IP address : 192.168.1.15
Netmask : 255.255.255.0
Default Gateway : 0.0.0.0

When DHCP is applied one needs to assure that the ISS receives a fixed "dynamic" IP address. The reason
for this is that the SIP driver will establish the connection with SIP@Net and needs to know its IP address.

During installation time the engineer must make the choice between DHCP and fixed IP address and change
the configuration to match that choice. The alternate IP address (in the "Alternate Configuration" tab of the
"Local Area Connection" properties) is only intended to enable the engineer to use the ISS in any
configuration.

The alternate IP address should be removed by the engineer during installation. In the DHCP configuration
having an alternate IP address might lead to unexpected situations when the DHCP server becomes
(temporarily) unreachable and the ISS was to fall back on the alternate IP address.
By default the ISS is configured with computer name "ISS". It can be reached (by PING for instance) under
that name. To contact the ISS without knowing its IP address, the Windows Firewall must make an
exception for the "UDP 137" service.

Note that the computer name "ISS" must be changed in case more than one ISS are applied in the same IP
network.

Once the ISS has an IP address, it is possible to get access to the ISS via "Remote Desktop". One user
account is available as default using "Admin" as username and password.
The first time the user attempts to logon to the ISS (via Remote Desktop) the user receives a text indicating
that a new password needs to be entered.

Note: The new password is valid for 42 days (default).

After these 42 days a new password has to defined.
How to adapt the password policy is given in section 3.3. PASSWORD POLICY (optional).

Notice that in cases where the Username/Password for Remote Desktop is lost the only alternative is to do
a complete re-install of Embedded XP (as described in section 5.1. RE-INSTALLATION OF EMBEDDED XP)
followed by a re-Install of SIP@Net.

- 16 -
Access of the flash disk is performed by using Remote Desktop. In this way it is possible to install a new
SIP@Net release on the flash disk.

TIP:
In the Remote Desktop, copying files to/from flash disk can be done via File Sharing or an USB memory
stick: USB memory stick is faster compared to File Sharing.

Note: Before re-installing Embedded XP, one can back-up the configuration files (PE/LL and journal file)
from flash-disk through a flash-disk reader connected to the PC.

This interface does not support 802.1p (priority handling) or 802.1q (VLAN tagging). Also DSCP (layer 3
priority handling) is not supported on this interface. Notice that in this respect the ISS behaves identical as
the CPU3000.

2.3.2. Ethernet Port for PMC-IP / PMC-SIC / SIC

The ISS has a 10/100 Ethernet port related to the PMC-IP / PMC-SIC / SIC. This IP connector is the bottom
connector and is applied for the communication with the PMC-IP / PMC-SIC / SIC. The major purpose of this
interface is to carry the IMP communication with SIP@Net.

The "MAC address" sticker on the PMC-IP board represents the MAC address of the PMC. Also the IPG has a
MAC address, however not visible on a sticker.
The MAC address of the IPG is always "one" higher than the MAC address of the PMC.
An IP address with related netmask, default gateway and TFTP server (to obtain the PMC-IP / PMC-SIC / SIC
configuration file) will be assigned using DHCP.

 MAC address PMC is: 00182701E1D5

 MAC address IPG is: 00182701E1D6

By means of OM command DISICI the IP addresses and PMC-IP / PMC-SIC / SIC related information can be
displayed (after it has been assigned using CHSICI).

2.3.3. Ethernet Port via USB interface

The Ethernet port via the USB interface can be used in case you want to separate the PBX LAN from the
customer’s LAN. Also in a "non-IP" environment, the ethernet port for SIP can be directly interconnected to
the ethernet port of the SIC, using a LAN cross cable: so no hub/switch is needed. In this case no ethernet
port is available for maintenance (remote desktop).
Therefore one of the USB interfaces can be used to connect a "USB - Ethernet Adaptor", offering an extra
ethernet interface. The following adaptors are verified/certified:

 Sitecom USB2.0-to-Fast Ethernet Adapter (LN-030).

 Conrad USB2.0 10/100 Mbits Ethernet Adapter Nr.973119.
 LevelOne USB-0201 USB Gigabit Ethernet Adapter.
 LevelOne USB-0301 USB Gigabit Ethernet-adapter.
 LevelOne USB-0401 USB Gigabit Ethernet-adapter (with LED indicator).

2.4. PMC-IP / PMC-SIC / SIC BOARD

- 17 -
Only one of the following 3 sub-sections (2.4.1 ... 2.4.3) is relevant, depending on which board the ISS is
mounted.

2.4.1. PMC-IP

The PMC-IP is the successor of the PMC-SIC board and the ISG board.
The PMC-IP is designed to control the (IP-)PM, therefore it must always be placed in the PMC board
position in a PM, IP-PM or RPM shelf:

- board position 17 in a 19 inch PM Shelf

- board position 17 in a PM1100 Shelf
- board position 7 in a PM255 Lower Shelf (iS3030 cabinet)
- board position 3 in a PM55 Lower Shelf (iS3010 cabinet)

WARNING: Because of power dissipation it is not allowed to install another board on the right-hand
side of the PMC-IP.
So positions respectively 18 (PM1100 (19 inch) Shelf), 8 (PM255) or 4 (PM55) must be left
empty. Even "parking" a board in those positions is not allowed.

The PMC-IP is a downloadable board.

The firmware packages required for the PMC-IP are:

- PMC : Firmware package : F19100.2xx

This PMC package can also be used on a PMC-SIC.

- IPG : Firmware package : FA3000.1xx

Boot package : F39a30.1xx

Loading the firmware (and boot) packages is done via TFTP.

In case of replacement of a PMC-G in a "TDM only" environment, the PMC package can still be downloaded
by the CPU, using OM command INSTPK.
Nowadays, in an IP environment, TFTP is advised (much faster).
Note that IPG firmware cannot be downloaded using OM command INSTPK !

Download the IPG Firmware via TFTP server

The configuration file may be available in 2 formats, either a common file called prebipg.txt or a specific
prebipg<mac address>.txt. In general all PMC-IP boards will have the same IPG application package, so one
common prebipg.txt is normally sufficient. The IPG will however scan for both files.

The first line of the prebipg.txt (or prebipg<mac address>.txt) configuration file indicates the application
package that needs to run on the IPG.
An example of such a file is:

FA3000v1.1xx
[SipPabxIp]
IP=192.168.1.100
Port=2610
[Control]
DhcpLease=Ignore
[WebServer]
WebServerEnabled=1

- 18 -
At power up of the PMC-IP, an IP address with related netmask, default gateway and TFTP server (to obtain
the IPG configuration file) will be assigned using DHCP.

Operation without DHCP can be achieved by assigning an infinite lease to the MAC address of the IPG.
This is done by including the following text in the prebipg.txt file:

[Control]
DhcpLease=Reuse

First the IPG package will be downloaded from the TFTP server when:

 The board is connected to Ethernet, and

 The DHCP server gives the address of a TFTP server via option 66 (or using "next server"), and
 The configuration file specifies another package than the currently loaded package, and
 The package is available at the TFTP server.

When one or more of these conditions is not met, the PMC-IP starts up with its current package.
In case the boot package has to be replaced, then first power up the PMC-IP with a prebipg.txt
configuration file indicating the boot package only:

F39a30.1xx

After the boot package is loaded, change the content of the prebipg.txt into:

FA3000v1.1xx
[SipPabxIp]
IP=192.168.1.100
etc.

Power down and power up the board again, or execute OM commands: SETOUT/ SETINS:11,20&&23,0;

Download the PMC Firmware via TFTP server

The principal is the same as for the IPG.
The configuration file may be available in 2 formats, either a common file called prebpmc.txt or a specific
prebpmc<mac address>.txt. In general all PMC-IP board will have the same application package, so one
common prebpmc.txt is normally sufficient. The PMC-IP will however scan for both files.
The first line of the prebpmc.txt (or prebpmc<mac address>.txt) configuration file indicates the application
package that needs to run on the PMC-IP.
An example of such a file is:

F19100v1.2xx

At power up of the PMC-IP, an IP address with related netmask, default gateway and TFTP server (to obtain
the SIC configuration file) will be assigned using DHCP. Operation without DHCP can be achieved by
assigning an infinite lease to the PMC-IP board. This is done by including the following text in the
prebpmc.txt file:

F19100v1.2xx
[Control]
DhcpLease=Reuse

First the PMC package will be downloaded from the TFTP server when:

- 19 -
 The board is connected to Ethernet, and
 The DHCP server gives the address of a TFTP server via option 66 (or using "next server"), and
 The configuration file specifies another package than the currently loaded package, and
 The package is available at the TFTP server.
When one or more of these conditions is not met, the PMC-IP starts up with its current package.

Download the PMC Firmware via OM Command INSTPK

Next the CPU will download a new package when:

 A package for the PMC-IP is defined by INSTPK, and

 That package differs from the currently loaded package, and
 The new package is available at the LBU.

When both methods are active and define different packages, the PMC-IP will first download the TFTP
package and then the INSTPK package.
So the package defined by INSTPK overrules the TFTP package.

WARNING: In case of upgrading an existing system (existing projecting) first modify the firmware
package relation to f19100v1.2xx or use a "board-subtype" for the PMC, otherwise the
PMC-IP will load a PMC-G (or PMC-MC) firmware package. When that is once loaded, the
PMC-IP will not become operational.

PMC part of the PMC-IP

The PMC part of the PMC-IP provides the following basic telephony functions:
 32 tone sources:
 16 tone sources are reserved for DTMF signals, compliant with CCITT recommendation Q.23, and
 16 tone sources are free for customer projecting.
 6 key tone receivers (RKT): circuits 2, 3 & 4 and 7, 8 & 9.
 Note that 6 extra RKT’s can be configured (OM command ASPCTB) on circuits 24 … 29.
 4 dial tone receivers (RDT): circuits 5 & 6 and 10 & 11.
 32 three-party conference circuits (Add-On / Break-In circuit).
 Peripheral switching network.
 Protocol Co-Processor (PCP) providing 16 channels for Internal Message Protocol or HDLC
communication. Two of those 16 channels are reserved for CPU-PMC communication.

The PMC-IP supports the standard Network Connection Cards: NCC-MC and NCC-HR.
To mount those cards, some extra connection material is required that is always supplied with the PMC-IP
board.

IPG part of the PMC-IP

The IPG part of the PMC-IP supports the media handling for the following protocol types:

 SIP extensions and SIP trunks.

 CCIS protocol, for interworking with the other NEC platforms.
 Media handling for the IP-PM.

The protocols listed above are similar to the ones, currently available on the ISG.
In case none of the above protocols are used in an existing SIP@Net system with the ISS, it is not necessary
to project the IPG part.
The IPG supports the following:

 118 ISG channels.

- 20 -
 SIP driver including support for TLS.
 Codecs G.711aLaw, G.711uLaw, G.729 (including G729A and G729AB).
 Payload of 20, 30 and 40 msec.
 RTCP and SRTP.
 Adjustable echo tail delay of 32, 64 and 128 msec.
 DTMF detection/relay using RFC2833.
 Management is done using DHCP/TFTP similar to the current ISG.
 One 10/100 Mb/s IP interface.
 Web interface: only for display purposes: IPG status and configuration.
 PMC-IP management using DHCP (including support for option 66)/TFTP similar to the current ISG.
Operation without DHCP/TFTP is possible.
 The IPG has one IP address.
 Prepared for Codecs G.722, G.722.1.24, G.722.1.32 without hardware changes.
 Prepared for IPv6 without hardware changes.

When running older IPG firmware packages (previous to fa3000v1.201), VLAN tagging and QOS for RTP is
not supported: in this case VLAN tagging and QOS must be arranged on the port of the LAN switch.
Since IPG firmware package "fa3000v1.201", next to IPv6 support, also VLAN tagging and QOS is supported.

The IPG functionality in the PMC-IP is enabled by assigning up to 4 ISG at virtual board positions. Supported
PM shelf types are:

6 = PM1100-shelf
11 = PM255L-shelf
13 = PM55L-shelf

Other PM shelf types including the Remote PM shelf types are not supported.

The PMC-IP is projected, using OM command ASBRDS given in the table below.

Virtual Board Positions in a PM shelf

(19")PM1100 shelf PM255L shelf PM55L shelf
20, 21, 22 & 23 10, 11, 12 & 13 5, 6, 7 & 8
ASBRDS:11,20,18,5D21; ASBRDS:12,10,18,5D21; ASBRDS:12,5,18,5D21;
ASBRDS:11,21,18,5D21; ASBRDS:12,11,18,5D21; ASBRDS:12,6,18,5D21;
ASBRDS:11,22,18,5D21; ASBRDS:12,12,18,5D21; ASBRDS:12,7,18,5D21;
ASBRDS:11,23,18,5D21; ASBRDS:12,13,18,5D21; ASBRDS:12,8,18,5D21;

Boards and circuits must be set INS (IN-Service).

With OM command ASLINE up to 118 trunk-lines per IPG can be assigned:

- the 1st and 2nd virtual ISG board have 30 B-channels.

- the 3rd and 4th virtual ISG-board have 29 B-channels.

ASLINE rejects assignment of B-channel 31 at the 3rd and 4th virtual ISG-board.

The maximum number of channels available depends on the number of virtual ISG boards assigned and the
number of boards that are INS.

Virtual Board Positions Number of Channels

20 (or 10 or 5) only 30

- 21 -
 21 (or 11 or 6) only 30
22 (or 12 or 7) only 29
23 (or 13 or 8) only 29
all possible combinations 29, 30, 58, 59, 60, 88, 89 or 118

Assigning ISG boards at virtual board positions is only allowed in shelves controlled by a PMC-IP.
Assignment in shelves controlled by an older type of PMC, when the PMC is INS (in-service) is signalled by
Alarm Code 45, QLF 1.
When the PMC was OUT (OUT-of-service), then at setting the PMC to INS, it may not become operational.
This is signalled by Alarm Code 120, QLF 7.

When projecting the board, also the following system boundaries are relevant:

- LOBOUND053 : Max number of trunks (e.g. 100)

- BOUND150 : Max number of PCTs per PM (e.g. 512)
- LOBOUND238 : Max number of ISDN trunk circuits (e.g. 100)
- LOBOUND239 : Max number of ISDN trunk B channels (e.g. 512)
- LOBOUND091 : Max number of resource relations (e.g. 2000)
- BOUND155 : System limited number of PCT boards per PM (e.g. 32)
The default value has changed to 32.

Configuration rules for the IPG

To prevent congestion on calls when virtual IPG (ISG) boards are used, it is advised NOT to assign ISDN
and/or QSIG trunk boards (DTU/DTX-I(7/15)) in a:

- 19" PM Shelf : on board positions 1 … 8.

- PM1100 Shelf : on board positions 1 … 8.
- PM255 Shelf : on board positions 1 … 8 in the upper shelf.
- PM55 Shelf : limit the number of ISDN/QSIG trunk lines to a maximum of 60 B-channels.

Be patient with the system: it can take a while before all 4 IPG’s are IN Service: meanwhile Alarm Code
62/QLF 3 (Board Absent) is given.

2.4.2. PMC-SIC

The PMC-SIC is the successor of the PMC-G board and the SIC board.
The PMC-SIC is designed to control the (IP-)PM, therefore it must always be placed in the PMC board
position in a PM, IP-PM or RPM shelf:

- board position 17 in a 19 inch PM Shelf

- board position 17 in a PM1100 Shelf
- board position 7 in a PM255 Lower Shelf (iS3030 cabinet)
- board position 3 in a PM55 Lower Shelf (iS3010 cabinet)

The PMC-SIC is a downloadable board with its own firmware package id: f19100.101.
The individual packages for the SIC and the PMC-G cannot be reused for the PMC-SIC.
The PMC-SIC firmware package can be downloaded from the CPU (using OM command INSTPK) or via a
TFTP server.

Download via TFTP server

- 22 -
The configuration file may be available in 2 formats, either a common file called prebpmc.txt or a specific
prebpmc<mac address>.txt. In general all PMC-SIC board will have the same application package, so one
common prebpmc.txt is normally sufficient. The PMC-SIC will however scan for both files.
The first line of the prebpmc.txt (or prebpmc<mac address>.txt) configuration file indicates the application
package that needs to run on the PMC-SIC.

An example of such a file is:

F19100v1.101

To enforce the PMC-SIC to perform a package load use OM command RESICI.

At power up of the PMC-SIC, an IP address with related netmask, default gateway and TFTP server (to
obtain the SIC configuration file) will be assigned using DHCP.
Operation without DHCP can be achieved by assigning an infinite lease to the PMC-SIC board. This is done
by including the following text in the PMC-SIC configuration file (identical to the prebisg.txt file of the ISG):

F19100v1.101
[Control]
DhcpLease=Reuse

First the package will be downloaded from the TFTP server when:

 The board is connected to Ethernet, and

 The DHCP server gives the address of a TFTP server, and
 The configuration file specifies another package than the currently loaded package, and
 The package is available at the TFTP server.

When one or more of these conditions is not met, the PMC-SIC starts up with its current package.

Download via OM Command INSTPK

Next the CPU will download a new package when:

 A package for the PMC-SIC is defined by INSTPK, and

 That package differs from the currently loaded package, and
 The new package is available at the LBU.

When both methods are active and define different packages, the PMC-SIC will first download the TFTP
package and then the INSTPK package.
So the package defined by INSTPK overrules the TFTP package.

WARNING: In case of upgrading an existing system (existing projecting) first modify the firmware
package relation to f19100v1.101 or use a "board-subtype" for the PMC, otherwise the
PMC-SIC will load a PMC-G (or PMC-MC) firmware package. When that is once loaded, the
PMC-SIC will not become operational.

The PMC-SIC provides the following basic telephony functions:

 32 tone sources:
 16 tone sources are reserved for DTMF signals, compliant with CCITT recommendation Q.23, and
 16 tone sources are free for customer projecting.
 6 key tone receivers (RKT): circuits 2, 3 & 4 and 7, 8 & 9.
 Note that 6 extra RKT’s can be configured (OM command ASPCTB) on circuits 24 … 29.

- 23 -
 4 dial tone receivers (RDT): circuits 5 & 6 and 10 & 11.
 32 three-party conference circuits (Add-On / Break-In circuit).
 Peripheral switching network.
 Protocol Co-Processor (PCP) providing 16 channels for Internal Message Protocol or HDLC
communication. Two of those 16 channels are reserved for CPU-PMC communication.

The PMC-SIC supports the standard Network Connection Cards: NCC-MC and NCC-HR.
To mount those cards, some extra connection material is required that is always supplied with the PMC-SIC
board.

2.4.3. SIC

The SIC must be placed on the right-hand side of the PMC position in a PM, IP-PM or RPM shelf:

- board position 18 in a 19 inch PM Shelf

- board position 18 in a PM1100 Shelf
- board position 8 in a PM255 Lower Shelf (iS3030 cabinet)
- board position 4 in a PM55 Lower Shelf (iS3010 cabinet)

The SIC is a downloadable board. The configuration file may be available in 2 formats, either a common file
called prebsic.txt or a specific prebsic<mac address>.txt. In general all SIC boards will have the same
application package, so one common prebsic.txt is normally sufficient. The SIC will however scan for both
files. The first line of the prebsic.txt (or prebsic<mac address>.txt) configuration file indicates the
application package that needs to run on the SIC.

An example of such a file is:

FC0000v1.101

To enforce the SIC to perform a package load use OM command RESICI.

The application package includes the boot package image of the SIC as well.
In case a new boot package is required, a new download (application) file must be present on the TFTP
server.
After the new download file is loaded, the application will program the new boot image into the flash
memory and after that, it will perform a reboot.

Note that a power-down during the boot upgrade process may lead to a defective SIC board !!!

At power up of the SIC, an IP address with related netmask, default gateway and TFTP server (to obtain the
SIC configuration file) will be assigned using DHCP. Operation without DHCP can be achieved by assigning
an infinite lease to the PMC-SIC / SIC board. This is done by including the following text in the SIC
configuration file (identical to the prebisg.txt file of the ISG):

FC0010v1.101
[Control]
DhcpLease=Reuse

- 24 -
2.5. APPLICATIONS

The ISS has more processing power than its predecessor the CPU3000. The additional capacity can be
applied to install a number of applications on the ISS. The applications that may be applied can be divided
into a number of categories:

 Call handling related applications.

 Management related applications.
 Service and maintenance related applications.
 OS related applications.

Even though the technical possibility exists to add additional features on top of SIP@Net, the number of
allowed applications on the ISS is limited. The reason for this is that quite some applications require
Windows 2008 server. Further the impact of the various applications on the performance of SIP@Net needs
to be determined before a decision is made to allow certain applications on the ISS.
In the table below an overview is given of the applications that can be seen as a candidate to run on the ISS.
For each application a description is given with an indication if it may be installed on the ISS as an additional
application. Notice that also XP related applications (e.g. Notepad) may be required for service related
activities. The elements mentioned here are required for diagnostic purposes; this is covered in detail in
section 2.9. Windows Embedded OS FOR THE ISS.
All other components not mentioned in the tables below will not be available on the ISS.

 Call handling related applications

DESCRIPTION PURPOSE
SIP@Net 4.3 Call control.
SIP driver Call handling on behalf of SIP *).

*) For the upgrade scenario of CPU3000 to the ISS, the SIP driver is already installed on the ISG or a
SIP@Net Server. To change the driver from ISG/external PC to the ISS is possible, but involves a
change in the configuration files of all SIP extensions.
An alternative change is to move the IP-address from ISG/external PC to the IP-address of the ISS
with this move the configuration files of all SIP extensions deos not need a modification. However all
IP connections on the CPU3000 for e.g. BCT, MA4000 has to be changed.
This would make an upgrade more complex and is therefore not advised. So keep the SIP driver on
the ISG/external PC and Move the IP-address of the CPU3000 to the ISS.
This would make an upgrade more complex and is therefore not advised.

 Management related applications

DESCRIPTION PURPOSE
Simple Alarming Alarm indication.

 Service and maintenance related applications

- 25 -
 DESCRIPTION PURPOSE
Diag@Net client and server. For diagnostic purposes.
System Info Console For diagnostic purposes.
iS3000 Convert For file format conversion.
 OS related applications

DESCRIPTION PURPOSE
CMDs Obtain the dos command prompt.
Windows Embedded XP or Windows
OS of the ISS.
Embedded Standard 7
DHCP Server *) Assign IP addresses to terminals, SIC, ISG etc.
TFTP Server **) TFTP is required for configuration purposes of the ISG, SIP
terminals, SIC configuration.
Windows Firewall For security. A preconfigured firewall is installed.
Event Viewer Required to display iS3000 alarming.
Internet Explorer To display HTML help information.
MSI Installer support Required to upgrade SIP@Net.
Notepad Required to look at text files, like log files, generated by
Diag@Net.
RegEdit Required to change registry entries.
Remote Desktop To gain access to the ISS Remote Desktop is applied.
Telnet Applied for Operational Maintenance.
Windows Explore Required to get access to the file system.
Wordpad To have the ability to make dumps of screenshots. For
diagnostic purposes.
Third party FTP server ***) For transferring e.g. all files on the LBU to another (backup)
server in the network.
Default it is NOT installed.

*) An installer version of the Uwe Ruttkamp DHCP server is made available.

Notice that also the firewall is opened for DHCP, during the installation.
Due to the fact that a freeware version of a TFTP server is selected, also the TFTP port is
opened at installation of the DHCP server.

**) As TFTP server the Jounin TFTP server will be delivered for the ISS.
The TFTP server is delivered as it can be obtained from http://tftpd32.jounin.net. The only
adjustment that has been done is the adjustment of the configuration file (tftpd32.ini) for the
TFTP server.
Details on the installation can be found in file tftpd32 service installation.txt.
The user interface can be adjusted by executing tftpd32_gui.exe. Via this interface it is
possible to select the proper base directory that TFTP applies.

The Jounin TFTP server (running as a service) will be delivered, together with a DHCP server in
a separate installer.

- 26 -
 ***) It is possible to install a third party FTP server, like FileZilla, on the ISS.
Note that it is the responsibility of the customer to take notice of the license
conditions/agreements to use this kind of third party software.

2.6. LICENSING

Detailed license related information can be found in the Software License Manual.

The following licenses are relevant for the ISS/ISS-2/ISS-3:

- 71: SIP Server, or : for SIP@Net on an external server: see note below.
- 72: SIP Server on ISS : for SIP@Net on an In Skin Server (ISS/ISS-2/ISS-3): see note below.
- 73: Start Upgrade Period : needed since SIP@Net 5.0.
- 79: Native SIP Server : since SIP@Net 6.0, when running in the "Native SIP mode" (system
option 179 is set to "1").

Note: For the SIP@Net Server always license 71 is needed, except when the ISS/ISS-2/ISS-3 is present, then
license 72 can be used also. So either license 71 or 72 is required !

License string for the ISS/ISS-2/ISS-3 is related to a USB dongle (Sentinel) or (since SIP@Net 6.2) to the Full
Computer Name. The fingerprint of an ISS/ISS-2/ISS-3 is fetched from the dongle or from the Full Computer
Name.

If option 179 "Native SIP Server" is set to "1", but license 79 "Native SIP Server" is absent, then Alarm Code
35, QLF 003 is raised.

Note that since SIP@Net 6.2 this License Warning Alarm Code 35, QLF 003 is not generated anymore. The
system will immediately degrade to basic functionality with the following other alarms:

- 082: UNLICENSED FACILITY ACCESSED, QLF 079 Native SIP Server.

- 036: LICENSE ALARM, QLF 004 Degraded to basic functionality.

License 73 (Start Upgrade Period) remains valid up to the expiry date. Note that the release date of license
73 may not be too low.

When no dongle or Full Computer Name is present (or the license file does not match the fingerprint of the
dongle), the system operates according the license file for 72 hours (3 days).

If no license file is present at start-up, the system operates with "basic functionality" (demo mode) meaning
10 SIP extensions, no licensed facilities: in these situations Alarm Code 36 is raised.

Take care that the dongle is plugged-in at an USB port before powering-up the ISS or starting up the
SIP@Net program on an external server.

It is possible that the ISS does not recognize the dongle. The LED in the Sentinel-USB-dongle is OFF. OM
command RTFING does not find a fingerprint and license Alarm Codes 035/036 (72 hrs degradation
warning) are raised. This problem can be solved by removing and reconnecting the dongle again.

In remote maintenance situation this removing and reconnecting the dongle is hardly possible. In that case
let the Windows Device Manager look for the new USB device.

- 27 -
2.7. SIP@Net SERVER CONFIGURATION

Instead of running SIP@Net on the ISS card, the system can also be controlled using an "external" SIP@Net
Server: then license 71 is needed. In this case there is no ISS required on the SIC board.
Both the SIP@Net Server and the SIC board are connected to the LAN network. In the SIP@Net Server the
IP link with the SIC board can be established, using OM commands CHSICI and RESICI.

2.8. SECURITY

The ISS is equipped with a preconfigured firewall. Notice that the ISS is delivered with the firewall switch
on.
The firewall is configured as given below: go to:

 Control Panel -> Windows Firewall -> Exceptions

 Notice that to operate SIP@Net Incoming echo requests may be turned off, however for diagnostic
purposes usage of 'ping' is quite often needed.
 Go to the "ICMP" settings.
This can be reached via the "Advanced" tab followed by selecting "Settings" under the ICMP section.

- 28 -
Because the firewall settings fully depend on the customers’ requirements and the functionality of SIP@Net
that is applied (e.g. is SIP applied or not) the firewall needs to be configured manually.
There are 2 ways to configure the firewall:

1. Make an exception for the application in the firewall. The firewall will make sure that all ports that
are applied by the application will be opened. Notice that is not the most secure way to configure the
firewall. Assume that for example no SIP is done on a specific system, this will take care that the SIP
port (2610) is made available for the outside world enlarging the vulnerability of the ISS.

2. Make an exception for a port that is used by SIP@Net. Notice that this does require some more
configuration effort but is the most secure way to configure the firewall.

Below the path that needs to be followed to make an exception in the firewall for an application is given.

 Go to "Windows Firewall -> Exceptions".

- 29 -
 Select "Add Program".
Now "Browse" to the application for which an exception needs to be made in the firewall.

The result is:

- 30 -
A similar path needs to be followed to allow incoming connection requests for a specific port.

 Go to "Windows Firewall -> Exceptions".

 Select "Add Port".

- 31 -
In the example above the SIP@Net port is opened: for a list of valid ports refer to
appendix A. PROTOCOLS AND PORT NUMBERS.

Since the ISS is controlled by Windows Embedded XP or Windows Embedded Standard 7 (WES7) the user
has the possibility to install virus scanners and use all the normal precautions to safeguard a secure
operation. The impact of virus scanners on the performance of the ISS may be severe and should be
prevented unless a customer demands the installation of virus scanners. The vulnerability of the ISS for
viruses is much less than for traditional desktops/laptops.
The reason for this is that:

 No additional software is installed by users, nor is the system used for other purposes than SIP@Net,
limiting the risk of infection by viruses.

 Windows Embedded XP or Windows Embedded Standard 7 (WES7) only contains the components that
are required for the operation of SIP@Net. Elements like Media Player and e-mail for example are not
available in the OS, reducing the vulnerability for viruses.

 Further the settings of the ISS are per default such that access of the ISS (by means of Remote Desktop)
is protected by means of a username and password.

 No additional programs shall be installed, nor shall access to the internet be done.

In the case where a user demands the installation of virus scanners, this is allowed when taking some
precautions:

 Don't do a full system scan; this will impose a high load on the ISS hampering a proper operation of
SIP@Net. A full system scan will increase the load to 100%. Notice that a call rate of 1 call/sec on the ISS
(XPE) imposes a load of roughly 7%.

 Prevent activity like updating of the virus scanner during normal operation of the ISS or plan the update
during non-office hours.

Basically the ISS is delivered with a well-known (and commonly used) default username and password. It is
the responsibility of the customer engineer to assure that this default username/password is replaced by a
more secure username and password combination.
Security updates for the Embedded OS appear with a lesser frequency than for example updates for
Windows 10. Therefore the following method is applied to make these updates available to our customers:

- 32 -
 If a customer wants to install the Embedded OS updates the moment they come available, he can do so
(but at the risk that this may disrupt a proper operation of his installation).

 Roughly once a year NEC Nederland B.V. composes a new Embedded OS image that incorporates the
latest security patches. This is synchronised with a SIP@Net release, assuring that this image functions
properly during the integration test of SIP@Net.

 The XPE image needs to be programmed on a flash disk following the procedure as described in
section 5.1. RE-INSTALLATION OF EMBEDDED XP.

 The WES 7 image needs to be programmed following the procedure as described in section 6.4.
RESTORE A NEW (OR INITIAL) WES 7 IMAGE ON THE ISS-2/ISS-3.

Notice that when such an upgrade is done SIP@Net and its related projecting files needs to be re-
installed.

2.9. Windows Embedded OS FOR THE ISS

Windows XP Embedded and Windows Embedded Standard 7 is pre-configured and contains (on top of the
items that are required to control the ISS and the items mentioned in section 2.5. APPLICATIONS) the
following additional components:

APPLICATION PURPOSE
Drivers for USB usage For back-up
Hardware watchdog To prevent board hang-ups
File sharing File transfer
SNMP Agent Used for alarming

The customer is not allowed to add applications and/or functionality others then described in this
document. Other applications may cause unpredicted behaviour and cause a high load on the ISS
influencing the performance of SIP@Net. The OS is only available in the English language.
Furthermore one user account with username Admin and password Admin is created. For security, during
installation the password has to be modified by the Customer Engineer.

For as far as security updates are concerned, a complete new OS image on a regular basis, incorporating
the available security updates can be obtained via the regular channels. By no means is it recommended to
have those security updates installed by the customer. The reason for this is that it is not always clear what
the impact of the security patches will be.
The ISS is equipped with a watchdog, to guard against hang-ups.

- 33 -
2.10. EXTERNAL ALARMING VIA V.24 ON USB

This functionality offers Alarm Signalling via V.24 on an iS3000 with a ISS (or external server). It is based on
the External Alarm Signalling that is offered on the CPU3000 (via the top connector at the front).

When system option LOSYSOP 187 (Use External Alarming Via USB) is set to "TRUE", then SIP@Net will
search for an active V.24 port that is connected via an USB-port. When it is found the V.24 port will be
initialised and the current alarm situation will be copied to the corresponding pins. The pins will be updated
whenever a Major or Minor alarm appears or disappears.
Blocked alarms will not be signalled, unless system option LOSYSOP 067 (SAS Alarm Handling V.28 Signalling
Ored) is set to "TRUE". Then all alarms (Major/Minor/Blocked) are signalled as Major.

Furthermore system option LOSYSOP 049 (SAS AH SAD Present) is set to "FALSE" and system boundary
LOBOUND099 (SAS AH Default Alarm Distribution) must be set to 2, meaning alarm distribution to
operator, but if not present then to the MDF.

SIP@Net connects to the first USB-V.24 connector based on a string provided by the USB-driver. So more
than one V.24/USB ports in the system is not advised: it may lead to unexpected events.
Unfortunately not all USB-V.24 converters supply that string and (even worse) Windows 7, Windows 8 and
Windows 2012 don't supply that string, but a significantly changed one. The NEC preferred USB-V.24
converter only works on desktop variants of Windows (e.g. XP on ISS). Therefore it is advised to use the
following alternative.

Since SIP@Net 5.3.3 it is possible to configure the COM port used for External Alarming based on its COM
port number. This is implemented by means of system boundary 460 (COM port number for external
alarming). When a value is specified, SIP@Net will use the corresponding COM port for External Alarming.
In that case system option 187 (Use External Alarming via USB) is ignored.
External Alarming will only be started when either system option 187 or system boundary 460 is set at
start-up. Option and boundary changes are executed immediately, provided the functionality is running.

REMARKS

 The time to activate the USB-to-V.24 driver in Windows XPE is ± 30 seconds.

The driver to be loaded is the "UC232A\Windows series\UC-232ADriverInstaller.exe" which belongs to
the equipment.
 As long as no V.24 port (connected via USB) can be found, or when the connection was lost, SIP@Net
will try to open a V.24 port every 30 seconds.
 When SIP@Net is not running the pins will fall-back to the OFF (= Alarm present) state.
 During Windows-start-up the V.24/USB port will be initialised. This leads to an undefined pattern of
ON/OFF for the 2 pins. It will eventually result in the OFF (= Alarm present) state of both pins.

Dual Server / Server Cluster Aspects

In case the ISS is used in a Dual Server or Server Cluster configuration the following aspects are relevant.
In a Server Cluster configuration in which the Master Server is a Windows 2008/2012 Server and the Slave
Server is an ISS, the same COM port number must be specified on the Windows 2008/2012 Server and on
the ISS. So it is important to which USB outlet the serial-over-USB cable is connected.

In the Stand-by Server (Dual Server configuration) the alarm LEDs (via the USB-V.24 converter) are switched
off when going into Stand-by mode. New alarms are generated and can be read out (DIMAJA, DIMINA or
DISILA), but the LEDs will remain switched off. When a Stand-by Server becomes Active (or enters the
"Split" or "Negotiating" status) the LEDs will be lit according to the presence of alarms at that moment.

When a server is the Stand-by Server or the Slave Server, no updates are made in the Windows Log
Register. The Windows log register can be viewed by the event viewer.

- 34 -
Pinning of the USB - V.24 converter

The following pins are used on the USB - V.24 converter (D9 connector):

SIGNAL PINS DESCRIPTION

Request To Send (RTS) 7 Major Alarm
- ON means: no alarm
- OFF means: Major Alarm(s) present
Data Terminal Ready (DTR) 4 Minor Alarm
- ON means: no alarm
- OFF means: Minor Alarm(s) present
Common Ground (G) 5 Signal ground

The typical level for a logical "0" is in between 0 V and 0.8 V.

The typical level for a logical "1" is 2.2 V (or higher)

- Alarm present : - 6.4 V

- No alarm present : + 6.4 V

2.11. JOURNALLING OF DYNAMIC DATA

When the iS3000 with an ISS performs a restart, either by manually restarting the service or caused by a
(software-) exception, the system is re-projected and all dynamic data is lost. For example the registration
of SIP terminals must be awaited before calls to and from SIP-terminals are possible.
To reduce the impact of a restart, changes to relevant dynamic data are saved in the journal file and are
restored after a restart by the normal execution of the journal file.

Journalling of dynamic data is available (since SIP@Net 4.5) when system option 190 'Enable journaling of
dynamic data' is 'yes'. It is advised to set this option to 'yes' (on the SIP@Net platform with an external
server or ISS) and to 'no' (default) on an iS3000 platform with CPU3000/CCS.

For more details: see the "SIP@Net Server CE Manual".

- 35 -
2.12. DIAGNOSTIC TOOLS

When the SIP@Net Server is successfully installed, the following diagnostic tools automatically become
available:

- Simple Alarming
- System Info Console
- Diag@Net

Furthermore the Windows Event Viewer can be used for diagnostics.

For more details: see the "SIP@Net Server CE Manual".

2.13. SIMPLE NETWORK MANAGEMENT PROTOCOL (SNMP)

With help of the (pre-installed) tool "evntwin.exe", the SIP@Net program log-events can be configured to
be translated into SNMP traps. An SNMP Trap is an SNMP message that is autonomously sent by an SNMP
Agent application to one or more SNMP Management applications.

For more details, see the "SIP@Net Server CE Manual", how to configure the MSWindows SNMP Agent to
generate SNMP Traps for the SIP@Net events.

2.14. MULTI PARTY CONFERENCE ON THE ISS

Multi Party Conference can be realized, using the CFC board(s). However, in case the CFC board is not
available, one can realize it by installing the Media Server on an ISS.

• in case the ISS is mounted on a PMC-IP board, one can use the ISG/IPG channels on the PMC-IP: take
care for sufficient licenses 59 (ISG channels).

• in case the ISS is mounted on a SIC or PMC-SIC board, next to sufficient licenses 59, also an ISG board
must be installed.

• in case no SIP driver is available yet, one also have to install the SIP driver, preferable on the ISS and
otherwise on the ISG board.

In the SIP Signalling Group of the SIP trunk to the Media Server, the Media Access Code of the ISG/IPG ("75"
in the example below) must defined.

<DIIPPD:B001;
SIG-GRP LANGUAGE ACCESS-CODE GATEKEEPER CODECS PAYLOAD RFC-2833 ROTA
B001 - 75 0.0.0.0 1 2 0 - 20 101 -
etc.

On the iS3000 platform, the parameter "ROTA" in the SIP Signalling Group (B001) has no meaning: this is
only relevant on a SIP@Net Server platform (system option 179 is set to "1").

For further details: see the "SIP@Net Server CE Manual" and the "SIP in iS3000 CE Manual".

- 36 -
3. INSTALLING THE ISS
This chapter describes how to install the ISS in new systems. For upgrading a CPU3000 to ISS, see chapter 4.
HOW TO UPGRADE A CPU3000 TO ISS.

3.1. PREPARATION

Although there is already a pre-installed Windows Embedded Standard 7 OS version present on the ISS-
2/ISS-3, it is advised first to create a:

• Bootable WINPE USB memory device as described in section 6.1.

This bootable USB memory device is needed to be able to handle images (creating/restoring).
• Clean image of the Windows Embedded Standard 7 OS as described in section 6.2.
This image can be used as a back-up.

For installing the ISS the following has to be prepared.

1. Collect the SIP@Net Server Installer software from the NEC SoftWare DataBase and copy this on the
"Remote Desktop" PC from which you do the installation.

2. Check that there is a DHCP/TFTP server in the network: when not available, the ISS can be accessed
using its Alternate IP address 192.168.1.15 and Subnet mask 255.255.255.0.
See also section 2.3.1. Ethernet Port for SIP.

3. Connect the top (ISS) and bottom (SIC) Ethernet connector to the LAN.

4. Connect the Sentinel dongle to one of the USB ports.

5. Power-up the ISS.

6. The DHCP server handouts 2 IP addresses: one to the SIC and one to the ISS.
Take care that those 2 IP addresses are static addresses.

7. Continue with configuring the Remote Desktop.

- 37 -
3.2. CONFIGURE REMOTE DESKTOP

On the ISS/ISS-2/ISS-3, first specify that users are allowed to connect to the ISS/ISS-2/ISS-3 remotely:

1. On the ISS, go to:

Control Panel-> System Properties-> Remote

on ISS (Windows XPE) on ISS-2/ISS-3 (WES7)

The Remote Desktop is configured as follows:

1. Now set up a Remote Desktop Connection to the IP address of the ISS as follows:
Programs-> Accessories-> Communication-> Remote Desktop Connection

Or go to:
Start -> Run and type in "mstsc"

2. Fill in the IP addresses of the ISS (or the computer name "ISS").

3. Select "Options".

- 38 -
4. In the "General" tab fill in "Admin" as the User Name and Password.
Optionally you can select "Save as ... " to create an "RDP" icon on the desktop labelled for example:
"ISS".

5. In the "Local Resources" tab select "Disk drives": this automatically connects the local "Disk drives" to
the remote computer.

6. Select "Connect".

WARNING:
Every time the ISS-2/ISS-3 is disconnected from the on-board battery on the SIC/PMC-SIC/PMC-IP
(the ISS-2/ISS-3 is removed from the board), the date & time of the ISS-2/ISS-3 is reset to a date in
the past. This old date & time give problems, in case a Remote Desktop connection is set up from a
Windows 2008/2012 Server. An error message is given that there is a too large time discrepancy
compared to the actual date & time.
In this case first a local monitor/keyboard/mouse is needed, to set the actual date & time in the
ISS-2/ISS-3.
Setting up a Remote Desktop connection from a Windows 7 PC gives a warning, but the connection
can be made. So, the advice is to use a Windows 7 PC for the Remote Desktop connection.

- 39 -
7. First plugin the Sentinel dongle in one of the USB ports (when not already done):

● Cancel the "New Hardware Found wizard" and then

● Run the "SIP@Net Server installer" including "Sentinel Protection Installer".

When this is not done, the Sentinel dongle driver cannot be found and the following screen pops-up.

8. Via "Start" and "Explore" you can browse to the OS of the ISS:

● XPE represents "Windows XP Embedded" (in case of an ISS).

● WES 7 represents "Windows Embedded Standard 7 OS" (in case of an ISS-2/ISS-3).
● the other drives for example "C on NEC" are the drives on your local PC.

- 40 -
 In the screen dump below the SIP@Net Installer is available on the PC from which you do the
installation as done in the step 1, in section 3.1. PREPARATION.

3.3. PASSWORD POLICY (optional)

Default the PW expires after 42 days. This means that when a service engineer visits the same customer
(system with ISS) after more than 42 days, the PW is expired and the engineer cannot log in anymore. You
can adapt the Password Policy as follows:

Control Panel -> (System and Security ->) Administrative Tools ->
Local Security Policy -> Security Settings -> Account Policies ->
Password Policy

 Maximum password age (default value is 42 days).

Determines the period of time (in days) that a password can be used before the system requires the
user to change it. You can specify that passwords never expire by setting the number of days to 0.
You can set passwords to expire after a number of days between 1 and 999.

- 41 -
 Enforce password history.
Current value: 0 passwords remembered.
One can re-enter the same password again.

 Minimum password age.

Current value: 0 days.
Allows user to immediately change his password again (and again).

 Minimum password length.

Current value: 0 characters (not advised).
Password may be changed into empty password.
This is not advised, because at attempt to login without password, one gets error message: "Unable to
log you on because of an account restriction." This is a restriction of Remote Desktop. One is required to
connect a local keyboard and monitor to login now.

 Passwords must meet complexity requirements.

Current value: Disabled.

 Store password using reversible encryption for all users in the domain.
Current value: Disabled.

3.4. INSTALLATION

Before installing SIP@Net it is advised to:

 Check/set the Date and Time of the Windows server.

 Check/set the required IP address/Subnet Mask of the Windows server.
 Clear the Windows Event Viewer to simplify troubleshooting in case the installation is not successful.

3.4.1. Installation of SIP@Net

1. Collect the SIP@Net 6.x Installer software from the NEC SoftWare DataBase and copy this on the
"Remote Desktop" PC from which you do the installation.

2. Double click the "Autorun.exe" file: the following "Welcome" screen is displayed.

- 42 -
3. Select the "SIP@Net Server" and select "Install".

4. Select "Install".

- 43 -
5. Select "Yes".

6. Select "Yes".

7. Select "Next".

- 44 -
8. Accept the "License Agreement" and select "Next".

9. Select "Next" for the default destination folders, or

Select "Change" to choose other destination folders, if required.

- 45 -
10. Select "Single Server" configuration and, for the iS3000 platform, fill in the Unit number (1 ... 14). This
Unit number is only relevant when having an existing system configuration, for example PE05 & LL05
files: then, in this case, one have to specify here Unit number "5".
Although the Unit number might suggest it, the ISS/ISS-2/ISS-3 can never be part of an existing multi-
unit configuration. Therefore it is advised to set system option 0 (multi-unit configuration) to "0"

Note that the three "Redundant Server" possibilities are only relevant for the SIP@Net Server
platform in a Dual Server LAN / WAN or in a Server Cluster configuration.

See the SIP@Net Server CE Manual for more details of the various "Redundant Server"
configurations.

Select "IPv4 Enabled".

Note that IPv6 Enabled and Dual Stack (both IPv4 and IPv6) is not possible for the ISS, running
Windows XPE.
Once the system is operational check whether system boundary 448 is set accordingly:

- 0 = IPv4 only
- 1 = IPv6 only
- 2 = both

- 46 -
11. Fill in the Application Interface IP address this is the IP address of the ISS. Select "Next".
It is not most likely, but in case of using a remote dongle server, fill-in the IP address of that server.

12. Fill in the various Port numbers and select the Firewall options: then select "Next".

- 47 -
 The Quality of Service (QoS) can only be set on the ISS-2/ISS-3 with WES7 image 2.2.2 (or higher)
using the "Policy-based QoS".
QoS cannot be configured on an ISS, running Windows XPE.
For more details how to set the QoS, refer to the "SIP@Net Server CE Manual".

Note that a couple of port numbers specified is also represented by a system boundary.
The port numbers for iTMP and CCIS are only relevant for the iS3000 platform.

After the complete installation procedure is finished, the specified settings filled in can be checked in
the Registry as follows:

Go to the "Registry Editor"

-> HKEY_LOCAL_MACHINE -> SOFTWARE -> iS3000 -> SIP@Net

13. In the next screen you can choose whether you want to load the
"Example PE/LL" (Demo configuration) or not.

● when selecting "This feature will not be available" no PE/LL files are loaded. This means that
after you have finished the installation, you have to load another existing customers projecting
(PE/LL file).

● when selecting "This feature will be installed on local hard drive", the "Example PE/LL" files are
loaded. This means that only 10 SIP ports are available and no license is required to run this demo
version.

- 48 -
 DO NOT USE THIS FOR OPERATIONAL SYSTEMS !

14. Select "This feature will not be available" and then "Next".
Keep in mind that you have to load a customer’s configuration (PE/LL file) later on.

15. Select "Install".

- 49 -
16. After the installation has completed select "Finish".

3.4.2. Installation of the SIP Driver

Now the installer continues with the option whether or not the SIP driver has to be installed.

• For (upgrading) an existing iS3000 platform system, it is most likely that the SIP driver is (already)
installed on one of the ISG board(s). In that case you can skip the installation of the SIP driver.
• For a new iS3000 platform system using SIP extensions and/or SIP trunks, the SIP driver is mandatory.
Continue the procedure as described in this section.
• For a SIP@Net Server platform system, the SIP driver is mandatory.
Continue the procedure as described in this section.

1. Proceed the installation procedure with the SIP Driver.

2. Select "Yes".

- 50 -
3. Select "Next".

4. Accept the "License Agreement" and select "Next".

- 51 -
5. Select "Next" for the default destination folder, or
Select "Change" to choose another destination folder, if required.

6. It is most likely that the SIP driver runs on the ISS, so fill in twice the IP address of the ISS.
The field "SIP Interface" holds the IP address of the network interface that the SIP driver will start
listening on.

- 52 -
 The field "SIP@Net IP address" is the IP address SIP@Net is running on.

Note that the SIP driver will always listen to one specific interface. Make sure that that interface is
reachable by the SIP extensions!

After the complete installation procedure is finished, the specified settings filled in can be checked in
the Registry as follows:

Go to the "Registry Editor"

-> HKEY_LOCAL_MACHINE -> SOFTWARE -> iS3000 -> SIP Driver -> Options

7. In case you use the built-in certificate, leave the 3 fields empty and select "Next".
In case you want to use another certificate (instead of the built-in certificate), enter the certificate
strings here, by specifying the full path, as illustrated below.

Certificate C:\Program Files\iS3000\SipDriver\Certificates\CryptoShark.server.crt

Private Key C:\Program Files\iS3000\SipDriver\Certificates\CryptoShark.server.key

Trusted C:\Program Files\iS3000\SipDriver\Certificates\CryptoShark.root.crt

Note that the last field (trusted root certificate) only has to be specified when the SIP@Net Server
acts as a client. This is the case when having a SIP trunk to another SIP Server.

- 53 -
8. Select "Install".

9. After the installation has completed select "Finish".

- 54 -
3.4.3. Installation of the Media Server

Now the installer continues with the option whether or not the Media Server has to be installed.
The Media Server is used to provide:

• various (progress) tones

• a Music-on Hold
• various announcements
• multi-party conference

On an iS3000 platform system, this part can be skipped, because in that system the first three functions are
provided by the traditional hardware like the PMC, MOH and IAS. However, if you want to use the "multi-
party conference" functionality (formerly offered by a CFC board), the complete Media Server has to be
installed.

On a SIP@Net Server platform, the Media Server is mandatory.

The Media Server is used for tones, DTMF-detection, announcements, MOH and conference circuits.
However it is advised to set system option LOSYSOP188 (Use ISG/IPG instead of Media Server for DTMF
detection) to "TRUE". In that case, the ISG/IPG is used for DTMF detection (only in the initial dialling and
enquiry dialling phase) instead of the Media Server. For all other situations like post dialling and MOH still
the Media Server is used.

This option is mainly relevant to reduce the load of the Media Server.

Continue the procedure as described in this section.

1. Proceed the installation procedure with the Media Server.

2. Select "Yes".

- 55 -
3. Select "Next".

4. Accept the "License Agreement" and select "Next".

- 56 -
5. Select "Next" for the default destination folders, or
Select "Change" to choose other destination folders, if required.

6. Fill in the two IP addresses and the Country Code (for the correct tones) and select "Next".

- 57 -
 ● Interface
When the Media Server is running on the same server as SIP@Net, then this IP address is the
same as specified in step 8 in subsection 3.4.1. Installation of SIP@Net.

● SIP-Driver IP
When the SIP driver is running on the same server as SIP@Net, then this IP address is also the
same as above.
In case the Media Server or SIP Driver are installed as separate components on another Windows
server than the one where SIP@Net is installed on, then fill in the IP address of that other server.

7. Specify the codecs used by the Media Server.

By default all codecs are enabled in order (highest priority first):
"G.711 ALaw --> G.711 µLaw --> G.729A".
For priorities 2 and 3 it is also possible to select "none".
In that case the Media Server always use the codec specified as "Priority 1".

IMPORTANT NOTE:
When the Media-Server is installed on an ISS, then in general one is advised not to configure the
G.729A codec, because an ISS can support only a limited number of media-channels with G.729A
codec. For an ISS (XPE) the number is 5 and for an ISS-2/ISS-3 (WES 7) the number is 25.
One have to configure this in:

• the installer of Media-Server in menu "Codec Selection" as shown above.

• the IP-projecting data of SIP trunk-lines and SIP extensions (CHIPPD), in case non-P2P SIP-trunk,
FCM 86 (Non Peer to peer media), FCM 87 Voice recording, or Voice-logging (CHVLRE) are used.

- 58 -
8. Specify the parameters for the Multi Party Conference function: see the SIP@Net Server - CE Manual
for more details.

9. Default, the Voice Recording .wav files are stored on the ISS/ISS-2/ISS-3 itself, in the directory
specified in the above screen.

- 59 -
 Select "Change" in case (from a management point of view) you might want to have the voice
recording .wav files stored on a central database on another server in the network. The side effect of
this solution is that it also saves disk space on the ISS/ISS-2/ISS-3.

10. Browse to the other server and directory.

Keep in mind that to this end, the ISS/ISS-2/ISS-3 must be placed in a Domain and that the directory
of the other server must be shared to the ISS/ISS-2/ISS-3.

Note that the Media Server will continue recording until the configured threshold of minimum free
disk space is reached. In case the threshold is reached the voice recording function stops and a Media
Server alarm (Alarm Code/QLF 063:005) is generated.

- 60 -
11. Choose for a "Complete setup" and select "Next".

12. Select "Install".

- 61 -
13. After the installation has completed, select "Finish".

After the complete installation procedure is finished, the specified settings filled in can be checked in
the Registry as follows:

Go to the "Registry Editor"

-> HKEY_LOCAL_MACHINE -> SOFTWARE -> iS3000 -> Media Server -> ms1

- 62 -
3.4.4. Installation of the Tools for the iS3000/SIP@Net Server

1. Proceed the installation procedure with the tools for the iS3000/SIP@Net Server.

2. Select "Next".

3. Select the destination folder and select "Next".

- 63 -
4. Choose for a "Complete setup" and select "Next".

5. Select "Install".

- 64 -
6. Select "Finish".

7. Now go to "Service and Applications" - "Services" and check that the following services are started:
- iS3000 SIP@Net Service
- iS3000 SIP Driver Service (when installed)
- iS3000 Media Server (when installed)

8. Go to the "SIP@Net OM" shortcut or go to "Run" and setup an OM session via "telnet <IP address>":
the IP address of SIP@Net (in this example 192.168.116.20).

9. Now an OM session can be opened, using "Ctrl-G".

REMARK: In the "Properties" of the telnet session window (right-hand mouse click on the top bar)
you can modify the various settings of the display. It is advised to put the height of the
Screen Buffer Size (in the "Layout" tab) to at least 700.

10. The system is running without a license.

One can check this by reading out the alarms in the usual way: OM commands DIMAJA, DIMINA,
DISILA, DIBLCK and DIHIBU.

11. Copy the SIP@Net Server license file in the following directory:

C:\Documents and Settings\All Users\Application Data\iS3000\SIP@Net

12. Execute OM command ACLICS to activate the loaded license.

- 65 -
13. Execute OM command DIDATI to check that the date and time of SIP@Net is in line with the date and
time of the server. Note that the date and time in SIP@Net cannot be set by OM command SEDATI.

14. Execute OM command CHSICI to set the IP address that the CPU will use to establish an IP link with
the SIC board, for example:
CHSICI:,,1,192.168.116.101;

Note that this IP address is the address handed out by the DHCP server to the SIC board. Only when
an IP address to the SIC has been projected by OM command CHSICI, the CPU will attempt to connect
to the SIC.

15. Execute OM command DISICI to display all information related to the SIC of the ISS. This includes the
following information:

 the loaded boot package and application package

 the IP address, default gateway, boot server, netmask with an indication if the IP address is a fixed
IP address or has been obtained using DHCP, and
 the status of the links for the PMC/CSN that are controlled via the SIC. Their requested status is
INS. The status shown is the current status.

Response example:

<DISICI:;
SIC IP ADDRESS NETMASK DEFAULT GATEWAY
192.168.1.101:2950 255.255.255.0 192.168.1.1

ETHERNET ADDRESS DHCP TFTP SERVER

00-18-27-00-63-9B Yes 192.168.1.251

SIC IP ADDRESS
[fd01:aaaa:0:22:38a7:bf2a:c35c:12f7]:2950

BOOT-PACK APPL-PACK HW-12NC HW-SERIAL#

C090.01.01 C000.01.01 9600-021-53003 SBxxx00012

SHELF BRD STATUS LPORT SIC IP ADDRESS SVR#

11 17 INS 20112 192.168.9.51:22094 10

16. Configure the Security settings as described in section 2.8. SECURITY.

3.4.5. Maintenance Aspects

- 66 -
• Date and Time
The iS3000 system synchronizes its date and time with the time of the Operating System of the ISS/ISS-
2/ISS-3 it is running on. This synchronization is done at least every minute. OM command SEDATI is not
supported on the ISS/ISS-2/ISS-3.
Note that "ISDN date/time synchronisation" is disabled on the SIP@Net Server.

• Maintenance & Management

The iS3000 can be managed via a "telnet session", MA4000 or the SMPC.
On the CPU3000 there is always a V.24 OM interface enabled. On the ISS/ISS-2/ISS-3 only clients that
have the OM service enabled can make a connection via IP. This is unwanted in case of (projecting)
failures. Therefore connections originating from the machine itself are always allowed. This is valid for
all services as defined with OM command CHPROF.

• Restart, Recovery and Backup

On the iS3000 platform, the system (re-)starts can be done by executing the various system start related
OM commands such as STCOLD (using the MIS file and journal file) and STPROJ (using the PE & LL file,
followed by the journal file). All system start related OM commands are not supported anymore on the
ISS/ISS-2/ISS-3 platform. On this platform, a system restart is executed by starting the "Services" in
Windows.

Also the MIS file mechanism is not supported anymore on the ISS/ISS-2/ISS-3 platform. SIP@Net starts-
up with the PE and LL projecting files, followed by the journal file. Depending on the amount of changes
made in the configuration, the journal file can become very large if it is never cleared. To avoid this
situation, OM command GEBUFI (Generate Backup File) has to be used: this command executes the
following as an automatic operation:

- Make a complete retrieve: network and local data, dynamic data and name-number relations. The
result will be a PR and OR file.
- Rename the retrieve files PR and OR back to PE and LL.
- Generate a new empty journal file.

The versioning mechanism takes care that always the latest PE and LL projecting files are used on a
restart. The maximum number of versions of the same file is 8.

• Location of the iS3000 Configuration Files

The directory ("LBU") where the iS3000 configuration files are stored is:

C:\Program Data\Application Data\iS3000\SIP@Net

Here the following files can be found:

- PE & LL and journal files
- License file
- MML files

- 67 -
4. HOW TO UPGRADE A CPU3000 TO ISS
4.1. PRECONDITIONS

 Note that iS3000 systems with a PMC-LU (in a PM250/PM1000 shelf), the CPU3000 can NOT be
replaced by the ISS !!!

 Collect the SIP@Net Server Installer software from our SoftWare DataBase and copy this on a PC in the
network from which you do the installation.

 Check that there is a DHCP/TFTP server in the network: when not available, the ISS can be accessed
using its Alternate IP address 192.168.1.15 and Netmask 255.255.255.0.
See also section 2.3.1. Ethernet Port for SIP.

 Check on what kind of board the ISS is mounted/used:

SIC + ISS : execute step 1a.
PMC-SIC + ISS : execute step 1b.
PMC-IP + ISS : execute step 1b.

 Check whether "FDCR over IP" is defined: if not, see section 4.4. CHANGE OVER TO FDCR OVER IP.

4.2. UPGRADING PROCEDURE

Upgrade using a SIC + ISS

Before removing the CPU3000 from the system, do the following actions in the CPU3000 environment !!!

1a. In case of systems having a PMC-G, upgrade the PMC to firmware package to F18100.801 (or higher).
INSTPK: F18100.801
In case of PMC-MC, no upgrade of the firmware is necessary.
Continue with step 2.

Upgrade using a PMC-SIC/PMC-IP + ISS

Before removing the PMC-G/MC and the CPU3000 from the system, do the following actions in the
CPU3000 environment !!!

1b. In case of upgrading an existing system (existing projecting) first modify the firmware package
relation to F19100v1.101 (or higher) or use a "board-subtype" for the PMC, otherwise the PMC-SIC
will load a PMC-G (or PMC-MC) firmware package. When that is once loaded, the PMC-SIC will not
become operational.
CHBDST:<EHWA of the PMC>,66;
INSTPK:F19100.101,,66;

When, in an existing projecting, an Operator circuit (signalling group 7D04) is projected on the PMC,
delete that circuit otherwise alarm code 61/6 is generated (error of assign signalling group to PCT).
Continue with step 2.

2. System option LOSYSOP 179 (Native SIP Server) must be "0".

Check this by executing OM command DIMDAT:1,179;
To set it to "0" execute OM command CHOPTI:179,0;

3. The various devices on the V.24 interfaces must be re-projected for IP. For example FDCR via V.24
must be changed to FDCR over IP.

- 68 -
4. Execute OM command DITCPC to find out the IP address of the CPU3000.
It is advised to use the same IP address for the ISS later on.

5. Execute OM command DILICS to find out the licenses granted.

6. Execute OM command RTRIEV to make a full retriev of the current customers configuration: rename
the PR and OR file to PE and LL.

7. Copy the projecting files (PE & LL) and all used firmware packages of the various PCT boards to the
PC from which you want to install the ISS.

8. Power-down the system for at least 1 minute.

9. Now remove the CPU3000 (or PMC-G/MC and CPU3000) from the shelf.

Continue with the following actions in the ISS environment !!!

Upgrade using a SIC + ISS

1a. Put the SIC + ISS in the CPU board position in the shelf.
Continue with step 2.

Upgrade using a PMC-SIC/PMC-IP + ISS

1b. Put the PMC-SIC/PMC-IP + ISS in the PMC board position in the shelf.
Continue with step 2.

2. Connect the top (ISS) and bottom (SIC/PMC-SIC) Ethernet connector to the LAN.

3. Connect the Sentinel dongle to one of the USB ports.

4. Power-up the system, including the ISS.

5. The DHCP server handouts 2 IP addresses: one to the SIC/PMC-SIC and one to the ISS.
Take care that those 2 IP addresses are static addresses.
Check whether the IP address of the ISS is the same as the IP address the CPU3000 had before.

6. Continue the installation by executing all steps as described in chapter 3. INSTALLING THE ISS.

7. When finished and SIP@Net is running on the ISS copy the projecting files (PE & LL) and all used
firmware packages of the various PCT boards (as obtained in the CPU3000 environment) to the LBU
of the ISS.

8. Finally restart the SIP@Net service.

Now the system becomes operational with the configuration it had before the upgrade.

9. Copy the new license file to the LBU and execute OM command ACLICS to activate the new licenses.
Check with OM command DILICS whether you have license 71 or 72.

10. Optionally one might have to change over to FDCR over IP: see section 4.4. CHANGE OVER TO FDCR
OVER IP.

- 69 -
4.3. ISS-2/ISS-3 IN iS3050 WITH CSN-BC BOARD

In case the ISS-2/ISS-3 is mounted on a SIC board, the board position directly on the right-hand side of the
SIC board cannot be used, because the heat sink is physically blocking that right-hand side board position.
This means that when the SIC board is in board position 18 in the top shelf of an iS3050 system, the CSN-BC
board in position 19 in the top shelf has to be moved to board position 19 in another PM shelf: PM shelf 12,
13 or 14.

Note that this is only relevant in case of a SIC: a PMC-SIC or PMC-IP is placed in board position 17, meaning
that the CSN-BC remains installed in position 19.

1. Execute OM command GEBUFI.

2. Execute OM command DIBRDS to check whether a board is projected in either PM shelf 12, 13 or 14,
board position 19.

3. Suppose board position 19 in PM shelf 12 is free.

Re-project the CSN-BC board to position 19 in PM shelf 12. This cannot be done by OM commands,
because the CSN-BC cannot be deleted using OM command DEBRDS: so this has to be done by
modifying the following subcommands in the LL file, generated in step 1.

WARNING: Do not execute a global replacement of "11,19" by "12,19" in the LL-file.

Existing projecting: CSN-BC New projecting: CSN-BC

in PM shelf 11, position 19 in PM shelf 12, position 19

S92410:10,11%19%,75;  S92410:10,12%19%,75;
| | | | | | | | |
S92430:11%19%22,11,11%17%;  S92430:12%19%22,11,11%17%;
S70100:0,11,19,22;  S70100:0,12,19,22;
S92430:11%19%23,11,11%17%;  S92430:12%19%23,11,11%17%;
S70100:0,11,19,23;  S70100:0,12,19,23;
S92430:11%19%24,11,12%17%;  S92430:12%19%24,11,12%17%;
S70100:0,11,19,24;  S70100:0,12,19,24;
S92430:11%19%25,11,12%17%;  S92430:12%19%25,11,12%17%;
S70100:0,11,19,25;  S70100:0,12,19,25;
S92430:11%19%26,11,13%17%;  S92430:12%19%26,11,13%17%;
S70100:0,11,19,26;  S70100:0,12,19,26;
S92430:11%19%27,11,13%17%;  S92430:12%19%27,11,13%17%;
S70100:0,11,19,27;;  S70100:0,12,19,27;;
S92430:11%19%28,11,14%17%;  S92430:12%19%28,11,14%17%;
S70100:0,11,19,28;  S70100:0,12,19,28;
S92430:11%19%29,11,14%17%;  S92430:12%19%29,11,14%17%;
S70100:0,11,19,29;  S70100:0,12,19,29;
| | | | | | | | |
S70100:0,11,19;  S70100:0,12,19;

4. Copy the modified LL file on the LBU and stop the SIP@Net service.

5. Move the CSN-BC board to position 19 in PM shelf 12 and re-arrange the cabling.

6. Re-start the SIP@Net service.

- 70 -
4.4. CHANGE OVER TO FDCR OVER IP

1. Although no physical V.24 ports are present on the ISS/ISS-2/ISS-3, still a Logical Device Name (LDN)
must be assigned to one of the "dummy V.24 ports" of the CPU in the shelf 11, board position 18,
circuit 20, for example:

ASDEVC:11,18,20,FDCR,33;
where "FDCR" is the LDN and 33 is the equipment-type "FDCR over IP".

2. Also the "FDCR" services must be defined and allowed in a Client Server Profile, for example:

CHPROF:1,3,1,FDCR;
where 1 is the "Client Service Profile ID", 3 means FDCR, 1 means allowed and FDCR is the LDN
defined with ASDEVC in step 1.

- 71 -
5. HANDLING IMAGES OF THE ISS
The ISS with Windows XP Embedded can be used to run either the SIP@Net or the BIM application.
Because of the fact that Windows XPE is declared "End of Service" at January 2016:

- the ISS-2/ISS-3 with Windows Embedded Standard 7 is introduced for running the SIP@Net application.
- the ISS with Windows Embedded Standard 2009 (WES2009) for running the BIM application.

See chapter 6 for handling the ISS-2/ISS-3 images.

Nowadays, the ISS is delivered (via FAS) with a preconfigured configuration of WES2009.
From the engineer point of view there is no real difference between Windows XPE and WES2009, with
respect to installing the BIM software and handling the XPE and WES2009 images on the ISS.

WARNING: In case of WES2009, never run the Windows Automatic Updates: this might result in a "blue
screen" situation.

5.1. RE-INSTALLATION OF EMBEDDED XP / WES2009

On a yearly basis (in general always in the first quarter of a new calendar year) NEC will release a new
version of the XPE/WES2009 image, which includes the latest MS/Security-Updates of the previous
calendar year. When necessary for urgent security reasons also intermediate releases can be possible.
To keep on track with those updates, it is necessary to do a re-install of Embedded XP/WES2009. Also for
emergency situations an image of the Embedded XP/WES2009 image is made available, which is installed
using SelfImage, on a separate PC.

Notice that there is no possibility to generate a full backup of the flash disk of the ISS (XPE/WES2009). The
reason for this is that creating a full backup of the flash disk is a very time consuming activity (roughly one
and a half with SelfImage).
Besides the fact that it is a time consuming operation, creating a backup also imposes a high load on the
CPU (50-70%) of the ISS (XPE/WES2009) and may therefore influence SIP@Net quite significant.

Under normal circumstances there is no need to fully re-install XPE/WES2009: normally only a re-install of
SIP@Net is required.

The XPE/WES2009 image is available in a compressed format that can be installed off line with a freeware
tool called SelfImage, which can be downloaded from http://selfimage.excelcia.org (or from the service
DVD). Creating a new flash will be done offline (by the Customer Engineer) for reasons mentioned earlier in
this section.

Compatible CF cards
If necessary, one can purchase an (extra) CF card locally. Note that that CF card must be an industrial type
because of the life cycle and wear levelling aspects.

Manufacturer Code number Description

Sandisk SDCFH-4096-388 UltraII flash card 4 GB 15 MB/s

Apacer AP-CF004GE3FR-NR(J) Industrial CFII standard Temp.

AP-CF004GE3FR-ETNR(J) Industrial CFII extended Temp.
AP-CF004GE3FR-NR(K)
AP-CF004GE3FR-ETNR(K)
AP-CF004GE3NR-NRQ

- 72 -
The following steps need to be taken to re-Install the XPE/WES2009 image.

1. Make sure you have the XPE/WES2009 image available, a PC with a flash card programmer
connected to your PC. Make sure SelfImage has been installed on the PC.

2. Start SelfImage.

3. Select the image that you want to put on the flashcard.

This gives the following screen output:

Be aware to select for the output location the entry for the "(entire disk)" of the Compact Flash
card. Do not select "Partition1" of the Compact Flash card and also not the hard-disk of the PC.

4. Press start: programming of the flash takes about 10 minutes.

5. Remove the flash card from your PC: ignore the "Stop Hardware Device" error message.

6. Re-insert the flash card: now Windows XPE/WES2009 is accessible.

For the projecting files, which are stored on a directory of the ISS (XPE/WES2009), the normal fire copy
mechanism applies. Note that in this case Remote Desktop, File Sharing or an USB memory stick can be
applied to obtain the projecting file from the flash disk: USB memory stick is faster compared to File
Sharing.

Windows XPE/WES2009 is not different compared with traditional XP. The OS has been configured in such a
way that only the relevant components available in XPE/WES2009 are applied.
For security reasons the access of ISS (XPE/WES2009) is limited to the access using Remote Desktop. File
sharing for example is available. It is up to the customer to decide if he wants to make use of these features
and how well he wants to have the access protected.

- 73 -
5.2. SELFIMAGE ON WINDOWS VISTA / WINDOWS 7

When you want to run SelfImage on a "Windows Vista" or "Windows 7" PC it will return the error message
"Access Denied". The cause of the problem can be that the privileges of the file "SelfImage.exe" are
insufficient.
Another reason can be that the Compact Flash card used, is formatted in FAT16/FAT32 or NTFS or any
other file system recognized by Windows.
In that case you will see an error screen like shown below:

To solve the problem do the following:

1. Change the properties of the file "SelfImage.exe" and check the option "Run as administrator" for all
users: compatibility TAB.

2. Next give all users, all access rights: Security TAB, e.g. Full control, Write etc.

3. If the Compact Flash card is formatted in any Windows file system format, like FAT16, FAT32 or NTFS,
Windows Vista and Windows 7 will not permit SelfImage to write on the Partion0 of the Compact
Flash card.
Continue with the next steps.

4. Open a command window as administrator ("cmd"): see note 1.

5. In the command window:

• Type "diskpart" and give "Enter".
• Type "list disk" and give "Enter" to find out the number of your drive: see note 2.
• Type "select disk X" (where X represents the number of your drive) and give "Enter".
• Type "clean" and give "Enter".

6. Now continue to use SelfImage to write a Compact Flash card with an image.

Note 1: Right-click the file cmd.exe (located in Windows\System32 directory) and check the option "Run
as administrator".

Note 2: If one hard-disk is present in the PC where the Compact Flash is connected to, the Compact Flash
card is "Disk 1". Check that the disk size corresponds to your Compact Flash card used.

- 74 -
5.3. READ OUT THE VERSION OF AN ISS IMAGE

To read out the version of an ISS image:

 Go to "System Properties" of the ISS: (My Computer / Properties):

 Select "Support Information" then the following window shows the version number and the build date:

- 75 -
6. HANDLING IMAGES OF THE ISS-2/ISS-3
A purchased ISS-2/ISS-3 "out-of-the-box" already contains a Windows 7 Embedded OS.
On a yearly basis (in general always in the first quarter of a new calendar year) NEC will release a new
version of the Windows 7 Embedded image, which includes the latest MS/Security-Updates of the previous
calendar year. When necessary for urgent security reasons also intermediate releases can be possible.
To keep on track with those updates, it is necessary to do a re-install of Windows 7 Embedded.
To be able to handle images (creating/restoring) of the ISS-2/ISS-3 it is necessary to have a bootable
memory device available.
Note that a "secured" USB memory device cannot be used as a bootable memory device.
Also not all types of "USB V3.0" memory device are working fine as a bootable memory device for WES7.
The following types are tested and verified:

Working USB V3.0 memory devices for WES7

• Transcend JetFlash 700 – USB Flash Station – 8 GB
• Toshiba TransMemory MX – USB Flash Station – 8 GB
• Sandisk Extreme – USB 3.0 Flash Drive – 16 GB

Failing USB V3.0 memory devices for WES7

• Verbatim Store 'n' Go V3 – USB Flash Station – 8GB
• Kingston DataTraveler 100 G3 – USB Flash Station – 16 GB

For creating a bootable memory device and handling the WES images, the following two .zip files have to
be downloaded from the NEC SoftWare DataBase/FTP site:

 960004040000_110_002_jjmmdd.zip
WinPE DISM bootstick
(jjmmdd represents the year, month and day: for example 170123
This .zip file contains all necessary files to create a bootable memory device with WinPE and DISM
(Deployment Image Servicing and Management tool).

 960004040000_110_003_jjmmdd.zip
This .zip file contains the actual WES7 image, named e.g. "NEC_ETE-PV510_V231.WIM".
A Windows 7 Embedded Image for the ETE-PV510 hardware, can be used in combination with the
WinPE DISM bootstick.

Note that a local monitor, USB keyboard and mouse have to be connected to the ISS-2/ISS-3, to be able to
handle the ISS-2/ISS-3 images.

6.1. CREATE A BOOTABLE WINPE USB MEMORY DEVICE

A bootable USB memory device (stick) can be created by executing the following steps:

1. Download the 960004040000_110_002_jjmmdd.zip file from the NEC SoftWare DataBase/FTP site.

2. Unzip the zip file and copy the contents on the USB memory device which you want to make
bootable.

3. Connect a local monitor, USB keyboard and mouse to the ISS-2/ISS-3.

4. Connect the USB memory device to the ISS-2/ISS-3.

A pop-up window appears.

- 76 -
5. Copy the folder "bootstick" onto the desktop.

6. Navigate to the folder <desktop>\bootstick\tools\bootstick.bat

Be sure that the bat file is selected.

7. Click the Right Mouse Button on the bootstick.bat file.

Select "Run as administrator".
A batch file is starting, with diskpart, formatting and a xcopy session: see screen shot.

The xcopy makes a copy of the bootstick folder to the memory device.

WARNING
The USB memory device is formatted.
Be sure that no other memory devices are connected.
The USB memory device to be formatted is drive D:.

To test the USB memory device go to Start (left under) and restart the ISS-2/ISS-3.
Press F10 to pop-up the boot list.
Select the USB memory device from the boot list.

At the end a DOS window starts with wpeinit.

After a while the DOS prompt is present.
In principle the directory on the desktop can be deleted (manually).

Used tooling: WinPE version 6.2.9200

DISM version 6.2.9200.16384

- 77 -
Both WinPE and DISM versions are based on Windows 8. Only this one is correct!
Once a bootable USB memory device is created it is possible to:

 Create an image of the ISS-2/ISS-3, including SIP@Net to be used as a back-up.

 Restore an existing image on the same or on another ISS-2/ISS-3.

6.2. CREATE AN IMAGE OF THE ISS-2/ISS-3

It is up to the maintenance engineer to decide what kind of image he wants to create. For example, an
image of the Windows Embedded Standard 7 OS plus the operational SIP@Net program, to be used as a
back-up of an existing SIP@Net configuration.

1. Connect a local monitor, USB keyboard and mouse to the ISS-2/ISS-3.

Be sure that no other memory devices are connected to the ISS-2/ISS-3.

2. Connect the bootable USB memory device to the ISS-2/ISS-3.

3. Power-up the ISS-2/ISS-3.

4. Use F10 during startup.

In the boot menu, select "USB HDD": the USB memory device.
• The SSD is drive C:
• The USB memory device is drive D:

5. Wait until "X:\windows\system32>" is shown.

6. Go to the root of the USB memory device:

D: <CR>

7. Start the batch file:

D:\>DoCopyFromSSD.bat <FileName><CR>
TIP: Type "doc" followed by the "Tab" key.

If no file name is given, then the default image file name "SSD16GB.WIM" is created.

DISM will now create an image file on the memory device.

Creating the image takes ≈ 20 minutes.

8. Wait for:

Saving Image
[================ 100% ================]
The operation completed successfully.
D:\>

9. Type "D:\> dir" and check that an image file (e.g. SSD16GM.WIM) is present on "D": the drive of the
USB memory device.
This created image file can be used to restore this image on the same or on another ISS-2 or on
another ISS-3.

10. Power down the ISS-2/ISS-3.

- 78 -
11. Remove the USB memory device and power up the ISS-2/ISS-3.

6.3. RESTORE AN EXISTING IMAGE ON THE ISS-2/ISS-3

In case an image has been created, as described in the previous section, it can be restored on the same or
on another ISS-2/ISS-3. On the root of the USB memory device the image file, e.g. "SSD16GB.WIM" file must
be present.

1. Connect a local monitor, USB keyboard and mouse to the ISS-2/ISS-3.

Be sure that no other memory devices are connected to the ISS-2/ISS-3.

2. Connect the bootable USB memory device to the ISS-2/ISS-3.

3. Power-up the ISS-2/ISS-3.

4. Use F10 during startup.

In the boot menu, select "USB HDD": the USB memory device.
• The SSD is drive C:
• The USB memory device is drive D:

5. Wait until "X:\windows\system32>" is shown.

6. Go to the root of the USB memory device:

D: <CR>

7. Start the next batch file:

DoRestoreToSSD.bat <FileName><CR>
Where < FileName> is the name of the image file to be loaded on the ISS2/ISS3.
If no file name is given, then the released image file name is assumed.
TIP: Type "dor" followed by the "Tab" key.
e.g.: DoRestoreToSSD.bat SSD16GB.WIM

Wait (≈ 15 minutes) for

check for errors
press spacebar
Check the screen for errors.
Press spacebar to reboot the ISS-2/ISS-3.

6.4. RESTORE A NEW (OR INITIAL) WES 7 IMAGE ON THE ISS-2/ISS-3

A new ISS-2/ISS-3 "out-of-the-box" already has the WES 7 image pre-installed.

In case one has to upgrade this image (or in the exceptional case that the installed WES 7 image is
corrupted), one have to restore a complete new image on the ISS-2/ISS-3.

The procedure to restore a complete new image is quite similar to the procedure described in the previous
section 6.3.

1. Download the 960004040000_110_003_jjmmdd.zip file from the NEC SoftWare DataBase/FTP site.

2. Unzip the zip file and copy the "NEC_ETE-PV510_V2xx.WIM" file to root of the bootable USB memory
device.

- 79 -
3. Execute steps 1 … 12 as described in the previous section 6.3.
In step 7 use “DoRestoreToSSD.bat NEC_ETE-PV510_V2xx.WIM”, corresponding the file name of the
released image.

6.5. READ OUT THE VERSION OF AN ISS-2/ISS-3 IMAGE

To read out the version of an ISS image:

• Go to "Computer" and select "Properties":

- 80 -
6.6. WINDOWS UPDATE

Instead of loading new images every now and then (to keep track on the latest Windows updates), it is
possible to use the "Windows Update" mechanism on an ISS-3
This function is also made available on the ISS-2 WES 7 with image 2.3.1 (and higher). Check that sufficient
disk space is available to install the updates, especially if you are using an ISS-2.
It is advised to collect the Windows Updates from a dedicated Windows Server Update Services (WSUS)
server within the company’s network.
Although it says "recommended", do not choose "Install updates automatically". This might cause that
SIP@Net is temporarily down because the ISS-3 is restarted. Execute the updates in a controlled way, by
either selecting:

- "Download updates but let me choose whether to install them"

or
- "Check for updates but let me choose whether to download and install them"

How to collect the updates

1. Go to "Computer", select "Properties" and select "Windows Update" (bottom left).

2. Check for updates (upper right).

This will take a couple of minutes, depending on processor load, network performance, etc.

3. Select all updates for installation.

4. After the installation, verify the functionality of the ISS-3.

In principle the SIP@Net software is running normal.

During the installation of security updates, the old files are hidden stored in the system directories.

- 81 -
With the tool "Disk Cleanup", these files can be removed.

1. Go to "Windows" flag (bottom left in the task bar).

2. Type in "Disk Cleanup" in the "Search programs and files".

The calculation takes many minutes.

3. Select "Clean up system files": again, wait a while.

4. Select everything, especially the "Service Pack Backup Files".

5. Click OK: clean process is running.

6. When ready, restart the ISS-3.

- 82 -
7. INCOMING RAS CONNECTION FOR REMOTE MAINTENANCE
An incoming Remote Access Services (RAS) connection for Remote Maintenance can be realized using USB
modems.
The modems used (tested and verified) for the RAS connection are:

- USRobotics : 56K USB Modem, model 5637

- Conceptronic : 56K USB voice/fax/modem

7.1. MODEM PREPARATION ON ISS/ISS-2/ISS-3

7.1.1. ISS with Windows XPE

1. Connect the USB modem (Conceptronic) to the ISS.

2. Check that the device drivers are installed correctly.

3. Open network connections.

4. Create a new connection.

- 83 -
5. Select "Next".

6. Select "Setup an advanced connection" and select "Next".

- 84 -
7. Select "Accept incoming connection" and select "Next".

8. Select your USB modem, check the properties and select "Next".
The modem type listed here is the Conceptronic 56K USB voice/fax/modem.

- 85 -
9. Select "Do not allow virtual private connections" (VPN) and select "Next".

10. Specify the users: select "Admin" and select "Next".

- 86 -
11. Select "Internet Protocol (TCP/IP)" and select "Properties".

12. Select the following:

- "Allow Callers to access my local area network".
- "Allow calling computer to specify its own IP Address".
- "Specify TCP/IP addresses" and specify an IP range, for example:
192.168.116.50 … 192.168.116.99

13. Select "OK".

- 87 -
14. Select "Finish".

15. Keep the window with network connections open, so you can watch what happens.
After the Host PC is configured too and an incoming RAS connection is then set up, you will see the
following:

Now, continue with the steps as described in sections 7.2. MODEM PREPARATION ON THE HOST PC and
7.3. SET UP A RAS CONNECTION TO THE ISS.

- 88 -
7.1.2. ISS-2/ISS-3 with WES7

1. Connect the USB modem (Conceptronic) to the ISS-2/ISS-3.

2. Check that the device drivers are installed correctly.

3. On the ISS-2/ISS-3, open "Network Connections".

Go to "Control Panel" -> "Network and Sharing Center" -> "Change adapter settings".
Note that an active network connection must be present !

4. Press the "ALT" key: the toolbar pops-up.

Select "File" and "New Incoming Connection".

- 89 -
5. Select the correct user account "Admin" and select "Next".

6. Select "Through a dial-up modem" and select "Next".

The modem type listed here is the Conceptronic 56K USB voice/fax/modem.

- 90 -
7. Keep all networking software selecting as is.
Select "Internet Protocol Version 4" and select "Properties".

8. Select the following:

- "Allow Callers to access my local area network".
- "Allow calling computer to specify its own IP Address".
- "Specify TCP/IP addresses" and specify an IP range, for example:
192.168.116.50 … 192.168.116.99

9. Select "OK".

- 91 -
10. Allow Access to this computer: this takes a while, the computer name is visible.
Select "Close".

11. Keep the window with network connections open, so you can watch what happens.
After the Host PC is configured too and an incoming RAS connection is then set up, you will see the
following:

Continue with configuring the remote desktop settings.

- 92 -
12. Go to "Start" -> "Computer" -> "Properties" -> "Remote settings".

13. Select "Allow connections from computer running any version of Remote Desktop (less secure)",
select "Apply" and "OK".

Now, continue with the steps as described in sections 7.2. MODEM PREPARATION ON THE HOST PC and
7.3. SET UP A RAS CONNECTION TO THE ISS.

- 93 -
7.2. MODEM PREPARATION ON THE HOST PC

1. Connect the USB modem (USRobotics) to the Host PC.

2. Check that the device drivers are installed correctly.

3. Open network connections.

4. Create a new connection.

5. Select "Next".

- 94 -
6. Select "Connect to the Internet" and select "Next".

7. Select "Setup my connection manually" and select "Next".

- 95 -
8. Select "Connect using a dial up modem" and select "Next".

9. Type in "ISS" as the ISP Name.

- 96 -
10. Type in the Phone number (enter exactly your number), for example 0356892001.

11. Type in 3x "Admin" for the Username, Password and Confirm.

In this example "Admin" is the Username and Password of the ISS.
Do not select "Make this the default internet connection".

- 97 -
12. Select "Add a shortcut of this connection onto the desktop" and select "Finish".

7.3. SET UP A RAS CONNECTION TO THE ISS

1. On the host PC, double click the "ISS" shortcut on the desktop to call in to the ISS.

- 98 -
 The Pre-Dial Terminal Screen will pop-up.

2. Select "Continue".
Now the modem connection is build up between the Host PC and the ISS.
Note that an extra network symbol is present, right under in the taskbar of both the Host PC and the
ISS.

3. You can check your IP addresses by opening a DOS Command window (Run, CMD) and entering
"IPconfig". You will then see on the:

- ISS : a PPP adaptor RAS Server (dial-in) Interface with IP address 192.168.116.50.
- Host PC : a PPP adaptor ISS with IP address 192.168.116.51.

The IP addresses shown here are in the range, specified in step 12 in section 7.1.1. ISS with Windows
XPE or step 8 in section 7.1.2. ISS-2/ISS-3 with WES7.

4. Now open on the Host PC a Remote Desktop session.

- Enter IP Address of the PPP adaptor RAS Server on the ISS:

in this example 192.168.116.50.
Note that this is not the physical IP address of the ISS !

- Enter the Username and Password "Admin".

Note that when using remote access software it can be a little bit slower than actually using a direct
connection.

- 99 -
A. 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 PROTOCOL DEFAULT DESTINATION PORT

DHCP DHCP Server UDP 67
69 (see note 1)
TFTP TFTP Server UDP
1024 – 65535
H.225.0 RAS not appl. not appl. not appl.
ISG / IPG TCP 1720
H.225.0 Call Signalling
ErgoLine@Net TCP 1720
H.323 ISG / IPG TCP 1100 - 1299
H.245 Media Control
Extensions
Signalling ErgoLine@Net TCP 1024 – 65535
and Trunks
ISG UDP 49000 – 49199 (see note 2)
H.225.0 RTP / RTCP IPG UDP 49600 – 49979 (see note 2)
ErgoLine@Net UDP 49000 – 49199 (see note 2)
CPU3000 TCP 2600
iTMP Aggregation
CIE TCP 2600
iTMP iTMP Server TCP 2600
Call Signalling CPU3000/ISS/CIE TCP 57000
Media Signalling (VPC) ISG / IPG UDP 4000 – 4031
CCIS
ISG UDP 49200 – 49399 (see note 2)
RTP / RTCP
IPG UDP 49200 – 49579 (see note 2)
SIP Aggregation CPU3000/ISS/CIE TCP 2610
SIP@Net Server / UDP/TCP 5060
SIP SIP
ISG / ISS TLS 5061
Extensions
and Trunks ISG UDP 49200 – 49399 (see note 2)
RTP / RTCP
IPG UDP 49200 – 49579 (see note 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.

Apart from the port numbers listed in the table, the following (default) port numbers are also used in the
iS3000/SIP@Net:

PORT NUMBER APPLICATION

23 OM
2555 CSTA
2565 TCP Monitor
2595 iPVN (system boundary 356)
2596 BCT Sync - PVE (system boundary 365)
2597 Switching Services
2598 Alarming
2599 FDCR
2800 Heart-Beat protocol (system boundary 445)
(used in a SIP@Net Dual Server and Server Cluster configuration)

- 100 -