locked
OCS 2007 R2 Remote Access - Puzzling?? RRS feed

  • Question

  • Hey

    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
    Thursday, November 12, 2009 11:07 PM

Answers

  • 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
    Friday, November 13, 2009 12:03 AM
    Moderator
  • 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
    Friday, November 13, 2009 12:38 AM
    Moderator

All replies

  • 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
    Thursday, November 12, 2009 11:08 PM
  • 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
    Friday, November 13, 2009 12:03 AM
    Moderator
  • Duplicate - see other post.
    Mike Stacy | Evangelyze Communications | http://www.evangelyze.net/cs/blogs/mike
    Friday, November 13, 2009 12:03 AM
    Moderator
  • So...which of the public names goes in the OC settings?
    jk
    Friday, November 13, 2009 12:31 AM
  • 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
    Friday, November 13, 2009 12:38 AM
    Moderator