01 · Inside the call control
Was it set up correctly?
Yesterday
Ask the UC team for CUCM traces and check the dial plan by hand.
Today with FRINK
Number format, partitions and cause codes shown for the call.
Whose problem is it?
One failed call.
Two ways to find whose problem it is.
Today, the UC team can show its side, the network team its side, and the carrier asks for logs. Each party proves it isn't them – and the ticket circulates until somebody gives up.
02 · At the edge
Did it leave correctly?
Yesterday
Ask the gateway owner for a debug capture – if anyone remembers how.
Today with FRINK
Dial-peer, calling and called number and media per leg on the gateway.
03 · Beyond the edge
What did the other side say?
Yesterday
Ask the carrier, who asks for logs that were overwritten a week ago.
Today with FRINK
The SIP response and reason from the far end, retained 30 days by default, longer if you choose.
04 · Result
The failing leg is named
Yesterday
The ticket circulates until somebody gives up.
Today with FRINK
The failing leg is named. Escalation with proof.
What changes
- Parties involvedYesterday: Three, each proving innocenceToday with FRINK: One, with evidence
- Ticket round-tripsYesterday: DaysToday with FRINK: One
- Evidence availableYesterday: Until the logs rotateToday with FRINK: Up to 10 years
Worked example · Insight 04
Calls to Dubai blocked by the provider
A customer couldn't reach one international destination. Both internal legs were right – so the ticket went to the carrier with that evidence.
Read the full case- Was it set up correctly?Number dialled in the correct format on CUCM.
- Did it leave correctly?Same call handed to the carrier with correct numbers.
- What did the other side say?No rejection from inside – the far end blocked it.
- The failing leg is namedCarrier-side fraud restriction, not the deployment.