ScottBub | 2017-03-10 16:25:18 UTC | #1
Hello All,
We are having an issue using Postman to test. Here is the background...
We have a bridge server, data dip connector, connector actions, a separate web service server, and a database server. The bridge server has the IP of our web service server as the endpoint. We have tried two different endpoint configurations for the connector actions:
- The web service server IP address (exactly like the connector)
- The web service server IP address + /WEBSERVICENAME
When we perform a test we get a connection time out error. We have checked and there are no restrictions from the bridge server to the web service server. We have the ability to ping it and receive a successful ping.
We just receive a generic Internal Server Error 500, the connection timed out.
Please help.
Richard.Schott | 2017-03-10 16:30:42 UTC | #2
I would suggest that this get taken up with PureCloud Support. Prior to contacting them, it might make sense to try your API calls to your web service endpoints from a tool like POSTMan to confirm that your service is operational.
juliocezargomes | 2017-03-10 16:32:31 UTC | #3
Richard: tim.smith says:
If you configure the bridge action in an Architect flow or a Script, you can place a call into your system and test it by executing the actions; there isn't currently an isolated test function.
Can we use postman or not? We are using and getting timeout
tim.smith | 2017-03-10 16:34:13 UTC | #4
Sorry, we can't help you troubleshoot your network's configuration on the forum. That's outside the scope of this site. You can open a ticket with PureCloud Support and they can investigate from the PureCloud side or Genesys Professional Services can be hired to help you with your local configuration.
ScottBub | 2017-03-10 16:39:35 UTC | #5
Where can we get logs from the tests that we performed? Is there somewhere in PureCloud that we can get the logs from our tests?
tim.smith | 2017-03-10 16:40:45 UTC | #6
PureCloud Support can help investigate from the PureCloud side. Our server logs are not accessible to the public.
system | 2017-08-28 19:32:53 UTC | #7
This post was migrated from the old Developer Forum.
ref: 1031