" /> Problems with SIPDialog between Genesys SIP Server and Avaya SES - Genesys CTI User Forum

Author Topic: Problems with SIPDialog between Genesys SIP Server and Avaya SES  (Read 3508 times)

Offline aochoavidaur

  • Newbie
  • *
  • Posts: 2
  • Karma: 0
Problems with SIPDialog between Genesys SIP Server and Avaya SES
« on: November 13, 2012, 07:14:40 AM »
Advertisement
Hi, there is a problem with the blind transfer between GVP and Avaya SES. Sometimes the SIP Dialog isn't established. Here is the log for a wrong call and a correct call. Can I determine if the caller hang-up?

[b]Wrong call:[/b]
@13:16:53.6200 [ISCC] Translate: '968641407' -> ''; result 1 ()
@13:16:53.6200 [ISCC] Party object is removed: p:0000000000000000,00000000 n::
@13:16:53.6200 [ISCC] Error: No call is associated with the event, skipped
@13:16:53.6200 [ISCC] Error: No call is associated with the event, skipped
@13:16:53.6200 [ISCC] Error: No call is associated with the event, skipped
@13:16:53.6200 [ISCC] Error: No call is associated with the event, skipped
13:16:53.620 Int 04544 Interaction message "EventReleased" generated
13:16:53.620 Trc 04542 EventReleased sent to [596] (0000000e LDServer 10.4.213.50:1547)
13:16:53.620 Trc 04542 EventReleased sent to [584] (0000000d LDServer 10.4.213.50:1546)
13:16:53.620 Trc 04542 EventReleased sent to [572] (0000000c StatServer_CCP_bck 10.4.213.32:2090)
13:16:53.620 Trc 04542 EventReleased sent to [560] (0000000b StatServer_URS_bck 10.4.213.37:1758)
13:16:53.620 Trc 04542 EventReleased sent to [548] (0000000a LDServer_bck 10.4.213.28:2053)
13:16:53.620 Trc 04542 EventReleased sent to [508] (00000007 StatServer_URS 10.4.213.55:4454)
13:16:53.620 Trc 04542 EventReleased sent to [496] (00000006 StatServer_CCP 10.4.213.53:2510)
@13:16:53.6200 [ISCC] Call destroyed:
                - c:00be021781d8bd25,01c90ff0 @ m:0000000000000000,00000000 p:0 i:0018c1a6 nw:0000000000000000 t:2
@13:16:53.6200 [ISCC] Call object is removed: c:00be021781d8bd25,00000000
13:16:53.620  -- call_info::committed destroyed
13:16:53.620  -- deleted call_info_tspp 00be021781d8bd25@01C90FF0
@13:16:53.6200 {tscp.call {destructed} {uuid 6TTMUFO9HP2S7AQVKHQ20US23O04DU5O} {connection-id 00be021781d8bd25} {call-id 1622438}}
[color=red]13:16:53.620 SipDialog: event DESTROY, t=0, s=10, r=4, m=00000000
13:16:53.620 SipDialog[3594010]:<< Abort ALL <<[/color]
@13:16:53.6200 [BSYNC] Trace: Send to backup (SIP_Server_bck) [452]:

[b]Correct call:[/b]
@14:01:05.0410 [ISCC] Translate: '915127199' -> ''; result 1 ()
@14:01:05.0410 [ISCC] Party object is removed: p:0000000000000000,00000000 n::
@14:01:05.0410 [ISCC] Error: No call is associated with the event, skipped
@14:01:05.0410 [ISCC] Error: No call is associated with the event, skipped
@14:01:05.0410 [ISCC] Error: No call is associated with the event, skipped
@14:01:05.0410 [ISCC] Error: No call is associated with the event, skipped
14:01:05.041 Int 04544 Interaction message "EventReleased" generated
14:01:05.041 Trc 04542 EventReleased sent to [596] (0000000e LDServer 10.4.213.50:1547)
14:01:05.041 Trc 04542 EventReleased sent to [584] (0000000d LDServer 10.4.213.50:1546)
14:01:05.041 Trc 04542 EventReleased sent to [572] (0000000c StatServer_CCP_bck 10.4.213.32:2090)
14:01:05.041 Trc 04542 EventReleased sent to [560] (0000000b StatServer_URS_bck 10.4.213.37:1758)
14:01:05.041 Trc 04542 EventReleased sent to [548] (0000000a LDServer_bck 10.4.213.28:2053)
14:01:05.041 Trc 04542 EventReleased sent to [508] (00000007 StatServer_URS 10.4.213.55:4454)
14:01:05.041 Trc 04542 EventReleased sent to [496] (00000006 StatServer_CCP 10.4.213.53:2510)
@14:01:05.0410 [ISCC] Call destroyed:
                - c:00be021781d8bfc9,02976780 @ m:0000000000000000,00000000 p:0 i:0018c44a nw:0000000000000000 t:2
@14:01:05.0410 [ISCC] Call object is removed: c:00be021781d8bfc9,00000000
14:01:05.041  -- call_info::committed destroyed
14:01:05.041  -- deleted call_info_tspp 00be021781d8bfc9@02976780
@14:01:05.0410 {tscp.call {destructed} {uuid 6TTMUFO9HP2S7AQVKHQ20US23O04ECJ4} {connection-id 00be021781d8bfc9} {call-id 1623114}}
14:01:05.041 -----------------------------------------------------------
[color=red]14:01:05.041 C[1623114]:CF[D[[0]]:SC[2991293]
14:01:05.041 HA: BEGIN SYNC: CALL[1623114] SYNCTYPE[4]: SECOND CALL[0] SYNCTYPE[-1]
14:01:05.041 HA: END SYNC: CALL[1623114] SYNCTYPE[4]: SECOND CALL[0] SYNCTYPE[-1][/color]
@14:01:05.0410 [BSYNC] Trace: Send to backup (SIP_Server_bck) [452]:

Thanks

Offline Fra

  • Hero Member
  • *****
  • Posts: 856
  • Karma: -3
Re: Problems with SIPDialog between Genesys SIP Server and Avaya SES
« Reply #1 on: November 13, 2012, 01:04:26 PM »
You have published a few lines after the very last event (EventReleased). That's not going to tell us anything about your potential issue.

Fra

Offline bublepaw

  • Sr. Member
  • ****
  • Posts: 283
  • Karma: 10
Re: Problems with SIPDialog between Genesys SIP Server and Avaya SES
« Reply #2 on: November 14, 2012, 07:41:01 AM »
To determine if customer hangup please enable proper option in TServer section of SIP Server and look at Extension data attached to Released event