locked
Lync Private Line not working RRS feed

  • Question

  • Hello,

    if I create a Response Group in Lync 2010 with telephonenumber eg +3211220011 I can make it work and connect to it .

    But if I would assign a telURI or a Private tel uri to a user I even don't ever get connected to the LYNC server. When I dial the number from my cellphone it just rêplies the network is not available.

    Is there something I need to activate to use the teluri or privatelines of a Enterprise enabled user ??

     

    Sunday, December 16, 2012 10:37 AM

Answers

  • None of the following features are available with a private telephone line: call forwarding, team call, delegation, team ring, and Response Group application. So you can’t assign a private line to response group.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    • Proposed as answer by Lisa.zheng Wednesday, January 2, 2013 9:18 AM
    • Marked as answer by Lisa.zheng Thursday, January 3, 2013 2:04 AM
    Tuesday, December 18, 2012 10:33 AM

All replies

  • If Response Groups are working then your basic voice infrastructure should be working. What this means is that if you assign a user a lineuri and enable them for Enterprise Voice then it should work. The steps are basic but I would double check that the user is configured correctly. Then capture the S4 log from the Mediation Server to see if you can find out why the inbound call is failing.
    Monday, December 17, 2012 12:42 AM
  • Well then I see in the log :

    TL_INFO(TF_PROTOCOL) [1]1520.3C68::12/17/2012-10:52:59.964.002058f9 (S4,SipMessage.DataLoggingHelper:sipmessage.cs(686))[2624742757]
    <<<<<<<<<<<<Incoming SipMessage c=[<SipTlsConnection_2226649>], 192.168.1.8:50193<-192.168.1.8:5061
    SIP/2.0 404 Not Found
    FROM: "32475888888"<sip:32475888888;phone-context=SiteHa@domein.be;user=phone>;epid=703FC00DFB;tag=dbbda5c23
    TO: <sip:3211220011;phone-context=SiteHa@domein.be;user=phone>;tag=F4BC444941909E4775FD6679BD773CAA
    CSEQ: 69521 INVITE
    CALL-ID: d40214c4-506e-4b76-8b9d-154d0f8ac00f
    VIA: SIP/2.0/TLS 192.168.1.8:50193;branch=z9hG4bKd1ca1a3e;ms-received-port=50193;ms-received-cid=27C7F00
    CONTENT-LENGTH: 0
    SERVER: RTC/4.0
    ms-diagnostics: 1003;reason="User does not exist";TargetUri="+3211220011@domein.be";source="LYNCFE01.office.local"
    ------------EndOfIncoming SipMessage

    Monday, December 17, 2012 10:57 AM
  • Well if I look at your log the number you tried to reach: +3211220011 does not exist. e.q the number or in this case user.
    Did you assign this number to a user or to the respone group?

    Monday, December 17, 2012 12:40 PM
  • This was assigned to a user LineURI AND PrivateLine, and in AD as well.

    Now I changed the number for the user to 12 and created a ResponseGroup for the number 11 and I get a ambigious error 485 on the ResponseGroup when trying to call. Allthough I don't even see it when doing a ADFIND

    What the hell

    Monday, December 17, 2012 12:48 PM
  • Remember if you change something in response group it can take some time to replicate. This could be the case when you get this error.
    Back to the line uri, did you assign the same number for one user as a LineUri and PrivateLine? If so, change this to only the LineUri and see if you are able to call the user. Remeber the replication within Lync ;)
    It could be that Lync has troubles with a number that is assigned as LineUri and PrivateLine (not sure but sounds like it)

    Monday, December 17, 2012 12:53 PM
  • Well I changed the numbers 2 hours ago, so the RGS should not see it qnymore I would guess. But I'll wait for that.

    For the LineURI , I had first used only the LINEURI and that did not work. It was a day later or so that I added the privateline to it. So that is not the problem.

    Can it be the problem that it was not entered in AD at first that it might not have worked ??

    Monday, December 17, 2012 1:03 PM
  • Well depending on you setup, after 2 hours it should be in sync.

    Yes, that could indeed be the case that the number was not entered in the AD (assuming you have a gateway that looks inside your AD)

    So, lets keep it one thing at the time. How is this user configured at the moment? LineUri filled in the way it should in Lync, filled in the way it should in the AD? Number is not assigned to any other user not assigned as a private line to or the same user?
    If so, test it again if you call the number. If it fails, check you reporting or do a new trace of this number/user.

    BTW, is this problem with on user or in your entire Lync enviorment?
    For you response group, check if the correct number is indeed assigned to the group. Also double check this with Lync command shell by calling up the application endpoints. The response group should be there with the assigned number.

    Monday, December 17, 2012 1:17 PM
  • None of the following features are available with a private telephone line: call forwarding, team call, delegation, team ring, and Response Group application. So you can’t assign a private line to response group.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    • Proposed as answer by Lisa.zheng Wednesday, January 2, 2013 9:18 AM
    • Marked as answer by Lisa.zheng Thursday, January 3, 2013 2:04 AM
    Tuesday, December 18, 2012 10:33 AM