Hi All

I am hoping someone can help.

We have deployed the Lync Hosting Pack deployment of Lync but are experiencing issues with the dialin URL. We use a standard lync.company.com base URL with the /Dialin at the end. We have publsihed the topology sucessfully without any issues however whenever we try to access the dial in conferencing web page externally we get the Meet URL is invalid. The other Simple URLs for meet work fine. When we test the simple URL publishing rule with TMG we get a 500 HTTP error back when it attempts to contact lync.company.com over port 4443, the rule tests out succesfully with a green tick for port 8080. Here is the error that we see on the TMG:

An unexpected response was received from the server. HTTP response: 500 Internal Server Error
Action: Verify that the intended server is published and that virtual directories exist. Ensure that you can browse the published site directly from an internal client computer.

If we go to the Director server itself and put the lync.company.com/dialin URL in the browser pointing to port 4443 we again get the same result - Meet URL is Invalid.

Now here is the strange thing if we add /conferenece.aspx to the end of the URL it works both externally and from the Director server itself. Also if we just use port 8080 when on the Director, it works as well and we see the conferencing page web site.

This sounds very much like an IIS issue but for the life of me we cannot work this out. Does anyone have any suggestions that we could try, getting pretty desperate now!

Many thanks

Adam

Just something else -  we can succesfully browse the dialin IIS virtual directory from within IIS, we get a certificate warning becuase it's using localhost but when we ignore this and proceed the dial in conferencing web site is displayed. It seems to have an issue with the lync.company.com URL and I dont have a clue why. Also if we use the director web services URL externally and append the /dialin that works as well.

Thanks

Adam

Ok so talking to myself again :)

It would appear that there are a lot of URL rewrites going on for that virtual directory. I can see lots of stuff that has been left over from the Lync Online version of Lync which I beleive the hosting pack has been based on. For example I see rewrite rules for meetbeta.online.lync.com! via IIS Manager and also in the web.config file. I'm assuming here that something to do with the redirection is not working correctly and this is causing our issues. I have checked this against an on-premise version of Lync and they are quite different. Does anyone have knowledge of what URL rewrtie rule should be defined for the dialin URL?

I dont understand these rewrite and redirect rules at all but I guess I will have to start to learn them!

Can anyone offer any pearls of wisdom?

TIA

Adam

So I found a way around this but would appreciate it if someone would sanity check it. Basically I found out which URL rewrite was firing and changed it to redirect to conference.aspx, it was previously set to \meet\default.aspx which failed. For some reason the rewrites on the dialin virtual directory don't look right to me. Now I have changed them everything appears to work as expected, however I still get the error when testing the rule on TMG.

I would appreciate is someone using the Lync Hosting Pack could let me know what their settings are.

TIA

Adam

This is normal.  Just going to https://meet.domain.com will give you Meeting URL is invalid.  This is because the Lync system is expecting to have data after meet.domain.com.  So for example, a valid meet  URL is https://meet.domain.com/eshudnow/13KLM400D.  So if you are just going to the URL https://meet.domain.com and getting that error, it's ok.

Also, it's expected to see the error in TMG when you test URL.  This is because again, TMG is sending data as https://meet.domain.com and you get the 500 Internal Server Error because there's no meeting information identified in the URL string as I explained above.

So this is all normal behavior.

Hello Elan

I think you mis-understood my post. I am talking about the Dialin URL. So ours is set at lync.company.co.uk/dialin. I beleive this is redirected at IIS and this redirection appears to of been incorrect. Like I said I updated the redirection and it works now. Previously we were getting invalid Meet URL coming up. This is the Lync Hosting Pack version of Lync and not the on-premise which are very different. there are all sorts of reference to lync online in the web.config file and it seems like this code needs cleaning up somewhat.

Your explantion in regard to the 500 internal server error makes sense so thanks for explaining that one,, should of realised that myself!

Thanks

Adam

Actually I'm not sure your explanation is correct as the rule passes when talking on 8080 its just 4443 that fails on TMG. That said its causing no issues we can see right now after we changed the redirection.

Thanks

Adam

My explanation is correct.

When you're using Meet and Dialin, it uses 4443, not 8080.  8080 is used for http based autodiscover when using mobility. In fact, 8080 really had no use until Autodiscover for mobility came into play. If putting lyncdiscover names on cert and using https for autodiscover, it won't use 8080 back to Pool and instead also use 4443.

With that said, you can rerun Step 2 in deploy.exe for the Setup/Install Proces and it will re-write the URL Rewrites fo

Im talking about the TMG rule that makes a connection back to the Director, so public name in the rule is lync.company.co.uk. When I hit test rule I see that 8080 passes for that URL and 4443 fails. Dialin is actually listening on 8080 as well as 4443 so I'm not sure I'm following what you are saying?

If I run deploy.exe I will be back to square one, and as I said I fixed it. That said I think I may just run it to see if it fails again.

Thanks

Adam

OK so running deploy.exe didn't do anything with the URLs. I'm not overly concerned about this anymore anyway since I have it working so dont wast your fingers on it.

Appreciate your response

Adam

I know this is old but did you get it working? I'm seeing a ton of errors in event logs about dialin meeting url is incorrect