Genesys CTI User Forum

Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: mohit on April 19, 2011, 11:35:10 AM

Title: No Available Channel for this place , IWS
Post by: mohit on April 19, 2011, 11:35:10 AM

Hi,

I am facing issue, while logging into Interaction Workspace, I am getting an error "No available Channel for this Place". ???  Can anybody help me in getting a resolution to this issue???

Thanks in Advance

regards,
Mohit

Title: Re: No Available Channel for this place , IWS
Post by: smile on April 19, 2011, 01:28:52 PM

Channel or Task? do you disable rbac (security.disable-rbac=true) in IW configuration or do you assign right access role for person?

Title: Re: No Available Channel for this place , IWS
Post by: mohit on April 20, 2011, 05:12:07 AM

Hi,

Yes I have disable rbac. I tried enabling and assigned role too, still issue remains same.

Regards,
Mohit

Title: Re: No Available Channel for this place , IWS
Post by: smile on April 20, 2011, 05:57:21 AM

did you add tserver and interaction server to IW application? and also check that dn is assigned to place.
also check does your agent has access to environment (i mean you can view and read switch, place, dn and other objects)

Title: Re: No Available Channel for this place , IWS
Post by: mohit on April 29, 2011, 10:57:38 AM

Thanks for replying.

Issue got resolved, as i made a mistake by trying to access multimedia through IWS 8.0... Chat and Email is supported from 8.1 version of IWS. Thanks once again for the help...

:) Mohit

Title: Re: No Available Channel for this place , IWS
Post by: bvanhop on October 10, 2011, 04:48:10 PM

Hello Guys,

I m facing the same issue, although I just kept the voice role in the role definition.
Once I have to select the place I want to log onto, I get the same message as yours.
I m using a multi tenant environment.. i don't know if the issue remains there..

any ideas?

thanks
Bernard

Title: Re: No Available Channel for this place , IWS
Post by: a.jay on January 17, 2012, 08:37:54 AM

In the same issue was : "The solution was to add Users access group (where my agent is) RX permission on TServer application and Host of TServer as well."

It's a right solution, but the access can be Read permissions