Wednesday, March 14, 2012 3:29 PM
We have a Lync deployment including external user access that is configured to use remote call control. We have a dedicated sip trunk to our Mitel 3300 which we are using for the dial-in conferencing feature, but we notice that when internal Lync users access online meetings they are showing up twice - as a presenter and as a guest. It seems as though Lync isn't associating our internal numbers with the relevant user when dialing into the conference. We are also unable to use the Call feature from the meeting pop-up to dial our extensions - which I guess is all part of the same problem. We have one Test user configured for Enterprise voice and with this everything works as it should, but converting all users just isn't an option for us. Is this one of the downfalls of using RCC or can it be made to work?
Alternatively if it isn't possible we were hoping to hide the "Call" options from within the meeting - it will only confuse users as it doesn't work. If I disable Audio/Video from within the conferencing settings in control panel, this tab is then greyed out - but it then removes the conferencing numbers from the Online Meeting invitations!
Can anyone make any suggestions as how best to move forward with this?
Many thanks in advance.
- Edited by msnoakesy Wednesday, March 14, 2012 3:31 PM spelling mistakes
Friday, March 16, 2012 10:19 AMModerator
Have you assigne the Linde server URI to the users?
To enable a user for remote call control, a user must have both a Line URI and a Line Server URI. As described in Deployment Tasks for Remote Call Control, ensure that you use the syntax that is required by the gateway for these settings.Ensure that the domain in the Line Server URI is the same as the destination domain you specified in the MatchUri parameter when configuring the static route to the gateway.Details you can check http://technet.microsoft.com/en-us/library/gg615048.aspx
Another more information about deploying RCC for your reference.
TechNet Community Support
Friday, March 16, 2012 11:24 AM
Not being able to use the Call feature from within a meeting is a limitation of RCC. The Lync user needs to be Enterprise Voice enabled to call out to their mobile/PBX number from a meeting.
Combining RCC with dial-in conferencing is a complex scenario because dial-in conferencing for Lync users is meant to be used with Enterprise Voice. The cleanest solution here generally is to have the RCC users dial into the conferencing number on Lync and provide the conference ID/PIN.
Justin Morris | Consultant | Modality Systems
Lync Blog - www.justin-morris.net
If this post has been useful please click the green arrow to the left or click "Propose as answer"
Friday, March 16, 2012 11:53 AM
Thanks for getting back to me. Everything in our setup seems to be as it should be - RCC works fine apart from the conferencing issues that I mentioned. I have also now noticed a related issue which is REALLY causing us a headache. All clients have been configured within the Telephone option to not use audio for conferencing. This works fine for scheduled meetings, but if we use the Meet Now feature, the user that is invited to the meeting automatically has the conference bridge try to dial their extension. This obviously fails and then disconnects the invited user from the meeting. The user that sets up the Meet Now doesn't get the call back - just the invited user. This is driving me crazy!
Have you heard of this before or perhaps have any suggestions?
Friday, March 16, 2012 11:55 AM
We are starting to realise the limitations of RCC. I replied to Sharon, who was also kind enough to offer advice, about another problem we have noticed. If you have any suggestions regarding that it would be great to hear back from you again!
Monday, March 19, 2012 5:34 PM
have you applied the latest CU5 Hotfix, because it enabled RCC Vidoe conferencing.
regards Holger Technical Specialist UC
Thursday, March 22, 2012 4:50 PM
Yes we have applied it. Glad Microsoft have finally enabled this feature - it was a long time coming!
Monday, April 02, 2012 7:32 AMModerator
Did you set up a TCP connection between your Front End Server and the Mitel 3300?
Some remote call control scenarios require a TCP connection between the Front End Server or Director and the PBX. Although Lync Server 2010 no longer uses TCP port 5060, during remote call control deployment you create a trusted server configuration, which associates the RCC Line Server FQDN with the TCP port that the Front End Server or Director will use to connect to the PBX system. For details, see the New-CsTrustedApplicationComputer cmdlet in the Lync Server Management Shell documentation.
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.
Sunday, May 13, 2012 9:47 PM
Did you have to do anything special to get the Lync front end pool server to pick up calls from the Mitel when people dial in to conferences from the PSTN? We have RCC with the Mitel 3300 as well (which works well) and a SIP trunk set up for conferencing. Users can join a conference by getting the server to dial out (like joining from a mobile client), but when I try to dial into a conference using the number configured the front end doesn't pick it up. I can see the SIP invite arriving at the front end with the correct SIP URI for the configured dialin number, but then it tries to route the call to the edge server. The dialin number is configured on the right pool with an associated region on the right dial plan, so I can't find what the problem is.
Yours is the only thread I've seen in conferencing with RCC and a Mitel 3300 configured, so I though I'd pick your brain. Hope that's OK.