Last week I was setting up Lync 2013 with Remote Call Control to a Mitel Live Business Gateway(LBG).
I expected not much had changed from Lync 2010, and the lack for any 2013 procedures took us the 2010 path.
After configuring the Lync environment to talk against the Mitel LBG, surprised I was to see no traffic at all was arriving at the LBG.
Going over the configuration several times and trying a few other things, I finally opened snooper to see what was happening.
The logs showed two interesting pieces of information that caught my attention:
SIPPROXY_E_CONNECTION_MISSING_TLS_TARGET
X.X.X.X is not a local IP
After trying my search karma I quickly found that I wasn't the only one facing this issue, but there wasn't any solution to the issue published online.
So digging further I reached the blogpost of Terence Luk which set me in the right direction, after configuring the identity on the staticroute RCC started working
So the solution to make RCC from Lync 2013 to a Mitel LBG work was to create the static route as following from the Lync command shell.
New-CsStaticRoutingConfiguration -Identity service:Registrar:lyncpool.domain.local
$TLSRoute = New-CsStaticRoute -TLSRoute -Destination lbg01.domain.local -Port 5061 -UseDefaultCertificate $true -MatchUri *.lbg01.domain.local
Set-CsStaticRoutingConfiguration -Identity service:Registrar:lyncpool.domain.local -Route @{Add=$TLSRoute}
Watch my blog for a complete configuration guide of the Mitel LBG together with Lync 2013 RCC