Filter
Top Products
4-2 Software License and Protocol Management
NEC MH150/MH160 Mobile Handset Administration Guide - Revision 2
Table 4-1 Software version requirements
Component Version
WLAN Voice Gateway 17x.028 or higher
OAI Server MOG 600 54.032 or higher
OAI Server MOG 700 82.017 or higher
• Finally, ensure that the Battery Pack
on the handset is fully charged.
Configuration Process
Step 1 Please contact NEC NTAC to obtain the latest software updates for the
MH150 and MH160 Mobile Handsets.
Step 2 Load the latest version of the SIP code and place it on the TFTP server
and ensure the TFTP server is started. The five files that are needed
must be named:
usb downloader
pd14udsp.bin
functional filename pd14csp.bin
phintl filename
pi1400sp.bin
ota downloader pd14odsp.bin
config file slnk_cfg.cfg
Step 3 Use the Handset Administration Tool to set up the configuration of each
handset to meet all essential requirements. If not using the Handset
Administration Tool, ensure the following parameters are correctly set in
the Admin menu for each handset:
—If statically assigning IP addresses, en
sure that the Phone IP, Subnet
Mask, and Default Gateway information are accurate. If using a DHCP
Server, ensure that the DHCP option is set.
—Ensure the handset has properly configured SSID and Reg Domain
informat
ion.
—Ensure the Telephony Protocol menu option is set to 36. This ensures
the
handset will check for the proper SRP files each time it powers on.
—Ensure security settings are properly programmed.
—Configure handset security settings
to match AP configuration. If
WPA2-Enterprise security is used, credentials will need to be installed
onto the handset. For EAP-FAST, the PAC file needs to be provisioned
and for PEAP the handset will need to be enrolled with a certificate
(requires use of the HAT).
See NEC MH150/MH160 Mobile Handset Overview for detailed
configuration instructions.
Step 4 Configure QoS mode to match the AP and site QoS plan.