Message Flows - Revision history

Moritz Orbach: tried to improve wording

2014-03-10T21:07:45Z

tried to improve wording

Monica at 11:41, 4 November 2013

2013-11-04T11:41:33Z

Dana: /* Hangup */

2012-11-20T11:51:39Z

‎Hangup

Dana at 11:45, 20 November 2012

2012-11-20T11:45:42Z

Dana at 14:22, 15 November 2012

2012-11-15T14:22:04Z

Dana: /* Hangup */

2012-11-15T14:19:12Z

‎Hangup

Dana: /* Incoming Call Setup */

2012-11-15T14:15:11Z

‎Incoming Call Setup

Dana: Created page with " ===Incoming Call Setup=== Flow of messages: File:callsetup.png ===Routing=== When a channel detects incoming call(1), it sends call.route(2) to decide where to rou..."

2012-11-15T14:14:04Z

Created page with " ===Incoming Call Setup=== Flow of messages: File:callsetup.png ===Routing=== When a channel detects incoming call(1), it sends call.route(2) to decide where to rou..."

New page

===Incoming Call Setup===

Flow of messages:
[[File:callsetup.png]]

===Routing===

When a channel detects incoming call(1), it sends [[call.route]](2) to decide where to route it to. The call.route message maps a called number to a call target.

===Connecting===

When the call target is known, incoming channel attaches its CallEndPoint to [[call.execute]] message(4). Recipient should connect its CallEndPoint to CallEndPoint attached to call.execute. While waiting for call acceptance recipient may send [[call.ringing]](6). On call acceptance [[call.answered]](7) is sent.

===During the call===

During the call [[chan.dtmf]] messages(8,9) may be sent in both directions.

===Hangup===

When incoming channel detects hangup(10) it disconects its CallEndPoint. That results in [[chan.disconnected]] and eventually [[chan.hangup]] messages(not included in the diagram) sent by both channels.

@@ Line 1: / Line 1: @@
-Page describes the flow of the messages for an incoming call. The flow of the messages is the same no matter the protocol used by the incoming call or on which protocol the call will go to.
+This page describes the flow of the messages for an incoming call. The flow is the same no matter the protocol used by the incoming call or to which protocol the call will go to.
 ===Incoming Call Setup===
@@ Line 10: / Line 10: @@
 ===Routing===
-When a channel detects incoming call(1), it sends [[call.route]](2) to decide where to route it to. The call.route message maps a called number to a call target.
+When a channel detects an incoming call(1), it sends a [[call.route]](2) message for a decision on where the call should be routed to. The call.route message maps a called number to a call target.
 ===Connecting===
-When the call target is known, incoming channel attaches its CallEndPoint to [[call.execute]] message(4). Recipient should connect its CallEndPoint to CallEndPoint attached to call.execute. While waiting for call acceptance recipient may send [[call.ringing]](6). On call acceptance [[call.answered]](7) is sent.
+When the call target is known, the incoming channel attaches its CallEndPoint to a [[call.execute]] message(4). On receiving this message, the destination channel connects its own CallEndPoint to the CallEndPoint of the incoming channel. While waiting for call acceptance, the destination channel may send [[call.ringing]](6). On call acceptance [[call.answered]](7) is sent.
 ===During the call===
@@ Line 22: / Line 22: @@
 ===Hangup===
-When incoming channel detects hangup(10) it disconnects its CallEndPoint. That results in [[chan.disconnected]] and eventually [[chan.hangup]] messages(not included in the diagram) sent by both channels.
+When the incoming channel detects hangup(10), it disconnects its CallEndPoint. This results in [[chan.disconnected]] and eventually [[chan.hangup]] messages (not included in the diagram) sent by both channels.

← Older revision		Revision as of 11:41, 4 November 2013
Line 28:		Line 28:

	* [[Messages]]		* [[Messages]]
		+
		+	[[Category:Messages]] [[Category:Programmers]]

← Older revision		Revision as of 11:51, 20 November 2012
Line 23:		Line 23:

	When incoming channel detects hangup(10) it disconnects its CallEndPoint. That results in [[chan.disconnected]] and eventually [[chan.hangup]] messages(not included in the diagram) sent by both channels.		When incoming channel detects hangup(10) it disconnects its CallEndPoint. That results in [[chan.disconnected]] and eventually [[chan.hangup]] messages(not included in the diagram) sent by both channels.
		+
		+
		+	'''See also'''
		+
		+	* [[Messages]]

← Older revision		Revision as of 11:45, 20 November 2012
Line 1:		Line 1:

−	Page describes the flow of the messages for an incoming call.	+	Page describes the flow of the messages for an incoming call. The flow of the messages is the same no matter the protocol used by the incoming call or on which protocol the call will go to.

	===Incoming Call Setup===		===Incoming Call Setup===

← Older revision		Revision as of 14:22, 15 November 2012
Line 1:		Line 1:
		+
		+	Page describes the flow of the messages for an incoming call.

	===Incoming Call Setup===		===Incoming Call Setup===

← Older revision		Revision as of 14:19, 15 November 2012
Line 20:		Line 20:
	===Hangup===		===Hangup===

−	When incoming channel detects hangup(10) it ~~disconects~~ its CallEndPoint. That results in [[chan.disconnected]] and eventually [[chan.hangup]] messages(not included in the diagram) sent by both channels.	+	When incoming channel detects hangup(10) it disconnects its CallEndPoint. That results in [[chan.disconnected]] and eventually [[chan.hangup]] messages(not included in the diagram) sent by both channels.

@@ Line 2: / Line 2: @@
 ===Incoming Call Setup===
-Flow of messages:
+Flow of messages:<br>
 [[File:callsetup.png]]