https://community.cisco.com/t5/call-control/question-regarding-jtapi-metadata/m-p/4418159#M3106 <P>In general, JTAPI provides cause/reason codes associated with object events, e.g.</P> <P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot-20210614174226-1037x131.png" style="width: 999px;"><img src="https://community.cisco.com/t5/image/serverpage/image-id/122770iB6C6D101B2C030E9/image-size/large?v=v2&amp;px=999" role="button" title="Screenshot-20210614174226-1037x131.png" alt="Screenshot-20210614174226-1037x131.png" /></span>However, these can bit a bit limited as an infinite number of things that can happen to a call in the CUCM universe must be mapped to a limited number of defined cause/reason codes.</P> <P>It the JTAPI cause/reason codes are not enough to determine what 'really' happened, you will likely need to have someone look at the detailed CTI Manager and/or Callmanager logs to suss out the specific details...</P> Mon, 14 Jun 2021 22:45:45 GMT dstaudt 2021-06-14T22:45:45Z https://community.cisco.com/t5/call-control/question-regarding-jtapi-metadata/m-p/4416559#M3102 <P><SPAN>Is there any metadata collected by JTAPI which would indicate the disconnection reason?</SPAN></P> <P><SPAN>CUCM version12.5 SU3</SPAN></P> Fri, 11 Jun 2021 05:53:03 GMT https://community.cisco.com/t5/call-control/question-regarding-jtapi-metadata/m-p/4416559#M3102 eyalraba 2021-06-11T05:53:03Z https://community.cisco.com/t5/call-control/question-regarding-jtapi-metadata/m-p/4418159#M3106 <P>In general, JTAPI provides cause/reason codes associated with object events, e.g.</P> <P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot-20210614174226-1037x131.png" style="width: 999px;"><img src="https://community.cisco.com/t5/image/serverpage/image-id/122770iB6C6D101B2C030E9/image-size/large?v=v2&amp;px=999" role="button" title="Screenshot-20210614174226-1037x131.png" alt="Screenshot-20210614174226-1037x131.png" /></span>However, these can bit a bit limited as an infinite number of things that can happen to a call in the CUCM universe must be mapped to a limited number of defined cause/reason codes.</P> <P>It the JTAPI cause/reason codes are not enough to determine what 'really' happened, you will likely need to have someone look at the detailed CTI Manager and/or Callmanager logs to suss out the specific details...</P> Mon, 14 Jun 2021 22:45:45 GMT https://community.cisco.com/t5/call-control/question-regarding-jtapi-metadata/m-p/4418159#M3106 dstaudt 2021-06-14T22:45:45Z