Hello All,<o:p></o:p>

situation: three Lync 2010 central sites (pool plus
directors) and one VCS Lync gateway (two VCS clustered together).<o:p></o:p>

Having said that a part from slightly changing what
said in CISCO literature (configuring pool FQDN in VSC Lync gateway rather than
the director) everything is running fine.<o:p></o:p>

The problem arose when the customer introduced a SBA
in the configuration. Users homed on it are not able to enjoy the integration
features (basically video calls from Lync clients and Tandberg stations do not work).

Can you please advise on the above?

Thank you in advance

beppe

Use Snooper to trace the issue: http://blogs.technet.com/b/nexthop/archive/2011/01/17/microsoft-lync-server-2010-resource-kit-tool-snooper.aspx

Or the Lync Monitoring Reports: http://www.microsoft.com/en-ca/download/details.aspx?id=8207

Once you have the sip error message, it will be easier to troubleshoot. 

Hello Michael,

error log is quite vague

04/28/2013|05:50:14.427 F58:F5C INFO  :: Data Received - 195.68.79.115:443 (To Local Address: 192.168.1.11:51038) 933 bytes:

04/28/2013|05:50:14.427 F58:F5C INFO  :: SIP/2.0 403 Forbidden

ms-user-logon-data

: RemoteUser

Authentication-Info

: TLS-DSK qop="auth", opaque="F7400E1E", srand="04D08FB0", snum="227", rspauth="3973379f551073e0dee64a0bb16029a555dd8e0c", targetname="LyncDIRLU1.global.sys", realm="SIP Communications Service", version=4

Via

: SIP/2.0/TLS 192.168.1.11:51038;received=109.214.195.106;ms-received-port=51038;ms-received-cid=4CD6F00

Call-ID

: c1c2cd9deb854ec0aea5de7e5b4f5a3c

CSeq

: 1 SUBSCRIBE

From

: "SURNAME name" <sip:name.surname@sipdomain.org>;tag=4d71bb0d17;epid=95a505c526

To

: <sip:8267368@videosipdomain.org>;tag=67be8543cd326c63

Allow

: INVITE,ACK,BYE,CANCEL,INFO,OPTIONS,REFER,SUBSCRIBE,NOTIFY

Server

: TANDBERG/4352 (X7.1-b2bua-1.0)

Content-Length

: 0

ms-diagnostics

: 1033;reason="Previous hop server component did not report diagnostic information";Domain="videosipdomain.org";PeerServer="vcs-lync.contoso.it";source="SBARI1.global.sys"

04/28/2013|05:50:14.427 F58:F5C INFO  :: End of Data Received - 195.68.79.115:443 (To Local Address: 192.168.1.11:51038) 933 bytes

As a matter of fact I'd like to know if somebody got it working when SBAs are involved (as said no problem with normal pools).

Cheeers

beppe

Are you registering the Cisco Tandberg to the SBA or the backup registrar (Full Front End)? An SBA only has Mediation and Registrar components and leverages the Data MCU from the backup registrar. 

Users homed to an SBA should be able to use a Tandberg registered to the Front End, is this not the case?

Hi Michael,

i see exact the same behaviour. Did you solved your problems for calls coming from SBS/SBS regsitered Clients ?!

Regards Timo

Hi all,

Solution is easy. Not only the server hosting the trusted appliaction must be entered under CISCO VSC - B2BUA trusted hosts configuration, every branch server using the trusted application to route traffic to VCS must be entered here.

Regards Timo