On Wed, Nov 11, 2009 at 3:17 PM, Raymond Dans <[email protected]> wrote:
> Tony wrote: > > >Subject: [sipX-dev] CDR Status Codes Question > > > >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. > > For the case of abandoned calls, there is no change in 4.2 planned to > how these calls are tagged (i.e. Failed). It is certainly a change that > I'd like to see and will investigate it further to see if we can easily > distinguish an Abandoned calls version an actual failed called. > The scenario where you describe calls that go to voicemail are showing > as a failure, I've not seen before. They certainly should not be and > should be shown as Completed with an appropriate call length. Could you > open an issue on this please and indicate which voicemail system (i.e. > the internal or MS Exchange ...) > Thanks, I will work on a couple of samples this week and open this. What logging levels apart from the defaults are needed? I will ceate snapshot of the failed scenarios (or just logs) once I know what logging levels to inlcude (siptrace, snapshot or just logs, etc.). > > > > >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 > > In release 4.2 a number of new pieces of data have been added to the CDR > record to: > > 1. Indicate who actually answered the call (based on contact > information - not yet used in displaying the record) > 2. Indicate if a call was transferred (i.e. like in the case of going > to voicemail). > 3. Link calls logically together. This information is available in the > record but not yet used in displaying the record) > > The new data fields are intended primarily for use of 3rd party CDR > applications but will hopefully in the future also be used in Config > when displaying the historical records. > > Raymond I read through the CDR issues slated/assigned for 4.2 and didn't see one that showed calls linked together, but realize sometimes that separate items link to another. Wish they would show what gateway was used! Maybe another version down the road.
_______________________________________________ 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/
