locked
remote outbound application 401 error RRS feed

  • Question

  •  

    I have an inbound and outbound SALT application working fine when they are installed locally on an OCS.  However, if I move the applications to a remote web server, the inbound application still works fine, but the outbound application does not.  The OCS gets a 401 error when trying to load the start page for the remote outbound application.  I've got anonymous access enabled within IIS for both applications so I can't understand why the inbound app loads while the outbound app fails to load.  Is there an additional step that I need to do to enable the OCS to run a remote outbound application?
    Friday, October 26, 2007 8:51 PM

Answers

  • Anthony,

     

    I was able to solve the problem by modifying settings in the Web.config file of my outbound application.

     

    Thanks,

     

    Randy

     

    Thursday, November 1, 2007 4:19 PM

All replies

  • There should be no difference between inbound and outbound for the download itself, so this is most likely a configuration issue, either of your application on Speech Server, or IIS for the web server. 

     

    How are initiating the outbound call - MSMQ or http request?  Have you specified the URL correctly?  For outbound applications, Speech Server doesn't use the configured startpage URL, it uses the URL provided in the MSMQ message or http request.  Make sure this is the correct URL.

     

    Try to identify whether the problem is with Speech Server's configuration or on your web server.  E.g. on Speech Server, try switching the start page URLs between inbound & outbound such that the inbound application tries to load the outbound startpage.  This will clearly fail when the outbound app tries to initiate an outbound call, but that doesn't matter.  If it successfully downloads the startpage, then your problem is on the speech server side whereas if it fails to download the startpage, your problem is on the web server. 

     

     

    Monday, October 29, 2007 1:46 PM
  • Anthony,

     

    My outbound application's start page does an HTTP request that loads a URL into MSMQ.  The URL points to the application page with the MakeCall Control.  I am confident that the URL is correct because the MakeCall page loads fine when the application is deployed locally on the Speech Server.

     

    As suggested, I have tried switching the start page URL's for my inbound & outbound applications within the Speech Server configuration.  I got the same 401 error when placing a call.  This confirms that I've got a web server configuration issue.  I'll continue investigating my IIS configuration settings.

     

    Thanks,

     

    Randy

     

     

    Monday, October 29, 2007 9:24 PM
  • The discrepancy I was thinking was that you'd perhaps forgotten to update the hostname portion of the outbound Salt apps URL.

     

    I don't understand your comment "My outbound application's start page does an HTTP request that loads a URL into MSMQ".  Could you elaborate further on your configuration?  What applications are registered with Speech Server?  What are their startpage URLs?  Which application have an associated MSMQ?  What initiates this http request to put a URL into MSMQ?  What URL is being put into MSMQ?

     

     

    A typical deployment would be to have 2 applications registered with Speech Server:

    1. Name: "inbound", type "Salt", start page http://<someremoteserver>/inbound.aspx
    2. Name: "outbound", type "Salt", start page http://<someremoteserver>/outbound.aspx, message queue "<someQueue>"

    Then, for outbound calls, some external trigger (e.g. from a database) puts a message http://<someremoteserver/outbound.aspx into "<someQueue>".  Speech Server picks this message up and loads outbound.aspx which places the outbound call.

     

     

    However from your description it sounds like you may have the following setup:

    1. Name: "inbound", type "Salt", start page http://<someremoteserver>/inbound.aspx
    2. Name: "outbound", type "Salt", start page http://<someremoteserver>/redirect.aspx, message queue "<someQueue>"

    Then, an incoming call to the outbound app is the external trigger.  redirect.aspx puts a message "http://<someremoteserver>/outbound.aspx" into "<someQueue>".  Speech Server picks this up and loads outbound.aspx which places the outbound call.

     

     

    Are either of these correct?

    Tuesday, October 30, 2007 10:35 AM
  • Anthony,

     

    I was able to solve the problem by modifying settings in the Web.config file of my outbound application.

     

    Thanks,

     

    Randy

     

    Thursday, November 1, 2007 4:19 PM