An IP DECT system can extend an organization’s IP telephony environment to cordless handsets, giving mobile employees access to voice and selected PBX features while they move through a site. For industrial operations, warehouses, campuses and other multi-area facilities, this can provide a wireless communications layer that works alongside the existing voice network. NEC’s AP400 series connects DECT access points directly to Ethernet and supports integration with NEC and third-party PBX platforms through SIP, subject to the capabilities of the specific system and level of interoperability.
How the AP400 IP DECT system fits into an IP network
An AP400 configuration brings together access points, DECT handsets and, where required, the DAP Controller software. The access points connect to the local IP network and provide the DECT radio connection for handsets. Calls can connect handset users with other VoIP users, while the link to a host PBX uses a dedicated IP protocol or SIP. SIP compatibility allows connection to certified SIP PBX platforms, but the available call features depend on how the IP DECT system and PBX interoperate.
The network itself may be a converged voice-and-data LAN or a network dedicated to voice. AP400 access points use a 10/100 Ethernet interface and support Power over Ethernet under IEEE 802.3af. The series supports G.711 and G.722 audio; CAT-iq functionality is available only in specified R6 versions. G.729AB compression is supported with an additional G7A board, so it should be treated as an option rather than a standard capability.
Capacity, coverage and mobility
Each AP400 has 12 DECT channels and can support up to 11 simultaneous calls, or up to five simultaneous HD voice calls according to the system overview. One channel is used for signaling between access points. A system can scale to a maximum of 750 AP400-series access points; the stated maximum extension count is 18,750 and depends on the PBX platform.
Roaming and handover allow a compatible handset to remain connected as a user moves between coverage areas. The source specifies indicative coverage of up to 50 metres indoors and 300 metres outdoors, but actual radio coverage depends on the environment and obstacles. Site design should therefore account for the facility layout and local conditions rather than treating these figures as guaranteed coverage.
For multi-site deployments, access points at a main site and branches can be managed as part of the same system. Multicast is used for AP400s in a DECT location on the same LAN. The DAP Manager is required for extended roaming and for wide-area network use without multicast, making network topology an important planning consideration.
Features for day-to-day operations
The AP400 series is designed to bring familiar telephony features to cordless handsets. Depending on the PBX and system configuration, these include caller ID and name presentation, conference calling, DTMF, presentation of a second call, PBX feature integration and access to a central directory. The platform also supports text messaging, including messages of up to 160 characters. The maximum length and available messaging functions depend on the PBX platform and application.
Messaging can support normal, urgent and very urgent priorities, message-waiting indication and broadcast messaging where the relevant system components support them. Location detection is also listed among the capabilities, with feature availability dependent on the IP DECT and PBX configuration. These functions may help organizations coordinate mobile users, but the specific workflow depends on the applications and integrations deployed.
Security features include DECT authentication and voice encryption. For deployment planning, engineers should verify supported handsets, PBX interoperability, radio-frequency requirements and the configuration’s required features rather than assuming every listed function is available in every installation.
Installation, management and environmental options
AP400 access points connect directly to Ethernet and can be mounted on a wall or ceiling. The standard AP400 uses an internal omnidirectional antenna; the AP400E supports an external antenna option. An external enclosure is available for outdoor use with the AP400E. The enclosure is specified as IP66, while the access point’s listed protection rating is IP20, so the enclosure and installation arrangement matter when equipment is exposed to environmental conditions.
DAP Manager provides web-based access and software management. It is used for installation and maintenance, but in most configurations it does not need to run continuously for routine operation, except where functions such as text messaging require it. Software updates can be delivered through the interface, and LEDs provide status indication. The system also supports a redundant DAP Controller arrangement for increased availability across local and remote sites, subject to the selected architecture.
Planning an AP400 deployment
Before selecting an IP DECT design, technical teams should confirm:
- PBX compatibility: Check the specific platform, SIP interoperability and which PBX features are exposed to handsets.
- Capacity: Size the number of access points for expected concurrent calls, remembering that HD voice capacity differs from the general call figure.
- Coverage and roaming: Assess the physical site and validate radio coverage, handover and any multi-site requirements.
- Network design: Confirm Ethernet, PoE, multicast or DAP Manager requirements for the intended topology.
- Regional requirements: Select equipment and frequency bands appropriate to the market and applicable regulations.
Conclusion
The NEC AP400 series provides a way to connect DECT cordless communications to an IP telephony environment, combining SIP-based PBX integration with handset mobility, messaging and scalable access-point deployment. Its practical fit depends on call capacity, radio conditions, network topology, handset compatibility and the feature support of the host PBX. Evaluating those factors early helps engineering and operations teams determine whether IP DECT can meet their site’s communication needs without assuming that every capability is universal across configurations.