Genesys CTI User Forum

Genesys CTI User Forum => Genesys-related Development => Topic started by: rajkishor09 on April 15, 2015, 01:43:37 PM

Title: Interaction Server Login Request Sequence
Post by: rajkishor09 on April 15, 2015, 01:43:37 PM
I am trying to built chat app and following is my Request sequence to login to Interaction Server. I am able to login successfully but I am not getting [b]EventInvite[/b] event on application when Customer is ready to chat. Any Idea what I missed?

First I am logging into Interaction server following below sequence
[list type=decimal]
[li]InteractionServerProtocol.Open[/li]
[li]RequestAgentLogin[/li]
[li]RequestAddMedia[/li]
[/list]
Then I log in chat server with below sequence. Still no [b]EventInvite[/b]
[list type=decimal]
[li]BasicChatProtocol.Open[/li]
[li]RequestRegister[/li]
[/list]
If I log into IWS then I am getting that Customer chat request and those two are able to exchange messages. So problem is in Interaction or BasicChat side. Any request is missing?
Title: Re: Interaction Server Login Request Sequence
Post by: Kubig on April 16, 2015, 10:31:22 AM
From my point of view, the right order is:

[list type=decimal]
[li]Open Connection[/li]
[li]Register client[/li]
[li]Login agent[/li]
[li]Add media[/li]
[li]Switch media status to the ready[/li]
[li]Request join[/li]
[/list]
Title: Re: Interaction Server Login Request Sequence
Post by: rajkishor09 on April 17, 2015, 01:03:06 PM
I tried to follow your sequence but I am getting below error when I am doing RegisterClient

[code]
'EventError' ('126')
message attributes:
attr_ref_id [int] = 2
attr_error_code [int] = 4
attr_error_desc [str] = "Unsupported protocol element"
[/code]

Log says

[code]
18:26:06.781 Trc 26015 Received message 'RequestRegisterClient' ('100') from client 'BasicChatApp' - Agent application:16:2628, message attributes:
attr_client_name [str] = "Place_SV_MCR"
attr_client_type [int] = 2 [AGENT APPLICATION]
attr_ref_id [int] = 2

18:26:06.781 Std 26006 Unsupported protocol message (100) received from client agent:16:2628
18:26:06.781 Trc 26016 Sending message 'EventError' ('126') to client 'BasicChatApp' - Agent application:16:2628, message attributes:
attr_ref_id [int] = 2
attr_error_code [int] = 4
attr_error_desc [str] = "Unsupported protocol element"
[/code]
Title: Re: Interaction Server Login Request Sequence
Post by: Kubig on April 17, 2015, 02:52:34 PM
You have posted you was successful -> http://www.sggu.com/smf/index.php/topic,8797.0.html
Title: Re: Interaction Server Login Request Sequence
Post by: rajkishor09 on April 17, 2015, 02:59:27 PM
If I skip Register Client request then I am able to login. But EventInvite is not firing.  Is Register Client is required to get EventInvite?
Title: Re: Interaction Server Login Request Sequence
Post by: gstkein on April 17, 2015, 06:08:17 PM
I do for 8.2

RequestAgentLogin
RequestAddMedia

Then RequestCancelNotReadyForMedia
and finally RequestChangeMediaStateReason: 

                requestChangeMediaStateReason.setMediaTypeName(mediaType);
ReasonInfo reasonInfo = ReasonInfo.create("","",0);
requestChangeMediaStateReason.setReason(reasonInfo);
Title: Re: Interaction Server Login Request Sequence
Post by: gstkein on April 17, 2015, 06:22:48 PM
I register to BasicChat after receiving the EventInvite
Title: Re: Interaction Server Login Request Sequence
Post by: rajkishor09 on April 20, 2015, 07:15:16 AM
Hi gstkein,

I followed your code sequence, there was no error from Interaction Server but there was no EventInvite also. Any further help is appreciated.
Title: Re: Interaction Server Login Request Sequence
Post by: Kubig on April 20, 2015, 07:48:00 AM
Use standard application (like IWS, GAD or something like that) and check the event-model and follow it within your code.
Title: Re: Interaction Server Login Request Sequence
Post by: gstkein on April 20, 2015, 06:44:01 PM
Are the capacity rules ok? Is the agent assigned to the proper groups or has the needed skills?

Does it work with GAD or IWS?
Title: Re: Interaction Server Login Request Sequence
Post by: rajkishor09 on April 21, 2015, 09:12:01 AM
Yes Its working with IWS, totally confused here  :o
Title: Re: Interaction Server Login Request Sequence
Post by: Kubig on April 21, 2015, 09:15:18 AM
As I wrote, check the event-model order and use it within your code/app.
Title: Re: Interaction Server Login Request Sequence
Post by: gstkein on April 23, 2015, 03:42:05 PM
Are we allowed to post old genesys code samples in here?
Title: Re: Interaction Server Login Request Sequence
Post by: cavagnaro on April 23, 2015, 04:14:46 PM
Don't see any reason why not. If G complains about CR we will remove the code then.
Title: Re: Interaction Server Login Request Sequence
Post by: gstkein on April 27, 2015, 04:48:05 PM
Here´s an old geneys email client example:

[url=https://mega.co.nz/#!ZwhwBbqL!ZP9qC9bV5TmcwuXiQ148b0qiKSXA3gz10B01vqSNtiA]https://mega.co.nz/#!ZwhwBbqL!ZP9qC9bV5TmcwuXiQ148b0qiKSXA3gz10B01vqSNtiA[/url]

Please erase this post if it is not appropiate.
Title: Re: Interaction Server Login Request Sequence
Post by: rajkishor09 on April 30, 2015, 12:20:37 PM
thanks gstkein, I will check your code and revert.
Title: Re: Interaction Server Login Request Sequence
Post by: gstkein on April 30, 2015, 02:31:44 PM
I hope it works, let me know if you figure out what was happening
Title: Re: Interaction Server Login Request Sequence
Post by: gstkein on April 30, 2015, 02:33:38 PM
The requirements for getting an EventInvite should be the same for all media.
Title: Re: Interaction Server Login Request Sequence
Post by: gstkein on April 30, 2015, 02:35:51 PM
Here I´ve found the CHAT client example

https://mega.co.nz/#!c8ZQ1SrY!EiXrOYRIAE6U4oHxXjg_t3IQpUdQ5OGogtE8LNeA48s
Title: Re: Interaction Server Login Request Sequence
Post by: rajkishor09 on June 17, 2015, 09:16:01 AM
Chat sample is working fine, thanks a lot.  ;D
Title: Re: Interaction Server Login Request Sequence
Post by: hamcro on July 11, 2016, 06:11:13 AM
Any chance that I can get a copy of that code sample, looks like its long since gone from the servers :)

Would be greatly appreciated, I'm facing similar problems.