Det går inte att Test-CsFederatedPartner Lync Server PowerShell-Test-CsFederatedPartner

Symptom

  • En Office Communications 2007 R2 Edge Server-pool fungerar med Lync Server Front End-serverdistributionen

  • För Test-CsFederatedPartner PowerShell-cmdleten visas inte följande fel i konsolen Lync Server Management Shell:

    Test-CsFederatedPartner : A 504 (Server time-out) response was received from the network and the operation failed. See the exception details for more information. At line:1 char:24 + Test-CsFederatedPartner <<<< -TargetFqdn ocsedge.contoso.com -Domain fabrikam.com -ProxyFqdn accessedge.fabrikam.com + CategoryInfo : OperationStopped: (:) [Test-CsFederatedPartner],FailureResponseException + FullyQualifiedErrorId : WorkflowNotCompleted,Microsoft.Rtc.Management.SyntheticTransactions.TestFederatedPartnerCmdlt
    

Orsak

Exemplet nedan tvingar tillägget av SIP-tillägget ms-edge-route att läggas till i Lync Server SIP OPTIONS Request:

Test-CsFederatedPartner -TargetFqdn ocsedge.contoso.com -Domain fabrikam.com -ProxyFQDN accessedge.fabrikam.com

Office Communications Server 2007 R2 Edge Server är inte utformad för att identifiera tillägget ms-edge-route SIP i rubriken ROUTE i Lync Server SIP OPTIONS Request

Lösning

Använd Lync Server PowerShell-cmdleten Test-CsFederatedPartner utan att lägga till parametern -ProxyFqdn. Se exemplet nedan:

Test-CsFederatedPartner -TargetFqdn ocsedge.contoso.com -Domain fabrikam.com

Mer information

Mer information om Test-CsFederatedPartner Lync Server PowerShell-cmdleten:

Test-CsFederatedPartner

Om du använder Test-CsFederatedPartner Lync Server PowerShell-cmdleten med parametern -ProxyFQDN enligt beskrivningen i avsnittet Orsak i den här artikeln får du ett resultat som liknar informationen nedan i Office Communications Server 2007 R2 Edge Server SipStack-loggning:

TL_INFO(TF_PROTOCOL) [0]06E4.0EB4::01/18/2012-05:00:43.101.00005386 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(125))$$begin_record
Trace-Correlation-Id: 2003888399
Instance-Id: 0000C23F
Direction: incoming;source="internal edge";destination="external edge"
Peer: lyncservr.contoso.com:61182
Message-Type: request
Start-Line: OPTIONS sip:Options_User@fabrikam.com SIP/2.0
To: <sip:Options_User@fabrikam.com>
CSeq: 1 OPTIONS
Call-ID: 017b06f397b14886bba5edf97ea206bd
MAX-FORWARDS: 70
VIA: SIP/2.0/TLS 10.10.10.10:61182;branch=z9hG4bK6de49c9a
ROUTE: <sip:accessedge.fabrikam.com;transport=tls;lr>;ms-edge-route
CONTACT: <sip:lyncserver.contoso.com;transport=Tls>
CONTENT-LENGTH: 0
USER-AGENT: RTCC/4.0.0.0
Message-Body: -
$$end_record

SIP-ALTERNATIV-begäran ovan som innehåller SIP-tillägget Lync Server ms-edge-route i rubriken ROUTE ger felinformation som liknar den som visas nedan i Office Communications Server 2007 R2 Edge Server SipStack-loggning:

TL_ERROR(TF_COMPONENT) [0]0860.0CDC::01/18/2012-05:07:42.622.000d0b31 (SIPStack,CSIPRequest::GetNextHopByRouteHeader:SIPRequest.cpp(2440))( 00000000028FDD70 ) Exit - route headers from untrusted source. Result 0xC3E93C5E(SIPPROXY_E_ROUTING)
LogType: diagnostic
Severity: warning
Text: Cannot process Route headers from a non-trusted source, or with first Route field in the set not matching the connection on which the request arrived
Result-Code: 0xc3e93c5e SIPPROXY_E_ROUTING
SIP-Start-Line: OPTIONS sip:Options_User@fabrikam.com SIP/2.0
SIP-Call-ID: c00bc6180f284b948be61febf274d05e
SIP-CSeq: 1 OPTIONS
$$end_record

Behöver du fortfarande hjälp? Gå till Microsoft Community.