I see a lot of failed calls in CDR using both an Ingate and sipXbridge. On my Ingate with inbound calls, I see "failed" a lot, which usually means to me the call came in, and the outside caller hung up instead of leaving a message. At the same time I see "Failed" when a call came in to a user and it went to voicemail. Even though the voicemail was left and the call ended "Successfully",CDR still shows "Failed, instead of Completed", with a "zero" (0) length call, which pretty much degrades the usefulness of CDR as a whole. I realize the call was not Successful to the end user, but the CDRdoes not show the media server and the proper length of the inbound call or the proper "Completed" status of the call.
Case2: I see even more of this in CDR with sipXbridge, in that it is very difficult to follow an inbound call to hunt groups, or the proper transfer of a call, and a call is hard to follow once a call is transferred from the AA to a user or hunt group and the from: contains ~~id~bridge and goes to ~~mh~ . What I would "expect" to happen would be "no answer" instead of failed", and or "left voicemail, 14 seconds, Completed". So my questions are, are there any forthcoming changes to CDR in the current 4.1 development version that might address the failed status to enhance it? Are there any upcoming changes to how CDR can show the flow of a call when using sipXbridge? If not, does enhancing the CDR to show a more meaningful status instead of just "failed". Perhaps adding a "callnumber" tag to allow looking up "that" call and seeing the path it takes from beginning to end in the drop down CDR for either superadmin and/or the UserUI? If there is nothing pending to address this, should it warrant a JIRA enhancement request? Thanks, Tony
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
