Details

    • Type: Bug Bug
    • Status: Closed
    • Severity: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Target Release Version/s: None
    • Component/s: Core/General
    • Labels:
      None
    • Mantis ID:
      240
    • Regression:
      No

      Description

      CDR not logging calls into Master.csv file that are made with call files that are dropped into /outgoing directory..

                • ADDITIONAL INFORMATION ******

      Maybe because I am using chan_capi but manually dialed calls are logged with no problems..

      Version : CVS-08/18/03-13:20:54

        Activity

        Hide
        gus added a comment -

        I'm moving asap 326 to 240.

        Show
        gus added a comment - I'm moving asap 326 to 240.
        Hide
        wipeout added a comment -

        After lots of playing I have worked out that the CDR does not log calls that use Application/Data as the desitination in the call file..

        If Context/Extension/Priority are used for the destination then it does log to the CDR..

        Also make sure to set the CallerID in the call file to your required source, typicaly this will be the extension of the person initiating the call, Otherwise the source field will be blank..

        Show
        wipeout added a comment - After lots of playing I have worked out that the CDR does not log calls that use Application/Data as the desitination in the call file.. If Context/Extension/Priority are used for the destination then it does log to the CDR.. Also make sure to set the CallerID in the call file to your required source, typicaly this will be the extension of the person initiating the call, Otherwise the source field will be blank..
        Hide
        Brian West added a comment -

        Any idea how to fix this? Or is this still an issue?

        Show
        Brian West added a comment - Any idea how to fix this? Or is this still an issue?
        Hide
        wipeout added a comment -

        I don't know about a fix, but a workaround is to use Context/Extension/Priority in the call file instead of Application/Data.. If Application/Data is used then it seems to bypass the process that tracks the call.. When using Context/Extension/Priority you are really using a Goto type function which just puts the call into the correct part of the dialplan and to it is the same as if the caller had dialed the call manually and so the call is logged..

        I am sure Mark and others have more important things to fix than this so I would say that the solution is to have a best practice of using Context/Extension/Priority..

        Show
        wipeout added a comment - I don't know about a fix, but a workaround is to use Context/Extension/Priority in the call file instead of Application/Data.. If Application/Data is used then it seems to bypass the process that tracks the call.. When using Context/Extension/Priority you are really using a Goto type function which just puts the call into the correct part of the dialplan and to it is the same as if the caller had dialed the call manually and so the call is logged.. I am sure Mark and others have more important things to fix than this so I would say that the solution is to have a best practice of using Context/Extension/Priority..
        Hide
        Brian West added a comment -

        It has been pointed out how to make calls be logged. If someone thinks this is still something needing fixed please msg me on irc (bkw_)

        Show
        Brian West added a comment - It has been pointed out how to make calls be logged. If someone thinks this is still something needing fixed please msg me on irc (bkw_)

          People

          • Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development