Filter
Top Products
6-2 Programming the Mobile Handset Features
NEC MH150/MH160 Mobile Handset Administration Guide - Revision 2
• Specific file information should contain data specific to each user such
as authentication credentials and line appearance data.
• Some parameter lines accept more t
han one value, separated by a
colon or semicolon character as defined in the following table.
• Any line that begins with a pound sign (#) is ignored.
• In general space characters are ignored. Space characters may be
incl
uded in string values by replacing the space with “%20” or by
enclosing the string in quotes (?).
• If necessary, other special characters
may be included by using a
hexadecimal representation: (%hh) where hh is the representation of
the character.
• Lines may appear in any order
although maintenance may be
simplified by preserving the order in the supplied example file.
Program each of the files according
to the following instructions.
The generic file (sip_allusers.cfg)
The generic configuration file provides system information common to
all
handsets.
The handset-specific files (e.g. sip_3001.cfg)
The handset-specific configuration file provides specific information for
the hands
et to identify itself and communicate to other phones. Each
handset must have its own file with a unique filename. You may use the
same parameters as the generic file when programming the handset
files if you wish to override a common setting.
You must configure a unique handset file for each handset being deployed. Typically
each of these files is named with the extension number or name of the person
assigned the handset. For example John Doe's handset could have a handset
filename of sip_3001.cfg or sip_JohnDoe.cfg.
NOTE