Nectar Diagnostics tracks SIP call journeys across on-premises, cloud and hybrid Unified Communications and Contact Center environments. The web platform provides signaling visibility, post-call metrics and media analysis, including in encrypted traffic. It correlates call legs across Teams, Genesys, Avaya, Cisco, SBCs, IVRs and carriers using unique Correlation IDs. KPI dashboards present performance trends, quality measures and call outcomes, while alerts notify teams of anomalies. Listed capabilities include MOS scoring, jitter and packet-loss tracking, and SIP trunk monitoring. Integrations named by the vendor include Skype for Business SDN, Ribbon SBCs, AudioCodes Mediant SBC, Cisco CUCM, Oracle SBC, Genesys Engage and Avaya components. Diagnostics can export session data to Nectar DXP over HTTPS on port 443, with HTTP proxy support. DXP is described as Nectar’s AWS public cloud infrastructure, with US and EU service locations. Security controls include role-based permissions, strong password rules, login lockout, IP blacklisting, HTTPS and audit logs. Pricing is available on request; the product page invites prospective customers to request a demo.
Who it is for
Nectar Diagnostics is aimed at enterprises and managed service providers working with communications and contact center environments. It suits teams that need visibility across call legs and multiple vendors.
What is good
- Analyzes signaling and media, including encrypted traffic.
- Correlates call legs across named platforms and carriers.
- Dashboards show trends, quality measures and outcomes.
- Tracks MOS, jitter, packet loss and SIP trunks.
- Offers email and phone technical support.
What to know first
- Pricing is available on request.
- Optional packet analysis may require network taps, spans or API access.
- Customers update on-premises applications such as RIGs.
Verdict
Nectar Diagnostics brings call journey analysis, dashboards and alerts together for multi-vendor communications environments. Prospective customers need to request pricing, and optional packet analysis may require access to adjacent network equipment.
Get started with Nectar Diagnostics
- Visit the Nectar Diagnostics website and request a demo.
- Contact Nectar for pricing.
- Plan whether optional packet analysis will use network taps, spans, or API access to adjacent equipment.
- If exporting session data to Nectar DXP, configure HTTPS on port 443; an HTTP proxy is supported.
- Set user access with role-appropriate permissions and follow Nectar’s security recommendations.
Questions about Nectar Diagnostics
How much does Nectar Diagnostics cost?
Pricing is available on request. The Diagnostics page invites prospective customers to request a demo.
What environments does it monitor?
It tracks SIP call journeys across on-premises, cloud, and hybrid Unified Communications and Contact Center environments.
Which platforms and vendors does it cover?
Call correlation spans Teams, Genesys, Avaya, Cisco, SBCs, IVRs, and carriers. Listed integrations also include Skype for Business SDN, Ribbon SBCs, AudioCodes Mediant SBC, Cisco CUCM, Oracle SBC, Genesys Engage, and Avaya components.
Can it analyze encrypted traffic?
Yes. Nectar lists media analysis that includes encrypted traffic.
Where is Nectar DXP hosted?
Nectar describes DXP as its secure public cloud infrastructure on AWS, with US and EU service locations.
What security controls are described?
Listed controls include role-based permissions, strong password rules, login lockout, IP blacklisting, HTTPS, and security audit logs. DXP 1.22.0 introduced role-based data access and PII data obfuscation.
Compared on VoIP monitoring software
- MOS scoring
- Yes
- Jitter tracking
- Yes
- Packet-loss tracking
- Yes
- SIP trunk monitoring
- Yes
