[telepathy-spec/master] Note that Jingle implementations may not send <ringing/>

Will Thompson will.thompson at collabora.co.uk
Fri Jun 12 00:54:47 PDT 2009


---
 spec/Channel_Interface_Call_State.xml |    4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)

diff --git a/spec/Channel_Interface_Call_State.xml b/spec/Channel_Interface_Call_State.xml
index eec6a4b..78a123f 100644
--- a/spec/Channel_Interface_Call_State.xml
+++ b/spec/Channel_Interface_Call_State.xml
@@ -25,7 +25,9 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.</
         progress or call states. The presence of this interface is no guarantee
         that call states will actually be signalled (for instance, SIP
         implementations are not guaranteed to generate status 180 Ringing, so a
-        call can be accepted without the Ringing flag ever having been set).</p>
+        call can be accepted without the Ringing flag ever having been set;
+        similarly, Jingle implementations are not guaranteed to send
+        <code>&lt;ringing/&gt;</code>).</p>
 
       <p>To notify the other participant in the call that they are on hold,
         see <tp:dbus-ref
-- 
1.5.6.5




More information about the telepathy-commits mailing list