I have been asked to investigate dropped calls... The scenario is that some tenants drop calls more then others, some drop on cell calls more then land lines, some calls only last for 30 seconds... you know the usual.
Although yes i can trace the calls, i can spot check, im sure this is possible... but I'm more interested in a permanent solution, something that i can report back on at the end of the month. I have noticed in the CLI in a day we would get say 100 - 200 "...No Reply to Our Critical Packet..." errors - I amuse that the calls is dropped shortly after that.
(yes, we are using phones behind NAT)
To ensure that we are capturing all the "legs" of the call i want to start with capturing the termination cause of the TL PBX to the phone device first. since the flow of a cell call would be:
PHONE > (Internet) > TL PBX > BILLING (ASTERISK) > UPSTREAM PROVIDER > CELL NETWORK > CELL PHONE
We will not be able to obtain the last three legs but we should at least be able to know the,
PHONE > (Internet) > TL PBX > BILLING (ASTERISK)
So far i have been able to capture the billing box termination cause into the CDR records. (16 being normal call termination)
So, how would include the termination cause into the CDR (MYSQL) for TL? Is this possible? My goal is to be able to show the clients that their calls where all terminated correctly (or not).