Aastra SIP-DECT User's Guide Page 14

  • Download
  • Add to my manuals
  • Print
  • Page
    / 23
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 13
12
Compendium: OM SIP – DECT Solution Large SIP-DECT System
DECT cluster number for RFPs that are deployed e.g. to a different building where
the distance prevents overlapping radio coverage. Also configure one RFP per
DECT cluster as the Preferred synchronization source, preferably an RFP that is
located in the middle of the radio domain.
>OM System Manual:
RFP Export File Format
For a larger RFP deployment, you should prepare a list of RFPs, their names
together with their MAC addresses. Also, a map or building plan that indicates the
RFP mounting positions may be helpful. The list of RFPs in CSV format can be
imported via OMP or on the Radio Fixed Parts page of the OMM Web service.
Exporting this list is only supported in the OMP Java tool.
>OM System Manual:
RFP Configuration Files
You can use a de-centralized configuration method that utilizes configuration files
directly queried by the RFPs during startup. You can use this method e.g. with
script generated configuration files.
>OM System Manual:
“Paging areas” Menu
For a large SIP-DECT 4.0 system, consider to define paging areas to keep the sig-
nalling traffic separated in the different areas.
Enable Hi-Q audio (CAT-iq)
The current RFPs support Hi-Q audio (via wideband speech according to CAT-iq)
for use with Aastra 650c DECT handsets. To manage this feature, RFPs can be
assigned to different sites. You can enable or disable the Hi-Q Audio Technology
switch per site. When assigning RFPs to sites, please consider the following rules:
Only current RFPs should be assigned to a Hi-Q-enabled site.
You should assign all RFPs with the same cluster number to the same site.
You also can assign RFPs with different cluster numbers to the same site, but
you should refrain from assigning different sites to RFPs of the same cluster.
Basically, this means that a handover between a Hi-Q-enabled (current) RFP and an
(older) Hi-Q-disabled RFP is not possible. If you operate one older RFP in a cluster,
you should therefore assign all RFPs of that cluster to a site with the Hi-Q feature
disabled.
To configure the Hi-Q feature, you need to add a site configuration with the fol-
lowing steps:
1. Navigate to Sites page of the OMM Web service or OMP Java tool.
2. If you plan to use Hi-Q audio throughout all RFPs, change the “default” site
entry and enable the Hi-Q Audio Technology option. You may also change
the name of the site entry, e.g. to “Hi-Q enabled site”.
If you plan to use a mixed configuration of older and current RFPs, add at least
one site entry, e.g. a site entry named “Hi-Q disabled site”. Disable the Hi-Q
Audio Technology option for this site entry.
3. Navigate to the Radio fixed parts page. Change the Site assignment for all
RFPs with the same cluster number either to “Hi-Q enabled site” or to “Hi-Q
disabled site”.
Note
You cannot combine a Hi-Q audio with DECT XQ audio within the same
connection. Depending on the Aastra 650c operation mode, either Hi-Q audio or
DECT XP audio is used (refer to the OM System Manual for details). Also note, that
Hi-Q audio doubles the required DECT air capacity, thus only 4 Hi-Q audio
connections per RFP are possible. For connections to external SIP devices, the
G.722 (wideband) audio codec is supported for Hi-Q audio.
Page view 13
1 2 ... 9 10 11 12 13 14 15 16 17 18 19 ... 22 23

Comments to this Manuals

No comments