Yeti Capacity Limit

@dmitry.s Please I noticed Yeti is not processing more than 170 calls at a time, We are sending 200+ concurrent calls but most are failing with 487 and 486 codes

according to your screenshot such calls cancelled by calls originator.

Yes because they have been waiting to be proceed long by the switch and then some timeout which comes from the originating side

I don’t think so. Could you provide trace where we can see this long delay caused by yeti? What value of routing delay you see in CDRs?


This is a search based on Pdd of above 6 seconds and you can see the results

I asked about routing delay, not pdd.

What kind of details do you require now?.. the trace? from the other end?

I need routing delay value from CDR. You said yeti is not processing calls fast enough but you haven’t provided any proofs.