AudioCodes Software-Defined Voice Network (SDvN) vs. Cisco Software-Defined Access (SD-Access)

It's well suited in our corporate offices, where all our business users resides and where we can control all their accesses. What doesn't really fit well is when we have our branch fronts, where all the software domain access features aren't utilized to its fullest, due to the fact that customers and users don't really need to have all the security features that SDA provides.

Incentivized

• Automation, pushing template-based configuration to multiple devices in one push saves time and manpower.
• Assurance [helps trace] issues related to devices, clients, and provide the troubleshoot as [the] best practices.
• Segmentation, with the use of the SGT tags, we are able to achieve segmentation and micro-segmentation securely.

Incentivized

• Documentation: Working in this solution I realized there were missing information details about the fusion device support for nexus.
• Fusion router: This roll in the fabric should be already integrated in the solution, right now it is configured manually.
• Bugs: Unfortunately the solution still present a lot of bugs, mainly in the controller.

Incentivized

As far as my experience with SD-Access -I'd say things that can be improved are - better functionality with ISE, ease to understand licensing and better documentation for configuration (add-ons, etc), and licensing.

Incentivized

Automation, pushing template-based configuration to multiple devices in one push saves time and manpower. Assurance helps trace issues related to devices, clients, and provide the troubleshoot as the best practices. Segmentation, with the use of the SGT tags, we are able to achieve segmentation and micro-segmentation securely.

Incentivized

• Integration with other platforms in a single platform is a great advantage for the user.
• Saves time in configuring devices on the network

Incentivized