Dect R4 extension capacity

[megaa]

Hi Guys,
we have a customer who wants to use more than 750 dect extension.
Now they have an R11.1 IPO SE with about 80 IP base stations and a digital gateway as the master B/S.
from the documentation:

DECT R4
The IP Office system can support DECT handsets through the attachment of a DECT R4 system.
The following capacity considerations apply:
• The DECT handset capacity must be within the overall extension capacity of the IP Office
system solution.
• Each DECT R4 system supports:
- A maximum of 750 DECT extensions (384 on IP500 V2/V2A systems).

my question is, what is the best way to expand the capacity of the system to the maximum of 1500 dect stations?
- to install a secondary SE server, and create a new dect line with a new master B/S (bacause each server or expansion system allows only one IP Dect line to administer)
in this scenario there will be two different dect systems without roaming among them, and has to use two different extensions for each system with the same handset (if it is possible)

or any other option or suggestion?

thank you

 

[derfloh]

You will not find a solution that fits your needs. The 750 is fixed. In the past I tried to go over the limit of 384 but it didn’t work. Do you will have to create two systems, connected to two servers. No internal twinning between different servers possible. You would have to deploy double the number of base stations to cover the area with two separate systems.

You can go with the Ascom labeled solution that would allow much more extensions. But they will be SIP extensions in IPO and you will 3rd Party IP Endpoint Licenses and new hardware for sure.

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[sizbut]

The 384 is a different limit, that's any type of extension on an IP500. So doesn't necessarily means the 750 is hardcoded for DECT as that will involve a different part of the core code - so worth a punt if you have a 751st handset to test with (though if it works it would put you into the situation of having an unsupported configuration if you ever want to raise an issue to Avaya).

Stuck in a never ending cycle of file copying.

 

[derfloh]

In an earlier release the limit was 384. I wasn’t able to add extension 385 with provisioning. Without provisioning it was possible to add but I had other issues then. Iirc it wasn’t possible to do any configuration of the extension within DECT R4. So it was not useable.

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[megaa]

Thank you guys.
So the only solution is to add a secondary server with a new sip line connected to a master B/S and many slaves.
This is a large factory with many bulidings relatively far away from each other, the roaming between the two systems in not a key point of the customer.

one more thing:
there is a priority order in the dect handsets. Is can be used to subscribe a handset for more than one systmem with two different extension numbers? and the handset can register automatically into the available system?

 

[sizbut]

Regardless of DECT it would be best for each site to host its own IP Office server if they are physically distant from each other. That will cut down on pointless traffic on the primary when two users on the secondary talk to each other. Also adds support for things like resilience.

Stuck in a never ending cycle of file copying.