ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Skype for Business - external connection issues

    Scheduled Pinned Locked Moved IT Discussion
    20 Posts 3 Posters 4.9k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • bbigfordB
      bbigford @Dashrender
      last edited by

      @Dashrender It would be rolled into the price we would pay for Skype for Business, much like we would have paid the rolled up cost for Lync. They charge based on the user count, all in one lump cost.

      1 Reply Last reply Reply Quote 0
      • DashrenderD
        Dashrender
        last edited by

        Oh, didn't know that SfB (or Lync) was sold as a full end to end phone solution (PBX onsite or hosted plus connectivity to the outside world (SIP trunks)).

        bbigfordB 1 Reply Last reply Reply Quote 1
        • bbigfordB
          bbigford @Dashrender
          last edited by

          @Dashrender I could be dead wrong or giving false information somewhere. Our phone solution is a Polycom system by InCom, but obviously there have to be trunks somewhere for SfB. Maybe I don't have the breadth of knowledge in SfB yet to answer your question accurately...

          1 Reply Last reply Reply Quote 0
          • DashrenderD
            Dashrender
            last edited by

            Nor do I to ask the right type of questions.

            bbigfordB 1 Reply Last reply Reply Quote 0
            • bbigfordB
              bbigford @Dashrender
              last edited by bbigford

              @Dashrender In theory, IM shouldn't have the same kind of connection as calling, so if I could even get a connection setup to IM, I could troubleshoot the calling issues afterward. SfB would process IM communication, but drop calls if improperly configured. I just don't know where to even start troubleshooting for the external connection cause everything looks good but obviously it isn't.

              1 Reply Last reply Reply Quote 0
              • DashrenderD
                Dashrender
                last edited by

                So the SfB client can't IM outside of your network?

                bbigfordB 1 Reply Last reply Reply Quote 0
                • bbigfordB
                  bbigford @Dashrender
                  last edited by

                  @Dashrender Correct. Down the road, it would be nice to use our phones and not have to VPN into the network to chat. Also being able to use SfB in place of WebEx/etc for video conferencing.

                  1 Reply Last reply Reply Quote 0
                  • bbigfordB
                    bbigford
                    last edited by

                    Here's a screenshot of the test breakdown if that helps at all...
                    0_1451951116204_test.PNG

                    1 Reply Last reply Reply Quote 0
                    • bbigfordB
                      bbigford
                      last edited by

                      It indicates that the From account on the test isn't an admin one, which it is... But still, I can't get any user to connect outside of running the test.

                      1 Reply Last reply Reply Quote 0
                      • bbigfordB
                        bbigford
                        last edited by 

                        Additional Details

                        Couldn't sign in. Error: Error Message: Not authorized to perform the requested operation, request is refused.
                        Error Type: AuthenticationException.
                        Error Code: 0.
                        Realm: .
                        Response Code: 403.
                        Response Text: Forbidden.
                        Diagnostic Header: ErrorCode=4004,Source=server.domain,Reason=Credentials provided are not authorized to act as specified from URI,authenticatedidentity=DOMAINusername
                        .
                        .
                        Elapsed Time: 386 ms.

                        1 Reply Last reply Reply Quote 0
                        • bbigfordB
                          bbigford
                          last edited by bbigford

                          I ran that with my domain admin account. If i use an account that is [email protected], I get the following (that account was used for a long time, and has the highest network credentials by far):

                          Additional Details

                          Exception details:
                          Message: Invalid Uri: parsing problem (no viable alternative): <
                          Parameter name: value
                          Type: System.ArgumentException
                          Stack trace:

                          Server stack trace:
                          at Microsoft.Rtc.Signaling.SipUriParser..ctor(String value)
                          at Microsoft.Rtc.Signaling.RealTimeAddress..ctor(String uri)
                          at Microsoft.Exchange.Tools.ExRca.Lync.TestOcsCore.DoMRASServiceRequest()
                          at Microsoft.Exchange.Tools.ExRca.Lync.TestOcsCore.Initialize()
                          at Microsoft.Exchange.Tools.ExRca.Lync.OcsSignInTest.PerformTestReally()
                          at Microsoft.Exchange.Tools.ExRca.Tests.Test.PerformTest()
                          at Microsoft.Exchange.Tools.ExRca.Tests.Test.PerformChildren()
                          at Microsoft.Exchange.Tools.ExRca.Tests.Test.PerformTest()
                          at Microsoft.Exchange.Tools.ExRca.Tests.TopLevelTest.PerformTest()
                          at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
                          at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)

                          Exception rethrown at [0]:
                          at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
                          at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
                          at Microsoft.Exchange.Tools.ExRca.Website.PerformTestAsyncDelegate.EndInvoke(IAsyncResult result)
                          at Microsoft.Exchange.Tools.ExRca.Website.TestExecutionManager.<>c__DisplayClass8.<TestCompleted>b__6()
                          at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(Action tryDelegate, Func2 filterDelegate, Action1 catchDelegate)
                          at Microsoft.Exchange.Tools.ExRca.Website.TestExecutionManager.TestCompleted(IAsyncResult asyncResult)
                          Exception details:
                          Message: Invalid Uri: parsing problem (no viable alternative): <
                          Type: Microsoft.Rtc.Internal.Sip.SipException
                          Stack trace:
                          at Microsoft.Rtc.Internal.Sip.SipUri.ParseUriString()
                          at Microsoft.Rtc.Signaling.SipUriParser..ctor(String value)

                          1 Reply Last reply Reply Quote 0
                          • 1 / 1
                          • First post
                            Last post