" /> Overflow Root Cause ? - Genesys CTI User Forum

Author Topic: Overflow Root Cause ?  (Read 2765 times)

Offline genecool

  • Jr. Member
  • **
  • Posts: 59
  • Karma: 0
Overflow Root Cause ?
« on: February 03, 2014, 10:30:00 AM »
Advertisement
Hi,

Have you any idea about the root cause of the following overflow ?


[code]
  +++ CIFace::Event +++
    +++ Pre-event +++
      Type EventDiverted
      Devices: <79427/-> <-/-> <-/->
      Calls: 0/006a023e43db688a/50228.27e8c78/c:2/r:0['c4 34'H] 0/none
      Parties: D79427/79427.29577e8-27e8c78:1/l:2/r:0/Queued,Destination[c='c4 3f'H r='24 00 15 e4'H d=dynamicID : '15 e4 01 04'H]
      none
      none
      Cause: Overflow/26, Info: 1793
      Flags: divert=0 hook=0 postCall=0 active=1 moveAll=1 callType=1 hideOtherPi=0 InternalOther=0
    --- Pre-event ---
    +++ Diverted +++
      DoDivert: from 79427.29577e8-27e8c78:1 cause Overflow
     
      +++ CSwitchEvent::Delete +++
        -- call retained
        Call 27e8c78:1 check scheduled at 09:25:26.127
      --- CSwitchEvent::Delete ---
    --- Diverted ---
    -- aTmParty::SetCause: Overflow
    +++ Post-event +++
      Type EventDiverted
      Devices: <79427/-> <-/-> <-/->
      Calls: 0/006a023e43db688a/50228.27e8c78/c:1/r:0['c4 34'H] 0/none
      Parties: D79427/79427.29577e8-27e8c78:1/l:2/r:0/Released,Destination[c='c4 3f'H d=dynamicID : '15 e4 01 04'H]
      none
      none
      Cause: Overflow/26, Info: 1793
      Flags: divert=0 hook=0 postCall=0 active=1 moveAll=1 callType=1 hideOtherPi=0 InternalOther=0
    --- Post-event ---
  --- CIFace::Event ---
[/code]

For your information, call comes from SIP Server to Alcatel TServer  and 79427 is and External Routing Point.

Thanks.

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: Overflow Root Cause ?
« Reply #1 on: February 03, 2014, 01:07:02 PM »
With this fragment of T-Server log is not possible to investigate anything. However, from the logs it seems like PBX "issue" - so try to investigate here (may be some RSI overflow or something like that)

Offline genecool

  • Jr. Member
  • **
  • Posts: 59
  • Karma: 0
Re: Overflow Root Cause ?
« Reply #2 on: February 07, 2014, 11:25:28 AM »
After analyzing a working case I found that in my wrong case there is not RequestRouteCall after the EventRouteRequest. Then, once the RSI overflow timer is reached, call is routed to the overflow address.

T-Server log shows the following lines after the EventRouteRequest :

[code]
@11:11:04.6870 [ISCC] Call had been matched/processed already
@11:11:04.6870 [ISCC] Call had been matched/processed already
@11:11:04.6870 [ISCC] Call had been matched/processed already
11:11:04.687 Int 04544 Interaction message "EventRouteRequest" generated
11:11:04.687 Trc 04542 EventRouteRequest sent to [700] (00000004 StatServer_URS_P 10.160.84.13:56471)
11:11:04.687 Trc 04542 EventRouteRequest sent to [692] (00000003 StatServer_CCA_P 10.160.84.44:50422)
11:11:04.687 Trc 04542 EventRouteRequest sent to [684] (00000002 StatServer_CCP_P 10.160.84.44:50423)
      DoDivert: from 79424.296c928-284cfd0:1 to 79435.296c7e0-284cfd0:1 cause NewCall
      inherit_queues: from 2936db0 to 29367c0
      -- inherit skipped
      -- party_info 79424.2936db0 state change: from <Alerting> to <Null>
      -- G7 release
@11:11:04.6870 [ISCC] Party removed [ssp view]:
@ c:006a023e43db88d2,02934200 @ m:0000000000000000,00000000,0000000000000000 p:3 i:0000ec5d nw:00000000:bcb4f4525bec0400 t:2
  p:02938440 @ c:006a023e43db88d2,02934200 r:1 t:1 s:1000c n:164537419
- p:02936db0 @ c:006a023e43db88d2,02934200 r:2 t:1 s:0 n:79424
  p:029367c0 @ c:006a023e43db88d2,02934200 r:2 t:0 s:809 n:79435
@11:11:04.6870 [ISCC] Party removed [kept for transit]:
@ c:006a023e43db88d2,02934200 @ m:0000000000000000,00000000 p:2 i:0000ec5d nw:bcb4f4525bec0400 t:2
- p:006a023e43db88d2,02936db0 @ c:006a023e43db88d2,02934200 r:2 c---- n:80001:SIPServer_P@Switch_SIP
  p:0000000000000000,029367c0 @ c:006a023e43db88d2,02934200 r:2 ----- n:79435:
      -- Cleanup call leg
      -- deleted aTmParty 296c928
      -- RemoveParty 79424.296c928-284cfd0:1
      -- deleted party_info_tspp 2936db0
    --- Ringing ---
    Call kill timer cancelled  for 284cfd0:1
    +++ Post-event +++
      Type EventRouteRequest
      Devices: <79435/-> <-/164537419> <-/79424>
      Calls: 60511/006a023e43db88d2/60509.284cfd0/c:2/r:0['ec 5d'H] 0/none
      Network ID: bcb4f4525bec0400:0
      Parties: D79435/79435.296c7e0-284cfd0:1/l:2/r:0/Queued,RtRequest,Destination[c='ec 5f'H r='7a 00 15 e4'H d=dynamicID : '15 e4 01 04'H]
      X164537419/164537419.296d0d8-284cfd0:1/l:1/r:0/Dialing,Origination[c='ec 5d'H d=dynamicID : '15 e4 01 04'H]
      none
      ANI/DNIS: <164537419> <79435>
      Cause: NewCall/22, Info: 0
      Call type: Inbound/2
      Flags: divert=0 hook=0 postCall=0 active=1 moveAll=1 callType=1 hideOtherPi=0 InternalOther=0
    --- Post-event ---
  --- CIFace::Event ---
11:11:04.687 --- Input ---
11:11:04.983 max bandwidth not updated, current value: 39
11:11:05.467 Trc 04541 RequestUpdateUserData received from [704] (00000005 URS_P 10.160.84.13:56472)
[/code]

Do you think that the "call kill timer" could explain my issue ?