SFB 項(xiàng)目經(jīng)驗(yàn)-30-SFB與SFB聯(lián)盟-IM-正常-狀態(tài)-不正常

現(xiàn)狀:

A環(huán)境:

Skype for Business Server 2015，前端服務(wù)器、持久聊天服務(wù)器、邊緣服務(wù)器。

與MSN、Skype、O365聯(lián)盟，IM、音頻和視頻正常。

A與B聯(lián)盟，A能看B的狀態(tài)，能發(fā)消息給B，B能有回消息，看不到A的 狀態(tài)。

B環(huán)境:

Skype for Business Server 2015，前端服務(wù)器、持久聊天服務(wù)器、邊緣服務(wù)器。

與MSN、Skype、O365聯(lián)盟，IM、音頻和視頻不正常。

A與B聯(lián)盟，A能看B的狀態(tài)，能發(fā)消息給B，B能有回消息，看不到A的 狀態(tài)。

問(wèn)題：

Skype for Business Server 2015，前端服務(wù)器、持久聊天服務(wù)器、邊緣服務(wù)器。

與MSN、Skype、O365聯(lián)盟，IM、音頻和視頻不正常。

A與B聯(lián)盟，A能看B的狀態(tài)，能發(fā)消息給B，B能有回消息，看不到A的 狀態(tài)。

解決方案：

1. 增加C環(huán)境

2. 測(cè)試C環(huán)境與A、B

3. 發(fā)現(xiàn)A與C正常

4. 發(fā)現(xiàn)A與B不正常

5. 發(fā)現(xiàn)C與B不正常

6. 發(fā)現(xiàn)A與B，C與B，問(wèn)題一樣

A與B聯(lián)盟，A能看B的狀態(tài)，能發(fā)消息給B，B能有回消息，看不到A的 狀態(tài)。

C與B聯(lián)盟，C能看B的狀態(tài)，能發(fā)消息給B，B能有回消息，看不到C的 狀態(tài)。

問(wèn)題出在B上， 檢查B上設(shè)置。同。

TL_INFO(TF_PROTOCOL) [Pool\SkypeSrv15-IP06]0C4C.BDDC::01/21/2017-05:12:54.578.0002B968 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(261)) [2166602313] Trace-Correlation-Id: 2166602313
Instance-Id: 5D2
Direction: outgoing
Peer: 192.168.1.6:51425
Message-Type: response
Start-Line: SIP/2.0 504 Server time-out
From: "............03-(...............)-OA"<sip:sales03@contoso.com>;tag=c5a4c97016;epid=2c401f2a22
To: <sip:sfbdemo01@i-x-cloud.com>;tag=345733AABF1549BBA3E4E1E2A5406FD1
Call-ID: 7e9210ed5ff044438925c226a4f2f7ea
CSeq: 1 SUBSCRIBE
Via: SIP/2.0/TLS 192.168.1.6:51425;ms-received-port=51425;ms-received-cid=100
Content-Length: 0
ms-diagnostics: 1008;reason="Unable to resolve DNS SRV record";domain="contoso.com";dns-srv-result="NegativeResult";dns-source="InternalCache";source="sip.contoso.com"
Authentication-Info: TLS-DSK qop="auth", opaque="4556B265", srand="B338FE87", snum="81", rspauth="383e05e98238d9c67c9e3829b0cd41a94a62632e", targetname="SkypeSrv15-IP06.contoso.local", realm="SIP Communications Service", version=4
Server: RTC/6.0

$$end_record

TL_INFO(TF_PROTOCOL) [Pool\SkypeSrv15-IP06]0C4C.BDDC::01/21/2017-05:12:54.578.0002B960 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(261)) [2166602313]

Trace-Correlation-Id: 2166602313

Instance-Id: 5D2

Direction: incoming

Peer: EdgePool01.contoso.local:5061

Message-Type: response

Start-Line: SIP/2.0 504 Server time-out

From: "............03-(...............)-OA"<sip:sales03@contoso.com>;tag=c5a4c97016;epid=2c401f2a22

To: <sip:sfbdemo01@i-x-cloud.com>;tag=345733AABF1549BBA3E4E1E2A5406FD1

Call-ID: 7e9210ed5ff044438925c226a4f2f7ea

CSeq: 1 SUBSCRIBE

Via: SIP/2.0/TLS 192.168.1.6:52981;branch=z9hG4bKD2246EB8.5F7C6012EE61B306;branched=FALSE;ms-received-port=52981;ms-received-cid=4500

Via: SIP/2.0/TLS 192.168.1.6:51425;ms-received-port=51425;ms-received-cid=100

Content-Length: 0

ms-diagnostics: 1008;reason="Unable to resolve DNS SRV record";domain="contoso.com";dns-srv-result="NegativeResult";dns-source="InternalCache";source="sip.contoso.com"

ms-edge-proxy-message-trust: ms-source-type=EdgeProxyGenerated;ms-ep-fqdn=EdgePool01.contoso.local;ms-source-verified-user=verified

Server: RTC/6.0

$$end_record

從以上可以看出，DNS的SRV記錄有問(wèn)題，但：

內(nèi)部與外部域名一致的時(shí)候，與其它SFB聯(lián)盟，只需要公網(wǎng)上面新建SRV記錄才可以。

目前環(huán)境，SFB的內(nèi)部域名，外部域名不一致，這與其它公司的SFB聯(lián)盟就報(bào)上面的問(wèn)題。

通過(guò)查詢(xún)了好多文檔，結(jié)果終于找到一個(gè)可以參考的。

No Presence for Fedrated partners – Event ID 11

https://ucsorted.com/2016/06/08/no-presence-for-fedrated-partners/

內(nèi)部SRV:

在內(nèi)部要為公網(wǎng)的聯(lián)盟新建SRV記錄，才可以!

內(nèi)外域名不同的SFB環(huán)境與其它企業(yè)的SFB環(huán)境聯(lián)盟:

內(nèi)外域名不同的SFB環(huán)境與其它企業(yè)的o365聯(lián)盟:

完成!!!

No Presence for Fedrated partners – Event ID 11

Posted on 08/06/2016 by Paul B

i

1 Vote

Problem

Came across a deployment with the following 2 issues:-

1. federated partners were showing up as presence unknown

2. unable to call voicemail (hosted in O365)

When trying to send messages to these “unknown” federated partners I got “This message wasn’t sent due to company policy”.

So why did I try to message a contact with a presence status of “unknown? Simply because the federated contact could see my users presence and send me IM’s, I was even able to respond to these IM’s although the presence was still “unknown”.

Troubleshooting

A quick look at the client side logs revealed an error in the presence Subscribe message

CSeq: 1 SUBSCRIBE
Via: SIP/2.0/TLS 172.11.12.13:24164;ms-received-port=24164;ms-received-cid=FC9300
ms-diagnostics: 1008;reason=”Unable to resolve DNS SRV record“;domain=”ucsorted.com”;dns-srv-result=”NegativeResult”;dns-source=”InternalCache”;source=”access.ucsorted.com”
Server: RTC/6.0
Content-Length: 0

Taking a look at the users (client side) local event log I found the same error.

Event ID 11
A SIP request made by Lync failed in an unexpected manner (status code 80ef01f8).

Response Data
504  Server time-out
ms-diagnostics:  1008;reason=”Unable to resolve DNS SRV record“;domain=”ucsorted.com”;dns-srv-result=”NegativeResult”;dns-source=”InternalCache”;source=”access.ucsorted.com”;OriginalPresenceState=”0″;CurrentPresenceState=”0″;MeInsideUser=”No”;ConversationInitiatedBy=”6″;SourceNetwork=”5″;RemotePartyCanDoIM=”Yes”

Clearly there is some issue with either the federation SRV record or resolving the federation SRV record.

Checking the SRV record from the Edge server I can see that this record is not found. Checking the DNS for the Edge server I noticed that the interfaces are pointing to the internal DNS servers.

Solution

We have 2 options here:-

1. Configure the Edge Server to point to a public (external) DNS server where the SRV record for _sipfederationtls._tcp.domain.com is valid (frowned upon by some security folks)

2. Add the SRV record for _sipfederationtls._tcp.domain.com to the internal DNS, making sure that the target FQDN is the Public Access FQDN of the Edge Server.

NOTE

Here is a little reason why you may want to avoid using the common sip.domain.com DNS name for your Edge Servers Access FQDN (only..). Internally the sip.domain.com record was generally configured to resolve to the front end pools, if we now need an internal SRV record for _sipfederationtls._tcp.domain.com then targeting this to sip.domain.com will simply get to the Front End Pool and not to the Federation point at the Access Edge FQDN.

********************************************

廣告：

********************************************

×××以下IT服務(wù)：

A. 項(xiàng)目

Lync Server 2013項(xiàng)目規(guī)劃、部署、運(yùn)維、排錯(cuò)。

Skype for Business Server 2015項(xiàng)目規(guī)劃、部署、運(yùn)維、排錯(cuò)。

大企業(yè)云桌面部署規(guī)劃、部署、運(yùn)維、排錯(cuò)。

小微型企業(yè)的Cisco UC項(xiàng)目規(guī)劃、部署、運(yùn)維、排錯(cuò)。

小微型企業(yè)的IT規(guī)劃、部署、運(yùn)維、排錯(cuò)。

B. 培訓(xùn)

/《Skype for Business 2015 項(xiàng)目實(shí)戰(zhàn)》

/ 《跟菜鳥(niǎo)學(xué)Cisco UC部署實(shí)戰(zhàn)》

/ 《大企業(yè)云桌面部署實(shí)戰(zhàn)》

《跟菜鳥(niǎo)學(xué)Cisco UC部署實(shí)戰(zhàn)》-上線了（線下培訓(xùn)班開(kāi)班，見(jiàn)百度云）

http://dynamic.blog.51cto.com/711418/1834588

C. 費(fèi)用

歡迎溝通，咨詢(xún)。

D. 聯(lián)系方式

咨詢(xún)QQ: 3313395633