PureEngage On-Premises

 View Only

Sign Up

  • 1.  Getting EventEstablished before RequestAnswerCall

    Posted 03-18-2016 14:29
    Hi All,

    Greeting of the day..!!
    I am seeing EventEstablished for random inbound calls before RequestAnswerCall. This is leading to EventError - 'Incorrect object state' with below details : 

    17:52:33.472 +++ CIFace::Request +++
       -- new invoke
       -- thisCall by party
      Parsed: RequestAnswerCall
      From: anonymousTServerClient[46756]/1130
      Numbers: +<11612> -<none>
      Calls: 24b41110:1 none
      Parties: 11612.230327b0-24b41110:1
               none
      Status: parsed:1 queued:0 sent:0 acked:0 preevent:0 event:0 context:0 transferred:0
      -----
       -- validate
       -- state check: call is not alerted
      CIFace: request not valid
       -- thisCall by party
    17:52:33.472 Trc 36002 Request rejected: error code 1161(Incorrect object state)

    Users are getting Beep tone (whisper alter) with little delay.

    More log Snippets as below : 
    @17:52:32.8320 [0] 8.1.101.34 distribute_event: message EventRinging
    @17:52:32.8790 [0] 8.1.101.34 distribute_event: message EventEstablished
    17:52:33.472 Trc 04541 RequestAnswerCall received from [46756] (00043904 anonymousTServerClient 10.250.80.91:50635)
    message RequestAnswerCall
    @17:52:33.4720 [0] 8.1.101.34 send_to_client: message EventError

    Can someone help me to understand the root for this cause.


    Many Thanks,
    Manoj
     


  • 2.  RE: Getting EventEstablished before RequestAnswerCall

    Posted 03-21-2016 13:18
    In case you are using any external switch, you have to consult with PBX admin to find out the root cause, it seems like auto-answer function or something like that on PBX level


  • 3.  RE: Getting EventEstablished before RequestAnswerCall

    Posted 03-23-2016 23:46
    If your using Workspace with SIP endpoint and make sure you have auto-answer set to true only on one of the options: voice.auto-answer OR sipendpoint.genesyslab.control.auto_answer (or equivalent for 8.5 cant remember off the top of my head).  If you've got it set to true on both, SIPEndpoint will answer first and Workspace will also request under 3PCC causing the error.
    Generally recommend setting it on voice.auto_answer as it allows you to overwrite in routing if required.
    If your using a different SIP Endpoint/T-Server you'll likely find a similar configuration.