Shulou(Shulou.com)06/03 Report--

Status quo:

An environment:

Skype for Business Server 2015, front-end server, persistent chat server, edge server.

Allied with MSN, Skype, O365, IM, audio and video are normal.

In the alliance between An and B, A can see the status of B, can send messages to B, B can reply messages, but can not see the status of A.

B environment:

Skype for Business Server 2015, front-end server, persistent chat server, edge server.

In alliance with MSN, Skype, O365, IM, audio and video are not normal.

In the alliance between An and B, A can see the status of B, can send messages to B, B can reply messages, but can not see the status of A.

Question:

Skype for Business Server 2015, front-end server, persistent chat server, edge server.

In alliance with MSN, Skype, O365, IM, audio and video are not normal.

In the alliance between An and B, A can see the status of B, can send messages to B, B can reply messages, but can not see the status of A.

Solution:

1. Add C environment

two。 Test C environment and A, B

3. Found that An and C are normal.

4. Found that An and B are not normal.

5. It is found that C and B are abnormal.

6. Found that An and B, C and B, the problem is the same.

In the alliance between An and B, A can see the status of B, can send messages to B, B can reply messages, but can not see the status of A.

C and B are allied, C can see the status of B, can send messages to B, B can reply messages, but can't see the status of C.

The problem is on B. check the settings on B. Same as.

TL_INFO (TF_PROTOCOL) [Pool\ SkypeSrv15-IP06] 0C4C.BDDC::01/21/2017-05:12:54.578.0002B968 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp) [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"; tag=c5a4c97016;epid=2c401f2a22

To:; tag=345733AABF1549BBA3E4E1E2A5406FD1

Call-ID: 7e9210ed5ff044438925c226a4f2f7ea

CSeq: 1 SUBSCRIBE

Via: SIP/2.0/TLS 192.168.1.6 Flux 51425 *

Content-Length: 0

Ms-diagnostics: 1008 position 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"; tag=c5a4c97016;epid=2c401f2a22

To:; tag=345733AABF1549BBA3E4E1E2A5406FD1

Call-ID: 7e9210ed5ff044438925c226a4f2f7ea

CSeq: 1 SUBSCRIBE

Via: SIP/2.0/TLS 192.168.1.6 Pluto 52981 inception z9hG4bKD2246EB8.5F7C6012EE61B306branchedFLSETIVITY

Via: SIP/2.0/TLS 192.168.1.6 Flux 51425 *

Content-Length: 0

Ms-diagnostics: 1008 position 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

As can be seen from the above, there is a problem with DNS's SRV record, but:

When the internal domain name is the same as the external domain name, with other SFB alliances, you only need to create a new SRV record on the public network.

In the current environment, the internal domain name of SFB is inconsistent with the external domain name, which is reported by the SFB alliance of other companies.

After querying a lot of documents, I finally found one for reference.

No Presence for Fedrated partners-Event ID 11

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

Internal SRV:

It is necessary to create a new SRV record for the public network alliance internally.

SFB environments with different internal and external domain names are allied with SFB environments of other enterprises:

SFB environments with different internal and external domain names and o365 alliances of other enterprises:

Done!

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-diagnostics: 1008 position 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 position reasoned = "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.

*

Advertising:

*

The following IT services:

a. Project

Lync Server 2013 project planning, deployment, operation and maintenance, troubleshooting.

Skype for Business Server 2015 project planning, deployment, operation and maintenance, troubleshooting.

Large enterprise cloud desktop deployment planning, deployment, operation and maintenance, troubleshooting.

Cisco UC project planning, deployment, operation and maintenance, troubleshooting for small and micro enterprises.

IT planning, deployment, operation and maintenance of small and micro enterprises.

b. Training

/ "Skype for Business 2015 Project practice"

/ "learn Cisco UC deployment from Cainiao"

/ "practice of large Enterprise Cloud Desktop deployment"

"learn the actual combat of Cisco UC deployment from Cainiao"-online (offline training course, see Baidu Cloud)

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

c. Expenses

Welcome to communicate and consult.

d. Contact information

Consult QQ: 3313395633

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.