Avaya Contact Recorder 403

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • shawk3
    Aspiring Member
    • Jul 2017
    • 2

    Avaya Contact Recorder 403

    I experienced this "Bad HTTP status code (403)" when try to play recorded calls.
    Avaya Contact Recorder R9.1
  • sbhano
    Whiz
    • Nov 2014
    • 38

    #2
    Its Time mismatch error.
    Check the timing at you IPO Server(Can verify in SSA) and client PC ( from where you were trying to open recorder), match the timings, it will work.

    Comment

    • shawk3
      Aspiring Member
      • Jul 2017
      • 2

      #3
      Originally posted by sbhano View Post
      Its Time mismatch error.
      Check the timing at you IPO Server(Can verify in SSA) and client PC ( from where you were trying to open recorder), match the timings, it will work.

      Unfortunately the time is correct, do you have other solution.

      Comment

      • sbhano
        Whiz
        • Nov 2014
        • 38

        #4
        Is it happening at all PC's or any specific user?

        Comment

        • husaia
          Aspiring Member
          • Jul 2017
          • 1

          #5
          Thanks it's worked for me

          Comment

          • hcouplet
            Aspiring Member
            • Dec 2011
            • 1

            #6
            Originally posted by husaia View Post
            Thanks it's worked for me
            What did you do to fix this?

            Comment

            • tdaway
              Whiz
              • Jun 2014
              • 31

              #7
              Mine as well, cant access recordings from any PC, we get error which says ( The website’s security certificate is not yet valid or has expired.
              The hostname in the website’s security certificate differs from the website you are trying to visit.
              The website’s security certificate has a weak signature and is not secure.
              )

              Error Code: DLG_FLAGS_SEC_CERT_DATE_INVALID
              DLG_FLAGS_SEC_CERT_CN_INVALID
              DLG_FLAGS_WEAK_SIGNATURE

              Comment

              • markgallagher
                Legend
                .
                • May 2010
                • 613

                #8
                @tdaway - Very clearly a different issue even if it has the same result for users. You should start a new thread rather than hijacking an existing one as discussion of two different problem scenarios in one thread leads to confusion.

                Comment

                Loading