CS1K 7.65SW/CDR format mismatch between 7.5 and 7.65

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • smaiyaur
    Guru
    .
    • Nov 2013
    • 107

    CS1K 7.65SW/CDR format mismatch between 7.5 and 7.65

    PROBLEM TEXT:
    Customer's CDR parser is unable to work with new CDR format since R7.6.
    Line 3 length was increased from 51 characters to 53 characters.

    SETUP AND ACTIONS PERFORMED TO CAUSE THE PROBLEM:
    1. Configure CDR.
    2. Make a call.
    3. Check the CDR record for the call.

    RELEVANT CONFIGURATION INFO:
    CDR is configured.

    UPGRADE/FRESH INSTALL: upgrade from R7.5 to R7.6

    EXPECTED RESULTS:
    1. CDR is configured.
    2. The call is established.
    3. CDR record's line 3 length has 51 characters.

    ACTUAL RESULTS:
    1 - 2. As expected.
    3. CDR record's line 3 length has 53 characters.

    END USER IMPACT OF PROBLEM:
    CDR parser is unable to work with new CDR format since R7.6. Cannot collect CDR statistics.


    The new design added the char C, or A, or two spaces to
    indicate the side disconnected from the ACD call. A - ACD agent disconnected, C - a
    caller disconnected in case ACDD in the CDR block is set to Yes. If ACDD is set to
    No, two spaces are printed out. The customer's setting is No, so 2 spaces are
    printed out. This behaviour will be documented.

    Avaya is aware of the issue and working on a fix for this issue.
  • smaiyaur
    Guru
    .
    • Nov 2013
    • 107

    #2
    Patch MPLR33093 for the 7.65 system to avoid the printing of two extra character when ACDD is set to NO

    Comment

    • micwood
      Whiz
      .
      • Oct 2013
      • 39

      #3
      Is there a Knowledge Base article that addresses this situation ? The number please.

      Comment

      • smaiyaur
        Guru
        .
        • Nov 2013
        • 107

        #4
        kb number is SOLN242838

        Comment

        • smaiyaur
          Guru
          .
          • Nov 2013
          • 107

          #5
          - R7.6 and CDR
          o A new PSN 4144 is in process of being published and should be on the Support Portal today / tomorrow.
          o This is for new MPLR33093 which can resolve a potential issue for some third party CDR applications, due to new ACDD functionality added in R7.6.

          Comment

          • smaiyaur
            Guru
            .
            • Nov 2013
            • 107

            #6
            The ACD Detailed Call Detail Recording (CDR) call release indicator functionality is added in R7.6. This feature allows CDR blocks configured for ACD agents to indicate whether a call was disconnected by the call originator or by the ACD agent. When printed, this indicator displays in the third line of the CDR record as either C (caller) or A (agent).
            The ACDD (ACD Detailed) parameter in the Customer Data Block (CDB) configuration for LD15 can have a value of YES (print the call disconnect indicator) or NO (do not print the call disconnect indicator). The default value is NO.
            ACD Package 45 (ACDA) must be unrestricted to use this feature.
            It has been noted that even with ACDD = NO in LD15, there is still an impact on line 3 of the CDR record – an extra two spaces are printed, extending the length from original 51 characters as in R7.5 to 53 characters. This can potentially cause an issue for some CDR applications.
            Patch MPLR33093 is now available in ESPL to revert line 3 of the CDR record from 53 characters to the original 51 characters in the case where ACDD = NO in LD15. This removes any possible issues for the CDR applications.

            Comment

            Loading