From ebe1c86f6670d01531db653c20db2246c960b891 Mon Sep 17 00:00:00 2001
From: Peter Saint-Andre Removed 'zeroconf' attribute for consistency with XEP-0065; clarified use of proxy-error condition; corrected schema. If a client is unable to connect to any candidate sent by its peer, or if it stopped trying to connect because its peer sent a candidate-used notification with a priority higher than its remaining candidate(s), it sends a candidate-error Jingle transport-info message (this is equivalent to the IQ-error with code="500" from the "fast-mode" extension). If a client is unable to connect to any candidate sent by its peer, or if it stopped trying to connect because its peer sent a candidate-used notification with a priority higher than its remaining candidate(s), it sends a candidate-error Jingle transport-info message (this is equivalent to the IQ-error with code='500' from the "fast-mode" extension). If the nominated candidate is of the proxy type and the party that offered that candidate can not connect to the proxy to activate it (for example because of a restrictive firewall), the party shall send a transport-info message containing an <proxy-error/> element as follows.