Bug 13161

Summary:	No way to indicate outgoing call progress stages such as "ringing"
Product:	Telepathy	Reporter:	Mikhail Zabaluev <mikhail.zabaluev>
Component:	tp-spec	Assignee:	Telepathy bugs list <telepathy-bugs>
Status:	VERIFIED FIXED	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	enhancement
Priority:	medium
Version:	unspecified
Hardware:	All
OS:	All
Whiteboard:
i915 platform:		i915 features:
Bug Depends on:
Bug Blocks:	14602

Description Mikhail Zabaluev 2007-11-09 06:18:50 UTC

With the streaming media channel API as of Telepathy spec version 0.16.0, there is no way to map call progress stages available in e.g. SIP or GSM calls.
There ought to be a way to inform the client that the outgoing call is in following stages:
- "Connecting": trying to reach the callee(s), no indication that a remote endpoint has received the call.
- "Ringing": a remote endpoint has received the call, but the remote user has not accepted it yet.

One more stage may be of use:
- "Initiating": the initial state of the call, an outgoing request have not been sent yet.

Comment 1 Simon McVittie 2008-02-21 04:12:16 UTC

telepathy-spec HEAD can distinguish between "Initiating" and "either Connecting or Ringing", in your terminology - if you request streams to a contact who has not already been added to the group with AddMembers, they will only appear in remote-pending state when the transition between "Initiating" and "Connecting" occurs. I'll file bugs against Gabble and telepathy-sofiasip to support this.

I'm awaiting review for the CallStates API, which will allow distinguishing between "Connecting" and "Ringing" too.

Comment 2 Simon McVittie 2008-02-26 09:51:26 UTC

Fixed in Darcs by the CallState interface.

Comment 3 Mikhail Zabaluev 2008-02-26 09:54:22 UTC

Verified by implementing in a telepathy-sofiasip branch.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.