" /> Troubleshooting a generic error code 50 on WDE - Genesys CTI User Forum

Author Topic: Troubleshooting a generic error code 50 on WDE  (Read 1317 times)

Offline Gef Buneri

  • Sr. Member
  • ****
  • Posts: 373
  • Karma: 0
  • Madness is just a point of view.
Troubleshooting a generic error code 50 on WDE
« on: November 04, 2022, 12:48:53 PM »
Advertisement
Hello all, hope everything's ok out there. I'm trying to troubleshoot a very rare and randomic "generic error 50" on certain WDEs. Any clue? this points are relevant, to me, but where to look at any doc that could help me out? (Reason: SIP;cause=408;text="timeout-ST" and Request rejected: error code 237)

11:28:20.298: $-NET:SIP::0:0

11:28:20.299: $+NET:SIP::0:0
11:28:20.299: SIPTR: Received [0,UDP] 476 bytes from [IPADDRESS]:[PORT] <<<<<
BYE sip:[CALLER]@[IPADDRESS]:[PORT] SIP/2.0
From: <sip:[ORIGINRP]@[IPADDRESS]:[PORT]>;tag=D16BA5D5-ACFD-487F-8A27-65E44818B429-21
To: sip:[CALLER]@[SBCADDRESS];tag=0076DE50-4A29-11C9-A4FE-D95E270AAA77-18453231
Call-ID: 0076DE32-4A29-11C9-A4FE-D95E270AAA77-14475655@[IPADDRESS]
CSeq: 1 BYE
Content-Length: 0
Via: SIP/2.0/UDP [IPADDRESS]:[PORT];branch=z9hG4bKB702BDF4-741E-47A4-9BF0-EE0A81678386-725
Max-Forwards: 70
Reason: SIP;cause=408;text="timeout-ST"


11:28:20.299: SIPDLG[12208634]: register TRN[209576992]
11:28:20.300: SipDialog: event BYE, t=209576992, s=8, r=5, m=129f33f8 port=5060
11:28:20.300: CID:CUUID>0076DE32-4A29-11C9-A4FE-D95E270AAA77-14475655@[IPADDRESS]:01VJTH2A548SJ97UR5F2E2LAES03O7G4:
11:28:20.300 SIPCONN([EXTENSIONDN]): HandleSipDialogEvent(BYE)
11:28:20.300 SIPCONN([EXTENSIONDN]): new transaction
11:28:20.300 SIPCONN([EXTENSIONDN]): 1pcc event BYE
11:28:20.300 SIPCONN([EXTENSIONDN]): SendResponse(200,209576992)
11:28:20.300: add party info '[EXTENSIONDN]' state 2.
11:28:20.300: SipAssert: SipContent.cpp,377 - m_content
11:28:20.300: ERROR: 10000000, GetOrCreateSdpPart(sdpPart), SipContent.cpp,1494
11:28:20.300: Sending  [0,UDP] 679 bytes to [IPADDRESS]:[PORT] >>>>> SIP/2.0 200 OK
From: <sip:[ORIGINRP]@[IPADDRESS]:[PORT]>;tag=D16BA5D5-ACFD-487F-8A27-65E44818B429-21
To: sip:[CALLER]@[SBCADDRESS];tag=0076DE50-4A29-11C9-A4FE-D95E270AAA77-18453231
Call-ID: 0076DE32-4A29-11C9-A4FE-D95E270AAA77-14475655@[IPADDRESS]
CSeq: 1 BYE
Via: SIP/2.0/UDP [IPADDRESS]:[PORT];branch=z9hG4bKB702BDF4-741E-47A4-9BF0-EE0A81678386-725;received=[IPADDRESS]
Contact: <sip:[CALLER]@[IPADDRESS]:[PORT]>
X-Genesys-CallUUID: 01VJTH2A548SJ97UR5F2E2LAES03O7G4
Allow: INVITE, ACK, PRACK, CANCEL, BYE, REFER, INFO, UPDATE, MESSAGE, NOTIFY, OPTIONS
P-Asserted-Identity: <sip:[CALLER]@[SBCADDRESS]>
Supported: uui,replaces
Content-Length: 0

11:28:20.300: SipDialog: event TERMINATING_SEND_BYE_RES, t=209576992, s=9, r=8, m=129f33f8 port=[PORT]
11:28:20.300: CID:CUUID>0076DE32-4A29-11C9-A4FE-D95E270AAA77-14475655@[IPADDRESS]:01VJTH2A548SJ97UR5F2E2LAES03O7G4:
11:28:20.300 SIPCONN([EXTENSIONDN]): HandleSipDialogEvent(TERMINATING_SEND_BYE_RES) - filtered
11:28:20.300 SIPCONN([EXTENSIONDN]): ClrMediaPeer
11:28:20.300 SIPCONN([CALLER]): ClrMediaPeer
11:28:20.300 SIPCONN([EXTENSIONDN]): CONNCHECK: dialog=9
11:28:20.300 SIPCONN([EXTENSIONDN]): set monitor 129f3320, 0
11:28:20.300 SIPCONN([EXTENSIONDN]): state e:1,p:2,s:0,c:8,rc:0,m:0
11:28:20.300: SipDialog: ClearCall(phone=1,state=9)
11:28:20.300: SipDialog::Terminate(state=9,reason=0)
11:28:20.300: SipDialog: set monitor 0
11:28:20.300 SIPCONN([EXTENSIONDN]): DetachMediaPeer
11:28:20.300 Trc 36002 Request rejected: error code 237(call disconnected)
@11:28:20.3004 [0] 8.1.103.66 send_to_client: message EventError
(Call has disconnected)
AttributeEventSequenceNumber 00000000132a1951
AttributeTimeinuSecs 300413
AttributeTimeinSecs 1667557700 (11:28:20)
AttributeErrorCode 237
AttributeErrorMessage 'call disconnected'
AttributeConnID 006d032c2ed9ddff
AttributeThisDN '[EXTENSIONDN]'
AttributeReferenceID 83
AttributeClientID 58444
11:28:20.300 Int 04545 Interaction message "EventError" sent to 74 ("[WDENAME]_[AGENTLOGIN]")
11:28:20.300 Trc 04542 EventError sent to [74] (0000e44c [WDENAME]_[AGENTLOGIN] [IPADDRESS]:[PORT])
11:28:20.300  -- setting cntrlDN=[EXTENSIONDN] (for 1 parties)
11:28:20.300  -- setting cntrlDN=[EXTENSIONDN] (for 1 parties)
11:28:20.300: Adding OtherTrunkName([TRUNKNAME]): done
11:28:20.300 ClearContext: party [EXTENSIONDN].1293dce0-12498e30:1
11:28:20.300 +++ CIFace::Event +++
  +++ Pre-event +++
    Type EventReleased
    Devices: <[EXTENSIONDN]/[EXTENSIONDN]> <-/[CALLER]> <-/->
    Calls: 20717060/006d032c2ed9ddff/20717060.12498e30/c:2/r:8 0/none
    Parties: D[EXTENSIONDN]/[EXTENSIONDN].1293dce0-12498e30:1/l:2/r:2/Alerting,DNull,Destination
    X[CALLER]/[CALLER].11d322d0-12498e30:1/l:1/r:0/Dialing,Origination
    none
    Flags: divert=0 hook=1 postCall=0 active=1 moveAll=1 callType=1 hideOtherPi=0 InternalOther=0
  --- Pre-event ---
  +++ Released +++
    -- XAction: start [EXTENSIONDN].1293dce0-12498e30:1
    SetReleased: party [EXTENSIONDN].1293dce0-12498e30:1, cause Null
    -- party_info [EXTENSIONDN].1028ef90 state change: from <Alerting> to <Null>
    -- G7 release

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Troubleshooting a generic error code 50 on WDE
« Reply #1 on: November 04, 2022, 03:33:42 PM »

[quote]
11:28:20.300: ERROR: 10000000, GetOrCreateSdpPart(sdpPart), SipContent.cpp,1494
[/quote]


Maybe some calls are arriving without SDP? Or in wrong expected message?

Offline Gef Buneri

  • Sr. Member
  • ****
  • Posts: 373
  • Karma: 0
  • Madness is just a point of view.
Re: Troubleshooting a generic error code 50 on WDE
« Reply #2 on: November 04, 2022, 04:01:54 PM »
Hi Cav! it seems that SDP error is present in any call, even OK ones.

Offline hsujdik

  • Hero Member
  • *****
  • Posts: 541
  • Karma: 30
Re: Troubleshooting a generic error code 50 on WDE
« Reply #3 on: November 04, 2022, 08:12:03 PM »
I see that your EventError has a Request associated. What was the request that the SIP Server client (WDE) sent? Look on the log file backwards for the "AttributeReferenceID 83" that is before the EventError (not always 83, only in that example because it is the sequential ID of the request performed by the client).
It probably could be some RequestSendDTMF, RequestSingleStepTransfer, RequestInitiateTrasnfer, RequestAnswerCall, RequestHoldCall... anything like that?

Also, are always the same DNs that randomly have this error? Or are they random?

Offline Gef Buneri

  • Sr. Member
  • ****
  • Posts: 373
  • Karma: 0
  • Madness is just a point of view.
Re: Troubleshooting a generic error code 50 on WDE
« Reply #4 on: November 09, 2022, 02:11:07 PM »
Hello Hsujdik, IDs are random, here's a bunch examples.

AttributeReferenceID 25
AttributeReferenceID 18
AttributeReferenceID 64
AttributeReferenceID 67
AttributeReferenceID 9
AttributeReferenceID 13

All DNs receiving that call flow, from that specific number, experience this error; It's for sure something related to the SBC in front of the SIP Server, but I really can't figure anything from SIP Server's logs.
« Last Edit: November 09, 2022, 02:17:50 PM by Gef Buneri »

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Troubleshooting a generic error code 50 on WDE
« Reply #5 on: November 09, 2022, 03:14:38 PM »
Check the SDP ;) You will see some difference or where the SDP comes in (invite or ACK)

Offline Gef Buneri

  • Sr. Member
  • ****
  • Posts: 373
  • Karma: 0
  • Madness is just a point of view.
Re: Troubleshooting a generic error code 50 on WDE
« Reply #6 on: November 09, 2022, 03:31:37 PM »
[quote author=cavagnaro link=topic=12360.msg55085#msg55085 date=1668006878]
Check the SDP ;) You will see some difference or where the SDP comes in (invite or ACK)
[/quote]

Ok!