[asterisk-commits] murf: branch murf/RFCs r157252 - /team/murf/RFCs/CDRfix2.rfc.txt
SVN commits to the Asterisk project
asterisk-commits at lists.digium.com
Mon Nov 17 16:13:58 CST 2008
Author: murf
Date: Mon Nov 17 16:13:58 2008
New Revision: 157252
URL: http://svn.digium.com/view/asterisk?view=rev&rev=157252
Log:
Pull the desired CDR's to be generic for the scenario; I may shift them back if role subcases demand different CDR's to be generated
Modified:
team/murf/RFCs/CDRfix2.rfc.txt
Modified: team/murf/RFCs/CDRfix2.rfc.txt
URL: http://svn.digium.com/view/asterisk/team/murf/RFCs/CDRfix2.rfc.txt?view=diff&rev=157252&r1=157251&r2=157252
==============================================================================
--- team/murf/RFCs/CDRfix2.rfc.txt (original)
+++ team/murf/RFCs/CDRfix2.rfc.txt Mon Nov 17 16:13:58 2008
@@ -82,24 +82,6 @@
BLIND XFERS: (Only when C answers in the following sequences):
===========================================================
-This involves these kinds of issues: A, and B, could each
-have CHANNEL or PEER role before/during the call.
-
-I can't imagine a scenario where C could have any status
-at all; if it exists, it should be BUSY. So, PEER is the only possibility.
-
-1. A is bridged to B; B blind xfers A to C
-
- | A channel | A Peer
- ================+====================+=================
- | |
- B Channel | CASE 3. | CASE 2.
- | |
- ================+====================+=================
- | |
- B peer | CASE 1. | CASE 4.
- | |
- ================+====================+=================
Assume these event times:
e1: either channel's start time. (Set previously)
e2: either channel's answer time (Set previously)
@@ -109,12 +91,42 @@
and ends his call.
e5: C answers
e6: A or C hang up.
-
- C is in peer role (4 cases):
- CASE 1:
+
CDRs wanted: (src -> dest)
CDR1: B -> C; start: e3 ans: e5 end: e6 AMA: DOCU type: BXFER Party: A
CDR2: A -> B; start: e1 ans: e2 end: e6 AMA: BILL type: CALL Party: A
+
+
+This involves these kinds of issues: A, and B, could each
+have CHANNEL or PEER role before/during the call.
+
+I can't imagine a scenario where C could have any status
+at all; if it exists, it should be BUSY. So, PEER is the only possibility.
+
+1. A is bridged to B; B blind xfers A to C
+
+ | A channel | A Peer
+ ================+====================+=================
+ | |
+ B Channel | CASE 3. | CASE 2.
+ | |
+ ================+====================+=================
+ | |
+ B peer | CASE 1. | CASE 4.
+ | |
+ ================+====================+=================
+ Assume these event times:
+ e1: either channel's start time. (Set previously)
+ e2: either channel's answer time (Set previously)
+ e3: B hits #, flashes hook, whatever to initiate
+ xfer and A starts getting MOH
+ e4: B finishes dialing, hits a button, whatever,
+ and ends his call.
+ e5: C answers
+ e6: A or C hang up.
+
+ C is in peer role (4 cases):
+ CASE 1:
CASE 2: I need to find a scenario, where B could be dialing A, with A in the Peer role...
and not dialing as an xfer or park case.
@@ -208,20 +220,6 @@
b. B stays online to parking expiry, then reconnected to A
c. B is picked up by C.
- | A channel | A Peer
- ================+====================+=================
- | |
- | |
- B Channel | CASE 1. | CASE 2.
- | |
- | |
- ================+====================+=================
- | |
- | |
- B peer | CASE 3. | CASE 4.
- | |
- | |
- ================+====================+=================
Assume these event times:
e1: A starts
e2: B answers
@@ -235,12 +233,7 @@
e9: B or C hangs up.
e10: where B stays on, parking expiry reached, A does not answer...
b is hung-up.
-
- CASE 1:
-
- CASE 2:
-
- CASE 3:
+
(a)
CDR1: A -> B; start: e1; ans: e2; end: e3 AMA: BILL type: CALL Party: B
CDR2: A -> B; start: e3; ans: NIL; end: e4 AMA: DOCU type: PARK Party: B
@@ -253,6 +246,29 @@
CDR1: A -> B; start: e1; ans: e2; end: e3 AMA: BILL type: CALL Party: B
CDR2: A -> B; start: e3; ans: NIL; end: e8 AMA: DOCU type: PARK Party: B
CDR3: C -> B; start: e7; ans: e8 end: e9 AMA: BILL type: CALL Party: B
+
+
+
+ | A channel | A Peer
+ ================+====================+=================
+ | |
+ | |
+ B Channel | CASE 1. | CASE 2.
+ | |
+ | |
+ ================+====================+=================
+ | |
+ | |
+ B peer | CASE 3. | CASE 4.
+ | |
+ | |
+ ================+====================+=================
+
+ CASE 1:
+
+ CASE 2:
+
+ CASE 3:
CASE 4:
More information about the asterisk-commits
mailing list