none
Simultaneous Ring + Lync Mobility = Double SIP Invite?

    Question

  • We've got an odd issue occuring at a client.  When users set simultaneous ring to call their cell phones and they are also logged into Lync mobility, calls to their desk phone go right to their cell voicemail.  I did a bit of investigating and can see that when they put their mobile number into the simultaneous ring settings, duplicate SIP Invites to their mobile occur from the mediation server (one of course is quickly answered by voicemail on the cell phone side).  If they simultaneously ring any other number, only a single invite occurs and the ringing works as expected.

    This doesn't seem to occur at my own office so I don't know what to make of it.  Has anyone seen this behavior?

    -Anthony

    Monday, February 13, 2012 6:45 PM

Answers

  • We've been struggling with this exact same issue and I've been banging my head against the wall trying to figure it out.  Like you, a user has sim ring set up and is running the mobile client, when someone calls, they get maybe 1 ring on their office phone before it hits the cell and then it goes to voicemail (on their cell phone).  I saw the same thing in traces as you, it looked like simring generated 2 outoing invites to the cell number.

    Something else I notcied was that when this occurred, it appeared as if their were 2 registered mobile clients for this user.

    You can use this script to get a list of registered endpoints on each front end server:

      http://blogs.technet.com/b/csps/archive/2011/03/10/list_2d00_users_2d00_and_2d00_endpoints_2d00_direct.aspx

    If you're just interested in the mobile clients, replace the '$overallrecords' at the end of the script with this:

      $overallrecords | Where-Object {$_.clientversion -like '*McxService*' -and $_.USerName} |sort-object -property username

    That will show you all of the registered mobile clients, sorted by username.

    When I saw the problem, there were 2 mobile registrations for the user who was experiencing it.  From what I could tell, 1 registration was tied to the user through our wireless network and the other was through the cell network.  i.e. if I had the user sign out of Lync mobile while connected to our wireless network, one of the registrations disappeared.  If I had them then disconnect from our wireless network, sign in and sign out of Lync while connected to the cell network, the other registration disappeared as well.

    That led me to believe that we might have something set up wrong but my understanding was that the mobile client connects through the reverse proxy so whether they are on the cell network or our internal wireless, they always come in through the same point and keep a persistent session.

    I would be really interested to know if the next time one of your users experiences this issue, whether or not you see multiple registrations as well. 

    Other than seeing multiple registrations, I can't find a way to associate those registrations with the original IP or reset one from an administrative standpoint (unless I restart the external web service on each frontend).  If anyone has tips on that, I'd greatly appreciate it.

    I also haven't been able to determine what the end user is doing to cause multiple registrations from the mobile client.  I worked with one guy in my department actually trying to make it happen and we couldn't.  We'd switch wireless on/off and go to a location with no cell service in the hopes that it'd create a duplicate registration but it didn't.  Then I noticed another guy with multiple registrations and he said all he did was go off campus for lunch and send a couple IMs from his phone.

    Wednesday, February 15, 2012 1:46 PM

All replies

  • More info... this appears to only happen if simultaneous ring was enabled first, then mobility was installed.  It's as if the simultaneous ring rule is in there twice somehow.  Turning it off or to another number and back doesn't resolve the issue.  We have found that turning off call forwarding, reinstalling the mobile client (these are all iPhones we're working with) and allowing it to set the simu-ring fixes the issue.

    Monday, February 13, 2012 7:05 PM
  • Does anyone know where the call forwarding settings are saved per user?  Somewhere in the rtc database?
    Monday, February 13, 2012 7:13 PM
  • Hi,Anthony,

    Unfortunately,the behaviour when set simulatenous ring on mobile and also log in the mobile client is by design,maybe it will be fixed in the next release but I am not sure.

    I can not tell exactly where the call forwarding setting stored,but yes it's in somewhere in the user database stored as configuration data in Lync database instance RTC ,this is why call forwarding settings will follow a user to any endpoint since the properties are defined in their database settings.

    Regards,

    Sharon


    Sharon Shen

    TechNet Community Support

    ******************************************************************************************************************************************************* 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 memb



    Wednesday, February 15, 2012 6:59 AM
  • We've been struggling with this exact same issue and I've been banging my head against the wall trying to figure it out.  Like you, a user has sim ring set up and is running the mobile client, when someone calls, they get maybe 1 ring on their office phone before it hits the cell and then it goes to voicemail (on their cell phone).  I saw the same thing in traces as you, it looked like simring generated 2 outoing invites to the cell number.

    Something else I notcied was that when this occurred, it appeared as if their were 2 registered mobile clients for this user.

    You can use this script to get a list of registered endpoints on each front end server:

      http://blogs.technet.com/b/csps/archive/2011/03/10/list_2d00_users_2d00_and_2d00_endpoints_2d00_direct.aspx

    If you're just interested in the mobile clients, replace the '$overallrecords' at the end of the script with this:

      $overallrecords | Where-Object {$_.clientversion -like '*McxService*' -and $_.USerName} |sort-object -property username

    That will show you all of the registered mobile clients, sorted by username.

    When I saw the problem, there were 2 mobile registrations for the user who was experiencing it.  From what I could tell, 1 registration was tied to the user through our wireless network and the other was through the cell network.  i.e. if I had the user sign out of Lync mobile while connected to our wireless network, one of the registrations disappeared.  If I had them then disconnect from our wireless network, sign in and sign out of Lync while connected to the cell network, the other registration disappeared as well.

    That led me to believe that we might have something set up wrong but my understanding was that the mobile client connects through the reverse proxy so whether they are on the cell network or our internal wireless, they always come in through the same point and keep a persistent session.

    I would be really interested to know if the next time one of your users experiences this issue, whether or not you see multiple registrations as well. 

    Other than seeing multiple registrations, I can't find a way to associate those registrations with the original IP or reset one from an administrative standpoint (unless I restart the external web service on each frontend).  If anyone has tips on that, I'd greatly appreciate it.

    I also haven't been able to determine what the end user is doing to cause multiple registrations from the mobile client.  I worked with one guy in my department actually trying to make it happen and we couldn't.  We'd switch wireless on/off and go to a location with no cell service in the hopes that it'd create a duplicate registration but it didn't.  Then I noticed another guy with multiple registrations and he said all he did was go off campus for lunch and send a couple IMs from his phone.

    Wednesday, February 15, 2012 1:46 PM
  • That's extremely helpful, I'm marking it as an answer as I believe that's about as close as we're going to get here.  I noticed the same oddity where it just couldn't be recreated with everyone.  Once we "fixed" it with the uninstall/disable forwarding/reinstall/let the phone enable forwarding trick we couldn't make it come back easily either (not that I spent hours trying).  I will continue to keep a record of it and if it comes back and report in this post.
    Wednesday, February 15, 2012 2:38 PM
  • We made a discovery today that leads me to believe this is a bug.  We signed in to the mobile client and set up simultaneously ring for someone on his iPhone.  We tested sim ring by calling his office number and it worked as expected.  I then had him sign in to the mobile client on an android tablet at the same time and tested sim ring.  That time, the call rang his office phone once and then went straight to his cell phone's voicemail.

    I still think it's possible that there's a configuration issue which causes our users to intermittently show up with multiple registrations for the same device as I mentioned in my last post but I think Lync should be smart enough not to send multiple SIP invites to the same external number for sim ring.

    As for where in the database Lync stores the sim ring information, I'm still at a loss.  All I could see from a SQL trace was Lync calling a stored procedure with sp_execute to update the data.  The sim ring number was buried in a huge binary variable that appeared to contain all of my contact info.  I'm not really savvy enough with SQL Profiler to easily track down what stored procedure is being called and where it's sticking that data.

    Tuesday, February 21, 2012 1:35 PM
  • I'm experiencing the same issue. The client with the issue has 2 McxService registrations in my environment as well.
    Wednesday, February 22, 2012 6:31 PM
  • I am seeing the same in my environment. Two registered RTCC connections per user on lync mobile. If i sign out of lync mobile I am left with one connection and simultaneous ring works as expected. Any update MS? I am going to run traces on my gateway to see if there are actually two calls generated. Will update with the results.<o:p></o:p>

    Thanks,

    Brian

    Wednesday, February 29, 2012 6:09 PM
  • Hi all,

    Anybody an update on this? I've got a customer that has this as well.


    Microsoft minded UC specialist - http://www.reijling.nl

    Thursday, April 12, 2012 1:11 PM
  • Not yet... but I haven't looked deeply into it recently.  I've been relying on the workaround of deleting the mobile app from the device, disabling all call forwarding, reinstalling the mobile app and letting it configure forwarding.  Have you tried this workaround at all?

    • Proposed as answer by Leonneven Friday, April 27, 2012 7:58 AM
    • Unproposed as answer by Leonneven Friday, April 27, 2012 7:58 AM
    Friday, April 13, 2012 4:44 PM
  • Hi all,

    I also did experience the same issue with double SIP invites for our mobile Lync clients. I did tried to work around this as descripted in this article but this worked for a sort amount of time, randomly for users a double invite came back.

    I did contact Microsoft on this and we came up with the following for my situation:

    It appears that these invites where caused by the use of DNS load balancing on the Lync Webservices. You must use a (hardware)load balancer to load balance reverse proxy traffic. DNS load balancing is not supported for reverse proxy traffic.

    See also: http://technet.microsoft.com/en-us/library/gg615011.aspx

    Friday, April 27, 2012 8:31 AM
  • Did you deploy a hardware load balancer after speaking with Microsoft and if so, has that solved the problem for you?  I ask because we've had a HLB in place from the start to balance web traffic and still experienced this issue.  I've considered that we may need to tweak the configuration to improve persistence but I haven't taken the time to dig into it.

    I also thought we could cause this issue if a user was signed in on 2 mobile devices (i.e. an iPhone and an iPad) but I may be remembering that wrong.

    Friday, April 27, 2012 12:04 PM
  • Hello,

    We have a HW LB in place for web traffic and still see the issue.  We use a KEMP LoadMaster 2200 which is certified by MS.  Any new info for this issue?

    Brian

    Friday, April 27, 2012 10:22 PM
  • Hi,

    No I did not deploy a HW load balancer. In my situation I just can fulfill with just one (1) DNS record for the external Webservice. I did use DNS loadbalancing only for fallback of the FE servers.

    I believe that if the mobile Lync application loses its connection for some reason it build up another connection when it's directed to the webservices on another FE server, instead of reconnecting to the excisting webservice server.  If it is directed to the excisting webservice server there is no problem.

    Thursday, May 03, 2012 7:21 PM
  • Sorry to revive an old thread, but I'm having the issue where the desk phone rings once and then goes to the cell voicemail, but this even occurs when using "dumb phones."
    Friday, September 07, 2012 3:10 PM
  • I don't remember for certain now but it should be easy enough to check... I think we sometimes experienced this if the cell phone was in a situation (e.g. no signal, turned off) where the carrier immediately routed the call to voicemail.
    Friday, September 07, 2012 5:04 PM
  • I was holding the cell phone that I tried to get to simultaneous ring.  Full signal, definitely powered on.  I don't understand what's going on here.
    Friday, September 07, 2012 6:45 PM
  • I believe I just resolved this issue using information in the link Leonneven provided: http://technet.microsoft.com/en-us/library/gg615011.aspx.

    We had cookie-based persistence configured incorrectly on our F5 load balancer. To resolve, I created a new cookie persistence profile based on the default cookie persistence profile. The new profile was configured like so:

    • Persistence Type: Cookie
    • Parent Profile: cookie
    • Cookie Method: HTTP Cookie Insert
    • Cookie Name: MS-WSMAN
    • Expiration: 3,650 days

    You may have to adapt for your HLB of choice.

    As B. Webster described, the problem was occurring when simultaneous ring was configured to forward calls to a phone with the Lync Mobility Client installed, and the Lync Mobility Client had multiple registrations on the FE pool. I was able to reproduce the problem by signing into Lync Mobility Client on an Android phone connecting over the carrier's network with WiFi off, then turning WiFi on and connecting to a wireless network. The Lync Mobility Client dropped offline briefly, then signed in again. At this point, multiple registrations were visible when executing the script in this article linked above by B. Webster:

    http://blogs.technet.com/b/csps/archive/2011/03/10/list_2d00_users_2d00_and_2d00_endpoints_2d00_direct.aspx.

    • Edited by R. Derickson Thursday, September 27, 2012 6:59 PM Changed expiration from "Session" to "3,650 days."
    Wednesday, September 26, 2012 8:42 PM
  • This type of issue is observed if there are multiple endpoints registered for the same client for some reasons.

    Generally this might happen if Cookie persistence is not correctly on the Hardware Load Balancer.

    We should ensure that the Hardware Load Balancer is configured as per the requirements.

    http://technet.microsoft.com/en-us/library/gg615011.aspx.

    The HTTP traffic for web services require HLB for load balancing.

    If you are using DNS load balancing and do not want to use HLB for HTTP traffic.... you need to override the “Internal Web Services”  FQDN and point it to one of the Front End servers in the pool.

    And on the Reverse Proxy also you need to point the rule to one FE server rather than pointing it to the Pool FQDN.  

    The PS script in the following article  is a good tool to determine if there are multiple endpoints registered.

    http://blogs.technet.com/b/csps/archive/2011/03/10/list_2d00_users_2d00_and_2d00_endpoints_2d00_direct.aspx 

    -Santosh  

    Wednesday, March 20, 2013 11:01 AM
  • No HLB or load balancing in the case I started with above, that was a simple standard edition server.  I haven't tested if this is still an issue, but I haven't heard of anyone having the issue since then so I imagine it was taken care of in some release or update.   I'll watch for that in my HLB environments as well.

    Good script though.  Thanks!

    Wednesday, March 20, 2013 2:25 PM
  • great info , Bill , thanks

    PS - if your running that script against a 2013 mobility deployment use this syntax..

    $overallrecords | Where-Object {$_.clientversion -like '*ucwa*' -and $_.USerName} |sort-object -property username



    Thursday, May 16, 2013 9:08 PM