MiCC and MBG

[AlphaMann]

Can anyone maybe present me with a solution OTHER than creating a simple port forward on MBG:

Running:
MBG: V9.4.0.18
MiCC: 8.1.06276.1

Have integration done for MiCC, using the MiCC softphone

When trying to access the /ccmweb reports page I get the following login error:

The Authentication Service was unable to authorize the user. The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.

Thanks,

 

[tlpeter]

Was this an upgrade?
And if yes why this release?
I have had this issue after an upgrade and ssl was turned on during the upgrade while it should have been off.
Mitel logged in and ran some queries to solve this.

BAZINGA!

I'm not insane, my mother had me tested!

 

[Mitelpassion]

normally a cert issue.
Also have you enabled all the necessary options for MiCC in MBG?

remember MBG will only do https:if using reverse proxy

 

[Valamagules]

Hi AlphaMann

Were you able to find a fix for this?
I am having the same issue as you, care to share?

Cheers

 

[jpruder]

Assuming you are using the remote proxy blade, it might be possible to modify the template that creates the proxypass to add /micc. I know the webpage isn't supported in the current proxy blade. I think the template is in /etc/e-smith/templates/etc/httpd/conf/httpd.conf/82WebProxyVirtualHosts. The proper way would be to copy the full path to this template to the custom-template location, modify and expand.

I don't have anything in front of me and am doing this from memory. Once you create the structure in custom-templates to enable the command would be expand-template /etc/httpd/conf/httpd.conf. This will rebuild the httpd.conf and I would restart the httpd-e-smith service command would be service httpd-e-smith restart. If things go bad you can delete the custom stuff, issues the expand-template again and restart httpd-e-smith.

I have modified this template for some customers who wanted the default to go to the portal page instead of the proxy not found

 

[Billz66]

are you using ad authentication ?
if so check that all iis services and pfyre services are running undre the domain account not a local one

If I never did anything I'd never done before , I'd never do anything.....

 

[Valamagules]

@Billz66
Not AD integrated.

When using port 80 (Http) on the server, can access CCMWeb, can login.

Using 443 (HTTPS) on the server, can get to CCMWeb, but getting the error: The Authentication Service was unable to authorize the user. The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.

I think jtruder is on the right track, just need more specific infor on the fix.





Clever men learns what Wise men shares!

 

[jpruder]

I would try to reroute the default for the web proxy error to this server. I think it is line 89 in the 82web fragment. Then you could get the https working and add a portion that would take the fqdn/micc to where it needs to go using what is there as in this fragment as an example