Legacy Dev Forum Posts

 View Only

Sign Up

Web Services Error with Bridge Server

  • 1.  Web Services Error with Bridge Server

    Posted 06-05-2025 18:41

    lvasquez | 2019-07-23 21:00:14 UTC | #1

    Hi,

    I have a little issue using a Data Action with Bridge Server, this is my stage,

    I already have my bridge server configured, online, my action associate to the bridge server. Now, I'm testing a simple webservices that I created with asp web api, the webservices is really simple, request me a parameter and response a object, my url of the webservices http:// 192.168.92.214/Customer/api/Customer/

    Now, I have my webservices in the same pc where is the bridge server, so this should not be a problem

    and the action has a custom scheme with the follows request and response

    EndpointAddress: http:// 192.168.92.214 (this is the local ip where the webservice is stored and also where the bridge server is installed) EndPoint: /Customer/api/Customer/

    Request { "$schema": "http://json-schema.org/draft-04/schema#", "type": "object", "properties": { "dpi": { "type": "string" } }, "additionalProperties": true }

    Response { "$schema": "http://json-schema.org/draft-04/schema#", "type": "object", "properties": { "dpi": { "type": "string" }, "first_name": { "type": "string" } }, "additionalProperties": true }

    this is the log from the data-dip

    and this is the log from the iis and it seems that the webservices return ok 2019-07-23 20:20:38 192.168.92.214 POST /Customer/api/Customer/ - 80 - 192.168.92.214 generic-datadip - 200 0 0 2

    but in my workflow it seems that never return and I got a timeout so the call disconnect

    so, what I'm doing wrong, I appreciate any suggestion or comentary

    Thanks in advance


    Jason_Mathison | 2019-07-24 14:23:46 UTC | #2

    Hi lvasquez,

    As an FYI, I highly recommend that you switch from integrating with a Bridge Web Service Integration to creating a public webservice that you can get to from a Data Action. We have deprecated the bridge and will be disabling it at the beginning of 2020. https://help.mypurecloud.com/articles/deprecation-purecloud-bridge-integrations/

    In terms of troubleshooting this, the first thing I would suggest you do is test out the new endpoint that you created with a tool like postman to make sure it is behaving as expected.

    Any additional troubleshooting would probably require opening a case with customer care to dig into the logs and see what is going on.

    --Jason


    system | 2019-08-24 14:23:51 UTC | #3

    This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.


    This post was migrated from the old Developer Forum.

    ref: 5618