Page 1 of 1
CDR for Failed Calls
Posted:
Fri May 01, 2009 2:29 pm
by globalme
We do get report for all calls connected.
But anyway to get report or list of all calls tried by dialer and rejected or not connected ?
Posted:
Fri May 01, 2009 7:16 pm
by mflorell
Those would be NA, DC and B mostly
What kind of report are you looking for?
Posted:
Fri May 01, 2009 7:19 pm
by globalme
Like Declined, Service Unavailable . etc from VOIP provider...
as we see in ASTERISK CLI ?
Posted:
Fri May 01, 2009 7:22 pm
by mflorell
That would be nice if service providers were consistent, but they are not unfortunately, and most of them do not follow industry standards.
A separate NA/DC/B call log is not a bad idea, but might not be that useful for actually fixing problems any more than the existing reports are already.
Posted:
Fri May 01, 2009 7:34 pm
by williamconley
Your provider may have more accurate results in their database. It could be time consuming to gather that data, but if you have a programmer build it ...you'll only have to do it once. Only helpful if your provider has call termination reasons stored in their CDR and will allow you to access it.
You can also check your SIP/agi debug information and see if they are providing enough detail TO YOU during the call. If they are it could be "logged" and mapped to the appropriate records. Certainly worth testing.
Does the Sangoma card give better (more accurate) results?
Posted:
Fri May 01, 2009 7:36 pm
by globalme
As far as I knoiw ,
Only helpful if your provider has call termination reasons stored in their CDR and will allow you to access it.
99.99 % Provider doesnt allow.
Posted:
Fri May 01, 2009 8:56 pm
by williamconley
depends on your level. if you use 500k minutes per month on a provider ... they will quite often be happy to give you any information you like. especially if you suggest this WILL help your ASR. especially since this information was already available to you to begin with. those who have reporting interfaces (for client billing) can be quite helpful in that regard.
But it is generally easier to just capture the information in the first place.
if it actually does go "shooting past" on the CLI ... it can be captured (and quite often is if you store all call detail information in asteriskcdrdb).