Lync 2013 / CIMP(CUPS) 9.1.2 - RCC

Has anyone successfully gotten RCC working between Lync 2013 and UCM(IM&P) 9.1? I have followed the docs but cannot seem to log in. From the traces/captures I have collected it appears CIMP is returning a 401. I ran the RCC troubleshooter on CIMP server and everything comes back green.
I should point out we are using different domains.
example.com is the Lync domain
vc.example.com is the CUPS domain
example.local is our internal (AD) domain
Here is a brief snippet of the log from the CIMP side when Lync client logs on.
INVITE sip:[email protected] SIP/2.0
Record-Route: <sip:pdx-lync-pool-2.example.local;transport=tcp;ms-fe=pdx-lync-2.example.local;opaque=state:T;lr>;tag=C4140F78AB707EE55A3542C290EE3BDD
Via: SIP/2.0/TCP 192.168.1.7:50752;branch=z9hG4bKCEFA4AC7.35E3FA581770D77B;branched=FALSE
Max-Forwards: 69
ms-application-via: SIP;ms-urc-rs-from;ms-server=pdx-lync-2.example.local;ms-pool=pdx-lync-pool-2.example.local;ms-application=ad894dc3-55e0-44bf-a07e-3c073aaa4a57
From: "Doe, John"<sip:[email protected]>;tag=a9affac418;epid=c39ec15244
Via: SIP/2.0/TLS 192.168.6.152:57095;ms-received-port=57095;ms-received-cid=1BF000
To: <sip:[email protected]>
Call-ID: 7fb389cf26a740309ac9f34eb6f5806d
CSeq: 1 INVITE
Contact: <sip:[email protected];opaque=user:epid:9TcRoRhNhVqj1eWYVIl_awAA;gruu>
User-Agent: UCCAPI/15.0.4623.1000 OC/15.0.4623.1000 (Microsoft Lync)
Supported: ms-dialog-route-set-update
Content-Disposition: signal;handling=required
Supported: timer
Supported: histinfo
Supported: ms-safe-transfer
Supported: ms-sender
Supported: ms-early-media
ms-keep-alive: UAC;hop-hop=yes
Allow: INVITE, BYE, ACK, CANCEL, INFO, UPDATE, REFER, NOTIFY, BENOTIFY, OPTIONS
ms-subnet: 192.168.0.0
Content-Type: application/csta+xml
Content-Length: 329
ms-routing-phase: from-uri-routing-done
ms-user-data: ms-publiccloud=TRUE;ms-federation=TRUE
<?xml version="1.0"?>
<RequestSystemStatus xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"><extensions><privateData><private><lcs:line xmlns:lcs="http://schemas.microsoft.com/Lcs/2005/04/RCCExtension">tel:2373;phone-context=dialstring</lcs:line></private></privateData></extensions></RequestSystemStatus>
13:31:55.674 |Mon Jun 16 13:31:55 2014] PID(25341) mod_sip_numexpand.c(891) User john.doe is IP or contains non-E164 character, no number expansion applied.
13:31:55.674 |Mon Jun 16 13:31:55 2014] PID(25341) mod_sip_numexpand.c(891) User john.doe is IP or contains non-E164 character, no number expansion applied.
13:31:55.674 |Mon Jun 16 13:31:55 2014] PID(25341) mod_sip_numexpand.c(788) URL host example.com doesn't point at proxy, no number expansion on user john.doe
13:31:55.674 |Mon Jun 16 13:31:55 2014] PID(25341) mod_sip_numexpand.c(891) User john.doe is IP or contains non-E164 character, no number expansion applied.
13:31:55.674 |ID(25341) sip_sm.c(1197) Sent 406 bytes TCP packet to 192.168.1.7:50752
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 192.168.1.7:50752;received=192.168.1.7;branch=z9hG4bKCEFA4AC7.35E3FA581770D77B;branched=FALSE, SIP/2.0/TLS 192.168.6.152:57095;ms-received-port=57095;ms-received-cid=1BF000
Call-ID: 7fb389cf26a740309ac9f34eb6f5806d
From: "Doe, John"<sip:[email protected]>;tag=a9affac418;epid=c39ec15244
To: <sip:[email protected]>
CSeq: 1 INVITE
Content-Length: 0
13:31:55.674 |Mon Jun 16 13:31:55 2014] [debug] mod_authz_host.c(287): [client (null)] find_allowdeny: match remotehost pdx-lync-2.example.local compare pdx-lync-2.example.local
PID(25341) sip_sm.c(4788) ACL - upstream trusted - no need to authenticate
13:31:55.674 |ID(25341) sip_sm.c(987) TCB_PROXIED_STATE_TIMER : 60 seconds.
13:31:55.674 |ID(25341) sip_sm.c(4874) Request received from non-local SIP domain: example.com
13:31:55.674 |Mon Jun 16 13:31:55 2014] PID(25341) mod_sip_ua.c(2998) sip_ua_handler: unparsed to: <sip:[email protected]>
13:31:55.674 |ID(25341) mod_sip_ua.c(1369) find_scb(): about to acquire 7fb389cf26a740309ac9f34eb6f5806d:507aab56-e707780a-27a4bc92-3129d56d
13:31:55.674 |ID(25341) mod_sip_ua.c(1379) find_scb(): failed to acquire scb 507aab56-e707780a-27a4bc92-3129d56d:7fb389cf26a740309ac9f34eb6f5806d
13:31:55.674 |ID(25341) mod_sip_ua.c(3041) sip_ua_handler(): scb not found for this request
13:31:55.674 |ID(25341) mod_sip_ua.c(1639) ua_handle_invite(): INVITE request with body: <?xml version="1.0"?>
<RequestSystemStatus xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3"><extensions><privateData><private><lcs:line xmlns:lcs="http://schemas.microsoft.com/Lcs/2005/04/RCCExtension">tel:2373;phone-context=dialstring</lcs:line></private></privateData></extensions></RequestSystemStatus>
13:31:55.674 |Mon Jun 16 13:31:55 2014] PID(25341) mod_sip_numexpand.c(788) URL host example.com doesn't point at proxy, no number expansion on user john.doe
13:31:55.674 |ID(25341) mod_sip_ctigw.c(6393) ctigw_csta_handler:: Session Time in config =1810
13:31:55.674 |ID(25341) mod_sip_ctigw.c(6494) ctigw_csta_handler:: Get CSTA request: 0
13:31:55.674 |Mon Jun 16 13:31:55 2014] PID(25341) sip_sm.c(1085) timer_ticks: id:9a39ab68 15 1810
13:31:55.674 |ID(25341) mod_sip_ctigw.c(6544) ctigw_csta_handler:: Get CSTA request: 0-RequestSystemStatus
13:31:55.674 |Mon Jun 16 13:31:55 2014] PID(25341) mod_sip_ctigw.c(6560) ctigw_csta_handler:: line=2373, device=, partition=, name=, phone-context=dialstring
13:31:55.674 |ID(25341) mod_sip_ctigw.c(2363) Authorizing user (john.doe [email protected]) DN (2373) DEV () Partition ()
13:31:55.674 |Mon Jun 16 13:31:55 2014] PID(25341) mod_sip_ctigw.c(1800) CTIGW DB query : execute procedure GetMOCLineAppearanceInEffect('john.doe', '[email protected]', '2373', '', '')
13:31:55.707 |ID(25351) mod_sip_ctigw.c(2408) user has multiple lines, but has yet selected one
13:31:55.707 |ID(25351) mod_sip_ctigw.c(6576) ctigw_csta_handler:: FAIL AUTHORIZED userID=john.doe [email protected] line=2373, device=
13:31:55.707 |Mon Jun 16 13:31:55 2014] PID(25351) mod_sip_ctigw.c(922) freeQCB(): QCB -1707780688 is about to be freed
13:31:55.707 |ID(25351) mod_sip_ua.c(221) ua_get_map_key(): SCB get failed 4125e7e6
13:31:55.707 |Mon Jun 16 13:31:55 2014] PID(25351) mod_sip_ua.c(2674) ua_scb_destroyed(): scb 9a397758:1 key: 7d1232f0-48071418-40399a77-299640
13:31:55.707 |ID(25351) sip_sm.c(1197) Sent 727 bytes TCP packet to 192.168.1.7:50752
SIP/2.0 401 Unauthorized
Via: SIP/2.0/TCP 192.168.1.7:50752;received=192.168.1.7;branch=z9hG4bK7E5EE7B5.ECF019B6176EE77B;branched=FALSE, SIP/2.0/TLS 192.168.6.152:57095;ms-received-port=57095;ms-received-cid=1BF000
Call-ID: ba0cd56054094212ba26145c96b39f2c
From: "Doe, John"<sip:[email protected]>;tag=41e8aed3ab;epid=c39ec15244
To: <sip:[email protected]>;tag=2241b56c-7230dd55
CSeq: 1 INVITE
Record-Route: <sip:pdx-lync-pool-2.example.local;transport=tcp;ms-fe=pdx-lync-2.example.local;opaque=state:T;lr>;tag=C4140F78AB707EE55A3542C290EE3BDD
Contact: <sip:[email protected]:5060;transport=TCP>
User-Agent: Cisco-Systems-Federation\8.0
Content-Disposition: signal;handling=required
Content-Length: 0

I still haven't gotten confirmation, but I was able to work with my Lync admin and we found that if a user has multiple devices, you have to put the specific device in the Line URI field that it is supposed to control. Still working through testing to confirm it will do what we need though...from what I've seen so far, I don't think it will...and Microsoft has said they're going to sunset RCC in the next version of Lync anyway, so...

Similar Messages

Lync 2013 to CUPS RCC - Record-Route signature is invalid

Hi all,
             I have a Lync 2013 environment and I'm trying to implement RCC with a CUPS 10 environment.
On the Lync side, I have run the following commands:
$tcpRoute = New-CsStaticRoute -TCPRoute -Destination 10.10.120.54 -Port 5060 -MatchUri cups.domain.com -ReplaceHostInRequestUri $true
Set-CsStaticRoutingConfiguration -Route @{Add=$tcpRoute}
CsTrustedApplicationpool -Identity 10.10.120.54 -Registrar LyncFE.domain.com–Site 1 –TreatAsAuthenticated $True –ThrottleAsServer $True –RequiresReplication $False
New-CsTrustedApplication -ApplicationID RCCGateway-1 –TrustedApplicationPoolFqdn 10.10.120.54 -Port 5060 -EnableTcp
Set-CsRegistrar registrar:LyncFE.domain.com -SipServerTcpPort 5060
on the test user I have set
Set “Telephony” to:
Remote call control
Set Line uri to:
tel:<ext>;phone-context=dialstring
Set Line server uri to:
sip:<username>@cups.domain.com
In the SIP logs I get the following (I have bolded the bits I think are important)
TL_INFO(TF_PROTOCOL) [0]1FDC.1670::02/19/2015-05:35:53.687.001b274e (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(265))[1932678887] $$begin_record
Trace-Correlation-Id: 1932678887
Instance-Id: 45F
Direction: incoming
Peer: 10.10.120.54:5060
Message-Type: response
Start-Line: SIP/2.0 200 OK
From: "Test ADL"<sip:[email protected]>;tag=224a04a9f9;epid=fa015fbbdb
To: <sip:[email protected]>;tag=29e9c078-ce4a5e7
Call-ID: 669e8717f0a0487fb09aed392d84f589
CSeq: 1 INVITE
Contact: <sip:[email protected]:5060;transport=TCP>
Via: SIP/2.0/TCP 10.70.11.70:52575;received=10.70.11.70;branch=z9hG4bKE005ADB2.742BA66DD49B1869;branched=FALSE;ms-internal-info="aaweLh0WVLdGLzdpabeIHETcyFKD5xJlVJz_tnBJ0l-7ptpit0RW23IQAA", SIP/2.0/TLS 10.70.20.36:52402;ms-received-port=52402;ms-received-cid=1A00
Record-Route: <sip:[email protected]:5060;maddr=10.10.120.54;transport=tcp;lr>,<sip:LyncFE.domain.com;transport=tcp;opaque=state:T;lr;ms-route-sig=aaF2AA9BciRLZcYZPN0XasMmn8g4LiFd4j7Fdcxg6R6uRtpit0mCXPOAAA>;tag=7E7648A7380D372597F42EAEAECC07A2
Content-Length: 190
Content-Type: application/csta+xml
Message-Body: <?xml version="1.0"?>?<RequestSystemStatusResponse xmlns="??<systemStatus>normal</systemStatus>?</RequestSystemStatusResponse">http://www.ecma-international.org/standards/ecma-323/csta/ed3">??<systemStatus>normal</systemStatus>?</RequestSystemStatusResponse>?
$$end_record
TL_ERROR(TF_SECURITY) [0]1FDC.1670::02/19/2015-05:35:53.687.001b2b66 (SIPStack,SIPAdminLog::WriteSecurityEvent:SIPAdminLog.cpp(319))[1932678887] $$begin_record
Text: Record-Route signature is invalid
Result-Code: 0xc3e93f1e SIPPROXY_E_INVALID_RECORD_ROUTE
Connection-ID: 0x1300
Peer-IP: 10.10.120.54:5060
Peer: 10.10.120.54:5060
SIP-Start-Line: SIP/2.0 200 OK
SIP-Call-ID: 669e8717f0a0487fb09aed392d84f589
SIP-CSeq: 1 INVITE
$$end_record
TL_WARN(TF_DIAG) [0]1FDC.1670::02/19/2015-05:35:53.687.001b2b74 (SIPStack,SIPAdminLog::WriteDiagnosticEvent:SIPAdminLog.cpp(805))[1932678887] $$begin_record
Severity: warning
Text: Routing error occurred; check Result-Code field for more information
Result-Code: 0xc3e93f1e SIPPROXY_E_INVALID_RECORD_ROUTE
SIP-Start-Line: SIP/2.0 200 OK
SIP-Call-ID: 669e8717f0a0487fb09aed392d84f589
SIP-CSeq: 1 INVITE
Peer: 10.10.120.54:5060
$$end_record
I have not had any luck finding the solution to this as yet - and any suggestions as to what I have done wrong would be appreciated.
Edit - apparently bold doesn't work.... sorry - it works in the editor, but not when I save the post! Please look at the ":record-route" line in the first log and the result code in the next two entries.

Hi Ben, thank you for your update.
To clarify, the
device=SEP0123456789F is an example, you have to change it with the correct Cisco IP-Phone serial number used by your user.
I've checked every step of your procedure and I've not found any issue, I've used the same procedure with a Cisco CUPS 10 and everything works fine.
Please be sure to check this on Cisco:
- the MatchURI need to be equal to the Cisco Unified Presence Domain
- on the CUCM the CTI Account (default is CtiGw) nned to have CTI controll of every phone (Standard CTI Allow Control of Phone supporting Connected Xfer and conf) and Supporting Rollover Mode
- it's important that the "Standard CTI Secure Connection" group is NOT associated to the CtiGw account (if it's associated it force the connection to TLS).
Let me know.
Regards
Luca
Luca Vitali | MCITP Lync/Exchange | snom Certified Engineer | Sonus SBC1000 Engineer

MS Lync 2013 federation with Cisco CUP 8.6

Hi all,
I am currently trying to federate CUPS 8.6 with MS Lync 2013.
After a lot of certificate issues we finally got a one-way IM from CUPS to Lync. I can't get Presence in either direction or send an IM from Lync to CUPS user.
I have followed the Cisco guide for inter-domain federation within an enterprise. so no edge server or Cisco ASA involved.
The error message I am seeing on the Lync side is:
ms-diagnostics:
1010;reason="Certificate trust with another server could not be established";ErrorType="Refer to HRESULT code for specific security status";tls-target="CUP-A.cupdomain.co.uk";HRESULT="0x80090326(SEC_E_ILLEGAL_MESSAGE)";source="LCT-LYNCFE01.lyncdomain.net"
On the CUP side I can see the TLS session being dropped with this error message:
17:22:58.945 |[Wed Apr 23 17:22:58 2014] PID(24295) sip_tls_verify_callback: TLS protocol error(ssl reason code=(null) [0]),lib=(null) [0],fun=(null) [0], errno=0
17:22:58.945 |[Wed Apr 23 17:22:58 2014] PID(24295) sip_tcp.c(2409) SSL server accept returned SSL_ERROR_SSL
17:22:58.945 |[Wed Apr 23 17:22:58 2014] PID(24295) sip_tls_accept: TLS protocol error(ssl reason code=no certificate returned [178]),lib=SSL routines [20],fun=SSL3_GET_CLIENT_CERTIFICATE [137], errno=0
17:22:58.945 |Wed Apr 23 17:22:58 2014] PID(24295) sip_tcp.c(1056) sip_tcp : Hard close/destroy of tcp connid 93 sock_fd 37 flags 0
On the cisco side I have only set a TLS Peer as the LYNCPOOL server. do I need to set up a TLS Peer for all of the Lync Servers?
The lyncpool server has client and server enhanced key usage - do I need to reissue the certs with this for ALL servers in the lync cluster?
It seems like TLS will neogotiate successfully using the LYNCPOOL server but not with any of the other servers. Must be missing something simple.
Many thanks for advice.
Regards
Lee.

Hi,
Please double check the listen port of Lync Server．
In the Lync Server Management Shell enter the following command to verify the current system configuration: Get-CSRegistrarConfiguration
More ports requirement for Lync server you can refer to the link below:
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cups/8_6/english/integration_notes/IntegrationNote_CUP86_MicrosoftLyncServer2010_RCC.html
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Cisco Call Manager 8.5 and Lync 2013

Dear all,
Our customer wants to integrate their Lync 2013 to the Cisco Call Manager 8.5.
Out of some not so recent information i thought that if u want to use the enterprise voice of lync you'll have to make a sip trunk between Cisco Call Manager & Lync 2013.
I think that this still counts, i've also heard that there have been a moderate amount of changes between cucm 8.5 and cucm 8.6 on matters of sip.
I'm unable to find them though, also what does CUCI - Lync do?
Kr,
Yannick Vranckx

Hi Yannick,
There can be three types of integrations between Lync and Cisco Systems
1) Direct SIP Trunk between Lync Server and Call Manager - In this, we can setup shared line between Cisco extensions and Lync extensions, and Sip trunk between the servers. Any Cisco phone / Lync client can call each other vice-versa. Initial setup needs planning, but later it does not need much configurations in client side. The following document explains the configurations needed.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucilync/9/CUCI_BK_C0B36AC1_00_cisco-uc-integration-for-microsoft.pdf
2) CUCILYNC, which is like Cisco Jabber client but connects with Lync and Call Manager: Lync Client <----> CUCILYNC <-----> CUCM
In this option, a plug-in is installed in each client side. Although initial configurations is easier, each user needs to install the client and operate it. The below document explains the configuration and setup.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucilync/9/CUCI_BK_C0545A41_00_cisco-uc-integration-for-microsoft.html
3) RCC (Remote Call Plugin) which just provides basic call control feature but for that you need Cisco Unified Presence Server: Lync Client <----> CUPS <-----> CUCM
HTH
Manish

Lync 2013 Cloud Service Limitations

Can anyone point me to some references on the limitations with Lync 2013 in the
cloud? What are some pros and cons about cloud services with voice and video?

How much of this list is still true to the limitations of Lync Online?
The features not available are:
Searching for employees by their skillset in an on-premise SharePoint Server and SharePoint Online
Persistent group chat
Connect (federate) to IBM Sametime unified communications platform
IM/presence federation with XMPP networks such as Jabber and Google Talk
IM/presence with AOL and Yahoo
Authenticated experience in Lync Web App
Outlook delegation for scheduling online meetings
Generate a link to schedule a meeting via web page
Schedule an online meeting in Outlook Web App
Dial-in audio conferencing on Lync Server
Multimedia content upload
Screen shot capture (including annotation)
Interoperability with on-premise video conferencing systems
Make incoming/outgoing calls over the phone network (PSTN dialling)
Call hold/retrieve
Dial-out over the phone network (PSTN) for meetings
Advanced call controls including transfer, forward and simultaneous ring
Access to Exchange Online voice mail
Team calling
Delegation for voice, for example, boss delegates to secretary
Call park
Outgoing Direct Inward Dialing (DID) manipulation
Enhanced 9-1-1 for location by emergency services
Dial plans and policies
IP desk phone support
Survivable Branch Appliances for branch office resiliency
Call admissions control
Support for analog devices such as a fax
Response groups
Private line (secondary DID for executives)
Interoperation with third-party private branch exchange (PBX)
Presence interoperation with third-party PBX
Remote call control (RCC) (also known as “click-to-call”) with on-premises PBX
Malicious call trace
Unassigned number
Network Quality of Service (QoS) and Differentiated Services Code Point (DSCP)
Media path optimisation
Phone number management
Call detail recording (CDR) and billing reporting
Integration with call centre solutions (Aspect)
Connect to IP phones (Lync 2010 Phone Edition)
Advanced interface for receptionists (Lync 2010 Attendant client)
Legacy clients (eg. Office Communication for Mac, 2007 R2, Mobile for Windows Mobile 6.x)
Anti-malware scanning for meeting content and file transfers
Instant message archiving (server-side only)
Exchange Unified Messaging (UM) interoperation with Exchange Online
Exchange UM interoperation with Exchange on-premise
Use the same domain for Lync on-premise and Lync Online users
Splitting workloads (for example, running IM/presence/voice on-premises, and conferencing in the cloud)
Attendee/user reporting
Reporting (using call recording and Quality of Experience)
Server side APIs to connect to other programs

Lync 2013 Server / Roles & Components

Lync
2013 Server / Roles & Components
Front End
User authentication and registration
Presence information and contact card exchange
Address book services and distribution list expansion
IM functionality, including multiparty IM conferences
Web conferencing, PSTN Dial-in conferencing and A/V conferencing (if deployed)
Application hosting, for both applications included with Lync Server (for example, Conferencing Attendant and Response Group application), and third-party applications
Primary store for user and conference data. Information about each user is replicated among Front End Servers in the pool
Optionally, Monitoring, to collect usage information in the form of call detail records (CDRs) and call error records (CERs). This information provides metrics about the quality of the media (audio and video) traversing your network for both Enterprise
Voice calls and A/V conferences.
Web components to supported web-based tasks such as web scheduler and join launcher.
One Front End pool runs the Central Management Server DB, which manages and deploys basic configuration data to all servers running Lync
Optionally, Archiving, to archive IM communications and meeting content for compliance reasons.
Optionally, if Persistent chat is enabled, Persistent Chat Web Services for Chat Room Management and Persistent Chat Web Services for File Upload/Download.
Back End
Database server running Microsoft SQL Server
Provide the DB services for the Front End pool
Acts as backup store for the pool’s user and conference data
Primary stores for other DB’s like Response Group
High Availability for the BE DB is provided via SQL Mirroring
Optional Witness to enable automatic failover for BE
SQL Sever 2008 R2 or higher required for SQL Mirroring
Edge Server
Enable users to communicate and collaborate with users outside the organization’s firewall
Comprises four separate server roles
Access Edge – Acts as a secure proxy for all remote Lync signaling traffic
Remote Access
Federation
Public IM Connectivity (PIC)
Web Conferencing Edge – Enable remote users to participate in Web conferences with internal or remote workers
A/V Edge – Responsible for secure relay of A/V media among internal, external, and federated contacts
XMPP Gateway – Allows IM/P with XMPP federated contacts
Reverse Proxy
Simple URL Publishing – Required for users to join Lync meetings
Web Conferencing Content – Users download meeting content (PowerPoint, Whiteboard, and Poll data) via Lync Web Services when in meeting
Address Book & Distribution List Expansion – Required for users to download Lync Address Book and perform DL expansion
User Certificates – Provides client certificate authentication via Lync Web Services
Device Updates – Provides software updates to Lync IP endpoints
Mobility – Provides connectivity for mobile clients via Lync Web Services
Mediation Server
Translates signaling and media between Lync Server and PSTN, IP-PBX, or SIP Trunk
Can be co-located on Front End or separated as stand-alone Server dependent on call volume
Role facilitates dial-in conferencing
Capacity
Co-located = 150 Concurrent Calls
Standalone = 1100 Concurrent Calls
Persistent Chat
Enable users to participate in multiparty, topic-based conversations that persist over time
Pchat Front End server role runs persistent chat service
Pchat Back End server stores chat content and compliance events
Geographic DR is provided via stretched pool and SQL log shipping to replicate DB info
150k provisioned users / 80k concurrent users
Archiving
Uses SQL Server 2008 R2 or SQL Server 2012 for DB
Capable of archiving the following:
Peer-to-peer IM
Multiparty IM
Web Conferences, including uploaded content and events
A/V for peer-to-peer IM and web conferences
Web conferencing annotations and polls
Monitoring
Agent that runs on each Front End Server that collects and manages information from the Front End and Mediation Servers
Stored on SQL Server DB
Leverages SQL Server Reporting Services for creation of reports related to call quality and metrics
Office Web Apps Server
External server leveraged for rendering PowerPoint slides within the Lync client and Lync Web App
Typically leveraged within SharePoint deployments to deliver browser-based versions of Microsoft Office applications
System Center Ops Mgr
Health configuration in Lync Server 2013 is built around System Center Operations Manager and the use of Lync Server Management Packs. These Management Packs include a number of new features and enhancements, including:
Feature
Description
Synthetic Transactions
Windows PowerShell cmdlets that can be run from various locations to ensure that end user scenarios such as sign-in, presence, IM, and conferencing are readily available to end users.
Call Reliability Alerts
Database queries for Call Detail Records (CDR). These records are written by Front End Servers to reflect whether end users were able to connect to a call or why a call was terminated. These queries result in alerts that indicate when a wide range of end
users are experiencing connectivity issues for peer-to-peer calls or basic conferencing functionality.
Media Quality Alerts
Database queries that look at Quality of Experience (QoE) reports published by clients at the end of each call. These queries result in alerts that pinpoint scenarios where users are likely to be experiencing poor media quality during calls and conferences.
The data is built upon key metrics such as packet latency and loss, metrics that are known to directly contribute to call quality.
Component Health
Individual server components raise alerts by using event logs and performance counters. These alerts indicate failure conditions that can severely impact one or more end user scenarios. These alerts can also indicate a variety of other failure conditions,
including services not running, high failure rates, high message latency, or connectivity issues.
Dependency Health
Failures can occur for a variety of external reasons. The management packs now monitor and collect data for some of the critical external dependencies that might indicate severe issues, including IIS availability, CPU and memory usage of servers and processes,
and disk metrics.
Exchange UM
http://www.contactcenterarchitects.com/lync-2013-server-roles-components/

Hi,
Thank you for sharing the information. It is useful for others who not understand Lync Server Roles and Components. You time and effort are appreciated.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Office web Apps server Lync 2013 Certificate

Hi,
I'll be installing Office web app (OWA) server with Lync 2013 std edition. External users access is disabled but federation is enabled, mean OWA will be exposed to internet as wabweb.contoso.com, the interal host name of OWA server is owa.contoso.local
Does the certificate on the on OWA server need to have owa.contoso.local and certificate principle name and wabweb.contoso.com as SAN? or only owa.contoso.local is enough?

It really depends on how you publish the server to the internet. You have some options. If you are publishing this via a reverse proxy, internally you would have a private cert with .local on it and the public name on the reverse proxy. If you are
punching a firewall hole/NAT directly to the server your best option is to use a public cert on that server directly.
That all said, personally I like to make both the internal and external farm URL the same, and use a public cert on the server (if no reverse proxy is in play). So I would actually enter the OWAS Farm as wabweb.contoso.com in topology builder, than
when creating the farm via PowerShell make that both the internal and external URL and get a certificate with a single name on it of wabweb.contoso.com.
Richard
Richard Brynteson, Lync MVP | http://masteringlync.com | http://lyncvalidator.com

Lync 2013 meeting invitation customizations not working for some users

Hello Microsoft TechNet Forms,
I have a strange problem that I am totally stumped on. I made some modifications to the Lync 2013 meeting configuration to add in my company's logo, a footer and set a custom help Lync URL. Now everything seemed to work expect for myself and
one other person I tested with. If I try creating a new Lync 2013 meeting via my Outlook 2013 the normal stock Lync meeting invite appears. Yet testing with any other user everything I have changed appears as expected and I am at a total loss to why.
I have so far from troubleshooting determined it must be something with my account that is causing it but I have just not been able to determine what. As signing into a different machine yields the same result yet testing with another account that is
known to work on the exact same machine works correctly with the different account. I have tired deleting and re-crating my Lync account just in case that had something to do with it but that didn't fix the problem. I have tired repairing Office 2013 to
running windows update on Office 2013 which didn't help.
The changes I made to the meeting configuration are global scoped. I have so far not found anything online from anyone ever reporting a similar issue to this. At this point I am stuck on what I should be looking for with regards to what is stopping
the meeting invite updating for myself and the other person. Given I don't know what mechanism is involved with updating the Lync meeting invite on Outlook 2013 I am stumped. I am open to any suggestions someone might have as to what to do next or what might
be the cause of this problem.
Nicholas,

Hi Nicholas,
Can you compare your account with other’s and check if your account is applied any special policy in Lync Control Panel ?
Best regards,
Eric

Lync 2013 Front-End HA

We are currently in a co-existence environment with both Lync 2010 and 2013 running side-by-side.
There are 2 FE pools with pool pairing setup for Lync 2013. We have been carrying out some testing before migrating all of our users over.
We have an issue where when we take out one of the 2013 front end servers the client does not automatically reconnect to one of the other servers in the pool, occasionally it will but can take 10-15 mins to do this. If we simulate a similar test on the 2010
front ends the client reconnects in seconds.
I am using the Lync 2013 client

Thanks for your replies.
I have setup DNS LB for the pool name (this is working correctly) and I am using a kemp load balancer for the internal web services FQDN
I checked the EndPointConfiguration.Cache file and it just had the name of the front end server I was connected to. I deleted it and restarted my client now the EndPointConfiguration.Cache file has the name of the pool, the front end server that I am connected
to and the IP addresses of the servers in the pool, is that correct?
I tested the failure of the server I was connected to by removing the network adapter in VMware.
It took 44 seconds for my client to sign out and 1:15 after that to sign back in. My LPE took 2:18 to sign out and 1:22 after that to sign back in. Surely this cant be right?
During the time the failure happens and the client signs out, it is unusable.
I have had a look in the snooper logs but it is difficult to see the wood for the trees.
Thanks for your help.

Lync 2013 Enterprise load balancing on the front end and edge pool

Hi,
I am setting up a Lync 2013 Enterprise deployment consisting of a Front End pool (x2 FE servers) and an Edge pool (x2 Edge servers). I'm seeing some conflicting advice regarding load balancing using hardware or DNS for the front end and the edge.
On the front end I have 2 internal DNS records 'lyncfepool1.contoso.local' each of which map to one of the IPs of the FE servers. I've used my details to populate the Detailed Design Planner excel spreadsheet and am told that I require a HLB to load
balance my front end pool. I'm aware of the need to load balance HTTPS traffic internally (which will be done by TMG) however other traffic to the front end (SIP, etc) can be balanced by DNS only, and not require a HLB?
Can someone clarify the front end requirement?
Also - looking now at the edge pool - this site again have two edge servers in a pool. We are using a total of six private IP addresses, two per edge service (2 x av.contoso.com, 2 x sip.contoso.com and 2 x webcon.contoso.com). These will be
NAT'ed by the external firewall and directed to the respective external (DMZ) IP addresses on the Edge servers on port 443. I know this isn't true roundrobin due to the intelligence of the Lync client when connecting (in that the Lync client will connect
to one of the public IPs and if it can't connect, it will know to connect to the other service IP), however I want to clarify this set up, particularly the need to direct the external public IP traffic at the DMZ Edge IP specified in the topology builder.
I've attached a basic diagram of the external/DMZ/Edge side which hopefully helps with this question
Persevere, Persevere, Per..

That is because you will always need HLB for a front-end server since it hosts the Lync webservices which use HTTP/HTTPS traffic.
The description on the calculation tool also describes this correctly:
Supports Standard and Enterprise pools (up to 12 nodes), with pure device-based load balancing or a combination of DNS load balancing and device-based load balancing (for
Lync web services)
You can use either Hardware or DNS loadbalancing for SIP traffic only, but you will always need a HLB for the webservices. Both are applicable for the Front-End so you have either
full HLB for both SIP and HTTP(S) traffic
DNS LB for SIP traffic and HLB for HTTP(S) traffic
Hope this is more clear :-)
Lync Server MVP | MCITP Lync Server 2010 | If you think my post is the answer to your question, please mark it as answer so future visitors can easily find it.

Lync 2013 updating databases after updating Front End servers

We have a front-end server pool consisting of 3 Lync 2013 servers and a back end of 2 SQL servers using SQL mirroring. All servers are Windows 2008 R2.
Following the instructions in
http://support2.microsoft.com/kb/2809243 , I verified that the servers were all ready for updates, then I ran the
Stop-CsWindowsService -Graceful cmdlet to stop the Lync services on the first FE server, then I ran LyncServerUpdateInstaller.exe to install the updates. After the updates were installed, I restarted the server, waited for Lync services
to all start, then repeated the process on the next 2 servers in turn. This was all successful.
I am now looking at step 2 in this document, applying the back-end database updates, and I have a problem and some questions. The problem is that all the databases had the principal copy on the mirrored SQL server. I ran the recommended Invoke-CsDatabaseFailover
-NewPrincipal Primary cmdlet repeatedly, using all the database types I could find, but I still have two databases (database names
xds and lis) on the mirrored server. Since the cmdlet requires a database type, what type of databases are the xds and the lis databases?
Once I get that done, I an still unsure of exactly what to run to update the databases. The KB article states to run Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn FEBE.FQDN -Verbose .  Do I type this in exactly
as stated, or is FEBE.FQDN a variable for our SQL server or some other entity in our environment? If I do use the actual SQL Server name in that, do I run it twice, using the name of the mirrored SQL server the second time?
Thank you very much for your help.

Hi Logan Burt,
Central Management store database files
Data file or log purpose
                Xds.ldf
Transaction log file for the Central Management store
                Xds.mdf
Maintains the configuration of the current Lync Server 2013 topology, as defined and published by Topology Builder
                Lis.mdf
Location Information service data file
                Lis.ldf
Transaction log for the Location Information service data file
And you could verify if Lync Server 2013 database updates have completed successfully.
How to Verify if Lync Server 2013 Database Updates Completed Successfully
http://blogs.technet.com/b/dodeitte/archive/2013/07/02/how-to-verify-if-lync-server-2013-database-updates-completed-successfully.aspx
Best regards,
Eric

Unable to search GAL on Lync 2013 Front End Pool through Lync 2013 client

I'm in the beginning of a 2010 to 2013 migration and I'm currently testing co-existence functionality between pools. I've noticed that users cannot search the GAL from their Lync client after being moved to the 2013 pool.
When trying to access the internal URL https://fepool13.domain.com/abs/handler the user is prompted to login and after three failed attempts, receives "401 - Unauthorized: Access is denied due to invalid credentials. You do not have permission
to view this directory or page using the credentials that you supplied".
Searching withing a Lync 2010 or Lync 2013 client returns no results, but there are no errors as well as nothing in the event logs or tracing folder regarding not being able to search.
The 2010 pool has been in production for a few years now and when accessing its internal ABS URL https://fepool10.domain.com/abs/handler the user is granted access after a successful login.
In the IIS logs there are slightly more detailed 401 error codes, but I’m not sure what to make of them.
The rtcab database appears to have user information and all three front end servers appear to be syncing with active directory. I say the rtcab database appears to have user info because the AbUserEntry table is filled with User ID'd, GUID's and a
bunch of other stuff.
The authentication on 2013 front end servers “internal lync website/abs/handler” is set to 1. Negotiate, 2. Ntlm - which is the same as the 2010 front end servers.
Any ideas?

Hi,
Which step did you do among migration from Lync Server 2010 to Lync Server 2013?
Did you already move CMS from Lync Server 2010 to Lync Server 2013?
Please create a new Lync account on Lync Server 2013 pool and test the issue again.
Please check if User Replication has completed with the help of the link below:
http://technet.microsoft.com/en-us/library/jj204680.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync 2013 Front End SIP/2.0 500 Compression algorithm refused

I've deployed a brand new Lync 2013 environment hosted on Windows Server 2012 R2 that is currently in co-existence mode with my Lync 2010 environment.
I have SCOM 2012 monitoring the environment and it recently started reporting that one or more of my front end servers
was in a critical state. Diving into it revealed the following perf counter threshold was being tripped:
Time Sampled: 3/26/2014 2:33:30 PM
Object Name: LS:SIP - Responses
Counter Name: SIP - Local 500 Responses
Instance Name:
First Value: 14287
Last Value: 14340
Delta Value: 53
Using OCSLOGGER.exe on the front end to capture logs, i trapped the following:
TL_INFO(TF_PROTOCOL) [11]9138.1C58::03/26/2014-19:12:39.098.0022c780 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(265))[120713120] $$begin_record
Trace-Correlation-Id: 120713120
Instance-Id: 7D80EB
Direction: outgoing;source="local"
Peer: poolA.contoso.com:63820
Message-Type: response
Start-Line: SIP/2.0 500 Compression algorithm refused
FROM: <sip:poolA.contoso.com>;ms-fe=FEserver1.contoso.com
To: <sip:poolA.contoso.com>;tag=F8B88CAB38613EB380773027C56D94AF
CALL-ID: 986f9f568c794ce39d33d7158376157b
CSEQ: 1 NEGOTIATE
Via: SIP/2.0/TLS 10.154.228.225:63820;ms-received-port=63820;ms-received-cid=C3D7C00
Content-Length: 0
ms-diagnostics: 2;reason="See response code and reason phrase";HRESULT="0xC3E93C0F(SIP_E_REACHED_CONFIGURED_LIMIT)";source="FEserver1.contoso.com"
Server: RTC/5.0
$$end_record
The only recent change made to the front end servers was making the registry change outlined in this article:
http://support.microsoft.com/kb/2901554/en-us so i'm wondering if that has something to do with it.

The MSFT support person said to re-apply CU5 to the Director servers and reboot. Since this is impactful to the environment and I would have to do reboots anyway, I opted to go the route of installing the more recent update so....
Last weekend I updated my Lync environment with what I think is considered CU6, the September 2014 updates for Lync 2013 Server (https://support.microsoft.com/kb/2809243) and still no luck. The front
end servers are fine; no excess SIP 500 errors occurring there but within 30 minutes of removing the SCOM override on the Director servers the alerts started firing again.
I reinstated the override in SCOM for the Directors and had my case with Premier support un-archived. The MSFT support person said if the alerts didn't go away she was going to have to engage the Lync product group for help. We'll see where it
goes from here.
JKuta

Iphone and ipad Lync Client Randomly cannot sign in to Lync 2013 Server

I have a Lync 2013 environment that will allow all clients to connect from inside and outside of the network except for ios devices. iOS devices are sometimes able to connect and sometimes not. When they are not able to sign in they receive a message stating,
"An Error Occurred in Lync. Please retry. If the problem persists, contact your support department"
I have run tests using the Microsoft Remote Connectivity Analyzer and all tests come back green. I have also used the Lync Connectivity Analyzer and get the results below:
Starting Lync server autodiscovery
Starting automatic discovery for secure (HTTPS) internal channel
Server discovery failed for secured internal channel against
https://lyncdiscoverinternal.earenfroe.com/
Starting automatic discovery for unsecure (HTTP) internal channel
Server discovery failed for unsecured internal channel against
http://lyncdiscoverinternal.earenfroe.com/
Starting automatic discovery for secure (HTTPS) external channel
Server discovery succeeded for secure (HTTPS) external channel against URL
https://lyncdiscover.earenfroe.com/
Starting automatic discovery for unsecure (HTTP) external channel
Server discovery failed for unsecured external channel against
http://lyncdiscover.earenfroe.com/
Starting the requirement tests for Lync Mobile 2013 App
Starting tests for Mobility (UCWA) service
Completed tests for Mobility (UCWA) service
Your deployment meets the minimum requirements for Lync Mobile 2013 App.
Anyone have any suggestions on where to go next? Troubleshooting an intermittent connection issue that only affects one mobile platform is tough...especially when all the testing tools say everything is configured correctly :)
Thanks in advance!
Tom

I have the same problem, and we have netscaller as revrse proxy solution and we have the required records created for mobility.
with lync2010 mobility it is working fine, but with lync 2013 mobiltity we have intermittent issue with error e2-3-33 error
raghu
I had the same problem (e2-3-33 on mobile devices at random times) and it turns out it was McAfee antivirus causing the UCWA service to crash repeatedly. The workaround for it is outlined in the below blog entry I found as well as the below Microsoft document.
Long story short you want to run follow the steps outlined in the workaround section below (I copied it from the linked MSFT document)
http://support.microsoft.com/kb/2997513
http://lynclounge.blogspot.com/2014/07/lync-mobility-issues-event-ids-1309.html
WORKAROUND
he following procedures must be performed on all Lync Server 2013 FE server and Director Lync 2013 server roles. To
perform these procedures, first open a command prompt as an administrator.
Windows Server 2008 R2
On the Start menu, type cmd.exe in the Windows search feature, and then press Enter.
Right-click cmd.exe, and then click Run as administrator.
Windows Server 2012
Press the Windows key to access the Start page.
Use the Windows search feature to locate cmd.exe.
Right-click cmd.exe, and then click Run as administrator.
In the Command Prompt window, follow these steps:
Navigate to the %install drive%:\Windows\System32\inetsrv> directory prompt.
Enter the following command, and then press Enter:
appcmd set config /section:applicationPools /[name='LyncUcwa'].recycling.disallowOverlappingRotation:true
Enter the following command, and then press Enter:
appcmd set config /section:applicationPools /[name='LyncUcwa'].processModel.shutdownTimeLimit:0.00:00:30
To confirm the changes from steps 2–3, enter the following command, and then press Enter:
appcmd list apppools lyncucwa /config
The following information should be returned to the console to confirm the update to the LyncUcwa application pool
settings:
<add name="LyncUcwa" autoStart="true" managedRuntimeVersion="v4.0" managedPipelneMode="Integrated" startMode="AlwaysRunning">
<processModel identityType="NetworkService" idleTimeout="00:00:00" shutdownTieLimit="00:00:30" />
<recycling disallowOverlappingRotation="true">
<periodicRestart time="00:00:00">
<schedule>
</schedule>
</periodicRestart>
</recycling>
<failure />
<cpu />
</add>

Voice problems with Lync 2013 Mobile

Hi
I have a situation where Lync 2013 on both iPhone & Android has started giving problems with making and receiving voice calls. There are no problems with Windows, Mac or Phone Edition clients that I'm aware of. I have not tested anything over the VPN,
but this should not be a factor.
For receiving calls - If the user is connected to the LAN via Wi-Fi AND the call is from an internal user, all works fine. If the call is from an external user OR the user is connected via 3G, then the call just shows "Connecting" indefinitely.
This includes transferred calls.
For making calls - If the user is connected to the LAN via Wi-FI and calls either an internal or external users, all works fine. If the user is connected via 3G and calls either an internal or external user, the phone rings, but when it's answered it shows
call ended.
I have ran RUCT on a computer outside the network, with the following findings:
DNS:
Record
Type
Hostname
IP Address
Port
Weight
Priority
_sip._tls.domain.com
SRV
sip.domain.com
Edge External IP
443
100
0
sip.domain.com
A
sip.domain.com
Edge External IP
sipexternal.domain.com
A
sipexternal.domain.com
Edge External IP
meet.domain.com
A
meet.domain.com
<null>
_ntp._udp.domain.com
SRV
pool.ntp.org
NTP Server IP
123
100
0
_sipfederationtls._tcp.domain.com
SRV
sip.domain.com
Edge External IP
5061
100
0
lyncdiscover.domain.com
A
sip.domain.com
Edge External IP
lyncdiscover.domain.com
CNAME
sip.domain.com
I have ran Test Port on each entry where there is a port with successful results. Ping works on all entries.
If I query Certificate Information on sip.domain.com with port 5061 or 444, it succeeds and returns the certificate with subject sip.domain.com. If I query 443, it fails with error "An error occurred while retrieving the certificate. Unable to read
data from the transport connection: An existing connection was forcibly closed by the remote host."
On Microsoft Remote Connectivity Analyzer, all tests pass except for the certificate test:
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server sip.domain.com on port 443
The Microsoft Connectivity Analyzer wasn't able to obtain the remote SSL certificate.
Running netstat on Lync Edge gives me the following with regards to port 443:
TCP <Internal IP>:443 Lync2:0 LISTENING
TCP <External IP>:443 Lync2:0 LISTENING
Firewall allows connections on port 443 and I've tried disabling the firewall as well. Trying to open https://sip.domain.com in the browser on the Lync Edge fails also, telnet succeeds, but no data is returned.
I've restarted the AV service and also rebooted the Lync Edge server, no change. In the topology builder, I can see that AV is configured to listen on port 443.
Any ideas would be most welcome.
Regards
Lionel
MCP Windows Server MCTS .NET

I have ran a large amount of additional tests. On my latest round of testing, I have obtained the following results:
Call received via PSTN gateway on user DID, answered by desktop client inside LAN - works.
Call received via PSTN gateway on response group, answered by desktop client inside LAN - works.
Call received via PSTN gateway on user DID, answered by desktop client outside LAN (behind NAT, DSL router) - works.
Call received via PSTN gateway on response group, answered by desktop client outside LAN (behind NAT, DSL router) - works.
Call received via PSTN gateway on user DID, answered by mobile client inside LAN - does not work.
Call received via PSTN gateway on response group, answered by mobile client inside LAN - does not work.
Call received via PSTN gateway on user DID, answered by mobile client outside LAN (behind NAT, DSL router) - works.
Call received via PSTN gateway on response group, answered by mobile client outside LAN (behind NAT, DSL router) - works.
Call received via PSTN gateway on user DID, answered by mobile client outside LAN (3G) - does not work.
Call received via PSTN gateway on response group, answered by mobile client outside LAN (3G) - does not work.
Call received via PSTN gateway on user DID, answered by desktop client inside LAN and transferred to mobile client inside LAN - does not work.
Call received via PSTN gateway on response group, answered by desktop client inside LAN and transferred to mobile client inside LAN - does not work.
Call received via PSTN gateway on user DID, answered by desktop client inside LAN and transferred to mobile client outside LAN (behind NAT, DSL router) - works.
Call received via PSTN gateway on response group, answered by desktop client inside LAN and transferred to mobile client outside LAN (behind NAT, DSL router) - works.
Call received via PSTN gateway on user DID, answered by desktop client inside LAN and transferred to mobile client outside LAN (3G) - does not work.
Call received via PSTN gateway on response group, answered by desktop client inside LAN and transferred to mobile client outside LAN (3G) - does not work.
Call made through PSTN gateway from desktop client inside LAN - works.
Call made through PSTN gateway from desktop client outside LAN (behind NAT, DSL router) - works.
Call made through PSTN gateway from mobile client inside LAN - does not work.
Call made through PSTN gateway from mobile client outside LAN (behind NAT, DSL router) - works.
Call made through PSTN gateway from mobile client outside LAN (3G) - does not work.
Call from desktop client inside LAN to desktop or mobile client (regardless of location) - works.
Call from desktop or mobile client (regardless of location) to desktop client inside LAN - works.
Call from desktop or mobile client (regardless of location) to desktop or mobile client (regardless of location) - works.
There is no difference in behaviour between normal calls and conference calls. Reproducing the problem seems to require the following:
1. PSTN gateway needs to be involved
2. One party needs to be on mobile client
3. The mobile client needs to be inside the LAN or on a 3G connection, but not behind NAT on a DSL connection
The only conclusion I can make is that somehow NAT makes the problem go away, but it does not affect desktop clients (on the LAN or Wi-Fi at least, I do not have a way to test them on 3G).
The PSTN gateway (Cisco UCM) could also be the problem, but it works fine in all other cases. It has 4 trunks and makes all kinds of routing decisions, but once a call is routed to/from Lync, it should not make a difference on what type of device it is answered.
I'm really baffled by this one. Perhaps the 3G thing is a service provider issue and the issue on the LAN has something to do with the internal DNS combined with the behaviour of the mobile client. Just not sure exactly what.
MCP Windows Server MCTS .NET

Lync 2013 / CIMP(CUPS) 9.1.2 - RCC

Similar Messages

Maybe you are looking for