lgaetz/Concurrent-Calls — Issue #5: Issues with Vitality trunk inbound
Author: lgaetz
Created: 2011-11-21 15:30:57+00:00
State: open

reported by hat on 05/18/2009

*Description*

Interesting situation. All my outbound trunks get graphed when selected individually. However, my incoming vitelity trunk shows up as 0 calls (yes, I have had actual incoming calls). I tried filtering set to just my vitel-outbound trunk with and without my DID, and all three (3) flavors of graphs, still 0 results. None of the date options worked either with the inbound trunk. I am not sure if inbound routes are covered by this module, hence the feature request. Please let me know if you need any other information.

Thanks,
Tom

*Update by hat*
I tried filtering set to just my vitel-outbound trunk with and without my DID
should be
I tried filtering set to just my vitel-inbound trunk with and without my DID

*Update by Boolah*
I think this depends on how the CDR is created. I just looked at two of my boxes that have Vitelity inbound routes; one with an IAX2 trunk and another with a SIP trunk. The one with the IAX2 trunk logs inbound calls (in the channel field in the cdr table) as IAX2/vitel-inbound whereas the one with the SIP trunk logs them as SIP/. On a related tangent, I'm seeing inbound calls through CallCentric coming in as SIP/ (which, obviously, changes).

Perhaps it's not practical to filter on a specific trunk. Does anyone have an algorithm to determine, irrespective of carrier, which trunk a call traverses?