TECHNICAL COMMUNICATION No. TC1330 Ed.

01

OmniPCX Enterprise Nb of pages : 6 Date : 07 April 2010

URGENT

NOT URGENT TEMPORARY PERMANENT

SUBJECT: BOOTING ISSUE OF GD/GD2 OR IP TERMINALS IN OmniPCX Enterprise R9.1

CONTENTS

1. OVERVIEW...................................................................................3

2. GD/GD2 CASE .............................................................................3

2.1 Cause ....................................................................................................... 3
2.2 Solution .................................................................................................... 3
2.2.1 Workaround 1 ..................................................................................................4
2.2.2 Workaround 2 ..................................................................................................4

3. IP TERMINALS CASE.....................................................................4

1
2
 OmniPCX Enterprise
BOOTING ISSUE OF GD/GD2 OR IP
TERMINALS IN OmniPCX Enterprise R9.1

1. OVERVIEW
As of patch I1.605.13.c, lanpbxbuild tool has been modified to take into account a new
parameter, APPLICATION_TYPE.
To goal of this parameter, when set to APPL_SIP, is to be able to switch all 4008/4018EE sets of
the system to SIP mode, instead of switching the sets one by one, via their administration menu. As a
reminder, Release 9.1 has introduced the possibility to use 4008/4018EE sets in SIP mode (declared
as SEPLOS sets in the OmniPCX Enterprise).
Due to this modification, if lanpbxbuild tool is used, in a generic configuration, to create a
lanpbx.cfg file or to modify an already existing one, a new line "APPLICATION_TYPE=APPL_NOE"
will be added at the end of the file. Only patches from I1.605.13.c are affected.

2. GD/GD2 CASE

2.1 Cause
During validation of the here above mentioned modification, it has been detected that GD/GD2
boards couldn’t boot properly if this parameter was present in lanpbx.cfg file. A bugfix has been
provided in GD/GD2 binary 44.34.1, integrated in patch I1.605.13.c.
Despite of this bugfix, if the lanpbx.cfg file is modified with lanpbxbuild tool before all
GD/GD2 boards are updated with a binary 44.34.1 minimum, then the non upgraded yet boards
will be blocked before being able to update their binary and get rid of this issue.
If the GD/GD2 boards are in binary 44.34.1 minimum, then no issue will be experienced.
This can be experienced in two cases:
• Upgrade of a system to R9.1 (as of I1.605.13.c) and modification of lanpbx.cfg before all
the GD/GD2 boards are updated with the new binary.
• System in R9.1 (as of I1.605.13.c) with a lanpbx.cfg file having this new parameter and a
new GD/GD2 board with a binary prior to 44.34.1 must be added to this system.

2.2 Solution
Generally speaking there is absolutely no need to create manually a lanpbx.cfg file with
lanpbxbuild tool in most of the OmniPCX Enterprise systems, as the Call Server is able to provide
it dynamically on demand. This file, when dynamically created by the Call Server, doesn’t contain
this new parameter.
Only for some specific configurations, it is required to create a lanpbx.cfg file with
lanpbxbuild tool:
• Networks where several OmniPCX Enterprises share the same lanpbx.cfg file
• OmniPCX Enterprise with IP Touch security Solution (encryption boxes)
• Use of lanpbx.cfg file to switch all the 4008/4018EE sets of the OmniPCX Enterprise
system in SIP mode

Ed. 01 / 07 April 2010 3 TC1330

 OmniPCX Enterprise
BOOTING ISSUE OF GD/GD2 OR IP
TERMINALS IN OmniPCX Enterprise R9.1

In any cases, the best is to avoid modifying lanpbx.cfg file before all the GD/GA2s are upgraded
to binary 44.34.1. But if the file has been created or updated before, then two workarounds are
possible.
After having applied one of the mentioned workarounds, once all the GDs are updated to binary
44.34.1 (minimum), if 4008/4018EE sets have to be switched to SIP mode globally via
lanpbx.cfg, the file can then be modified again to add the new parameter.

2.2.1 Workaround 1

If your configuration doesn’t require to create manually the lanpbx.cfg file (standard case), then
the file can be simply deleted on both Call Servers.
The affected GD/GD2 boards have then to be rebooted.
This workaround can’t be used if the system uses IP Touch Security solution.

2.2.2 Workaround 2

If the configuration requires to use a lanpbx.cfg file created manually with lanpbxbuild, then it
is possible to modify manually lanpbx.cfg file without using lanpbxbuild tool.
This can be done at linux prompt with the utility vi :
− Type vi lanpbx.cfg
The cursor being at the beginning of the file, go with the navigation keys to the line which
contains APPLICATION_TYPE=APPL_NOE.
− Type dd to suppress this line, then :wq! to save and exit the file.
An alternative way is to transfer the file to a PC, modify it with windows notepad and transfer it back
to the Call Server.
If the system is using IP Touch Security solution, the modified file can’t be used directly like this
because its integrity has been broken: lanpbx.cfg file has then to be signed again by the SSM.
This operation has to be carried on in mgr > Encryption > Sign lanpbx.cfg and not via
lanpbxbuild tool.
Don’t forget to perform the same operation on the Stand-By Call Server if the system is duplicated.

3. IP TERMINALS CASE
In case lanpbx.cfg file contains the new parameter APPLICATION_TYPE, some IP terminals will
experience troubles to boot. This concerns:
• IP Touch sets of the Fast Ethernet series
• E-reflexes sets
• IP desktop softphone
The workarounds, mentioned previously for GD/GD2 boards, can be applied whatever the version
of these IP terminals.

TC1330 4 Ed. 01 / 07 April 2010

 OmniPCX Enterprise
BOOTING ISSUE OF GD/GD2 OR IP
TERMINALS IN OmniPCX Enterprise R9.1

Regarding IP desktop softphone, a fix is present in the version 9.1.2.4. The issue can then only be
experienced if the parameter is added to lanpbx.cfg file before the softphone is updated to this
version.
Concerning IP Touch Fast Ethernet, the correction is ongoing. A new edition of this document will
precise the patch which will fix this issue. The Extended Edition sets are not affected by the issue.
No evolution is planned for e-reflexes sets. The consequence is that it won’t be possible to have on
the same system e-reflexes sets and 4008/4018EE sets in SIP mode (with use of
APPLICATION_MODE parameter), except if one of the following two workarounds is used:
• The switch of 4008/4018EE sets in SIP mode is done manually set by set via their
administration menu and not globally via lanpbx.cfg file.
• The switch of all 4008/4018EE sets in SIP mode is done globally via the lanpbx.cfg. Once
all these sets have booted in SIP mode, the lanpbx.cfg file can then be modified in order
to remove the line with APPLICATION_MODE parameter.
Note
On secured systems, the lanpbx.cfg file will have to be signed again via mgr in order to
maintain the integrity information.
In case of future 4008/4018EE sets add-on, their switch in SIP mode will have to be
performed either manually set by set or via lanpbx.cfg by adding again
APPLICATION_MODE parameter in the file and then removing it afterwards.

Ed. 01 / 07 April 2010 5 TC1330

 OmniPCX Enterprise
BOOTING ISSUE OF GD/GD2 OR IP
TERMINALS IN OmniPCX Enterprise R9.1

TC1330 6 Ed. 01 / 07 April 2010