Page Comparison

<div id="fb-root"></div>
<script>(function(d, s, id) {
  var js, fjs = d.getElementsByTagName(s)[0];
  if (d.getElementById(id)) return;
  js = d.createElement(s); js.id = id;
  js.src = 'https://connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.11';
  fjs.parentNode.insertBefore(js, fjs);
}(document, 'script', 'facebook-jssdk'));</script>

...

 <div class="lang-box-pdf">
	<div>
		<div class="google-lang-switch">
			<span<div classid="letters-form"><a title="English" href="#">EN</a>&nbsp;|&nbsp;<a title="Italian" href="#" >IT</a>&nbsp;|&nbsp;<a title="French" href="#" target="_blank">FR</a>&nbsp;|&nbsp;<a title="German" href="#">DE</a></span>
		</div>
		<div class="google-lang">
			<div id="google_translate_element">
			</div>
			<script type="text/javascript">
					function googleTranslateElementInit() {
						new google_translate_element">
			</div>
			<script type="text/javascript">
					function googleTranslateElementInit() {
						new google.translate.TranslateElement({pageLanguage: 'en', includedLanguages: 'de,es,fr,it,nl', autoDisplay: false}, 'google_translate_element');
						}
			</script>
			<script type="text/javascript" src="//translate.google.com/translate_a/element.js?cb=googleTranslateElementInit"></script>
		</div>
		
		<div class="pdf-button">
			<a href="https://confluence.wildix.com/spaces/flyingpdf/pdfpageexport.action?pageId=48168992" alt="Convert to .pdf" title="Convert to .pdf"><img src="https://confluence.wildix.com/download/attachments/14549012/pdf-button-download-wildix-documentation.png"></a>
		</div>
	</div>
</div>

...

Here is radiation pattern, measured when the unit is in an upright position. Antenna 0 is the right antenna seen from the back of the base station. If you print the pattern out on a paper and place a base station in the center you can see the radiation pattern:

Antenna 0:Image Removed

Antenna 1:

Image Removed

From the radiation pattern it can be seen that the optimal position of the base for optimal coverage is upright position. When base is deployed this position must be considered as it is optimal for cell coverage between base chains and handset usage.

...

1. Go to the WMS menu Devices → W-AIR Networks → click Add
2. Enter the name Name for your W-AIR Network

3. Select the gateways from the list on the left and move them to the list on the right

   Warning
   Limitation: it is impossible to register a W-AIR Headset if the code of W-AIR network is different from "0000" (default code). Workaround: temporarily change the code to default one ("0000") , register and assign the Headset(s), and then change it back to custom one.

   
   

4. Click “Save”

   Note
   The first base becomes the Main base of the network (M). The gateways make radio sync over the air with each other automatically to extend the work range if possible.

   
   

   
   

5. Go back to the Devices Menu, select your base/bases and press “Configure/ Sync device” button

Step 3. Register a W-AIR Handset

...

• If you have any problems with registering Repeater(s), reset it by pressing the Reset button on the back side for more than 2 seconds (LED turns solid RED and then GREEN with a double pulsation). Start the registration procedure again by following the last three points above.
• The Repeater should be placed on a distance not less than 10 meters from its Base station.
• For a good conversation and a correct handover between bases and Repeaters the dBm value should be between -75 and 0. (See the chapter 2.2. Check the Radio Coverage - Repeaters)

W-AIR Network

...

Features:

• up to 250 offices/ base stations – 1000 handsets/ users in one DECT network
• redundant – all offices base stations are autonomous
• roaming – users can roam over all base stations/ offices
• user sign-on/ hot desking
• centralized phonebook with presence

Thanks to WMS Network up to 500 PBXs – HW, VM or Cloud PBXs – connect together and create a peer to peer Telephony network which is secure, synchronized. The base stations of the DECT network can be connected to any one of the PBX (with a secondary one as failover) and work even in case internet is not available. The handsets information is shared via IP service over the DECT gateways network.

Users can roam all over the base stations preserving their internal number. When a user moves between from office to another, location is automatically updated and the personal settings (forwards, call management rules) are retrieved. Users do not need the help of an administrator to start using an handset, the sign-on require to enter via IVR the phone number and personal pin code. It is easy to share the phone between many users as sign-on / sign-off operators require just a few seconds.

Requirements:

• layer 3 VPN over all sites
• support for UDP fragmentation (since MTU of packets is over 1500 bytes)
• base stations must be able to reach each other via IP

How-to:

1. Enter the local IP address of the Primary Base Station into the field “Primary Base IP” (Devices -> W-AIR Networks -> "Edit Network")
2. Connect all the base stations and add them to the WMS Network Server PBX
3. Set as DNS server for each base station (in Devices -> “Edit” device) the PBX to which the base station must be connected
4. Set as DNS name “auto.wildixin.com” in the field “SIP Proxy” (Devices -> W-AIR Networks -> “Edit” Network) to have all phones connected to the correct PBX (this is possible thanks to point 3)

W-AIR Network deployment

Case 1: Sync chain with one Primary Base

• The sync chain must always overlap with other Base stations in order to latch each other in sync.

• Primary base is the one that performs the sync.

• A maximum of 24 sync levels (Including the primary base) can be used in a deployment.

• Secondary base stations or repeaters are connected to the Primary base through the synchronisation chain

• If one of the base or repeater units in the sync chain is broken or not working, then the units that follow the non-working device are cut off from the sync chain, and sync can be lost. In this case, handover between the two clusters is not possible.

Bad deployment example:

Good deployment example (Secondary Base 1 and 2 are at sync level 1, Secondary Base 3 is at sync level 2)

Case 2: Sync chain without alternative sync paths

• A maximum of 250 base stations can be deployed in one setup (depending on the network requirement not all base stations should be chained).

• A maximum of 24 sync levels can be used in any deployment.

• Depending on the system setup, it is recommended to place the Primary base station in the middle of the building and to assign numbers/addresses, radio ID (RPN), etc. to each base station or repeater for easy identification.

  • Continuous line: Shows the primary sync paths, with the relevant bases chained in the multicell network.

  • Dotted line: Alternative sync paths.

Case 3. Sync chain with alternative sync paths. 

The scheme below shows a multicell network with alternative synchronisation paths. A failure of one base unit does not mean handset or users cannot perform handovers to other active cells.

If the Secondary Base 2 is down, the majority of user handovers can be performed via 3 other alternative cells (i.e. Secondary Base 3, 5 and 1) without any problems.

Take into consideration the following:

• Base 4 and 1 are Primary with alternative sync to the Primary Base.
• Base 5 is primary sync to Base 4 while alternative sync is Base 1 or 2. 
• Base 3 is primary sync to Base 2 while alternative sync is Base 5 or 6.

In the scheme below:

• Base 24 is the primary sync to Base 25 while alternative sync is Base 20
• Base 22 is the primary sync to Base 20 while alternative sync is Base 21 or Base 23

Verify deployment

The actual sync RSSI may be read on the base station web interface. It is recommended to have a RSSI value better than/ equal to -75dBm, and never below 090dBm. Take a look at the DECT Chain Tree to check the solution you have decided to set up.

The DECT Chain Tree should correspond to the real Bases deployment (as in the following example)

The value shown in the “DECT sync source” field indicates the real dBm value.

Based on this value you can choose the best connection solution for your system, taking into consideration any obstacles present in the environment.

...

deployment

Case 1: Sync chain with one Primary Base

• The sync chain must always overlap with other Base stations in order to latch each other in sync.

• Primary base is the one that performs the sync.

• A maximum of 24 sync levels (Including the primary base) can be used in a deployment.

• Secondary base stations or repeaters are connected to the Primary base through the synchronisation chain

• If one of the base or repeater units in the sync chain is broken or not working, then the units that follow the non-working device are cut off from the sync chain, and sync can be lost. In this case, handover between the two clusters is not possible.

Bad deployment example:

Good deployment example (Secondary Base 1 and 2 are at sync level 1, Secondary Base 3 is at sync level 2)

Case 2: Sync chain without alternative sync paths

• A maximum of 250 base stations can be deployed in one setup (depending on the network requirement not all base stations should be chained).

• A maximum of 24 sync levels can be used in any deployment.

• Depending on the system setup, it is recommended to place the Primary base station in the middle of the building and to assign numbers/addresses, radio ID (RPN), etc. to each base station or repeater for easy identification.

  • Continuous line: Shows the primary sync paths, with the relevant bases chained in the multicell network.

  • Dotted line: Alternative sync paths.

Case 3. Sync chain with alternative sync paths. 

The scheme below shows a multicell network with alternative synchronisation paths. A failure of one base unit does not mean handset or users cannot perform handovers to other active cells.

If the Secondary Base 2 is down, the majority of user handovers can be performed via 3 other alternative cells (i.e. Secondary Base 3, 5 and 1) without any problems.

Take into consideration the following:

• Base 4 and 1 are Primary with alternative sync to the Primary Base.
• Base 5 is primary sync to Base 4 while alternative sync is Base 1 or 2. 
• Base 3 is primary sync to Base 2 while alternative sync is Base 5 or 6.

In the scheme below:

• Base 24 is the primary sync to Base 25 while alternative sync is Base 20
• Base 22 is the primary sync to Base 20 while alternative sync is Base 21 or Base 23

Verify deployment

The actual sync RSSI may be read on the base station web interface. It is recommended to have a RSSI value better than/ equal to -75dBm, and never below 090dBm. Take a look at the DECT Chain Tree to check the solution you have decided to set up.

The DECT Chain Tree should correspond to the real Bases deployment (as in the following example)

The value shown in the “DECT sync source” field indicates the real dBm value.

Based on this value you can choose the best connection solution for your system, taking into consideration any obstacles present in the environment.

W-AIR Network auto roaming feature

Features:

• up to 250 offices/ base stations – 1000 handsets/ users in one DECT network
• redundant – all offices base stations are autonomous
• roaming – users can roam over all base stations/ offices
• user sign-on/ hot desking
• centralized phonebook with presence

Thanks to WMS Network up to 500 PBXs – HW, VM or Cloud PBXs – connect together and create a peer to peer Telephony network which is secure, synchronized. The base stations of the DECT network can be connected to any one of the PBX (with a secondary one as failover) and work even in case internet is not available. The handsets information is shared via IP service over the DECT gateways network.

Users can roam all over the base stations preserving their internal number. When a user moves between from office to another, location is automatically updated and the personal settings (forwards, call management rules) are retrieved. Users do not need the help of an administrator to start using an handset, the sign-on require to enter via IVR the phone number and personal pin code. It is easy to share the phone between many users as sign-on / sign-off operators require just a few seconds.

Requirements:

• layer 3 VPN over all sites
• support for UDP fragmentation (since MTU of packets is over 1500 bytes)
• base stations must be able to reach each other via IP

How-to:

1. Enter the local IP address of the Primary Base Station into the field “Primary Base IP” (Devices -> W-AIR Networks -> "Edit Network")
2. Connect all the base stations and add them to the WMS Network Server PBX
3. Set as DNS server for each base station (in Devices -> “Edit” device) the PBX to which the base station must be connected
4. Set as DNS name “auto.wildixin.com” in the field “SIP Proxy” (Devices -> W-AIR Networks -> “Edit” Network) to have all phones connected to the correct PBX (this is possible thanks to point 3)

Call Features 

DND, Call forwarding, Paging, Call intrusion, Intercom

...

Howling: Enable/Disable the howling of the handset when the alarm is triggered.

Image Removed

After you have defined the Emergency profiles, click “Save” to apply.

Assign emergency profile to handsets

...

1. Go to the menu

...

1. Extensions

...

1. Click on the field “Idx” or “Extension” of the handset:

Image Removed

...

1. 
   

   
   

2. The following window is displayed, allowing you to set up emergency settings:

Image Removed

...

1. 
   

   
   

2. Modify the parameter “Alarm Number”: Enter the number to be called when the alarm is triggered from the handset

   
   

   Note

...

1. You can enter an extension number that must be called or customise the service by modifying the Dialplan in the WMS and to add the “Alarm Number” as a Called number into a Dialplan procedure.

...

1. 
   

2. Tick off the Profiles that you wish to enable for this handset

...

1. Click

...

1. Save at the bottom of the page

...

1. Go to

...

1. Management menu and click

...

1. Save and

...

1. reboot to reboot the base station and apply the new parameters.

<div class="fb-like" data-href="https://confluence.wildix.com/x/IADfAg" data-layout="button_count" data-action="recommend" data-size="large" data-show-faces="true" data-share="true"></div>

...