AASTRA SIP-DECT (Release 3.0)- OM System Manual - Installation, Administration and Maintenance EN - Manual (Page 47)

SIP–DECT OM System Manual Release 3.0 7 OMM Web Service
Aastra depl-1624/1.0 Page: 47 (241)
•
ToS for voice packets : Determines the type of service (ToS resp. DiffServ) byte of the IP
packet header for all packets that transport RTP voice streams.
•
ToS for signalling packets : Determines the type of service (ToS resp. DiffServ) byte of
the IP packet header for all packets related to VoIP signaling.
•
TTL (Time to live) : Determines the maximum hop count for all IP packets.
•
VLAN priority call control : Determines the VLAN priority tag for VoIP-signaling packets.
•
VLAN priority audio : Determines the VLAN priority tag for RTP packets.
DECT settings
•
PARK : This setting depends on the licensing mode:
Demo mode: shows the default PARK.
L-RFP systems: Enter the PARK key as labeled on the OpenMobility CD.
License file: shows the PARK included in the license file.
•
Encryption : Activate this option, if you want to enable DECT encryption for the whole
system.
Please note: Make sure that all deployed 3rd party handsets support DECT encryption. If
not, encryption can be disabled per device (see 8.8.4).
•
DECT monitor : For monitoring the DECT system behavior of the OpenMobility Manager
the separate DECT monitor application exists. This tool needs an access to the
OpenMobility Manager which is disabled by default and can be enabled here. Because of
security, the DECT monitor flag is not stored permanently in the internal flash memory of
the OMM/RFP. After a reset the DECT monitor flag is ever disabled.
•
Regulatory domain : To define where the IP DECT is used the parameter regulatory
domain has to be configured.
Note, that current RFPs support different DECT frequencies, thus operating these devices
in different regulatory domains is possible provided that the
Regulatory domain setting is
configured accordingly.
For older RFPs, different RFP models exist to meet the different regulatory domain
demands. To setup a North American FCC compliant RFP, the value has to be set to
US (FCC/IC) . In a North American US (FCC/IC) deployment, ETSI compliant RFPs are
made inactive and can not be activated if the regulatory domain is set to US (FCC/IC) .
Vice-versa is also true.
WARNING: Please note that selecting the incorrect regulatory domain may result in
a violation of applicable law in your country!
•
DECT authentication code : The authentication code is used during initial PP
subscription as a security option. A code entered here provides a system-wide DECT
authentication code for each PP subscription. Alternatively, a handset-specific
authentication code can be set (see chapter 7.7.1).
•
Portable part user login type : Two kinds of login types are supported. During the login
the user can either be determined by the telephone number ( Number ) or by the unique
user login ID ( Login ID ). Both elements are part of each user data set. The Portable part
user login type setting specifies the system-wide login variant.
Note: Changing this setting forces an automatic logout of all logged in DECT handsets.