Hello guys,
I’m having a lot of errors on RequestGiveRingBackTreatment:
“TMsg [RequestGiveRingBackTreatment(4092)] Generating EventError [56: ‘Invalid connection id’]”
Can you please explain how this RequestGiveRingBackTreatment can occur after on an invalid call?
Regards,
Valeriu
Has the call already been routed? Or hung up? or diverted somewhere other than the DN you were trying to put the ringback on.
OR is ringback a valid action to take at that point in the call?
Hi;
I offer check PBX log and TServer log files for error. Genesys assign an Connection id to call and follow all call operations this id. But pbx side unique number is call id. Sometimes TServer lose connection id information. Some of error i catch on my system pbx related. (not all of them) Sometime Pbx call id information changed(usually in incorrect transfer or conference operation). May be you have same problem. In TServer log files check connection id and call id information for related call.
Is the call failing or are these just events from the log ? A separate connection id can be generated for the consult portion of a call, i.e call transferred to/from IVR or external source. Depending on your URS configuration it may start running the strategy immediately for the consult portion of the call, thereby using that conn id. Once the call is established the consult call is destroyed and the original conn id is used. The router will issue a request for service on the consult connid, but as it’s destroyed t-server won’t recognise it and generate an invalid conn id message.
If you send the tserver/URS logs I can check this out for you.
I am facing the same issue,Its very important for me to solve this. Can you please help.
whenever a users is on a call suddenly the call drops. Whenever i tried to analyze the logs i found that there is no entry for that time in the CTI logs.
I took a look at the genesys toolkit 5.1(Tserver) logs and i found that there is a invalid ConnId. Error message is Invalid ConnId code 56.
Please suggest me some points to debug and solve this error.
Please post some logs and some call flow in order to be able to help, without them it is almost impossible for us to help, we can only guess.
Log…
Here is the Tserver log for the invalid ConnId, i have no idea from where 4c61… is coming from.
Is siebel sending it! Please help
12:35:35.293 Trc 04541 RequestHoldCall received from 2484 (90c3 Desktop Toolkit 5.1 OLE/COM)
message RequestHoldCall
AttributeThisDN ‘86449’
AttributeConnID 4c616e6775616765
AttributeExtensions [2] 00 00..
AttributeReason [75] 00 03 00 00..
‘Reason’ ‘Unknown’
‘Language’ ‘English’
‘Caller Type’ ‘Commercial Property’
AttributeReferenceID 114
12:35:35.293 Int 04543 Interaction message “RequestHoldCall” received from 2484 (“Desktop Toolkit 5.1 OLE/COM”)
@12:35:35.2930 [0] 7.2.011.00 send_to_client: message EventError
(Invalid connection id)
AttributeEventSequenceNumber 0000000003e073e1
AttributeTimeinuSecs 293000
AttributeTimeinSecs 1250098535 (12:35:35)
AttributeErrorCode 56
AttributeErrorMessage ‘Invalid ConnID’
AttributeReason [75] 00 03 00 00..
‘Reason’ ‘Unknown’
‘Language’ ‘English’
‘Caller Type’ ‘Commercial Property’
AttributeReferenceID 114
AttributeThisDN ‘86449’
12:35:35.293 Int 04545 Interaction message “EventError” sent to 2484 (“Desktop Toolkit 5.1 OLE/COM”)
12:35:35.293 Trc 04542 EventError sent to 2484 (90c3 Desktop Toolkit 5.1 OLE/COM)
Please, stop posting like that, we do not live here in the forum, we will help when we can, we also work you know?
Now, we need a complete log of the full ConnID you mention, not only a fragment.
Sandy,
I has been written here several times - this forum is run by Genesys users and fans. We all have our own jobs and helping the others in our free time. So posts like “Help Help” won’t help you at all… >
Back to your issue - based on provided snippet of log I can tell you only that request “RequestHoldCall” generated by T-Server client named “Desktop Toolkit 5.1 OLE/COM” contains wrong ConnectionId so T-Server rejects that request.
You can’t expect any help if you don’t provide us with relevant information… Post here T-Server log (debug mode) covering call from the beginning to the end and not only part showing the error if you expect some help!
R.
Sorry about that! My computer was behaving weird! Even i was Shocked to see that Help coming! I was trying to edit my existing post and it happened.
I always appreciate your help and is very happy that u guys are really helpful. I am really sorry for that mistake as even i was not aware why they appeared when i haven’t created them.
-Sandy
Thread edited, as requested.
T
Thanks, Sir!
Hi Sandy,
T-Server log attached to your last post isn’t very helpful. It does contain only the error message! We need to see whole call flow. How can I help you when not having clue what happened before the error occurred?
As I do understand your situation:
Is that right? If it is post here T-Server log covering call flow described above.
R.
You are sending us a log from @12:35:25.3240 to 12:35:35.293, in 10 seconds I doubt we can catch the whole call flow.
The only event is the
12:35:35.293 Trc 04541 RequestHoldCall received from 2484 (90c3 Desktop Toolkit 5.1 OLE/COM)
message RequestHoldCall
AttributeThisDN ‘86449’
AttributeConnID 4c616e6775616765
AttributeExtensions [2] 00 00..
AttributeReason [75] 00 03 00 00..
‘Reason’ ‘Unknown’
‘Language’ ‘English’
‘Caller Type’ ‘Commercial Property’
AttributeReferenceID 114
12:35:35.293 Int 04543 Interaction message “RequestHoldCall” received from 2484 (“Desktop Toolkit 5.1 OLE/COM”)
@12:35:35.2930 [0] 7.2.011.00 send_to_client: message EventError
(Invalid connection id)
AttributeEventSequenceNumber 0000000003e073e1
AttributeTimeinuSecs 293000
AttributeTimeinSecs 1250098535 (12:35:35)
AttributeErrorCode 56
AttributeErrorMessage ‘Invalid ConnID’
AttributeReason [75] 00 03 00 00..
‘Reason’ ‘Unknown’
‘Language’ ‘English’
‘Caller Type’ ‘Commercial Property’
AttributeReferenceID 114
AttributeThisDN ‘86449’
12:35:35.293 Int 04545 Interaction message “EventError” sent to 2484 (“Desktop Toolkit 5.1 OLE/COM”)
12:35:35.293 Trc 04542 EventError sent to 2484 (90c3 Desktop Toolkit 5.1 OLE/COM)
But there is not init for that ConnID or even an event for that DN…please, help us to help you…
Sandy,
Compressed attachments are allowed so the easiest way would be compressing (zip) your log and uploading it here.
R.
Sandy,
I’ve made quick analysis of your T-Server log and found some strange things:
** link[1] <> ** 12:35:27.7930 08 02 84 A8 62 96 1C 38 91 A1 35 02 01 02 02 01 95 40 2D 08 02 E1 99 0C 06 FF 38 36 30 35 30 10 02 1C 86 6C 06 FF 36 38 36 32 30 70 06 FF 38 36 38 35 31 96 0A 04 80 1F A0 83 44 01 82 47 01 81 === parsed message === prot_discr = 8 CRV = 84a8 MsgType = 98 (FACILITY)Facility: serv_discr = 17(q932_suppl) fac_ie = component_tag = A1(INVOKE)
invoke_id tag: 02, value = 2
operation tag: 02, value = 149(EventReport)
params = q931_tag = 40
list =
Cause: code_std_loc = 97(ASAI_PubNetLocUsr) cause = 25(C_FORWARD_BUSY)
Connected_Number: type_plan = 127(local) address = 86050
Call_Id: call_id = 7302
Calling_Party_Number: type_plan = 127(local) address = 68620
Called_Party_Number: type_plan = 127(local) address = 86851
Trunk_Group_Id: direction = 0 group_number = 250 member_number = 3
Party_Id: party_id = 2
Specific_Event: value = 1(Alerting)@12:35:27.7930 [0] 7.2.011.00 distribute_event: message EventRinging
AttributeEventSequenceNumber 0000000003e072f7
AttributeTimeinuSecs 793000
AttributeTimeinSecs 1250098527 (12:35:27)
AttributeThisTrunk 16384003
AttributeCallState 0
AttributeOtherDNRole 1
AttributeOtherDN ‘68620’
AttributeThisDNRole 2
AttributeThisDN ‘86050’
AttributeExtensions [22] 00 01 01 00..
‘TimeInQueue’ 0
AttributeDNIS ‘86851’
AttributeCallUUID ‘27FFA7E9-57D0-470B-93B3-ECAB6A03D4FB’
AttributeConnID 006601b3774eed34
AttributeCallID 7302
AttributeCallType 1
12:35:41.558 Trc 04541 RequestMakeCall received from 2916 (9168 Desktop Toolkit 5.1 OLE/COM) message RequestMakeCall AttributeThisDN '86050' AttributeOtherDN '68620' AttributeMakeCallType 0 (MakeCallRegular) AttributeUserData [166] 00 07 00 00.. 'Reason' 'Unknown' 'EndCallTime' 'NA' 'FirstCallID' '0' 'SiebelViewBmk' ' ' 'Call Purpose' 'Unknown' 'TNumber' 'x68620' 'CallNotifyText' 'Call to x68620 from USWTNS43...' AttributeExtensions [2] 00 00.. AttributeReason [78] 00 03 00 00.. 'Reason' 'New Claim' 'Language' 'English' 'Caller Type' 'Directory Assistance' AttributeReferenceID 101@12:35:41.5890 [0] 7.2.011.00 distribute_response: message EventDialing
AttributeEventSequenceNumber 0000000003e07504
AttributeTimeinuSecs 589000
AttributeTimeinSecs 1250098541 (12:35:41)
AttributeReferenceID 101
AttributeReason [78] 00 03 00 00..
‘Reason’ ‘New Claim’
‘Language’ ‘English’
‘Caller Type’ ‘Directory Assistance’
AttributeOtherDNRole 2
AttributeOtherDN ‘68620’
AttributeThisDNRole 1
AttributeThisDN ‘86050’
AttributeUserData [166] 00 07 00 00..
‘Reason’ ‘Unknown’
‘EndCallTime’ ‘NA’
‘FirstCallID’ ‘0’
‘SiebelViewBmk’ ’ ’
‘Call Purpose’ ‘Unknown’
‘TNumber’ ‘x68620’
‘CallNotifyText’ ‘Call to x68620 from USWTNS43…’
AttributeCallUUID ‘6B3575AB-D2DB-4A4B-AD60-D494B6B561C4’
AttributeConnID 006601b3774eed44
AttributeCallID 7348
AttributeCallType 1
And before this call is established the agent tries to transfer it??? Of course, such ends up with error. Seems to be PEBKAC (Problem between keyboard and the chair) 
Then the agent tries to hold the call (006601b3774eed44) and succeed
In next step agent answers call that is ringing on his extension for more than 10 seconds…
And the same call is answered at 12:35:46.105 so there is more than 10 seconds between ringing and established. Is that normal?
12:35:46.105 Trc 04541 RequestAnswerCall received from 2916 (9168 Desktop Toolkit 5.1 OLE/COM) message RequestAnswerCall AttributeThisDN '86050' AttributeConnID 006601b3774eed34 AttributeExtensions [2] 00 00.. AttributeReason [78] 00 03 00 00.. 'Reason' 'New Claim' 'Language' 'English' 'Caller Type' 'Directory Assistance' AttributeReferenceID 106
12:35:46.808 Trc 04541 RequestReleaseCall received from 2916 (9168 Desktop Toolkit 5.1 OLE/COM) message RequestReleaseCall AttributeThisDN '86050' AttributeConnID 006601b3774eed34 AttributeReason [78] 00 03 00 00.. 'Reason' 'New Claim' 'Language' 'English' 'Caller Type' 'Directory Assistance' AttributeExtensions [2] 00 00.. AttributeReferenceID 107
Honestly, I don’t know what the agent was doing but it seems to me as a “big chaos”. Maybe you can check with the agent what has happened…
The errors are caused by the agent that tries to work with call that doesn’t exist (wasn’t established)… The fact that call is routed to an agent that is busy (based on ASAI message) isn’t good as well.
Hope it helps you a bit.
R.
I would run to the CSA floor and try getting you some more logs. This issue happens for only couple of CSA and is very random. What is Keyboard and Chair problem?
The scenario is that the Agent can see the Answer Call flashing whenever he is receiving a call.When the user answers the call and if he needs to transfer it or hold it doesn’t work. I have told users to use hard phone to transfer the calls for time being but this is a very crucial issue and i really appreciate ur help. I have already attached genesys logs, did you find anything useful in that.
Thanks
S
lol, what is between the chair and the PC? Imagine…you are not a systems person, right?
Now René already told you some strange things he found, I also see that behaviour on logs, of course we trust what the logs says more that what your agents says…
I think you need someone who can analyze your system, review configurations and CC behaviour on site, we can help on a configuration issue but usually to someone who has some idea on how Genesys works and a CC integration. There is a limit for our forum support which is when you need an engineer on site.
I was appreciating Rene as he said its keyboard and chair problem 
Thanks a lot for ur help. Please let me know if you want to look at another TServer log, just as to confirm the behavior we were discussing earlier.
Please lemme know and i would get the tserver logs and upload here.
Thanks!
Sandy,
We have recently run into the same issue that you are having. We are using Siebel 6 and the OLE/COM 5.1 object as well. Our issues started after we introduced NICE perform (we have tried both single step transfer and service observer). We have narrowed the issue down to Siebel or the OLE/COM object by placing the Genesys Starter app softphone on the same client. When we had a call with the issue happen we had the user try using the starter app instead of Siebel to hold the call which worked. In addition where ever that incorrect connid is stored was replaced once we used the Starter App to hold the call and Siebel regained normal function. In our case the issue is sporadic and does not happen on every call and we are not able to reproduce it, so my best guess currently is it is some sort of timing issue.
Mike