locked
Validation A/V Conferencing RRS feed

  • Question

  • Good afternoon colleagues. Help to solve one problem.

     

     

    Office Communications Server 2007 Deployment Log 

          Office Communications Server 2007 Deployment Log


                Time Logged:15 августа 2007 г. 16:07:23Expand All
                Collapse All


                ActionAction InformationExecution Result

                Execute Action   Failure
                [0xC3FC200D] One or more errors were detected

                Initialize Machine FQDN: server-ocs.company.local
                WMI Repository Path: \\.\root\cimv2
                Host Name: server-ocs.company.local
                Product Version: Microsoft Office Communications Server 2007
                3.0.6362.0
                Installed components:
                DATAMCUWEB
                ACPMCU
                GROUPEXPANSION
                IMMCU
                DATAMCU
                AUDIOVIDEOMCU
                ARCHIVINGSERVER
                ARCHIVINGAGENT
                ADMINTOOL
                EE

                Service Status:

                RTCDATAMCU: Running
                RTCLOG: Running
                RTCSRV: Running
                RTCACPMCU: Running
                RTCIMMCU: Running
                RTCAVMCU: Running

                Backend: server-ocs
                 Success


                Diagnose MCU Check Configuration: True
                Check Connectivity: True
                 Failure
                [0xC3FC200D] One or more errors were detected

                Check Configuration   Success


                WMI Class MSFT_SIPMCUSetting WMI Class Path:
                \\SERVER-OCS\root\cimv2:MSFT_SIPMCUSetting
                WMI Instance Path:
                \\SERVER-OCS\root\cimv2:MSFT_SIPMCUSetting.InstanceID="{20EC4043-AA14-4DA7-897E-D70CB4FEE004}"
                FQDN (String): server-ocs.company.local
                InstanceID (String): {20EC4043-AA14-4DA7-897E-D70CB4FEE004}
                MajorVersion (UInt32): 3
                MCUDN (String): CN=LS AV
                MCU,CN=Microsoft,CN=SERVER-OCS,CN=Computers,DC=company,DC=local
                MCUFactory (String):
                CN={AB800EB2-E860-4917-A09C-242F80F49CCC},CN=MCU Factories,CN=RTC
                Service,CN=Microsoft,CN=System,DC=company,DC=local
                MCUURL (String):
                https://server-ocs.company.local:444/LiveServer/AVMCU/
                MinorVersion (UInt32): 0
                 Success


                WMI Class MSFT_SIPMCUFactorySetting WMI Class Path:
                \\SERVER-OCS\root\cimv2:MSFT_SIPMCUFactorySetting
                WMI Instance Path:
                \\SERVER-OCS\root\cimv2:MSFT_SIPMCUFactorySetting.InstanceID="{6084F58C-B4BE-4132-A25C-7771E43B6ABF}"
                FactoryURL (String):
                https://pool.company.local:444/LiveServer/MCUFactory/
                InstanceID (String): {6084F58C-B4BE-4132-A25C-7771E43B6ABF}
                MajorVersion (UInt32): 3
                MCUFactoryDN (String):
                CN={AB800EB2-E860-4917-A09C-242F80F49CCC},CN=MCU Factories,CN=RTC
                Service,CN=Microsoft,CN=System,DC=company,DC=local
                MCUFactoryProviderID (String): [NULL]
                MCUList (String):
                CN=LS AV
                MCU,CN=Microsoft,CN=SERVER-OCS,CN=Computers,DC=company,DC=local
                MinorVersion (UInt32): 0
                PoolList (String):
                CN=LC Services,CN=Microsoft,CN=pool,CN=Pools,CN=RTC
                Service,CN=Microsoft,CN=System,DC=company,DC=local
                Type (String): audio-video
                Vendor (String): Microsoft Corporation
                 Success


                WMI Class MSFT_SIPPoolSetting WMI Class Path:
                \\SERVER-OCS\root\cimv2:MSFT_SIPPoolSetting
                WMI Instance Path:
                \\SERVER-OCS\root\cimv2:MSFT_SIPPoolSetting.InstanceID="{D1A90802-CB09-4B38-8166-A0A150349F39}"
                BackEndDBPath (String): server-ocs
                DefaultLocationProfile (String):
                CN={9574CD47-EC1A-4E74-A745-167DD4C2B3A7},CN=Location
                Profiles,CN=RTC Service,CN=Microsoft,CN=System,DC=company,DC=local
                DomainFQDN (String): company.local
                InstanceID (String): {D1A90802-CB09-4B38-8166-A0A150349F39}
                MajorVersion (UInt32): 3
                MCUFactoryList (String):
                CN={AB800EB2-E860-4917-A09C-242F80F49CCC},CN=MCU Factories,CN=RTC
                Service,CN=Microsoft,CN=System,DC=company,DC=local
                CN={152507C0-A58D-4CB3-8C80-C982308E9A12},CN=MCU Factories,CN=RTC
                Service,CN=Microsoft,CN=System,DC=company,DC=local
                CN={98100171-76C1-4684-AFC4-23655BBF1B6A},CN=MCU Factories,CN=RTC
                Service,CN=Microsoft,CN=System,DC=company,DC=local
                CN={893837BC-EC07-49B0-B257-51BDE5D2FC31},CN=MCU Factories,CN=RTC
                Service,CN=Microsoft,CN=System,DC=company,DC=local
                MinorVersion (UInt32): 0
                PoolDisplayName (String): pool
                PoolDN (String): CN=LC Services,CN=Microsoft,CN=pool,CN=Pools,CN=RTC
                Service,CN=Microsoft,CN=System,DC=company,DC=local
                PoolFQDN (String): pool.company.local
                PoolMemberList (String):
                server-ocs.company.local
                PoolType (String): FEPool
                SupportIMPresence (Boolean): True
                SupportMeeting (Boolean): True
                TrustedMRASServer (String):
                CN={5EF03370-DA59-4D5C-9208-8A43ACCF9AAD},CN=Trusted Services,CN=RTC
                Service,CN=Microsoft,CN=System,DC=company,DC=local
                TrustedQoSServer (String): [NULL]
                WebComponentsServerList (String):
                CN=LS WebComponents
                Service,CN=Microsoft,CN=SERVER-OCS,CN=Computers,DC=company,DC=local
                 Success


                Check Pool Front End Server Setting   Success


                WMI Class MSFT_SIPESServerSetting WMI Class Path:
                \\SERVER-OCS\root\cimv2:MSFT_SIPESServerSetting
                WMI Instance Path:
                \\SERVER-OCS\root\cimv2:MSFT_SIPESServerSetting.InstanceID="{47BE5F59-942B-45A4-8E0D-4BAA6C1E928E}"
                ESInstalled (Boolean): True
                FQDN (String): server-ocs.company.local
                HomeServerDN (String): CN=RTC
                Services,CN=Microsoft,CN=SERVER-OCS,CN=Computers,DC=company,DC=local
                HomeUsers (Boolean): [NULL]
                InstanceID (String): {47BE5F59-942B-45A4-8E0D-4BAA6C1E928E}
                MajorVersion (UInt32): 3
                MinorVersion (UInt32): 0
                PoolDN (String): CN=LC Services,CN=Microsoft,CN=pool,CN=Pools,CN=RTC
                Service,CN=Microsoft,CN=System,DC=company,DC=local
                 Success


                WMI Class MSFT_SIPAvMcuSetting WMI Class Path:
                \\SERVER-OCS\root\cimv2:MSFT_SIPAVMCUSetting
                WMI Instance Path:
                \\SERVER-OCS\root\cimv2:MSFT_SIPAVMCUSetting.InstanceID="{598BA72F-2DAA-455D-8BC1-439E30E23170}"
                IgnoreIceFailure (Boolean): False
                InstanceID (String): {598BA72F-2DAA-455D-8BC1-439E30E23170}
                ListeningIPAddress (String): 10.0.0.6
                MediaListeningPortFrom (UInt32): 49152
                MediaListeningPortTo (UInt32): 65535
                SIPListeningPort (UInt32): 5063
                 Success


                WMI Class MSFT_SIPTrustedMRASServer WMI Class Path:
                \\SERVER-OCS\root\cimv2:MSFT_SIPTrustedMRASServer
                WMI Instance Path:
                \\SERVER-OCS\root\cimv2:MSFT_SIPTrustedMRASServer.InstanceID="{18C2CB2C-C1D4-4E82-987A-86B7121DCEEF}"
                FQDN (String): server-get.company.local
                InstanceID (String): {18C2CB2C-C1D4-4E82-987A-86B7121DCEEF}
                Port (UInt32): 5062
                Routable (Boolean): True
                ServerReference (String):
                CN=LS Mediation
                Service,CN=Microsoft,CN=SERVER-MED,CN=Computers,DC=company,DC=local
                CN=pool,CN=Pools,CN=RTC
                Service,CN=Microsoft,CN=System,DC=company,DC=local
                TrustedServiceDN (String):
                CN={5EF03370-DA59-4D5C-9208-8A43ACCF9AAD},CN=Trusted Services,CN=RTC
                Service,CN=Microsoft,CN=System,DC=company,DC=local
                Type (String): MRAS
                 Success


                Check Connectivity   Failure
                [0xC3FC200D] One or more errors were detected

                Check MCU Connectivity URL:
                https://server-ocs.company.local:444/LiveServer/AVMCU/
                Received a successful HTTP response: HTTP Response: 200 OK
                Content-Length:0
                Date:Wed, 15 Aug 2007 12:07:33 GMT
                Server:Microsoft-HTTPAPI/1.0

                Received a successful HTTP response: OK
                 Success


                Check MCU Factory Connectivity MCU Type: audio-video
                URL: https://pool.company.local:444/LiveServer/MCUFactory/
                Received a successful HTTP response: HTTP Response: 200 OK
                Content-Length:0
                Date:Wed, 15 Aug 2007 12:07:33 GMT
                Server:Microsoft-HTTPAPI/1.0

                Received a successful HTTP response: OK
                 Success


                Attempting to send a CCCP HTTP request
                https://pool.company.local:444/LiveServer/Focus Received a
                successful HTTP response: HTTP Response: 200
                Content-Length:0
                Date:Wed, 15 Aug 2007 12:07:33 GMT
                Server:Microsoft-HTTPAPI/1.0

                Received a successful HTTP response: OK
                 Success


                Audio/Video Conferencing Server server-ocs.company.local DNS
                Resolution succeeded: 192.168.5.95 10.0.0.6
                TCP connect failed: 192.168.5.95:5063 Error Code: 0x274d No
                connection could be made because the target machine actively refused
                it
                Suggested Resolution: Make sure that the server is listening on the
                specified IP address/Port/Transport. If you have a firewall make
                sure that this port is open. Make sure that the server is running.
                If this is an Edge Server, ensure that remote user access has been
                enabled. This can be ignored if you have not enabled the transport
                on the target server.
                Suggested Resolution: Ensure that the DNS records have been setup
                correctly. If this server is an Access Edge Server, make sure
                outside user access is enabled.
                TCP connect succeeded: 10.0.0.6:5063
                 Warning
                [0x43FC200C] Not all checks were successful

                Diagnosing Edge Authentication Server and Edge Server WMI Repository
                Path: \\server-ocs.company.local\root\cimv2
                 Failure
                [0xC3FC200D] One or more errors were detected

                A/V Authentication Edge Server server-get.company.local DNS
                Resolution succeeded: 10.0.0.9
                TCP connect succeeded: 10.0.0.9:5062
                 Success


                WMI Class MSFT_SIPTrustedServiceSetting WMI Class Path:
                \\SERVER-OCS\root\cimv2:MSFT_SIPTrustedServiceSetting
                WMI Instance Path:
                \\SERVER-OCS\root\cimv2:MSFT_SIPTrustedServiceSetting.InstanceID="{18C2CB2C-C1D4-4E82-987A-86B7121DCEEF}"
                FQDN (String): server-get.company.local
                GRUU (String):
                sipTongue Tiederver-get.company.local@company.local;gruu;opaque=srvr:MRAS:LMvCGNTBgk6Yeoa3Eh3O7wAA
                GruuID (String): [NULL]
                InstanceID (String): {18C2CB2C-C1D4-4E82-987A-86B7121DCEEF}
                Port (UInt32): 5062
                Routable (Boolean): True
                ServerReference (String):
                CN=LS Mediation
                Service,CN=Microsoft,CN=SERVER-MED,CN=Computers,DC=company,DC=local
                CN=pool,CN=Pools,CN=RTC
                Service,CN=Microsoft,CN=System,DC=company,DC=local
                TrustedServiceDN (String):
                CN={5EF03370-DA59-4D5C-9208-8A43ACCF9AAD},CN=Trusted Services,CN=RTC
                Service,CN=Microsoft,CN=System,DC=company,DC=local
                Type (String): MRAS
                Version (UInt32): [NULL]
                 Success


                WMI Class MSFT_SIPRoutingSetting WMI Class Path:
                \\SERVER-OCS\root\cimv2:MSFT_SIPRoutingSetting
                WMI Instance Path:
                \\SERVER-OCS\root\cimv2:MSFT_SIPRoutingSetting.InstanceID="{2390CE8B-5794-4789-9D11-D891502BA6EB}"
                DefaultPort (UInt32): 5061
                InstanceID (String): {2390CE8B-5794-4789-9D11-D891502BA6EB}
                TLSCertIssuer (UInt8): 48 77 49 21 48 19 06 10 09 146 38 137 147 242
                44 100 01 25 22 05 108 111 99 97 108 49 23 48 21 06 10 09 146 38 137
                147 242 44 100 01 25 22 07 99 111 109 112 97 110 121 49 27 48 25 06
                03 85 04 03 19 18 112 111 111 108 46 99 111 109 112 97 110 121 46
                108 111 99 97 108
                TLSCertSN (UInt8): 02 00 00 00 00 00 70 43 115 97
                 Success


                WMI Class MSFT_SIPListeningAddressData WMI Class Path:
                \\SERVER-OCS\root\cimv2:MSFT_SIPListeningAddressData
                WMI Instance Path:
                \\SERVER-OCS\root\cimv2:MSFT_SIPListeningAddressData.InstanceID="{0E185A69-870F-45F9-AE78-7DD2E3D70074}"
                Enabled (Boolean): True
                InstanceID (String): {0E185A69-870F-45F9-AE78-7DD2E3D70074}
                IPAddress (String): 10.0.0.6
                Port (UInt32): 5060
                TLSCertIssuer (UInt8): [NULL]
                TLSCertSN (UInt8): [NULL]
                TransportType (String): TCP
                 Success


                WMI Class MSFT_SIPListeningAddressData WMI Class Path:
                \\SERVER-OCS\root\cimv2:MSFT_SIPListeningAddressData
                WMI Instance Path:
                \\SERVER-OCS\root\cimv2:MSFT_SIPListeningAddressData.InstanceID="{CEC52D55-8A78-43CE-A152-98394412086E}"
                Enabled (Boolean): True
                InstanceID (String): {CEC52D55-8A78-43CE-A152-98394412086E}
                IPAddress (String): 192.168.5.95
                Port (UInt32): 5060
                TLSCertIssuer (UInt8): [NULL]
                TLSCertSN (UInt8): [NULL]
                TransportType (String): TCP
                 Success


                WMI Class MSFT_SIPListeningAddressData WMI Class Path:
                \\SERVER-OCS\root\cimv2:MSFT_SIPListeningAddressData
                WMI Instance Path:
                \\SERVER-OCS\root\cimv2:MSFT_SIPListeningAddressData.InstanceID="{1D3A517C-930C-43EE-9F30-C7304ED0922F}"
                Enabled (Boolean): True
                InstanceID (String): {1D3A517C-930C-43EE-9F30-C7304ED0922F}
                IPAddress (String): 10.0.0.6
                Port (UInt32): 5061
                TLSCertIssuer (UInt8): [NULL]
                TLSCertSN (UInt8): [NULL]
                TransportType (String): MTLS
                 Success


                Connecting to A/V Authentication Edge Server to get credentials  A/V
                Authentication Edge Server: Could not contact A/V Authentication
                Edge Server.
                To resolve this error, check for the following
                1. The outbound proxy is reachable.
                2. The outbound proxy and A/V Authentication Edge Server are in
                trusted server list of each other.
                3. The outbound proxy and A/V Authentication Edge Server have valid
                certificates.
                4. Conference Server certificate is valid.
                5. A/V Authentication Edge Server Gruu is correct.
                 Failure
                [0xC3FC200D] One or more errors were detected


    DIV1, DIV3, DIV4, DIV8, DIV12, DIV17

    Wednesday, August 15, 2007 12:59 PM

All replies

  • Iawash,

     

    I believe what we have here is a cut and paste from the A/V Edge Server Validation log. Unfortunately it's not very readable without the formatting around it!

     

    I do have the same problem as you and I think the important part of the log reads:

     

     

    Connecting to A/V Authentication Edge Server to get credentials  A/V Authentication Edge Server: Could not contact A/V Authentication
                Edge Server.
                To resolve this error, check for the following
                1. The outbound proxy is reachable.
                2. The outbound proxy and A/V Authentication Edge Server are in
                trusted server list of each other.
                3. The outbound proxy and A/V Authentication Edge Server have valid
                certificates.
                4. Conference Server certificate is valid.
                5. A/V Authentication Edge Server Gruu is correct.
                 Failure
                [0xC3FC200D] One or more errors were detected

     

     

    What I'd like to know is what is the outbound proxy?

    Where is the trusted server list that I'm supposed to check in step 2?

    Where do I find the A/V Authentication Edge Server GRUU?

     

    Thanks,

     

    Charlie222.

    Saturday, November 24, 2007 9:00 PM
  • The "trusted server list" is on the Internal tab of the Edge Server properties.

     

    Is the A/V Edge Server on a dedicated server or is this a consolidated deployment?  If the former, I'd look at name resolution to see why the server's aren't finding each other correctly.

    Sunday, November 25, 2007 3:47 AM
    Moderator
  • Where do I see the properties of the Edge Server? The OCS admin tool doesn't run on the edge server as it's not in AD, and the only reference to the edge server is on the properties of the OCS Pool when running the admin tool on my OCS server.

     

    The Edge server is deployed in the Colsolidated topology. I've opened all firewall ports between the edge and internal OCS standard edition server as a test. DNS resolution from both sides looks fine.

     

    Here's the Edge Server Settings file:

     

    Access Edge Server: Activated
    Web Conferencing Edge Server: Activated
    A/V Edge Server: Activated
    Internal interface IP address: 192.168.0.200
    Internal interface FQDN: ssdubedge1.blah.com
    Internal interface port for Access Edge Server: 5061
    Internal interface port for Web Conferencing Edge Server: 8057
    Internal interface port for A/V Conferencing Server: 443
    External interface IP address for Access Edge Server: 194.x.x.x
    External interface FQDN for Access Edge Server: accesses.blah.com
    External interface federation port for Access Edge Server: 5061
    External interface remote access port for Access Edge Server: 443
    External interface IP address for Web Conferencing Edge Server: 194.x.x.x
    External interface FQDN for Web Conferencing Edge Server: webconfes.blah.com
    External interface port for Web Conferencing Edge Server: 443
    External interface IP address for A/V Edge Server: 194.x.x.x
    External interface FQDN for A/V Edge Server: aves.blah.com
    External interface port for A/V Edge Server: 443
    Access Edge Server remote employee access: Enabled
    Access Edge Server allows anonymous users: True
    Access Edge Server allows remote users: False
    Access Edge Server federation: Enabled
    Access Edge Server automatic federation: Enabled
    Access Edge Server federation with public IM provider: Enabled
    Access Edge Server federation with MSN: Enabled
    Access Edge Server federation with Yahoo!: Enabled
    Access Edge Server federation with AOL: Enabled
    Access Edge Server internal next hop: ssdubocs1.blah.com
    Access Edge Server internal SIP domains:
            blah.com
    Internal Enterprise pools or Standard Edition Servers:
            ssdubocs1.blah.com

     

    Thursday, November 29, 2007 5:43 PM
  •  Charlie222 wrote:

    Where do I see the properties of the Edge Server? The OCS admin tool doesn't run on the edge server as it's not in AD, and the only reference to the edge server is on the properties of the OCS Pool when running the admin tool on my OCS server.

     

    Charlie,

     

    You need to open the Computer Management tool on the Edge Server as the OCS snap-in doens't work on a computer that is not a member of an AD domain.

     

    In short, right-click My Computer and select Manage.  Look under the Service and Applications section for the Microsoft Office Communications Server 2007 console.  It's hard to find the first time, but makes perfect sense once you realize where it's at Smile

    Thursday, November 29, 2007 7:48 PM
    Moderator
  •  Jeff Schertz wrote:

     

    In short, right-click My Computer and select Manage.  Look under the Service and Applications section for the Microsoft Office Communications Server 2007 console.  It's hard to find the first time, but makes perfect sense once you realize where it's at

     

     

    Thanks Jeff I never would have looked there!

     

    Validation on the edge server succeeds. However validation from the internal OCS server still fails with the error above. I still don't know what the message is referring to as the "outbound proxy". Is this my ISA server?

     

    Thanks,

     

    Charlie222.

    Friday, November 30, 2007 3:05 PM
  • Here's the definition of "outbound proxy" from RFC 3976 as it relates to SIP (no, it's not your ISA Server):

     


          -  Outbound proxy: A SIP proxy located near the originator of
             requests.  It receives all outgoing requests from a particular
             UAC, including those requests whose R-URIs identify a host
             other than the outbound proxy.  The outbound proxy sends these
             requests, after any local processing, to the address indicated
             in the R-URI.

    Saturday, December 1, 2007 5:41 AM
    Moderator
  • OK.

     

    One thing I noticed in the results of A/V validation is that the GruuID for the edge server is null.

     

    Under the WMI Class MSFT_SIPTrustedServiceSetting, the instance for the edge server shows:

     

    GRUU (String): sip: ssdubedge1.blah.com@blah.com;gruu;opaque=srvr:MRAS:Q8ptwU5yiE6rq3yv1O9AawAA
    GruuID (String): [NULL]


     

    Is this normal or should the GruuID have a value?

     

    Thanks again,

     

    Cathal.

    Monday, December 3, 2007 2:28 PM
  • I opened a case with Microsoft Tech Support on this and after a bit of analysis etc. the resolution was simple! The A/V edge server port setting on the front end server was set to the wrong port number. Once this was corrected everything worked perfectly.

     

    To check that this is correct:

     

    1. Open Computer Management on your edge server and navigate to the OCS icon in the tree.

    2. Under the Status tab, expand Internal Interface Settings and then Internal Edge Ports. A/V User Authentication port defaults to 5062.

    3. Log on to your OCS front end server and run the OCS management tool.

    4. Get the Global Properties of the forest and click on the edge servers tab. Make sure there's an entry under A/V edge servers for your edge server and that the port number matches the port found on the edge server in step 2. If not, click add and fill in your edge server FQDN and port number.

    5. Get the A/V Conferencing Properties of your front end server pool and make sure the selected A/V authentication server is using the correct port number. If you added a server in step 4 then select the newly added server here. Do this for each front end pool that uses the edge server from step 2.

    6. Get the properties of your Mediation Server and make sure the A/V Edge Server selected is the using the correct port number. Again if you added a new server in step 4 then select this server here.

    7. At this stage if there is an incorrect edge server entry in the forest Global Properties you should now be able to go back to the Global Properties dialog and delete this entry.

     

    Hope this makes sense! I'm using standard edition so my setup is fairly simple. I'd imagine the instructions above might not apply to an enterprise edition setup where there may be many edge servers and many mediation servers.

     

    Thanks,

     

    Charlie222.

     

     

    Thursday, January 3, 2008 9:53 AM
  •  

    Hello Charlie,

    thanks a lot!!!

    !!!

    !!!

    I had the same problem with our Enterprise edition, and it works!

    Thanks :-)

    Ravie.

    Thursday, February 28, 2008 7:35 AM
  •  

    Monday, March 10, 2008 12:25 PM
  • On my Edge server or Front-End server, if I got to computer managment, I do not have anything regarding OCS under Services and Applications, how can I get that added? 

    Monday, May 19, 2008 1:49 PM
  • You should only have that on your Edge server.  If you are running a 64 bit OS then you will only see it if you load Computer Management from a 32 bit MMC (mmc -32).

     

    Monday, May 19, 2008 1:54 PM
    Moderator