FAQs, Helpful Tips, and Screenshots

 View Only
  • 1.  CDR format custom

    Posted 04-22-2022 09:02 PM
    Hi, my question is very simple why CDR not display  ( haven´t )  one field the "Name description "  for example the extension or the loginID when it is created in the PBX?
    Only contains " Calling Number" o Called number ( all digits ) 
    My PBX is CM 6.3 Dup  where CDR Storage have customized and has external storage o be processed by an external provider
    Thanks,

    Regards

    ------------------------------
    Gustavo Caracciolo
    Customer Support Engineer
    Avaya
    Buenos Aires
    ------------------------------


  • 2.  RE: CDR format custom

    Posted 04-23-2022 01:23 PM
    Hello Gustavo,
    I'm not aware of any Communication Manager CDR fields that will show the name.  CDR packages tend to pair up this information by maintaining extension lists that are frequently updated, but that only covers that station and not the name of the inbound callers.  If you are using the Avaya SBC, you may get more information by looking at its CDR records.  Here's a link to the field definitions for the SBC: https://documentation.avaya.com/bundle/AdministeringAvayaSBCE_r7.2.2/page/CDR_file_field_description.html

    Unfortunately, in over thirty years of working with Avaya CM, the only development I've seen in this area is lengthening fields when CM was given longer extension lengths and allowing the media server to store records.  The CDR formats provided in CM are very simple.  Other platforms, for example Freeswitch, provide MOS scores and a host of information about each call and separate the report for the A and B call legs.  I WISH AVAYA WOULD FOLLOW SUIT.  Sounds like a feature request.

    I wish you luck.

    ------------------------------
    Tom Lynn
    ------------------------------



  • 3.  RE: CDR format custom

    Posted 04-23-2022 01:28 PM
    Edited by Tom Lynn 04-23-2022 02:43 PM
    There's also this page that discusses Session Manager CDR, but if you're not using SIP phones, CDR from SM and SBC will omit station to station calls.

    https://www.devconnectprogram.com/site/global/products_resources/avaya_aura_session_manager/interfaces/cdr/overview/index.gsp

    ------------------------------
    Tom Lynn
    ------------------------------



  • 4.  RE: CDR format custom

    Posted 04-23-2022 05:29 PM
    Hi Tom ,thanks you for your comments. I expected it.
    The customer use  protocol H323  with One X Communicator and  One X agent for the agents ( CallCenter / TLMK /Collections) and the trunks use inbound/ outbond E1 ( DIOD )  and ISDN ( TIE) for CISCO
    Nothing por SIP for this moments. may be in the future where if the problem would be solved.
    At the moment APS Upgrade Plataform 6.3 to 8.x  with VM CM cluster ( main and  ESS ) with GW650  , AES 5/7 to 8.x
    CMS 16.3 to  19.2  and the new SMGR 8.x  only for license , nothing SM, SBC, AMS.
    Thanks for the links!!!

    Best regards,







    ------------------------------
    Gustavo Caracciolo
    Customer Support Engineer
    Avaya
    Buenos Aires
    ------------------------------



  • 5.  RE: CDR format custom

    Posted 04-23-2022 07:40 PM
    The most interesting part of your upgrades, as it pertains to your question, is AES.  I'm not sure your licensing would be sufficient, but if your stations or trunk were monitored, you might be able to get the name provided on the inbound calls logged.


    ------------------------------
    Tom Lynn
    ------------------------------



  • 6.  RE: CDR format custom

    Posted 04-24-2022 02:28 PM
    Hi Tom, I'm telling you this AES is used for connection to Alvaria-Belltech (unified IP) Nice/Verint and IVR with AEP.
    That's why my question was very simple that my client asked me regarding the Primary CDR
    Why is there no "display name" field in the extension or agent ID in the CDR output format? Simple : "no alphanumeric characters" and don't use SIP, use H323 and done.
    And it is what you indicated in the previous post.
    The customer thinks that enable functions (system parameters), intraswitch, intraswitch by COS, raw format should show it, and compares Avaya PBX with CISCO PBX that does, but as I clarified, CISCO handles SIP.
    Now, both myself and the client ask me this question: how is it possible that when registering an extension or an agent loginID it does not save the number with the name in the relation table?
    I'll have to engage Avaya Professional Services to implement a build and get them a quote.
    Thank you very much for your comments and your technical background.

    Regards,


    Gustavo 



    ------------------------------
    Gustavo Caracciolo
    Customer Support Engineer
    Avaya
    Buenos Aires
    ------------------------------