OCS 2007 R2 Remote Access - Puzzling??
-
12. listopadu 2009 23:07Hey
The OCS 2007 R2 remote access implementation is puzzling to me. From what I understand, one would need an independent Public IP and associated A records for each of the three (3) OCS Edge roles and HTTP proxy. However, the Office Communicator (OC) settings only has a single field to enter an external server name. How do all these Public names for each role fit in the OC client configuration.
Regards
JK
jk
Všechny reakce
-
12. listopadu 2009 23:08
The OCS 2007 R2 remote access implementation is puzzling to me. From what I understand, one would need an independent Public IP and associated A records for each of the three (3) OCS Edge roles and HTTP proxy. However, the Office Communicator (OC) settings only has a single field to enter an external server name. How do all these Public names for each role fit in the OC client configuration?
Regards
JK
jk- Sloučený Jeff SchertzMVP, Moderator 24. listopadu 2009 17:09 Duplicate Post
-
13. listopadu 2009 0:03Moderátor
Communicator, and Live Meeting (as applicable), receive the FQDNs of the necessary services through in-band provisioning, which basically means that the server passes the necessary information to the client so it can make the connections to the other services.
Mike Stacy | Evangelyze Communications | http://www.evangelyze.net/cs/blogs/mike- Navržen jako odpověď Gavin-ZhangModerator 18. listopadu 2009 10:28
- Označen jako odpověď Gavin-ZhangModerator 20. listopadu 2009 10:05
-
13. listopadu 2009 0:03ModerátorDuplicate - see other post.
Mike Stacy | Evangelyze Communications | http://www.evangelyze.net/cs/blogs/mike -
13. listopadu 2009 0:31So...which of the public names goes in the OC settings?
jk -
13. listopadu 2009 0:38Moderátor
Ideally none by using autoconfiguration, which involves an SRV record of _sip._tls.<domain.com> that points to the access edge FQDN. However, if you are planning to manually configure your clients then you would enter the access edge FQDN. If you are using the recommended port 443 then the configuration would reflect that (edge.domain.com:443).
Mike Stacy | Evangelyze Communications | http://www.evangelyze.net/cs/blogs/mike- Navržen jako odpověď Gavin-ZhangModerator 18. listopadu 2009 10:28
- Označen jako odpověď Gavin-ZhangModerator 20. listopadu 2009 10:05