Author Topic: UCA 5.0 in Teleworker Mode Cert Fail  (Read 3454 times)

Offline mcoupe

  • New Member
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
UCA 5.0 in Teleworker Mode Cert Fail
« on: June 08, 2012, 12:07:36 PM »
Hi,

I'm trying to run UCA 5.0 in teleworker mode but am having issues retrieving a certificate from the mbg.  When I try, I'm getting "Failed to send certificate request" in the UCA Configuration Teleworker window after hitting the 'Retrieve Certificate' button. 

The client works fine internally and when I review the client logs I'm seeing (among other things...)

Mitel.Communicator.WebServices.WebServiceExceptio n: Unable to connect to the Web Service endpoint: There was no endpoint listening at http://127.0.0.1:36005/ucs/ws/service/ucs that could accept the message. This is often caused by an incorrect address or SOAP action.

I'm not sure why it's using 127.0.0.1 rather than the configured teleworker gateway IP address.  Earlier in the log I see the webservices hostame set to the correct IP address and then right after I see it set to 127.0.0.1.

thanks for any guidance,
Mark
mcoupe@edwardswildman<dot>com


Offline boycey9

  • Full Member
  • ***
  • Posts: 182
  • Karma: +4/-0
    • View Profile
Re: UCA 5.0 in Teleworker Mode Cert Fail
« Reply #1 on: June 11, 2012, 02:37:34 PM »
Sounds like you have port 80 closed on your MBG

Offline martyn

  • Hero Member
  • *****
  • Posts: 688
  • Country: au
  • Karma: +10/-0
    • View Profile
Re: UCA 5.0 in Teleworker Mode Cert Fail
« Reply #2 on: June 11, 2012, 10:01:04 PM »
If you run the TNA tool against the public IP address of your MBG server does it show as the ports being open?

Offline dozer

  • Contributer
  • *
  • Posts: 27
  • Karma: +2/-0
    • View Profile
Re: UCA 5.0 in Teleworker Mode Cert Fail
« Reply #3 on: June 14, 2012, 11:55:18 PM »
Verify your UCA is actually programmed via FQDN and NOT IP as well.  This can cause weird random issues.


 

Sitemap 1 2 3 4 5 6 7 8 9 10