Interoperability
49 TopicsSalesforce Integration with Skype For Business
A while back you may have heard that there is a way to integrate Skype for Business with Salesforce. We just posted an article to the Skype for Business Community Blog detailing how to do this. Check it out here. Salesforce currently has this feature available as a public Beta. Over time we hope to see continued enhancements to this integration. Let us know what you think!13KViews7likes4CommentsJoin Zoom meeting from Skype Room System v2
Hi there, Trying to join a Zoom meeting from Skype Room System V2. We can join the meeting using the SfB client or on a Polycom Trio signed in with a skype account. We do so by dialing: 4105555555@lync.zoom.us However, on SRS v2 the dial pad only supports numeric input. Is this something we can enable, or that might be available in future updates?Solved21KViews0likes12CommentsSkype for Business messaging skype user due to 'company policy'
We can successfully add regular Skype users to our Skype for Business contacts list but when we try to communicate with them we get the following message: "This message wasn't sent to xxxx yyyy due to company policy." I've checked in the Skype for Business admin center and made sure that the public IM connectivity is set to allow communication with Skype users. And, there are no blocked domains and the default "external access" settings is configured to "On except for blocked domains". Anyone know why this would be happening?60KViews0likes13CommentsWhat is the Expected Behaviour of Interop?
Hello Community I am doing some testing for a client to try and get to a point where interop works as expected. However, repeated tests yield different results, so I am confused as what the expected experience should be. Summary Skype for Business OnPrem with Hybrid configured Chat & Meeting users in Teams Only mode SfB EV users in Teams Islands Mode When initiating a chat from the Skype client to a Teams only user we experience 2 different interop results Chat is sent from skype client and received in Teams client. The Teams user is told that the person is a Skype user and to continue their conversation link at the bottom appears. After that is clicked, the conversation moves to a Teams to Teams chat, and the Skype user gets the reply in their Teams client. The same setup scenario, but the Teams Only user does not get the "continue this conversation in Teams" link and the chat box is activated. At this point the response is received to the Skype user's Skype client with limited functionality Both times, both clients where logged in at the same time on the same code version. What is the expected experience supposed to be? Personally, I prefer scenario 1, but it seems random selection right now as to which experience is chosen. What has your experience been?1.5KViews0likes2CommentsSMS Texting through Skype for Business
We are looking for a solution to enhance communications and increase employee engagement through SMS text messaging. Can we do this through Skype for Business? I've found info on paying for text messages for consumer Skype -- is there anything available through Office 365? Would like for specific individuals and groups (e.g., HR) to have permissions to send to other individuals or groups (e.g., all employees) without opening up (and paying for) text messages between everyone in the company. Similar to a product like http://www.textrecruit.com/texthr/. Anyone have information or experience to share? Thanks.41KViews2likes9CommentsSIP 2.0 error 503 incoming from cisco CUCM
Hello Team, i have a trunk CUCM to SFB 2015 where skype can call Cisco extension but Cisco cannot call Skype extensions, i get the error 503 service unavailable on the skype server. So far i downloaded and installed the latest SFB update that did not fix the issue. here are some logs of Cisco to SFB fetch from Skype: TL_INFO(TF_PROTOCOL) [SFB\PR-VM-SFB-01]1594.3D3C::07/01/2019-11:43:13.941.00002000 (S4,SipMessage.DataLoggingHelper:sipmessage.cs(801)) [431143657] <<<<<<<<<<<<Incoming SipMessage c=[<SipTcpConnection_5291CE>], 10.10.30.23:5068<-10.10.60.250:35810 INVITE sip:820993@10.10.30.23:5068 SIP/2.0 FROM: "AMBOZOO" <sip:25006@10.10.60.250>;tag=40478~bb16990c-bb8d-474d-e339-4cb6bd7d93e7-23478979 TO: <sip:820993@10.10.30.23> CSEQ: 101 INVITE CALL-ID: ff535980-d191edc8-41b-fa3c0a0a@10.10.60.250 MAX-FORWARDS: 69 VIA: SIP/2.0/TCP 10.10.60.250:5060;branch=z9hG4bK41e3a437828 ALLOW-EVENTS: presence CONTACT: <sip:25006@10.10.60.250:5060;transport=tcp>;+u.sip!devicename.ccm.cisco.com="CSFAMBOZOO";bfcp CONTENT-LENGTH: 202 DATE: Mon, 01 Jul 2019 11:26:00 GMT EXPIRES: 180 SUPPORTED: timer,resource-priority,replaces SUPPORTED: X-cisco-srtp-fallback,X-cisco-original-called USER-AGENT: Cisco-CUCM11.0 CONTENT-TYPE: application/sdp ALLOW: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY P-ASSERTED-IDENTITY: "AMBOZOO" <sip:25006@10.10.60.250> Min-SE: 1800 Session-ID: 00001cc400105000a0001002b529e1f4;remote=00000000000000000000000000000000 Cisco-Guid: 4283652480-0000065536-0000000002-4198238730 Session-Expires: 1800 Remote-Party-ID: "AMBOZOO" <sip:25006@10.10.60.250>;party=calling;screen=yes;privacy=off v=0 o=CiscoSystemsCCM-SIP 40478 1 IN IP4 10.10.60.250 s=SIP Call c=IN IP4 10.123.123.10 t=0 0 m=audio 16386 RTP/AVP 0 101 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 ------------EndOfIncoming SipMessage TL_INFO(TF_PROTOCOL) [SFB\PR-VM-SFB-01]1594.2FE8::07/01/2019-11:43:13.942.00002001 (S4,SipMessage.DataLoggingHelper:sipmessage.cs(801)) [431143657] >>>>>>>>>>>>Outgoing SipMessage c=[<SipTcpConnection_5291CE>], 10.10.30.23:5068->10.10.60.250:35810 SIP/2.0 100 Trying FROM: "AMBOZOO"<sip:25006@10.10.60.250>;tag=40478~bb16990c-bb8d-474d-e339-4cb6bd7d93e7-23478979 TO: <sip:820993@10.10.30.23> CSEQ: 101 INVITE CALL-ID: ff535980-d191edc8-41b-fa3c0a0a@10.10.60.250 VIA: SIP/2.0/TCP 10.10.60.250:5060;branch=z9hG4bK41e3a437828 CONTENT-LENGTH: 0 ------------EndOfOutgoing SipMessage TL_INFO(TF_PROTOCOL) [SFB\PR-VM-SFB-01]1594.36B0::07/01/2019-11:43:13.953.00002005 (S4,SipMessage.DataLoggingHelper:sipmessage.cs(801)) [431143657] >>>>>>>>>>>>Outgoing SipMessage c=[<SipTcpConnection_5291CE>], 10.10.30.23:5068->10.10.60.250:35810 SIP/2.0 503 Service Unavailable FROM: "AMBOZOO"<sip:25006@10.10.60.250>;tag=40478~bb16990c-bb8d-474d-e339-4cb6bd7d93e7-23478979 TO: <sip:820993@10.10.30.23>;epid=4A4C146B07;tag=707bec76e1 CSEQ: 101 INVITE CALL-ID: ff535980-d191edc8-41b-fa3c0a0a@10.10.60.250 VIA: SIP/2.0/TCP 10.10.60.250:5060;branch=z9hG4bK41e3a437828 CONTENT-LENGTH: 0 SERVER: RTCC/6.0.0.0 MediationServer ------------EndOfOutgoing SipMessage TL_INFO(TF_PROTOCOL) [SFB\PR-VM-SFB-01]1594.3D3C::07/01/2019-11:43:14.063.0000200C (S4,SipMessage.DataLoggingHelper:sipmessage.cs(801)) [546807437] <<<<<<<<<<<<Incoming SipMessage c=[<SipTcpConnection_5291CE>], 10.10.30.23:5068<-10.10.60.250:35810 ACK sip:820993@10.10.30.23:5068 SIP/2.0 FROM: "AMBOZOO" <sip:25006@10.10.60.250>;tag=40478~bb16990c-bb8d-474d-e339-4cb6bd7d93e7-23478979 TO: <sip:820993@10.10.30.23>;epid=4A4C146B07;tag=707bec76e1 CSEQ: 101 ACK CALL-ID: ff535980-d191edc8-41b-fa3c0a0a@10.10.60.250 MAX-FORWARDS: 70 VIA: SIP/2.0/TCP 10.10.60.250:5060;branch=z9hG4bK41e3a437828 ALLOW-EVENTS: presence CONTENT-LENGTH: 0 DATE: Mon, 01 Jul 2019 11:26:00 GMT USER-AGENT: Cisco-CUCM11.0 ------------EndOfIncoming SipMessage Any help will be appreciated. thank youSolved7.1KViews0likes1CommentSFB office web app link (cipher suite)
Hi everyone, I am experiencing problem with powerpoint sharing, other function is ok, so i went to to front-end server and try to access https://serverwac.domain.com/hosting/discovery and found i am not able to browse the page with tls error. gpreult /h show the following cipher suite order TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_256_GCM_SHA384, -------------- TLS_DHE_RSA_WITH_AES_128_GCM_SHA256, -------------- TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, ---------------- TLS_DHE_DSS_WITH_AES_256_CBC_SHA256,----------- TLS_DHE_DSS_WITH_AES_128_CBC_SHA256,----------------- TLS_DHE_DSS_WITH_AES_256_CBC_SHA,--------------- TLS_DHE_DSS_WITH_AES_128_CBC_SHA,-------------------- TLS_RSA_WITH_NULL_SHA256, TLS_RSA_WITH_NULL_SHA, TLS_PSK_WITH_AES_256_GCM_SHA384, TLS_PSK_WITH_AES_128_GCM_SHA256, TLS_PSK_WITH_AES_256_CBC_SHA384, TLS_PSK_WITH_AES_128_CBC_SHA256, TLS_PSK_WITH_NULL_SHA384, TLS_PSK_WITH_NULL_SHA256 Using wireshark, the hello shows version: TLS 1.2 (0X0303) Cipher Suites Length: 14 Cipher Suites (7 suites) TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 TLS_RSA_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_AES_128_CBC_SHA The cipher order in the packet does not list everything in the group policy. I have tried to unlink the cipher hardening in group policy and it was advertising more cipher (windows default cipher) and i was able to browse the office web app link. the sfb server is running sfb 2015 cu7 and windows 2012 R2. the following update was applied https://docs.microsoft.com/en-us/windows/desktop/secauthn/tls-cipher-suites-in-windows-8-1 although some update was saying not applicable for the machine when i tried to install again. I was able to see the cipher suite listed in the microsoft link (https://docs.microsoft.com/en-us/windows/desktop/secauthn/tls-cipher-suites-in-windows-8-1) using wireshark after removing the cipher hardening policy. does anyone knows why the cipher suite in the group policy does not take effect? or what might have conflicting it? I have to get the hardened cipher suite to work with the load balanced office web app link. Thanks! Edit: I have further tried to create a new policy as in following table "Match". The idea is to get hardened cipher suites and apply it only to Windows 2012 R2. The table "Wireshark" refers to cipher suites gather from the machine without any group policy/or cipher order with Wireshark "Hello". The table "Manual cipher order" refers to the cipher order from the group policy. The table "Match" derives from "Wireshark" matches "Manual cipher order" Wireshark Manual cipher order Match TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 #N/A TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 #N/A TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 TLS_DHE_RSA_WITH_AES_128_CBC_SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 TLS_RSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_128_GCM_SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_AES_256_CBC_SHA256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 TLS_RSA_WITH_NULL_SHA256 #N/A TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_NULL_SHA #N/A TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA TLS_PSK_WITH_AES_256_GCM_SHA384 #N/A TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 TLS_PSK_WITH_AES_128_GCM_SHA256 #N/A TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 TLS_PSK_WITH_AES_256_CBC_SHA384 #N/A TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_PSK_WITH_AES_128_CBC_SHA256 #N/A TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_PSK_WITH_NULL_SHA384 #N/A TLS_RSA_WITH_3DES_EDE_CBC_SHA TLS_PSK_WITH_NULL_SHA256 #N/A TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA #N/A However with the newly created group policy from the above table "Match", wireshark shows only 3 cipher suites and the gpresult /h shows the "match" values has applied.Solved1.2KViews0likes1CommentUnable to schedule Skype meetings after mailbox migration
Hi, hoping someone can help me with an issue we are facing. We have a client with Skype for Business Server 2015, as well as mailboxes in Office 365. We have recently moved some users from their Office 365 tenant into a different tenant with a different domain. The users now sign into outlook with user@domainb.com but still sign into Skype on Prem with user@domaina.com. When they try and create a Skype meeting in their Outlook after the migration they receive an error to make sure they are signed into Outlook and Skype with the same email, which of course they are not. I have looked at various articles dealing with SIP and SMTP mismatch and they advised to set DisableEmailComparisonCheck to true. I have tried doing this both in the registry and also by creating a separate client side policy with Email check disabled and scoping it to a test user but I am still unable to create meetings. I know the policy is taking affect as if I make other changes to it, ie disabling emoticons the test user picks up those settings. Does anyone have any experience with having different SIP and SMTP addresses with S4B server 2015 and Skype client 2013/2016? Thanks Nick1.3KViews0likes2Commentsconversation history in oulook 2016
I'm experiencing a Problem with Skype for Business users, who have an addittional Exchange mail account in their Outlook. We are using the latest Outlook and also the latest Skype for Business Client (monthly channel). Our Skype for Business and on-prem Exchange Servers are patched to the latest release. The conversation history for some users gets saved in their additional Mailbox, which doesn't match the user's own UPN or Emailadress. The only way to resolve this issue I could find out, was deleting the additional Mailbox, disable the saving in the S4B Client, reboot, re-enable saving in the S4B Client, test that conversation gets saved to user's Mailbox, re-enable additional Mailbox. Does anybody have any ideas on this?9.6KViews0likes5Comments