Genesys CTI User Forum
Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: maheshbabu on May 16, 2009, 06:03:12 AM
-
Hi All,
This is a problem we are facing in our organization for the past 3 days. We are unable to complete the conference call.
The conference gets initiated and when we try to complete the conference by clicking the conf button, the first party connected in the call gets disconnected and only the second party and the agent are connected finally.
......... Can any body suggest to get rid of this issue............
-
Maheshbabu, guys,
we can't analyze an issue just reading the description of it. If you require any help, please post the logs of the relevant app. All the rest is speculation.
Fra
-
Hey Fra,......... here is a call log ( T-server ) pasted for your reference in which we faced the problem...
Not only this particular call... every call that we attempt to make conference happens like the same as I mentioned earlier.............
+++ NewCall +++
@11:15:00.4060 {tscp.call {constructed} {uuid RPB5NCQOF54CL6RL4E7VJ8D8D800FHUE} {connection-id 009c01b0078e3a1e} {call-id 0}}
-- created call_info_tspp 009c01b0078e3a1e@032B9610
@11:15:00.4060 Call [009c01b0078e3a1e]: urid 0001009c
-- created aTmCall 03358970/032B9610
sipcs: CALL[154142l]:MEDIAMASK=0
-- TmCallThread created: 042C6000
SetANI for 03358970:1: 399
SetDNIS for 03358970:1: 309388437960
-- call_info::committed created
-- created party_info_tspp 044A7B78
-- created aTmParty 045FB8C0
sipcs: IFACE(207): << PARTY[355761]:0x45FB8C0 <<
sipcs: PARTY[355761:0x45FB8C0]: new SIPTS_Party
sipcs: +party [399@045fb8c0:0], call[009c01b0078e3a1e@03358970]
SetRole: Origination for 399.045FB8C0-03358970:1
-- AddParty to 03358970: 399.045FB8C0-03358970:1
-- new TSCP call leg 1
-- call leg created leg_id=1
CreateParty new internal: 399.045FB8C0-03358970:1
SetContext: for party 399.045FB8C0-03358970:1
@11:15:00.4060
* 7.5.000.41 distribute_event: message EventOffHook
AttributeEventSequenceNumber 00000000002038ba
AttributeTimeinuSecs 406000
AttributeTimeinSecs 1242279900 (11:15:00)
AttributeThisDN '399'
11:15:00.406 Int 04544 Interaction message "EventOffHook" generated
11:15:00.406 Trc 04542 EventOffHook sent to [2756] (00000b35 amb-rec-ser-01 172.20.191.213:1975)
masked for 452 (00000004 OCS_Ambattur)
11:15:00.406 Trc 04542 EventOffHook sent to [476] (00000006 ReportingStatServer_p 172.20.191.214:3367)
11:15:00.406 Trc 04542 EventOffHook sent to [464] (00000005 ReportingStatServer 172.20.191.214:3158)
11:15:00.406 Trc 04542 EventOffHook sent to [436] (00000003 StatServer 172.20.191.214:3103)
SetActive: party 399.045FB8C0-03358970:1, cause Null
sipcs: HA:PARTY[399@045fb8c0:0]:SetActive
SetOriginating: party 399.045FB8C0-03358970:1, cause NewCall
-- party_info 399.044A7B78 state change: from <Null> to <Initiated>
-- AgnEmu: btype Work related
-- G7 init
sipcs: HA:PARTY[399@045fb8c0:0]:SetOriginating
--- NewCall ---
-- AgnEmu: btype Work related
+++ Post-event +++
Type EventInitiated
Devices: <399/399> <-/309388437960> <-/->
Calls: 0/009c01b0078e3a1e/154142.03358970/c:1/r:0 0/none
Parties: D399/399.045FB8C0-03358970:1/l:1/r:0/Originating,Active,Origination
none
none
ANI/DNIS: <399> <309388437960>
Flags: divert=0 hook=1 postCall=0 active=1 moveAll=1 callType=1 hideOtherPi=0 InternalOther=0
--- Post-event ---
--- CIFace::Event ---
SIPS-IID:RPB5NCQOF54CL6RL4E7VJ8D8D800FHUE:009c01b0078e3a1e:RPB5NCQOF54CL6RL4E7VJ8D8D800FHUE:TLIBEVT
-- created party_info_tspp 0471CEB8
-- created aTmParty 04B03880
sipcs: IFACE(208): << PARTY[355762]:0x4B03880 <<
sipcs: PARTY[355762:0x4B03880]: new SIPTS_Party
sipcs: +party [309388437960@04b03880:0], call[009c01b0078e3a1e@03358970]
SetRole: Destination for 309388437960.04B03880-03358970:1
-- AddParty to 03358970: 309388437960.04B03880-03358970:1
-- new TSCP call leg 2
-- call leg created leg_id=2
CreateParty new external: 309388437960.04B03880-03358970:1
SetDialling: party 399.045FB8C0-03358970:1, cause Null
-- party_info 399.044A7B78 state change: from <Initiated> to <Connected,Dialing>
-- G7 dialing
@11:15:00.4060
* 7.5.000.41 distribute_response: message EventDialing
AttributeEventSequenceNumber 00000000002038bb
AttributeTimeinuSecs 406000
AttributeTimeinSecs 1242279900 (11:15:00)
AttributeExtensions [23] 00 01 01 00..
'BusinessCall' 2
AttributeReferenceID 63
AttributeANI '399'
AttributeDNIS '309388437960'
AttributeCallUUID 'RPB5NCQOF54CL6RL4E7VJ8D8D800FHUE'
AttributeConnID 009c01b0078e3a1e
AttributeCallID 154142
AttributeCallType 0
AttributeCallState 0
AttributeThisDNRole 1
AttributeAgentID '2509'
AttributeThisDN '399'
AttributeOtherDNRole 2
AttributeOtherDN '309388437960'
11:15:00.406 Int 04544 Interaction message "EventDialing" generated
11:15:00.406 Trc 04542 EventDialing sent to [2756] (00000b35 amb-rec-ser-01 172.20.191.213:1975)
11:15:00.406 Trc 04542 EventDialing sent to [452] (00000004 OCS_Ambattur 172.20.191.214:2757)
11:15:00.406 Trc 04542 EventDialing sent to [476] (00000006 ReportingStatServer_p 172.20.191.214:3367)
11:15:00.406 Trc 04542 EventDialing sent to [464] (00000005 ReportingStatServer 172.20.191.214:3158)
11:15:00.406 Trc 04542 EventDialing sent to [436] (00000003 StatServer 172.20.191.214:3103)
sipcs: HA:PARTY[399@045fb8c0:0]:SetDialing
SetDelivered: party 309388437960.04B03880-03358970:1, cause Null
-- TellDelivered
-- party_info 309388437960.0471CEB8 state change: from <Null> to <Alerting>
sipcs: HA:PARTY[309388437960@04b03880:0]:SetRinging
--- Dialing ---
FinishRequest CRequest@042E9E40 RequestMakeCall-amb-rec-ser-01[2756]/63
IFace stats: q=0 s=2
-- complete
-- deleted: CRequest@042E9E40 RequestMakeCall-amb-rec-ser-01[2756]/63
+++ Post-event +++
Type EventOriginated
Devices: <399/399> <-/309388437960> <-/->
Calls: 0/009c01b0078e3a1e/154142.03358970/c:2/r:0 0/none
Parties: D399/399.045FB8C0-03358970:1/l:1/r:0/Dialing,Active,Origination
X309388437960/309388437960.04B03880-03358970:1/l:2/r:0/Alerting,Destination
none
ANI/DNIS: <399> <309388437960>
Flags: divert=0 hook=1 postCall=0 active=1 moveAll=1 callType=1 hideOtherPi=0 InternalOther=0
--- Post-event ---
11:15:00.406 --- CIFace::Event ---
SIPS-IID:RPB5NCQOF54CL6RL4E7VJ8D8D800FHUE:009c01b0078e3a1e:RPB5NCQOF54CL6RL4E7VJ8D8D800FHUE:TLIBEVT
sipcs: party [399@045fb8c0:0] +dlg [425686@47f2260]
sipcs: dialog [425686:02@047f2260] : -party [@00000000] +party [399@045fb8c0]
sipcs: Reg. Info Party: dn[399]<=cme[399]
sipcs: Reg. Info: dn[399]<=cme[399]
sipcs: Reg. Info: dn[399]<=cme[399]
sipcs: SUBSCRIPTION MANAGER: NOTIFY >> "sip:399@172.20.191.218" {172.20.196.165:5060,UDP}
sipcs: Aquired Client Transaction (id=1755631)
sipcs: 11:15:00.406 Sending [420,UDP] 822 bytes to 172.20.196.165:5060 >>>>>
NOTIFY sip:399@172.20.191.218 SIP/2.0
From: <sip:gsipcti@172.20.191.218>;tag=8532CFF2-B5F8-4C81-9A7A-274088B3C9E3
To: "genesys" <sip:399@172.20.191.218>;tag=vabtw
Call-ID: tujlodsuekutprd@172.20.196.165
CSeq: 1242278983 NOTIFY
Content-Length: 424
Content-Type: application/xpidf+xml
Via: SIP/2.0/UDP 172.20.191.218:5060;branch=z9hG4bK27B7DA5B-E22A-4C0C-AF62-0813224CCE5F
Event: presence
<?xml version="1.0"?><!DOCTYPE presence SYSTEM "http://schemas.microsoft.com/2002/09/sip/presence"><presence><presentity uri="sip:399@172.20.191.218;method=SUBSCRIBE" /><atom id="0"><address uri="sip:gsipcti@172.20.191.218;user=ip" priority="0.800000"><status status="open" /><note><![CDATA[<gcti><action id="1242278982" type="accept" uri="sip:309388437960@172.20.191.218:5060"/></gcti>]]></note></address></atom></presence>
sipcs: party [399@045fb8c0:1]:ANSWER(GSIPCTI):FORCED
SIPS:LOGBLOCK:END:SIPDATA:]
-
This is not enough, please attach (better than post) the whole events sequence.
Fra
-
Hi Fra,
CHeck out with the logs attached here..
We are using Twinkle on linux PC's.... will there be any changes to be made in tat ???
-
Maheshbabu (or Vjmaheshbabu?),
1. I suggest you to remove your customers' info off the logs before attaching them
2. You have posted two not consecutive logs, the first ends @11:12:32.859, the second starts @11:13:45.093
3. Anyway, from the info I have:[list]
[li]agent 2509, logged on dn 399, dials ***7960[/li]
[li]requests conference call for recording[/li][/list]
###missing log###
[list][li]the agent seems now to be on a consult call with ***8946 [/li]
[li]the agent tries to initiate a conference calling again ***8946 (!!)[/li]
[li]obviously SIPServer doesn't really like that and responds with
[font=Times New Roman] [size=8pt]
sipcs: Call 0x045f1f30 is consult. No Consult call anymore
Response (496): for CRequest@042E9E40 RequestInitiateConference-amb-rec-ser-01[2756]/39
11:13:49.750 Trc 36002 Request rejected: error code 496(Call in invalid state)
@11:13:49.7500 [0] 7.5.000.41 send_to_client: message EventError
(Call in invalid state)
AttributeEventSequenceNumber 0000000000203061
AttributeTimeinuSecs 750000
AttributeTimeinSecs 1242279829 (11:13:49)
AttributeErrorCode 496
AttributeErrorMessage 'Call in invalid state'
AttributeThisDN '399'
AttributeConnID 009c01b0078e3956
AttributeOtherDN '***8946'
AttributeUserData [91] 00 01 00 00..
'GSIP_EMRGREC_FN' '2009-05-14\2509\2509_2009-05-14_309388437960_399_399_009c01b0078e3880'
AttributeReferenceID 39
AttributeClientID 2869
[/size][/font][/list]
[list][li]SIPServer doesn't get himself persuaded by the agent trying over and over again to initiate the conference call ;D[/li][/list]
Fra
-
Hi Mahesh,
I have some doubt in your question
1. Can i know which system platform (Windows or Linux) u used for agent login? U get the same issue in both platform or not?
2. If u click the conference button, the first party can listen the hold music or not?
Thanks n' Regards,
Sundaram
-
comment4,