Hi, I have a problem with grouping channels into calls. I am working on a module which will store info about ongoing calls in real time. My app is connected to Asterisk via AMI interface and listens to incoming events. Based on that, I build channel list in real time, but I’m having a really hard time identifying which channel is starting a new call and joining those channels. I already know that normally we have PJSIP channel joined with Local channel, and another Local channel connected to another PJSIP channel. Problem is, in real time I can match two similar local channels, but when it comes to events, BridgeEvent which joins two channels comes after phone answers which is too late. I tried connecting channels via LinkedId, but there were scenarios when more than 1 call had the same LinkedId in its channels. Is there a way to identify which channels are connected in call in real time?
I’m using Asterisk 18.4.0
What exactly is the list used for, since the BridgeEvent is too late in the process?
The events in Asterisk are sent the moment things happen, that is before you get the BridgeEvent, there’s NO actual call running, just two channels, that are somewhat related to each other. Multiple channels can be related when you dial multiple numbers using Dial, and probably also when dispatching calls from a queue.
I need an app which will hold current state of all calls in Asterisk. I need to know that someone is calling and waiting. for an answer. A tool that can provide datas on how many calls are on queue, how many of them are waiting etc.
I think you and I define calls differently… To me, a call is two persons connected to each other, with bidirectional audio, and eventually video.
Unless you have an answer for the called party, there’s no call in progress.
What it sounds like you’re really after, is a list of channels, showing who created what, handling linked channels as a sort of sub-channel, with the ability to show the entire hierachy. What use such a list would have, is beyond me, but I suppose you have your reasons.
I would listen for NewChannel events, and make a data structure based on UniqueID and LinkedID as a key, referring to all channels associated with a transaction/flow. When presenting the list I just loop through the ID’s, then present them in a tree view, or whatever makes sense for you. That would also account for more than 2 channels in a flow.
For queues the queue related events, would do the best job getting the state you want.
You might look at the QueueStatus AMI Action and its related QueueEntry AMI Event.
I would listen for NewChannel events, and make a data structure based on UniqueID and LinkedID as a key, referring to all channels associated with a transaction/flow.
Does this mean that it LinkedId/UniqueId always point to one transaction flow/one caller?
Linked ID is updated as calls merge.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.