Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
OCS Setup RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,
    We have setup office communications server 2007 in our site. Our Active Directory is named as eg: xyz in our DNS(Local) server , but our OCS users login to OCS server as username@xyz.com. All the OCS users are configured the same way. I am in the process of enabling automatic logon for all users through TCP and how to go about creating DNS srv records for XYZ .

    Please guide me.

    Regards
    Sanj
    Sanju
    Wednesday, July 29, 2009 12:04 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    If you use Manual Configuration then the externally published FQDN can be in any DNS zone, it does not have to match the SIP domain name.  Full client functionality will be available using either method (Automatic or Manual).

    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    Monday, August 3, 2009 10:53 AM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Here are the directions for configuring internal DNS records to support Automatic Configuration on the OC client:
    http://technet.microsoft.com/en-us/library/dd425235(office.13).aspx
    http://technet.microsoft.com/en-us/library/dd441238(office.13).aspx

    Assuming you have a Standard Edition deployment, the SRV record will point to the existing, registered A record for the OCS server FQDN.  If you've setup an Enterprise Edition server than the SRV record points to the manually created A record for the OCS Pool FQDN.

    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    Wednesday, July 29, 2009 12:27 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Jeff,

    The above link which you specified doesn't have any information to set DNS records for automatic configuration.
    To continue with the same query, in office communicator 2007 client, we have in Tools -> Options -> External Server Name and IP address.

    We have some extra Public IP addresses , can we use this IP in Office Communicator client tool (Users working from home) to logon to our OCS server (Provided we create separate firewall rules to map this WAN IP to OCS IP) and participate in Audio/Video call? Also to have chat with other users.

    Please clarify.

    Thanks in advance,

    Rgds
    Sanj
    Sanju
    Thursday, July 30, 2009 4:17 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I fixed the link in my original reply.

    You'll need to deploy an Edge server to support external client login and A/V media communications.
    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    Thursday, July 30, 2009 4:57 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Jeff,
    With regards to External access to OCS server for Audio/Video communication, I experimented to login using an Public IP address provided at External servername or IP address in Tools -> option of Office Communicator 2007 Client . Prior to which, I had enabled in our Firewall using a FireWall rule to allow communcation from WAN to this Public IP address mapped to internal IP of OCS server. I could able to Login to our OCS server from home using the above configuration (Manual Configuration) without VPN. I didn't try Audio/Video and Conference Audio/Video call.

    We have some restriction creating a separate DNS zone in the same name as of our SIP Login xyz.com as this DNS is registered for some other application, but our users have their SIP Login in the format username@xyz.com.

    Suppose if we use External IP (Manual Configuration) with Edge Server deployment in our site using the existing sip login format, Will I be able to achieve the Audio/Video communication?

    Please assist me further .

    Thanks in advance.

    Rgds
    Sanj
    Sanju
    Monday, August 3, 2009 5:37 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    If you are using OCS 2007 R1 then you need Public IP on A/V edge interface for A/V to work. In case ocs 2007 R2 you dont need public IP.

    You have to create a Host A record for your Access Edge and AV edge Ip address. Then you can specify the Access Edge FQDN in your Communicator using Manuval Configuration.

    If you still have any confusion doing this i would suggest you to go through the Edge Server Deployment guide and open a case with Microsoft PSS for furthur assistence.

    Jithendranath Reddy
    Monday, August 3, 2009 9:06 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    If you use Manual Configuration then the externally published FQDN can be in any DNS zone, it does not have to match the SIP domain name.  Full client functionality will be available using either method (Automatic or Manual).

    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    Monday, August 3, 2009 10:53 AM
    Moderator