Filtering Channel_Destroy Webhook?

[Rick Guyton]

I setup a channel_destroy webhook and I'm getting a lot more responses than I was expecting. I'm getting a bunch of lose_race hooks. This makes sense I guess because a lot of my callflows dump into a call group and technically, I guess you are destroying a channel whenever one of the attempted legs of the call groups looses to another one. But, is there any way to filter this so that I don't get all of these unnecessary (in my case at least) updates?

[Tuly]

you will get 1 for each call leg, if you have 10 phones in a ring-group, you will get 11, 1 for the incoming and 10 for the outgoing 10 phones, (you will see "call_direction": "outbound"  outgoing from the system to the phones) 


i guess this is for missed call, right?

if you see "Loos race" on ANY of the webhooks = the call was not answered

if you see "Originator cancel" on ALL webhooks = the call was not answered

if you see "Originator cancel" on most but on 1 you see ANSWER = the call was answered

[Rick Guyton]

Yea, I was hoping I could pull something resembling real-time CDRs off the webhook. But, I think I'm better off just downloading CDRs at night.

[Darren Schreiber]

The channel destroys will indeed be returned for each leg, as you've discovered. The CDRs are de-duped and we're working on different ways to pull CDRs because actually when people say CDR they mean 3 different things.

More to come on that but the just released interaction IDs are the first start.