CDR messages request for interpretation

Status
Not open for further replies.

Gurei123

SMB User
Advanced Certified
Joined
Feb 28, 2018
Messages
86
Reaction score
6
Good day.
I see the following messages in CDR cll logs when exported to an external application and am requesting for their interpretation or document therefore.
TerminatedByDst
TerminatedBySrc
Failed
Failed_Cancelled
TerminatedByRule
Thank you.
 
Have you checked this guideline for the supported output fields?
 
Hi Theodoros.
Thank you for the response. I require a list of reason-terminated and reason-changed messages and their interpretation or causes for these two output fields. I have given examples in my first post. The guideline that you have provided doesn't have such details.
Please assist further.
 
Hi there.
Do you mean you are looking for the reasons that the CDR can have?
 
  • reason-changed - The Reason why a change occurred in a call - example in a transfer you will see "ReplacedDst" which means that the destination was replaced with something else.
I am looking for all the possible messages for what I have colored in red for reason-terminated and reason-changed fields.
 
reason-changed we do not have specific info to provide you and each call could be checked in the CALL REPORT and if not clear, in the logs of the PBX.
Some of the outcomes are more straightforward forward such as:
Fwd_NoAnswer - forwarded on no answer
PickedUp - the call was picked up Dialcode for example
ReplacedDst - the destination was replaced with something else.
ReplacedSrc - the same as above but the source number was now replaced
 
I agree some of the outcomes are straightforward to interpret and for that that are not I can interrogate the system as you suggest. At this point I will be happy to get a list of the possible outcomes than for me to wait for when they show up for me to know them. Some of them have already showed up hence I could list them.
 
Below are the possible reason-terminated for the calls:

  • CallerDisabled: Caller is a disabled extension. - ExternalCallDisabled: The caller has the option "Disallow external calls" ticked
  • ExternalCallDirectionForbidden: Forbidden country code.
  • Failed: Call has failed, no further information. Had this case of calling externally and then the caller hung up before getting connected. Had also it in case the gateway timed out. Also can be push-related and a networking issue.
  • Failed_Cancelled: The call has failed and was cancelled, had this case when disconnecting the call from the console and also when Abandoned from the Switchboard before being connected. Also when a queue call goes to an agent who does not answer til ring timeout.
  • NoRouteExists: No outbound rules matching or rule with the blocked route or disabled trunk.
  • NotAvailable: could not replicate that one, but I believe is related to the trunk giving particular errors and failing to connect the call
  • PINProtected: Extension is PIN Protected to call out
  • Redirected: The call has been redirected by the endpoint before picking the handset.
  • RouteBusy: Outbound rule route is busy, or the agent actively rejects a call in the queue (send Busy).
  • RouteDisabled: Disbaled/Invalid route, had this case if transferring to invalid dial code such as *0 ending up with Forbidden as missing parking slot number.
  • TargetDisabled: Callee is a disabled extension.
  • TargetNotFound: Callee is not found in 404.
  • TerminatedByDst: The call has been terminated by the callee.
  • TerminatedByRule: The call has been terminated by the Forwarding Rule with the Terminate call route.
  • TerminatedBySrc: The call has been terminated by the caller.
  • FwdFailedNoOutboundRule: This is most likely due to forwarding to an external number which does not match your outbound rule
  • CallerBlacklisted : Caller is blacklisted
  • TargetBusy: Callee is busy (sends 486/end call)
 
  • Like
Reactions: Evolute IT
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,951
Messages
589,886
Members
164,843
Latest member
sambannoura