Icon should not trigger alert for packet loss on remote endpoint

Idea created by gvillardi Employee on Apr 26, 2017
    Pending Review
    • afiliceva
    • pete.shora
    • jlacey
    • gvillardi

    Idea created on behalf of partner: S.I. Contact


    Today, an Icon will trigger packet loss alerts if a remote endpoint not belonging to his same Cloud presents loss on his call leg.

    Example: Let's suppose I have a point-to-point call between 2 Icons and each one belongs to a different Cloud subscription. Now let's suppose I have packet loss between Icon A and the Cloud server. In this case will Icon B notice that packet loss and raise an alert.


    This behaviour generates alerts to a Cloud admin while there's no problem on his Icons' network.