newchannel: SIP/192.168.10.252-00000008
newchannel: SIP/1001-00000009
link: SIP/192.168.10.252-00000008 - SIP/1001-00000009
unlink: SIP/192.168.10.252-00000008 - SIP/1001-00000009
link: SIP/192.168.10.252-00000008 - SIP/1001-00000009
unlink: SIP/192.168.10.252-00000008 - SIP/1001-00000009
link: SIP/192.168.10.252-00000008 - SIP/1001-00000009
unlink: SIP/192.168.10.252-00000008 - SIP/1001-00000009
link: SIP/192.168.10.252-00000008 - SIP/1001-00000009
unlink: SIP/192.168.10.252-00000008 - SIP/1001-00000009
newchannel: Local/1002@transferencias-aaa8,1
newchannel: Local/1002@transferencias-aaa8,2
newchannel: SIP/1002-0000000a
link: Local/1002@transferencias-aaa8,2 - SIP/1002-0000000a
link: SIP/1001-00000009 - Local/1002@transferencias-aaa8,1
unlink: SIP/1001-00000009 - Local/1002@transferencias-aaa8,1
link: SIP/1001-00000009 - Local/1002@transferencias-aaa8,1
unlink: Local/1002@transferencias-aaa8,2 - Local/1002@transferencias-aaa8,1
hangup: Local/1002@transferencias-aaa8,1
hangup: Local/1002@transferencias-aaa8,2
unlink: SIP/1001-00000009 - SIP/1002-0000000a
newchannel: Transfered/SIP/192.168.10.252-00000008
link: SIP/192.168.10.252-00000008 - SIP/1002-0000000a
hangup: SIP/1001-00000009
hangup: Transfered/SIP/192.168.10.252-00000008
unlink: SIP/192.168.10.252-00000008 - SIP/1002-0000000a
hangup: SIP/1002-0000000a
hangup: SIP/192.168.10.252-00000008

I searched for a diagram that could represent the call flow in a more intuitive way. I didn’t found something that was easy and clear enough for me. So i sketched some small diagrams and developed the following diagram structure that i will use on my documentation about telephony. I am still accepting better suggestions about representing calls in a more clear way.

update: why? Sometimes we need to draw things to our boss and clients to understand, people usually don’t have the same data abstraction skills that you have on seeing a lot of CDR’s rows and messages as audio streams flowing through dialplan logic. I had a good experience to explain what happened to calls using this. So i’m sharing. =)

Basic Call Representation

The first call we can represent is the most basic and common case on telephony. A calls B and that’s everything that happens.

A simple call that connects A to B

As you see those two elements represent communication end-points that we can say are physical channels that comes and goes out from the PBX. Could represent a persons phone or a PSTN or a trunk with another PBX.

The number on the connection line determinate the order the calls were placed on the system. So we can use a dashed line to represent calls that were not answered by our called party (B). By now we have the basic call redirection scenario where the first destination does not answer so the call is made with C instead of B.

B don't answer and the call overflowed to C

Another way a call can walk between end-points is when one of these points transfer its party. When this happens we need to keep track of who made the transfer. That is represented by the curved arrow that shows who transfer to who and in what moment.

B transfer A to C.

Note that transfer can make a communication channel as well between B and C during the transfer operation, the attended transfer. In this cases you can represent it textually, since most of people don’t care about that conversation.

Not all the times calls fallow an specific order. We have situations where many end-points are talking in the same time in the same call, in a conference for example. Conferences are the most common way to unite two calls that starts independently and when it appear in complex scenarios we will need a more complete way to represent the time sequence of call placing, but i will let this for later work. For now we can just represent the connections on a special element and say that all the connections happened at the same time.

A conference between A, B, C and N more end-points.

Applications and Contextualization

PBX’s are known for give some intelligence in call routing. This is the ability to use applications that apply one specific logic on the calls. These can be queues, call groups or even the Interactive Voice Response systems (IVR’s). The main difference between them is that some may answer the call and make data transmission to the connection party. When the application answer the call is easy to represent it as and special end-point, as we did with conferences. When just routing is involved we need to contextualize a group of calls in the scenario so we can determine the actions taken by the app. We can see those two cases in the next diagram.

Call Contexts

Approach Issues

One concern i have with this representation is that it could be a little confuse in a first moment about how the call flowed. I didn’t made the diagram in a standard way by considering that i am not taking a peer point of view, but the macro view of the call flow. In a simpler approach it would be ignored for example in a conference what was the path taken by the other participants, since the most common way to someone to get into a conference is to be transfered to the number that represents it.

I understand some misconceptions can happen since i am trying to represent something that is dynamic in a static view which is the call states along a time period. A snapshot of the PBX in any moment will only show a simple call.

PS. English corrections will be appreciated.