![]() Download the certificate in Certificate Path.Click Secure Token Server Configuration.Open Interaction Administrator on the PureConnect CIC server.If one certificate becomes invalid or expires, the backup certificate will preserve the integration.Ĭonfigure PureConnect Get the certificate for Genesys Cloud configurationįind and download PureConnect’s encoded public certificate for SAML signature validation. Administrators can choose to store one additional certificate to ensure business continuity.Verify that the required languages are available on the PureConnect CIC server. Only PureConnect supported languages are available to PureConnect users when they log in to Genesys Cloud.If your PureConnect hybrid organization already uses a single sign-on third party identity provider such a Microsoft Azure AD or Okta, this configuration is not needed.If there some information that you can provide to us that would help move our configuration forward we would be very grateful. However the phone would show as not Registered. Without the DNS and DHCP configurations we had been able to send text messages from one agent to another. Is this mixed domain configuration possible and if yes is there a work around for this type of configuration? For our situation would those changes need to be made in both domains, Domain A (local domain where we have the Agent Managed IP Softphones) and Domain B (Rackspace domain where the IC server is installed) ?Ģ.Ĝan we configure the local domain (Domain A) so that the softphones would reach the CIC servers?ģ. In the video at minute 3:55 the presenter is preparing to make changes to the DNS server. We have the CIC servers installed at our hosting provider which is not on the same domain as our office where the agent desktop and softphone.ġ. It has two domains over there - Voice and Data and he made changes in the DNS and DHCP configurations. ![]() The video talks about registration of IP phones before provisioning them and it was informative. Please find the details of the setup in the attached document. I get the error ?There is no contact address for your station? when I make callsĬould you please let me know how to resolve this problem? Is it due to two different domains used for the I3 server and the Client? Or any registration errors? In either case, if I use the full computer name in the managed IP phone configuration (provisioning happens successfully in this case as mentioned in the 10th page number of the document ) or if I do not use the full computer name (then I try to provide the admin user privileges to manually provision the soft phone in the client machine as informed in the page 11 of the above pdf document) - I still get that the IP phone is not registered and I am unable to make calls from Agent to Agent Station calls but I am able to initiate chat. So, as expected the managed IP phone gets provisioned in the client side but it shows as not registered in the Interactive Administrator as shown in the attached document: If I use the fully computer name in the Managed IP Phone Configuration the it should auto provision the managed IP phone. I have my I3 server in Domain A and Client in Domain B.īut when I try to provision my soft phone in the Client machine, I do not get the dial pad activated in the last screen of the provisioning wizard and it gets disconnected: In the same way, I have added IP address and fully qualified name of the I3 server in the host file of the Client. The Client machine is where I will login to the Interaction Desktop as the Agent. ![]() ![]() This means the host?s records / DNS entries are correct. I am still facing issues with Provisioning and Registration of the Managed IP Phones:įirst of all I have added the fully qualified domain name and the IP address of the Client machine in the hosts file of the server where the I3 is installed.
0 Comments
Leave a Reply. |