Unable to establish AV call with Lync server 2013 from internal to external remote users

Hi,
Instant messaging is working fine
When trying to video call from the internal Lan to an remote external user Video call connects for 10 seconds and then drops.
This also happens between federated sites when we initiate the call
Internal to internal video call works
External to external video works
Please see logs below, can anyone advise on this issue or point me in the direction
The logs show trying to make a video call from user on the same domain, one user on the internal network and the other user is external
08/08/2014|11:25:44.523 4024:4344 INFO :: End of Sending Packet - 192.168.10.4:5061 (From Local Address: 192.168.11.77:62287) 1082 bytes
08/08/2014|11:25:44.523 4024:4344 TRACE :: CSIPCompression::CompressSendBuffer after compression, BytesLeft = 1082, BytesProcessed = 1082, cbDataCompressed = 465, psCompressedData = 16A01FD8
08/08/2014|11:25:44.523 4024:4344 TRACE :: - encrypted buffer length: 533 bytes. First 8 bytes:
08/08/2014|11:25:44.523 4024:4344 TRACE :: 17 03 03 02 10 D0 D8 3D :.....ÐØ=
08/08/2014|11:25:44.523 4024:4344 TRACE :: CSIPTransportLayerSecurity::Send after encryption, BytesLeft = 465, BytesProcessed = 465, cbEncryptedBufSize = 533, spEncryptedBuff = 0C2B13C8
08/08/2014|11:25:44.523 4024:4344 TRACE :: CSIPAsyncSocket::Send this 07B3B000, sending pbSendBuf 0C2B13C8, dwSendBufSize = 533
08/08/2014|11:25:44.523 4024:4344 TRACE :: CSIPAsyncSocket::SendHelper - [0x07B3B000]
08/08/2014|11:25:44.523 4024:4344 TRACE :: CAsyncSocketWin32::Send this 0C47D5A0, pbSendBuf 0C2B13C8, dwSendBufSize = 533, dwBytesSent = 533
08/08/2014|11:25:44.523 4024:4344 INFO :: REGISTER_CONTEXT(c554a20) SetAndNotify Recv(2) at State (1)
08/08/2014|11:25:44.523 4024:4344 INFO :: REGISTER_CONTEXT:State (1) => (2)
08/08/2014|11:25:44.523 4024:4344 INFO :: UCCP:NegotiatedAuthProt0x8
08/08/2014|11:25:44.523 4024:4344 INFO :: Function: CUccPlatform::GetMetricsDataPoints
08/08/2014|11:25:44.523 4024:4344 ERROR :: Failure condition: 'm_spMediaManage == NULL'
08/08/2014|11:25:44.594 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x07B3B008]
08/08/2014|11:25:44.594 4024:4344 TRACE :: SECURE_SOCKET: decrypting buffer size: 543 (first 8):
08/08/2014|11:25:44.594 4024:4344 TRACE :: 17 03 03 00 E0 C4 48 8E :....àÄHŽ
08/08/2014|11:25:44.594 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C3DC610]
08/08/2014|11:25:44.594 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C2B5E68]
08/08/2014|11:25:44.594 4024:4344 INFO :: Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 662 bytes:
08/08/2014|11:25:44.594 4024:4344 INFO :: SIP/2.0 200 OK
Contact: <sip:PMDLONLYC01.int.*******.com:5061;transport=tls>
Proxy-Authentication-Info: Kerberos qop="auth", opaque="DC934C0A", srand="CEA1D9C7", snum="34", rspauth="040401ffffffffff000000000000000008fa065605ec8ffed4978ee2", targetname="sip/PMDLONLYC01.int.*******.com",
realm="SIP Communications Service", version=4
From: "Administrator"<sip:*****@*******.com>;tag=e56751f845;epid=6969679f0b
To: <sip:*****@*******.com>;tag=EB010080
Call-ID: aa4c7843a0c14678a03acc30a615c81b
CSeq: 2 SUBSCRIBE
Via: SIP/2.0/TLS 192.168.11.77:62287;ms-received-port=62287;ms-received-cid=13CB00
Expires: 0
Content-Length: 0
08/08/2014|11:25:44.594 4024:4344 INFO :: End of Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 662 bytes
08/08/2014|11:25:44.594 4024:4344 TRACE :: CSIPMessageCollator::AsyncProcessSipMsg - [0x0C4826E0]
08/08/2014|11:25:44.594 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C4826E0]
08/08/2014|11:25:44.594 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C484940]
08/08/2014|11:25:44.594 4024:4344 TRACE :: SECURE_SOCKET: decrypting buffer size: 314 (first 8):
08/08/2014|11:25:44.594 4024:4344 TRACE :: 17 03 03 00 B0 42 E2 01 :....°Bâ.
08/08/2014|11:25:44.594 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C3DC610]
08/08/2014|11:25:44.595 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C2B5E68]
08/08/2014|11:25:44.595 4024:4344 INFO :: Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 662 bytes:
08/08/2014|11:25:44.595 4024:4344 INFO :: SIP/2.0 200 OK
Contact: <sip:PMDLONLYC01.int.*******.com:5061;transport=tls>
Proxy-Authentication-Info: Kerberos qop="auth", opaque="DC934C0A", srand="A79E32E6", snum="35", rspauth="040401ffffffffff0000000000000000435392b30686e91dd20b3120", targetname="sip/PMDLONLYC01.int.*******.com",
realm="SIP Communications Service", version=4
From: "Administrator"<sip:*****@*******.com>;tag=457d67e5ba;epid=6969679f0b
To: <sip:*****@*******.com>;tag=3D631C5A
Call-ID: 7666f05a981c4eb28c8bd44d497382a2
CSeq: 2 SUBSCRIBE
Via: SIP/2.0/TLS 192.168.11.77:62287;ms-received-port=62287;ms-received-cid=13CB00
Expires: 0
Content-Length: 0
08/08/2014|11:25:44.595 4024:4344 INFO :: End of Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 662 bytes
08/08/2014|11:25:44.595 4024:4344 TRACE :: CSIPMessageCollator::AsyncProcessSipMsg - [0x0C4826E0]
08/08/2014|11:25:44.595 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C4826E0]
08/08/2014|11:25:44.595 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C484940]
08/08/2014|11:25:44.595 4024:4344 TRACE :: SECURE_SOCKET: decrypting buffer size: 133 (first 8):
08/08/2014|11:25:44.595 4024:4344 TRACE :: 17 03 03 00 80 46 FC D6 :....€FüÖ
08/08/2014|11:25:44.595 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C3DC610]
08/08/2014|11:25:44.595 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C2B5E68]
08/08/2014|11:25:44.595 4024:4344 INFO :: Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 662 bytes:
08/08/2014|11:25:44.595 4024:4344 INFO :: SIP/2.0 200 OK
Contact: <sip:PMDLONLYC01.int.*******.com:5061;transport=tls>
Proxy-Authentication-Info: Kerberos qop="auth", opaque="DC934C0A", srand="8FB2392C", snum="36", rspauth="040401ffffffffff00000000000000005c89df75c789bd815f2c87c7", targetname="sip/PMDLONLYC01.int.*******.com",
realm="SIP Communications Service", version=4
From: "Administrator"<sip:*****@*******.com>;tag=b87f3eb341;epid=6969679f0b
To: <sip:*****@*******.com>;tag=447B0080
Call-ID: 78fff0c6673c4c209914ba91221e7a71
CSeq: 3 SUBSCRIBE
Via: SIP/2.0/TLS 192.168.11.77:62287;ms-received-port=62287;ms-received-cid=13CB00
Expires: 0
Content-Length: 0
08/08/2014|11:25:44.595 4024:4344 INFO :: End of Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 662 bytes
08/08/2014|11:25:44.595 4024:4344 TRACE :: CSIPMessageCollator::AsyncProcessSipMsg - [0x0C4826E0]
08/08/2014|11:25:44.595 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C4826E0]
08/08/2014|11:25:44.595 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C484940]
08/08/2014|11:25:44.596 4024:4344 INFO :: CUccLogicalSubscription::~CUccLogicalSubscription [0C3DCE28] dtor
08/08/2014|11:25:44.597 4024:4344 INFO :: CUccLogicalSubscription::~CUccLogicalSubscription [0C3DCEC8] dtor
08/08/2014|11:25:44.597 4024:4344 INFO :: CUccLogicalSubscription::~CUccLogicalSubscription [0C3DCC48] dtor
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [sourcenetwork] has no context, this 0C47E850
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [services] has no context, this 0C47E850
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [state] has no context, this 0C47E850
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [note] has no context, this 0C47E850
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [calendarData] has no context, this 0C47E850
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [sourcenetwork] has no context, this 0C47E300
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [note] has no context, this 0C47E300
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [sourcenetwork] has no context, this 07B818F0
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [services] has no context, this 07B818F0
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [state] has no context, this 07B818F0
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [note] has no context, this 07B818F0
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [calendarData] has no context, this 07B818F0
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [sourcenetwork] has no context, this 0C47E740
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [services] has no context, this 0C47E740
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [state] has no context, this 0C47E740
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [note] has no context, this 0C47E740
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [calendarData] has no context, this 0C47E740
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [sourcenetwork] has no context, this 0C47E6B8
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [services] has no context, this 0C47E6B8
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [state] has no context, this 0C47E6B8
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [note] has no context, this 0C47E6B8
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [calendarData] has no context, this 0C47E6B8
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [sourcenetwork] has no context, this 0C47EAF8
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [services] has no context, this 0C47EAF8
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [state] has no context, this 0C47EAF8
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [note] has no context, this 0C47EAF8
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [calendarData] has no context, this 0C47EAF8
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [sourcenetwork] has no context, this 0C51B0C8
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [services] has no context, this 0C51B0C8
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [state] has no context, this 0C51B0C8
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [contactCard] has no context, this 0C51B0C8
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [note] has no context, this 0C51B0C8
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [calendarData] has no context, this 0C51B0C8
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [sourcenetwork] has no context, this 0C47E960
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [services] has no context, this 0C47E960
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [state] has no context, this 0C47E960
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [note] has no context, this 0C47E960
08/08/2014|11:25:44.597 4024:4344 WARN :: CUccCategoryManager::RemoveCategory category [calendarData] has no context, this 0C47E960
08/08/2014|11:25:44.597 4024:4344 INFO :: CUccLogicalSubscription::~CUccLogicalSubscription [0C3DCCE8] dtor
08/08/2014|11:25:44.597 4024:4344 INFO :: ~Out trxn corr-id (18680A38)
08/08/2014|11:25:44.601 4024:4344 TRACE :: verified buffer: <Kerberos><CEA1D9C7><34><SIP Communications Service><sip/PMDLONLYC01.int.*******.com><aa4c7843a0c14678a03acc30a615c81b><2><SUBSCRIBE><sip:*****@*******.com><e56751f845><sip:*****@*******.com><EB010080><><><0><200>-length-238.
signature:040401ffffffffff000000000000000008fa065605ec8ffed4978ee2
08/08/2014|11:25:44.601 4024:4344 INFO :: Trxn corr-id (184AD1C8), SIP msg corr-id (b7eb295)
08/08/2014|11:25:44.601 4024:4344 INFO :: ~Out trxn corr-id (184AD1C8)
08/08/2014|11:25:44.601 4024:4344 TRACE :: verified buffer: <Kerberos><A79E32E6><35><SIP Communications Service><sip/PMDLONLYC01.int.*******.com><7666f05a981c4eb28c8bd44d497382a2><2><SUBSCRIBE><sip:*****@*******.com><457d67e5ba><sip:*****@*******.com><3D631C5A><><><0><200>-length-238.
signature:040401ffffffffff0000000000000000435392b30686e91dd20b3120
08/08/2014|11:25:44.601 4024:4344 INFO :: Trxn corr-id (184AD2E0), SIP msg corr-id (e46ab49b)
08/08/2014|11:25:44.601 4024:4344 INFO :: ~Out trxn corr-id (184AD2E0)
08/08/2014|11:25:44.601 4024:4344 TRACE :: verified buffer: <Kerberos><8FB2392C><36><SIP Communications Service><sip/PMDLONLYC01.int.*******.com><78fff0c6673c4c209914ba91221e7a71><3><SUBSCRIBE><sip:*****@*******.com><b87f3eb341><sip:*****@*******.com><447B0080><><><0><200>-length-238.
signature:040401ffffffffff00000000000000005c89df75c789bd815f2c87c7
08/08/2014|11:25:44.601 4024:4344 INFO :: Trxn corr-id (186E42C8), SIP msg corr-id (b03cc2c3)
08/08/2014|11:25:44.601 4024:4344 INFO :: ~Out trxn corr-id (186E42C8)
08/08/2014|11:25:44.757 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x07B3B008]
08/08/2014|11:25:44.757 4024:4344 TRACE :: SECURE_SOCKET: decrypting buffer size: 373 (first 8):
08/08/2014|11:25:44.757 4024:4344 TRACE :: 17 03 03 01 70 6D 6F B0 :....pmo°
08/08/2014|11:25:44.757 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C3DC610]
08/08/2014|11:25:44.757 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C2B5E68]
08/08/2014|11:25:44.757 4024:4344 INFO :: Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 959 bytes:
08/08/2014|11:25:44.757 4024:4344 INFO :: SIP/2.0 200 OK
Proxy-Authentication-Info: Kerberos qop="auth", opaque="DC934C0A", srand="FBA1D2E0", snum="37", rspauth="040401ffffffffff00000000000000009dbeae96bc6990dd02bfb9bd", targetname="sip/PMDLONLYC01.int.*******.com",
realm="SIP Communications Service", version=4
From: "Administrator"<sip:*****@*******.com>;tag=50091c6b22;epid=6969679f0b
To: <sip:*****@*******.com>;tag=AC6EA9B1891BDC84CB8DED81E89D55FF
Call-ID: 6f1ec22d6c96481093ebcdd126f5b255
CSeq: 3 REGISTER
Via: SIP/2.0/TLS 192.168.11.77:62287;ms-received-port=62287;ms-received-cid=13CB00
Expires: 0
Allow-Events: vnd-microsoft-provisioning,vnd-microsoft-roaming-contacts,vnd-microsoft-roaming-ACL,presence,presence.wpending,vnd-microsoft-roaming-self,vnd-microsoft-provisioning-v2
Supported: adhoclist
Server: RTC/5.0
Supported: msrtc-event-categories
Supported: ms-keepalive-deregister
Supported: ms-userservices-state-notification
Content-Length: 0
08/08/2014|11:25:44.757 4024:4344 INFO :: End of Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 959 bytes
08/08/2014|11:25:44.757 4024:4344 TRACE :: CSIPMessageCollator::AsyncProcessSipMsg - [0x0C4826E0]
08/08/2014|11:25:44.757 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C4826E0]
08/08/2014|11:25:44.757 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C484940]
08/08/2014|11:25:44.758 4024:4344 TRACE :: verified buffer: <Kerberos><FBA1D2E0><37><SIP Communications Service><sip/PMDLONLYC01.int.*******.com><6f1ec22d6c96481093ebcdd126f5b255><3><REGISTER><sip:*****@*******.com><50091c6b22><sip:*****@*******.com><AC6EA9B1891BDC84CB8DED81E89D55FF><><><0><200>-length-261.
signature:040401ffffffffff00000000000000009dbeae96bc6990dd02bfb9bd
08/08/2014|11:25:44.758 4024:4344 INFO :: Trxn corr-id (0C2E3618), SIP msg corr-id (67f10dc5)
08/08/2014|11:25:44.758 4024:4344 INFO :: REGISTER_CONTEXT(c554a20) SetAndNotify Recv(3) at State (2)
08/08/2014|11:25:44.758 4024:4344 INFO :: REGISTER_CONTEXT:State (2) => (3)
08/08/2014|11:25:44.758 4024:4344 INFO :: SIP_REGISTER:State (3) => (0)
08/08/2014|11:25:44.758 4024:4344 INFO :: UCCP:NegotiatedAuthProt0x8
08/08/2014|11:25:44.758 4024:4344 TRACE :: CUccServerEndpoint::UpdateEndpointState - Update state from 3 to 4. Status 0. Status text (null).
08/08/2014|11:25:44.758 4024:4344 INFO :: CUccDnsResolverManager::Stop MR-INFO - [05026010] DNS resolver manager stopped
08/08/2014|11:25:44.758 4024:4344 TRACE :: OUTGOING_REGISTER_TRANSACTION::ProcessSuccessfulResponse received 200 UnRegistration SUCCEEDED
08/08/2014|11:25:44.758 4024:4344 INFO :: ~Out trxn corr-id (0C2E3618)
08/08/2014|11:25:44.758 4024:4344 INFO :: CUccPlatform::WriteStreamToLog:
08/08/2014|11:25:44.758 4024:4344 INFO :: <?xml version="1.0" encoding="UTF-8"?>
<root>
<Login>
    <Info><![CDATA[Executing wws method with windows auth auth, asyncContext=16C3E478,
context: WebRequest context@ :415272512
MethodType:10
ExecutionComplete? :1
Callback@ :07AB55A4
AsyncHResult:3d0000
TargetUri:https://owa.lon.*******.com/EWS/Exchange.asmx
.]]></Info>
    <Info><![CDATA[Logon success state 1 reported by user id=EWS (adjusted=EWS) on CManagedCredential[DEFAULT this=01B6C988]]]></Info>
    <ExecuteWithWindowsOrNoAuthInternal>
      <SequenceID>1.1.1</SequenceID>
      <hr>0x0</hr>
    </ExecuteWithWindowsOrNoAuthInternal>
    <SequenceID>1.1</SequenceID>
    <hr>0x0</hr>
</Login>
</root>
08/08/2014|11:25:44.974 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x07B3B008]
08/08/2014|11:25:44.974 4024:4344 TRACE :: SECURE_SOCKET: decrypting buffer size: 1125 (first 8):
08/08/2014|11:25:44.974 4024:4344 TRACE :: 17 03 03 04 60 1A 0C FC :....`..ü
08/08/2014|11:25:44.974 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C3DC610]
08/08/2014|11:25:44.974 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C2B5E68]
08/08/2014|11:25:44.974 4024:4344 INFO :: Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 1891 bytes:
08/08/2014|11:25:44.974 4024:4344 INFO :: SIP/2.0 200 OK
Proxy-Authentication-Info: Kerberos qop="auth", opaque="DC934C0A", srand="4C70707C", snum="38", rspauth="040401ffffffffff000000000000000023304d3690145c9d580a26a5", targetname="sip/PMDLONLYC01.int.*******.com",
realm="SIP Communications Service", version=4
Contact: <sip:LyncSG.dymonasia.com:5061;transport=tls>
From: <sip:*****@*******.com>;tag=4c49873a8c;epid=6969679f0b
To: <sip:[email protected]>;tag=925E0080
Call-ID: 612b2be69bbe45479e2676a9c89605a3
CSeq: 2 SUBSCRIBE
Via: SIP/2.0/TLS 192.168.11.77:62287;ms-received-port=62287;ms-received-cid=13CB00
Record-Route: <sip:sip.dymonasia.com:5061;transport=tls;lr;ms-key-info=AAEAAQy-Hptx2bBz4bLPASfi0Q8AhsIHwfOZFhikS5I3lhvpZ6FVtoDW4nKeyfA65H-h1EPauf6Bo4PDT0Nc93YHKHPl5ZBwmxjvyetg5BZQ7yraK2EZvGpZ_bkQJlXyIw3lVlxFe-h2PmfG6lfKBZ8To-piAjW4LQLcr3Z7cic1p_GtAFi1lXOOdlcXxfUKQ_vqQjvpuZIrI7xCmomXlvM9o7Ue8lXbq3TndzkR-ghwnju0QJjj5GrUJ3Ia82bfodQYntaJaJG2bf5oUMAVJkX5_84vNcFhZRTRilUI-lC1wyChOjjWVV56ndqCVY7oiitF5HHDpfVg58-SSzRiHKhFZJKvyZtcorcM5WHuJwYNw7sdxzc2vB6hqN4vTdRjlpb1jhG35BsQ2usDMPfc8EZYGY-S5SW6C_NUgrh3Fb-_f0qcnXV92JDu55rbTy-Apz4GJk8Ivrt-PNr99CbhUoyRg_8301OIivRJAExy_xMjyIJBWkoJp7IVQjvhLL_bQWAFQn0HhJTpf13NpT-if54k7l5KbgL6K0vkcMnc8WVkgm5a_c2Dewp_RG-7jIbr5xxZXuJAxK9indqeCXnfjbIk6mhEAZI7SJmlK9_SJt0H94HutoIVwHYLarDclsdKrR7Xb-5nDPkFE4U4LjWRLf-7ff7MJJbzhbaXTE6o_t4nFFQ8kWxiRWBN2kMLChKY;ms-route-sig=bdBGMrXXhjLMmcJ4Ej8ReFZ_nqkUoCWKhFB19tji2ro5-_BAzrBqDJlQAA>
Record-Route: <sip:pmdlonedg01.int.*******.com:5061;transport=tls;lr>
Expires: 0
Content-Length: 0
ms-edge-proxy-message-trust: ms-source-type=DirectPartner;ms-ep-fqdn=pmdlonedg01.int.*******.com;ms-source-verified-user=verified;ms-source-network=federation
Record-Route: <sip:PMDLONLYC01.int.*******.com:5061;transport=tls;opaque=state:F:Ci.R13cb00;lr;ms-route-sig=bc4_1nrdDL4-KX7KrdReLOthlr4n7DTIcsDrkM0bP4gGNYk0BjUtG1CwAA>
08/08/2014|11:25:44.974 4024:4344 INFO :: End of Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 1891 bytes
08/08/2014|11:25:44.974 4024:4344 TRACE :: CSIPMessageCollator::AsyncProcessSipMsg - [0x0C4826E0]
08/08/2014|11:25:44.974 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C4826E0]
08/08/2014|11:25:44.974 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C484940]
08/08/2014|11:25:44.974 4024:4344 TRACE :: verified buffer: <Kerberos><4C70707C><38><SIP Communications Service><sip/PMDLONLYC01.int.*******.com><612b2be69bbe45479e2676a9c89605a3><2><SUBSCRIBE><sip:*****@*******.com><4c49873a8c><sip:[email protected]><925E0080><><><0><200>-length-233.
signature:040401ffffffffff000000000000000023304d3690145c9d580a26a5
08/08/2014|11:25:44.974 4024:4344 INFO :: Trxn corr-id (184AD3F8), SIP msg corr-id (e3f780cb)
08/08/2014|11:25:44.974 4024:4344 INFO :: ~Out trxn corr-id (184AD3F8)
08/08/2014|11:25:45.288 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x07B3B008]
08/08/2014|11:25:45.288 4024:4344 TRACE :: SECURE_SOCKET: decrypting buffer size: 277 (first 8):
08/08/2014|11:25:45.288 4024:4344 TRACE :: 17 03 03 01 10 3B 87 16 :.....;‡.
08/08/2014|11:25:45.288 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C3DC610]
08/08/2014|11:25:45.288 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C2B5E68]
08/08/2014|11:25:45.288 4024:4344 INFO :: Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 1888 bytes:
08/08/2014|11:25:45.288 4024:4344 INFO :: SIP/2.0 200 OK
Proxy-Authentication-Info: Kerberos qop="auth", opaque="DC934C0A", srand="59667E0A", snum="39", rspauth="040401ffffffffff00000000000000002641ec9a3a4c088b301bcf5e", targetname="sip/PMDLONLYC01.int.*******.com",
realm="SIP Communications Service", version=4
Contact: <sip:LyncSG.dymonasia.com:5061;transport=tls>
From: <sip:*****@*******.com>;tag=04814352f9;epid=6969679f0b
To: <sip:[email protected]>;tag=3F0E0080
Call-ID: 8115c934d1fd446eb7d034c4fc773ec0
CSeq: 2 SUBSCRIBE
Via: SIP/2.0/TLS 192.168.11.77:62287;ms-received-port=62287;ms-received-cid=13CB00
Record-Route: <sip:sip.dymonasia.com:5061;transport=tls;lr;ms-key-info=AAEAAQy-Hptx2bBz4bLPASfi0Q8AhsIHwfOZFhikS5I3lhvpZ6FVtoDW4nKeyfA65H-h1EPauf6Bo4PDT0Nc93YHKHPl5ZBwmxjvyetg5BZQ7yraK2EZvGpZ_bkQJlXyIw3lVlxFe-h2PmfG6lfKBZ8To-piAjW4LQLcr3Z7cic1p_GtAFi1lXOOdlcXxfUKQ_vqQjvpuZIrI7xCmomXlvM9o7Ue8lXbq3TndzkR-ghwnju0QJjj5GrUJ3Ia82bfodQYntaJaJG2bf5oUMAVJkX5_84vNcFhZRTRilUI-lC1wyChOjjWVV56ndqCVY7oiitF5HHDpfVg58-SSzRiHKhFZJKvyZtcorcM5WHuJwYNw7sdxzc2vB6hqN4vTdRjlpb1jhG35BsQ2usDMPfc8EZYGY-S5SW6C_NUgrh3Fb-_f0qcnXV92JDu55rbTy-Apz4GJk8Ivrt-PNr99CbhUoyRg_8301OIivRJAExy_xMjyIJBWkoJp7IVQjvhLL_bQWAFQn0HhJTpf13NpT-if54k7l5KbgL6K0vkcMnc8WVkgm5a_c2Dewp_RG-7jIbr5xxZXuJAxK9indqeCXnfjbIk6mhEAZI7SJmlK9_SJt0H94HutoIVwHYLarDclsdKrR7Xb-5nDPkFE4U4LjWRLf-7ff7MJJbzhbaXTE6o_t4nFFQ8kWxiRWBN2kMLChKY;ms-route-sig=bd5A_eMqoaHs_fuYP-5aSBoYbANCe_p5RWv6n6yajgyfxebrRuBqDJlQAA>
Record-Route: <sip:pmdlonedg01.int.*******.com:5061;transport=tls;lr>
Expires: 0
Content-Length: 0
ms-edge-proxy-message-trust: ms-source-type=DirectPartner;ms-ep-fqdn=pmdlonedg01.int.*******.com;ms-source-verified-user=verified;ms-source-network=federation
Record-Route: <sip:PMDLONLYC01.int.*******.com:5061;transport=tls;opaque=state:F:Ci.R13cb00;lr;ms-route-sig=bcFuhIALmH85OaoJh25uPG5Y8-bgabM97QpJ5ypCK7x_cYXXQWUtG1CwAA>
08/08/2014|11:25:45.288 4024:4344 INFO :: End of Data Received -192.168.10.4:5061 (To Local Address: 192.168.11.77:62287) 1888 bytes
08/08/2014|11:25:45.288 4024:4344 TRACE :: CSIPMessageCollator::AsyncProcessSipMsg - [0x0C4826E0]
08/08/2014|11:25:45.288 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C4826E0]
08/08/2014|11:25:45.288 4024:4344 TRACE :: CSIPTransportLayerNotify::OnRecv - [0x0C484940]
08/08/2014|11:25:45.288 4024:4344 TRACE :: verified buffer: <Kerberos><59667E0A><39><SIP Communications Service><sip/PMDLONLYC01.int.*******.com><8115c934d1fd446eb7d034c4fc773ec0><2><SUBSCRIBE><sip:*****@*******.com><04814352f9><sip:[email protected]><3F0E0080><><><0><200>-length-230.
signature:040401ffffffffff00000000000000002641ec9a3a4c088b301bcf5e
08/08/2014|11:25:45.289 4024:4344 INFO :: Trxn corr-id (184AD510), SIP msg corr-id (42a27507)
08/08/2014|11:25:45.289 4024:4344 INFO :: ~Out trxn corr-id (184AD510)
08/08/2014|11:25:49.397 4024:4344 TRACE :: MULTIPARTY_SESSION::RemoveFromLinkedList[17060C50] removed from linked list

As with the original issue, your problem is likely with the Edge server. The first thing I would do is check all of your ports and DNS settings.
Remember that Edge may use somewhat unique ports for AV if you, or the federation target, used a single IP address. If you haven't, see if you have that unique port open on the firewall. If you used a single IP address, ensure that the federation target
has the correct port open also.

Similar Messages

SCOM 2012 R2 Integration with Lync Server 2013

Hi,
I am trying to configure SCOM 2012 R2 to work with Lync server 2013 standard edition. I have successfully installed and tested Lync Server 2013. But the problem is, I never worked on SCOM application before and I can not find any easy documents online. So
could you please help me and suggest any step by step guide for the same purpose!
BR,
Ajit

Hi,
Glad to hear that you have solved the issue. For the second question, what did you want to do with the Windows Server (anything to do with Lync Server)? As it is another question, you can also post another case on Technet forum and more engineers will help
you solve the issue.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync HP 4120 Sign in problems with Lync Server 2013

Hi, this is my second request for help, this with more information...
I`ll ready install the follow infrastructure: (I change the name of my organization for contoso)
Lync Server 2013 Installation with Enterprise mode with 1 front end : Pool: lync.contoso.com Front End: lyncfe01.contoso.com Back End: lyncsql01.contoso.com
I`ll ready install a PKI infrastructure with two tiers, the root offline and the subordnate ac.contoso.com
This with the defailt algorithm configuration RSA SHA1
My phones are HP 4120
In the Front End Server i configured the SCHANNEL registers:
EnableSessionTicket in 2
Send..etc in 0
Ok, the installation is ok, services are OK, Client login trough PC its OK, PSTN Configuration... (I can make a phonecall with the lync client of Office 365)
Commnd Checks:
When i run the command Test-CsPhoneBootstrap -PhoneOrExt 12345 -PIN 123456 -TargetFqdn lync.contoso.com
The result is:
Target Fqdn : lync.contoso.com
Target Uri : https://lync.contoso.com:443/CertProv/CertProvisioningService.svc
Result : Success
Latency : 00:00:09.0559615
Error Message :
Diagnosis :
When i run the command Test-CsPhoneBootstrap -PhoneOrExt 12345 -PIN 123456 for
check the DHCP the result is:
Target Fqdn : lync.contoso.com
Target Uri : https://lync.contoso.com:443/CertProv/CertProvisioningService.svc
Result : Success
Latency : 00:00:09.0559615
Error Message :
Diagnosis :
When i run the follow command
PS C:\Users\Administrator> $cred = Get-Credential
cmdlet Get-Credential at command pipeline position 1
Supply values for the following parameters:
Credential
PS C:\Users\Administrator> Test-CsClientAuth -TargetFqdn lync.contoso.com -UserSipAddress "sip:[email protected]" -UserCredential $cred
I got this:
Target Fqdn : lync.contoso.com
Target Uri : https://lync.contoso.com:443/CertProv/CertProvisioningService.svc
Result : Success
Latency : 00:00:00.3431783
Error Message :
Diagnosis :
But.. when i use the same command but i remove the -targetFqdn for check the Dhcp i got this:
VERBOSE: Workflow Instance Id 'bca95636-af7b-4b0a-b43d-dba259294b2d', started.
VERBOSE: Command line executed is 'Test-CsClientAuth -UserSipAddress "sip:[email protected]" -UserCredential $cred
-Verbose'.
Target Fqdn :
Target Uri :
Result : Failure
Latency : 00:00:00
Error Message : 10060, A connection attempt failed because the connected party did not properly respond after a period
of time, or established connection failed because connected host has failed to respond 194.90.8.20:5061
Inner Exception:A connection attempt failed because the connected party did not properly respond after
a period of time, or established connection failed because connected host has failed to respond
194.90.8.20:5061
Diagnosis :
VERBOSE: Workflow 'Microsoft.Rtc.SyntheticTransactions.Workflows.STClientAuthWorkflow' started.
Workflow 'Microsoft.Rtc.SyntheticTransactions.Workflows.STClientAuthWorkflow' completed in '5.62E-05' seconds.
Target web service Url not provided. Will have to extract it from authentication challenge.
An exception 'Unable to establish a connection.' occurred during Workflow
Microsoft.Rtc.SyntheticTransactions.Workflows.STClientAuthWorkflow execution.
Exception Call Stack: at Microsoft.Rtc.Signaling.SipAsyncResult`1.ThrowIfFailed()
at Microsoft.Rtc.Signaling.Helper.EndAsyncOperation[T](Object owner, IAsyncResult result)
at Microsoft.Rtc.SyntheticTransactions.Activities.GetSTSUriActivity.InternalExecute(ActivityExecutionContext
executionContext)
at Microsoft.Rtc.SyntheticTransactions.Activities.SyntheticTransactionsActivity.Execute(ActivityExecutionContext
executionContext)
at System.Workflow.ComponentModel.ActivityExecutor`1.Execute(T activity, ActivityExecutionContext executionContext)
at System.Workflow.ComponentModel.ActivityExecutorOperation.Run(IWorkflowCoreRuntime workflowCoreRuntime)
at System.Workflow.Runtime.Scheduler.Run()
at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
at Microsoft.Rtc.Internal.Sip.TcpTransport.OnConnected(Object arg)
'GetSTSUri' activity started.
Starting STS Uri Discovery...
ERROR getting STS Uri.
'UnRegister' activity started.
'UnRegister' activity completed in '3.12E-05' seconds.
VERBOSE: Workflow Instance ID 'bca95636-af7b-4b0a-b43d-dba259294b2d' completed.
VERBOSE: Workflow run-time (sec): 126.0548512.
The Real Problem is that my Lync HP 4120 Phone can't make a sign in, not from USB cable loging, nor with PIN authentification
When I try to make a login with the USB cable, I set the user and password and the phone says "Connecting to Lync".. "Downloading a certificate" ... "Installing certificate"... "Downloading Certificate"...
"Installing Certificate".. forever
When I try to make a login with PIN Authentification, the phone first displays the following:
Account used is not authorized, Please Contact your support team and then shows this:
An Account matching this phone number cannot be found. Please contact your support team.
The Pin authentification is enable
In the Lync Server Enable Kerberos Authentification, Enable Integrated Windows Authentification and Enable Certificate Authentification are enable
This is the configuration from DHCP
Starting Discovery ...
Sending Packet (Size: 284, Network Adapter: xx.xx.xx.xx, Attempt Type: Broadcast only)
--Begin Packet--
DHCP: INFORM (xid=130EA7FA)
DHCP: Op Code (op) = 1
DHCP: Hardware Type (htype) = 6
DHCP: Hops (hops) = 0
DHCP: Transaction ID (xid) = 319727610
DHCP: Seconds (secs) = 0
DHCP: Flags (flags) = 0000
DHCP: Client IP Address (ciaddr) = Xx.xx.xx.xx
DHCP: Your IP Address (yiaddr) = 0.0.0.0
DHCP: Server IP Address (siaddr) = 0.0.0.0
DHCP: Relay IP Address (giaddr) = 0.0.0.0
DHCP: Client HW Address (chaddr) = FC15B4###--End Packet--
Received Packet
Sender:xx.xx.xx.xx:67, Size:363
--Begin Packet--
DHCP: ACK (xid=130EA7FA)
DHCP: Op Code (op) = 1
DHCP: Hardware Type (htype) = 6
DHCP: Hops (hops) = 0
DHCP: Transaction ID (xid) = 319727610
DHCP: Seconds (secs) = 0
DHCP: Flags (flags) = 0000
DHCP: Client IP Address (ciaddr) = xx.xx.xx.xx
DHCP: Your IP Address (yiaddr) = 0.0.0.0
DHCP: Server IP Address (siaddr) = 0.0.0.0
DHCP: Relay IP Address (giaddr) = 0.0.0.0
DHCP: Client HW Address (chaddr) = FC15B4100289
DHCP: Server Host Name (sname) =
DHCP: Boot File Name (file) =
DHCP: Magic Cookie = 99.130.83.99
DHCP: Option Field
DHCP: DHCP MESSAGE TYPE( 53) = (Length: 1) DHCP ACK
DHCP: Server Identifier( 54) = (Length: 4) XX.XX.XX.XX
DHCP: Client Identifier( 61) = (Length: 0) ()
DHCP: SIP Server( 120) = (Length: 17) enc:0 lync.contoso.com (00046C796E6306756E69736F6E026D7800)
DHCP: Host Name( 12) = (Length: 0)
DHCP: Vendor Identifier( 60) = (Length: 0)
DHCP: Param Req List( 55) = (Length: 0) 0 0
DHCP: Vendor Info( 43) = (Length: 86) MS-UC-Clienthttpslync.contoso.com443%/CertProv/CertProvisioningService.svcÜNAP (010C4D532D55432D436C69656E7402056874747073030E6C796E632E756E69736F6E2E6D78040334343305252F4365727450726F762F4365727450726F766973696F6E696E67536572766963652E737663DC034E4150)
DHCP: End of this option field
--End Packet--
Result: Success
DHCP Server : xx.xx.x.xx.
SIP Server FQDN : lync.contoso.com
Certificate Provisioning Service URL : https://lync.contoso.com:443/CertProv/CertProvisioningService.svc
thanks for all, hope somebody can help me with this problem.. i am going crazy...

Hi, i connected the Lync Phone to another switch and i update the firmware to the newest firmware and i got the same problem..
The lync phone download the certificate but cant install it and the still the same error with the SIP login
An Account matching this phone number cannot be found. Please contact your support team.

Is it possible to connect to LYNC Server 2013 from outside without public certificate

Hello to everybody
I have a rather simple question but i cannot find a definite answer
I have installed Lync server for purely testing purposes on my work lab
I have internal communication ...even web based but i don't know how to get external communication
I have a domain with FQDN : domain.abc.com .... please
take note that the FQDN is 3 part...my computer are registered under computer.domain.abc.com.....and my domain is presented as
abc
My lync server is lsvr.domain.abc.com
We also have DNS records to external.abc.gr pointing to my static IP
Is it possible to create a self signed certificate that will enable us to perform external communications...especially with the Lync Web app or i should
definitely get a public certificate.
The whole issue is that we wish to make a presentation to the company's owner in order to get the approval to buy Lync and the required infrastructure or will use some other way of communication like Skype
It seems i cannot get a definite answers if i can do it without paying the money for the certificate or we should bite the bullet and pay the certificate

Well i had a mistake in network configuration but now i have different issue and i can't find how to begin with this
Let me take it from the beginning ...
I am user :Tsuser
I connect internally to my Lync Server :lsvr.domain.abc.com
with internal IP 192.168.1.200
I use
the meet url : https://meet.domain.abc.com/Tsuser/randomnumbersletters
I connect
ok
I change
the meet url to : https://Internal IP of lsvr(192.168.1.200)/Tsuser/randomnumbersletters
i get 404 File or directory not found.
I change
the meet url to : https://lsvr.domain.abc.com/Tsuser/randomnumbersletters
i get 404 File or directory not found.
I port forward my public ip to lsvr.domain.abc.com
port 4443 the same 404
Something is wrong here but i can't figure it out
Can anyone give me a helping hand...i think this is the main obstacle

Outlook 2013 not connect with Exchange server 2013 in internal network

Hello All,
I Have two Exchange server 2013 in our environment. Both server install mailbox and CAS role. After configure exchange server 2013, Outlook 2013 not connect in internal network. I have configure outlook manually. i tried by using the suggestion from blog
but not work. Outlook show that Server cannot connect/ server name could not be resolved. in outlook setting i also put exchange proxy setting. In exchange admin center i have changed the OWA, OAB, Auto discover name. But still not work.
I know that outlook can be connect from external by using ssl certificate and publish outlook anywhere but i did my configure from internal network.
Can you please suggest as soon as possible.
Thanks,
Parvez

Hi,
Firstly, I’d like to explain, same with external users, internal users use Outlook Anywhere to connect with Exchange server and use Autodiscover get all settings.
Thus, let’s try the following resolutions:
1. run the following command: get-clientaccessservice |fl autodiscoverserviceinternaluri
2. check if the host name in the above URL is in the DNS server and there is a DNS entry about the host name points to the proper IP address.
3. Check if the above host name is in your certificate.
Thanks,
Angela
Angela Shi
TechNet Community Support

Client support on Mavericks (OSX 10.9) for Lync 2011 with Lync Server 2013

It was just pointed out to me by Microsoft Product Support that Mac OS 10.9 (Mavericks) operating system is not currently supported by Microsoft. See the paragraph entitled Macintosh Operating Systems in this link:
http://technet.microsoft.com/en-us/library/gg412781.aspx
Does anyone in the Lync community know when it will be supported?

Nothing that I've heard. Having said that although unsupported it seems to work fine (well no worse than it did on 10.8 with its intermittent crashing for no reason) I've been running it on Mavericks pretty much daily since October last year and am running
14.0.7 of Lync 2011.
I have seen a few people report issues though mainly inability to download/search the address book, but not sure if these are related. (although the reports say it's after they upgraded)
If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer" | Blog
www.lynced.com.au | Twitter
@imlynced

Make Call Fail on B2B in Lync Server 2013

Hi,
I am facing an issue while working with Lync server 2013.
My analysis on the issue is as follows:
Lync Client 2013 (SIP Scenario) :
1) Invite from UCMA application to Lync Server and then to reach Lync Agent.
2) Trying
3) 180 Ringing
4) "488 not acceptable here" responded by the Lync Server
Lync Client 2010 (SIP Scenario):
1) Invite from UCMA application to Lync Server and then to reach Lync Agent.
2) Trying
3) 180 Ringing
4) 200 Ok (Lync Agent attends the call)
The scenario works properly with Lync Client 2010 and Lync Server 2013.
But the same doesn't work with Lync Client 2013 and Lync Server 2013.
Kindly revert back with a possible solution ASAP.
Regards,
Harish

Hi,
Make sure Lync 2013 client update to the latest version and then test again.
If the issue persists, you might post the issue on Lync MSDN forum and more developing expert will help to solve the issue. Thank you for your understanding.
http://social.msdn.microsoft.com/Forums/en-US/communicatorsdk/threads
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

How to achieve Multi-Tenant in Lync Server 2013 Enterprise Edition

Hi,
As LHPv2 is discontinued, is anyone has idea how to achieve Multi-Tenant in Lync Server 2013 Enterprise Edition?
e.g users from different tenants should not be able to communicate unless it is allowed either by federation or any other form.
J.B.Patnaik

once a Topology has been published you can not change the FQDN.
Also you can refer shah-Khan answer, it will be helpful for you
http://social.technet.microsoft.com/Forums/lync/en-US/47d4e101-4f7b-4115-8f44-897eb5410acb/need-to-change-a-published-fqdn-lync-pool-for-lync-enterprise-2010?forum=ocsplanningdeployment
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

Unable to establish a session with the Address Book Server

I have installed the following
Sun Java System Messaging Server 7 Update 3
Sun Java System Calendar Server 6.3
Sun Java System Directory Server 6.3.1
GlassFish Enterprise Server 2.1 Patch 2 with HADB support
Delegated Administrator 7
Sun Convergence 1 Update 3
as per the instruction here
http://wikis.sun.com/display/CommSuite7/Sun+Java+Communications+Suite+7+on+a+Single+Host
My problem is that when I open outlook and try to add a new contact, I get a message saying:
Unable to establish a session with the Address Book Server. Contact your server administrator for help or try later.
When using webmail, I can add contacts just fine.
How can I fix this problem?
Thanks
Edited by: Nevron on 26 ??? 2010 11:31 ??

Nevron wrote:
My problem is that when I open outlook and try to add a new contact, I get a message saying:
Unable to establish a session with the Address Book Server. Contact your server administrator for help or try later.Refer here:
http://forums.sun.com/thread.jspa?threadID=5424727
You need to log a Sun support request to get the latest Convergence patch.
Regards,
Shane.

Persistent Chat (Lync Server 2013) with Lync 2010 Group Chat

I have successfully deployed Lync Server 2013 and both 2013 and 2010 desktop clients connect and function as expected.
The problem is with Persistent Chat. It works perfectly with the 2013 desktop client but - whilst 2010 Group Chat connects - I receive the error message "The [LOGON_DOMAIN] is not available". No chat rooms are available and I am unable to search.
I have been unable to locate anything on the web which discusses the problem.
I do not know whether this makes a difference but the 2010 clients use terminals rather than dedicated workstations.
Can anyone shed any light on what the problem may be?

Have you created a CsPersistentChatEndpoint to allow the Group Chat client (2010) to connect to Persistent
Chat server? Please take a look at: http://technet.microsoft.com/en-us/library/jj204901.aspx
Please mark posts as answers/helpful if it answers your question.
Blog
Lync Validator - Used to assist in the validation and documentation of Lync Server 2013.

Establishing Lync Server 2013 on a Child Domain

Hi,
We want to establish Lync Server 2013 Enterprise Edition on a child-domain. I finished the installation. Now, if i add to users to child domain and enable from Lync Server Control Panel for test, users can be signed in. However, we use child domain for only
domain computers. We want to keep users on parent domain, not child domain.
I can enable users which are on parent domain, but users can not sign in. When i look Lync troobleshooting program, i got this error: "user is not sip enabled"
How can i solve this problem not adding users to child domain?

Check whether the SIP address is enabled for the user
Get-CSUser -Identity <Alias>
SipAddress : sip:[email protected]
Enable-CsUser –Identity "Raji" –RegistrarPool Pool01.Lync.com –SipAddress "sip:[email protected]" –SipDomain Lync.com
Verify the output
Get-CsAdUser | Select-Object DisplayName, SipAddress, UserPrincipalName
Or
Construct a SIP address using the user’s SamAccountName and domain name
The SamAccountName is the user’s logon name: it’s the kenmyer portion of litwareinc\kenmyer. To use the SamAccountName as the SIP address use the –SipAddressType parameter followed by the parameter value SamAccountName:
Enable-CsUser –Identity "Ken Myer" –RegistrarPool atl-cs-001.litwareinc.com –SipAddressType SamAccountName –SipDomain litwareinc.com
Note that you also need to include the –SipDomain parameter followed by the appropriate SIP domain. With both FirstLastName and SamAccountName you must explicitly indicate the SIP domain; Enable-CsUser won’t try to make a “best guess” at determining the domain
name for you.
Use the user’s email address as his or her SIP address
This is kind of a nice option: it simply grabs the user’s email address and uses that same value for his SIP address. (That way, users have just one address to remember.) To use this option, simply include the –SipAddressType parameter followed by the parameter
value EmailAddress:
Enable-CsUser –Identity "Ken Myer" –RegistrarPool atl-cs-001.litwareinc.com –SipAddressType EmailAddress
Reference: https://blogs.technet.com/b/csps/archive/2010/06/06/howtoenableusers.aspx
Exchange Queries

Unable to start Lync 2013 FE service on one of the pooled server, error "The evaluation period for Microsoft Lync Server 2013 has expired"

Team,
Unable to start FE service on one of the FE server, 2 Enterprise lync 2013 pool one FE in each pool, only following error in event vrw,
Log Name: Lync Server
Source: LS Server
Date: 12/30/2013 12:10:55 PM
Event ID: 12290
Task Category: (1000)
Level: Error
Keywords: Classic
User: N/A
Computer: ACS465-BH102.me.ykgw.net
Description:
The evaluation period has expired.
The evaluation period for Microsoft Lync Server 2013 has expired. Please upgrade from the evaluation version to the fully licensed version of the product. Look at help for Setup.exe to learn how to upgrade from evaluation version to the licensed version.
Cause: The evaluation period for Microsoft Lync Server 2013 has expired.
Resolution:
Please upgrade from the evaluation version to the licensed version of the product. Look at help for Setup.exe to learn how to upgrade from evaluation version to the licensed version.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="LS Server" />
<EventID Qualifiers="50152">12290</EventID>
<Level>2</Level>
<Task>1000</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-12-30T09:10:55.000000000Z" />
<EventRecordID>73953</EventRecordID>
<Channel>Lync Server</Channel>
<Computer>ACS465-BH102.me.ykgw.net</Computer>
<Security />
</System>
<EventData>
</EventData>
</Event>
Log Name: System
Source: Schannel
Date: 12/30/2013 12:13:36 PM
Event ID: 36888
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: ACS465-BH102.me.ykgw.net
Description:
The following fatal alert was generated: 10. The internal error state is 1203.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Schannel" Guid="{1F678132-5938-4686-9FDC-C8FF68F15C85}" />
<EventID>36888</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2013-12-30T09:13:36.779033200Z" />
<EventRecordID>83985</EventRecordID>
<Correlation />
<Execution ProcessID="556" ThreadID="3668" />
<Channel>System</Channel>
<Computer>ACS465-BH102.me.ykgw.net</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="AlertDesc">10</Data>
<Data Name="ErrorState">1203</Data>
</EventData>
</Event>
Server is already on Full version, ran Reset-CsPoolRegistrarState
for fillrest as wel as serviceret
Followed below as well,
http://social.technet.microsoft.com/Forums/lync/en-US/2a7e27ce-2dea-4e37-91ea-1ed42e110198/issue-updating-from-eval-to-volume-licenses?forum=ocsplanningdeployment
Currently done failover to another pool and users can login,
however i cant get the front end service on this server.Any pointers would be appreciated.
Praveen | MCSE Messaging 2003

rit, the command is not doing the trick since its already full version,
PS C:\Users\lyncadmin> Get-CsServerVersion
Microsoft Lync Server 2013 (5.0.8308.0): Volume license key installed.
only one server in one pool, total two pools.
Lync 2013 is on Win 2008 R2, and the event in system im inclining to since i have tried all,
Log Name: System
Source: Schannel
Date: 12/30/2013 9:26:34 AM
Event ID: 36888
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: ACS465-BH102.me.ykgw.net
Description:
The following fatal alert was generated: 10. The internal error state is 1203.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Schannel" Guid="{1F678132-5938-4686-9FDC-C8FF68F15C85}" />
<EventID>36888</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2013-12-30T06:26:34.877077500Z" />
<EventRecordID>64911</EventRecordID>
<Correlation />
<Execution ProcessID="556" ThreadID="620" />
<Channel>System</Channel>
<Computer>ACS465-BH102.me.ykgw.net</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="AlertDesc">10</Data>
<Data Name="ErrorState">1203</Data>
</EventData>
</Event>
Praveen | MCSE Messaging 2003

Error - unable to establish JCO connection with SSO

Hello,
I have implemented XSS on WebDP and this is working fine. So my JCO connections SAP_R3_HumanResources must be configured correctly. However I have just done the 'GetFlight' BAPI tutorial and upon execution I get the error:
'com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCException: Could not create JCOClientConnection for logical System: SAP_R3_HumanResources - Model: class com.sap.tut.wd.flightlist.model.FlightModel. Please assure that you have configured the RFC connections and/or logical system name properly for this model!'
CAUSED BY
'User not authenticated (is anonymous) - unable to establish JCO connection with SSO'
Can anyone help here?
Thanks
Mr.T

HI
GOOD
GO THROUGH THIS LINK WHICH CONTAINS THE A SINGLE SIGN-ON IN A COMPLEX SYSTEM LANDSCAPE.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/80fbc690-0201-0010-1aba-93d5c8232b4a
http://www.sap-press.de/download/dateien/1020/sappress_sap_security_authorizations.pdf
http://sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ff65b5a2-0a01-0010-5b97-e747192a1d49
THANKS
MRUTYUN

How do I enforce "Show My Picture" instead of "Hide My Picture" in Lync Server 2013?

I was scouring TechNet and the web for a script that could perform the same task as one that I previously used for Lync 2010.
In Lync 2010, we had already used Lync policy to enforce that only the Active Directory photo could be used. One thing that we couldn't set via policy however was the ability to complete remove the "Hide My Picture" option in Lync 2010 client.
This left users with the ability to freely switch between showing the Corporate photo or no photo. I did eventually find and make use of script that constantly checked for this setting switch, then switched all users back to the desired "Show My Picture"
setting. I don't recall who wrote it, but it's easy to find on technet. As we started to move more and more users to our Lync 2013 enterprise pool, I noted that even though the script was running, the setting seemed to be changeable. A closer look revealed
that the script didn't function correctly against SQL for our 2013 pool.
I took the concept and applied it to Lync Server 2013 after studying the differences in Userdata. In Lync 2013, because UserData is in .zip, you need to convert it to 2010 format XML to use logic intended for Lync 2010. My script will extract 2013 data,
convert it to 2010, query for users who are set to "Hide My Picture" and then export any guilty users to an edited2010 XML. The script then converts this to 2013 Format .zip, and uploads the data for these users only. I chose to use Update-CSUserData
insted of Import-CSUserData as this avoids having to restart my Front End. I then use a scheduled task on my Front End server which runs this script every hour.
Please note: You can use this script, but I guarantee nothing about it's functionality, and I am not responsible for how you positively/negatively use it. You should always test things in a Lab Environment. Furthermore, this script was run on a relatively
smaller Enterprise system in which we are by default set to "Show My Picture" and already assigned as part of our user policy the ForceADPhoto attribute. This means that running the script is less intensive on my FE than say on a FE with 10,000 users
where none of the users were set to "Show My Picture". Please keep this in mind when planning to execute against your FE. You may want to edit my script and insert the -UserFilter or -WhatIf in the Export-CsUserData UpDate-CsUserData.
Anyways, I hope this solves the similar issue for many of you Lync 2013 administrators. Please feel free to share my work with others if it does, and also give this post some good feedback and/or mark my post as the answer to your problem.
Alas, here's the script (save it as a .ps1 , i.e. ForceShowMyPicture.ps1)
#Lync 2013 ForceShowMyPicture - Compiled by Octavio A. Serpa (Octavio-Admin on TechNet)
# Import Lync Module
Import-Module “C:\Program Files\Common Files\Microsoft Lync Server 2013\Modules\Lync\Lync.psd1"
###Variables To Set
#This variable is a folder where files will be temporarily written
$folderPath = “C:\Lync2013Scripts\Export”
#This is the FQDN of the pool in which the users you want to target reside
$poolFQDN = “<lyncpool.domain.local>”
###Done
#Message Out
Write-Host -ForegroundColor YELLOW “CHECKING THAT TEMP EXPORT FOLDER PATH EXISTS"
If (-not (Test-Path "$folderPath" -pathType container))
"ERROR: Your Export Directory doesn't exist!"
Exit
Write-Host -ForegroundColor Green “TEMP EXPORT FOLDER DOES EXIST"
Write-Host -ForegroundColor YELLOW “PRE-CLEANING OLD EXPORT/IMPORT FILES"
If (Test-Path "$folderPath\Lync2013UserData.zip") { Remove-Item "$folderPath\Lync2013UserData.zip" }
If (Test-Path "$folderPath\Lync2010UserData.xml") { Remove-Item "$folderPath\Lync2010UserData.xml" }
If (Test-Path "$folderPath\Lync2010EditedUserData.xml") { Remove-Item "$folderPath\Lync2010EditedUserData.xml" }
If (Test-Path "$folderPath\Lync2013EditedUserData.zip") { Remove-Item "$folderPath\Lync2013EditedUserData.zip" }
Write-Host -ForegroundColor Green “PRE-CLEANING COMPLETED SUCCESSFULLY"
#Message Out
Write-Host -ForegroundColor YELLOW “EXPORTING LYNC 2013 POOL USER DATA”
Export-CsUserData -PoolFqdn $poolFQDN -FileName $folderPath\Lync2013UserData.zip
Write-Host -ForegroundColor Green “EXPORT COMPLETED SUCCESSFULLY"
#Message Out
Write-Host -ForegroundColor YELLOW “CONVERTING LYNC 2013 USER DATA TO 2010 FORMAT”
Convert-CsUserData -InputFile "$folderPath\Lync2013UserData.Zip" -OutputFile "$folderPath\Lync2010UserData.xml" -TargetVersion Lync2010
Write-Host -ForegroundColor Green “CONVERSION COMPLETED SUCCESSFULLY"
#Message Out
Write-Host -ForegroundColor YELLOW “CHECKING THAT FORMAT CONVERSION WAS SUCCESSFUL AND .XML EXISTS”
If (-not (Test-Path "$folderPath\Lync2010UserData.xml" -pathType leaf))
"ERROR: Verify that $folderPath is writable!"
Exit
Write-Host -ForegroundColor Green “CONVERSION COMPLETED SUCCESSFULLY"
#Message Out
Write-Host -ForegroundColor YELLOW “LOADING XML”
$d = [xml] (Get-Content "$folderPath\Lync2010UserData.xml")
Write-Host -ForegroundColor Green “XML LOADING COMPLETED SUCCESSFULLY"
#Message Out
Write-Host -ForegroundColor YELLOW “CORRECTING AD PHOTO SETTING”
$changes = 0
$lastProcessedUser = $null
foreach ($hr in $d.HomedResources.HomedResource)
$found = 0
foreach ($c in $hr.Containers.Container)
  foreach ($p in $c.Publication)
   If ($p.CategoryName -eq 'contactCard' -and $p.InstanceNum -eq 6 -and $p.Data.contactCard.displayADPhoto -eq 'false')
    If ($hr.UserAtHost -ne $lastProcessedUser)
     "$($hr.UserAtHost) reset"
     $lastProcessedUser = $hr.UserAtHost
    $p.Data.contactCard.displayADPhoto = 'true'
    $p.Version = (([int] $p.Version) + 1).ToString()
    $p.PrevPubTime = $p.LastPubTime
    $p.LastPubTime = (Get-Date -Format s).ToString()
    $found = 1
    $changes++
If ($found -eq 0) { [Void]$d.HomedResources.RemoveChild($hr) }
Write-Host -ForegroundColor Green “AD PHOTO SETTING CORRECTIONS COMPLETED SUCCESSFULLY"
#Message Out
Write-Host -ForegroundColor YELLOW “Changes: $changes"
If ($changes -ne 0)
#Message Out
Write-Host -ForegroundColor YELLOW “RE-SAVING XML”
$d.Save("$folderPath\Lync2010EditedUserData.xml")
#Message Out
Write-Host -ForegroundColor YELLOW “CONVERTING LYNC 2010 .XML BACK TO 2013 .ZIP FORMAT"
Convert-CsUserData -InputFile "$folderPath\Lync2010EditedUserData.xml" -OutputFile "$folderPath\Lync2013EditedUserData.zip" -TargetVersion Current
#Message Out
Write-Host -ForegroundColor Green “CONVERSION BACK TO 2013 .ZIP FORMAT SUCCESSFUL"
#Message Out
Write-Host -ForegroundColor YELLOW “IMPORTING LYNC 2013 POOL DATA FOR CORRECTED USERS”
Update-CsUserData -FileName $folderPath\Lync2013EditedUserData.zip -Confirm:$false -Verbose
Write-Host -ForegroundColor Green “IMPORT COMPLETED SUCCESSFULLY"
Write-Host -ForegroundColor YELLOW “STARTING POST-IMPORT-CLEANUP OF EXPORT/IMPORT FILES"
If (Test-Path "$folderPath\Lync2013UserData.zip") { Remove-Item "$folderPath\Lync2013UserData.zip" }
If (Test-Path "$folderPath\Lync2010UserData.xml") { Remove-Item "$folderPath\Lync2010UserData.xml" }
If (Test-Path "$folderPath\Lync2010EditedUserData.xml") { Remove-Item "$folderPath\Lync2010EditedUserData.xml" }
If (Test-Path "$folderPath\Lync2013EditedUserData.zip") { Remove-Item "$folderPath\Lync2013EditedUserData.zip" }
Write-Host -ForegroundColor Green “POST-IMPORT-CLEANUP COMPLETED"
#Message Out
Write-Host -ForegroundColor Green “AD PHOTO SETTING SUCCESSFULLY UPDATED"

When I try to run this I get the follow error. Any thoughts?
Update-CsUserData : Unable to cast COM object of type 'System.__ComObject' to interface type
'Microsoft.Rtc.Interop.User.ICsUserManagement'. This operation failed because the QueryInterface call on
the COM component for the interface with IID '{D5ADD966-BDC3-4A8F-BFE8-6A59A9F74CB2}' failed due to the
following error: Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).
At C:\Lync2013Scripts\ForceDisplayPhoto.ps1:113 char:1
+ Update-CsUserData -FileName $folderPath\Lync2013EditedUserData.zip -Confirm:$fal ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: ([email protected]:String) [Update-CsUserData], Invalid
   CastException
    + FullyQualifiedErrorId : Microsoft.Rtc.Management.AD.Cmdlets.ImportOcsUserDataCmdlet

2 Problems using lync client andriod conncet to lync server 2013 ( contacts status is Presence Unkhown)

Hello Everybody
I have installed lync server 2013 in my lab . Everything is ok . but internal mobile client in my LAN can not work with lync !
I installed lync server 2013.
I create 2 DNS record to lync-server : lyncdiscoverinternal and lyncdiscover.
clients on PC (windows) work and everything is ok . when user use Anroid phone , cleint connect to lync server and list connnact list .BUT when Send IM to contact or start video call come this error :
" Failed to process the server response.Please try again . if the problem persists,contact your support team."
This is first problem. Another problem is the contact list for every user status is "Presence Unkhown" !
No online , No Offline and all of contact status "Presence Unkhown" !
If i had to config mobility in in lync server 2013 ? or mobility service built-in in lync server 2013 ?
please help me .

Hi Meysam Halvaei,
As Thamara mentioned, you need to deploy reverse proxy.
Lync 2013 mobility clients are using a separate dedicated Ucwa parameter the URL is the same web services location as provided by the
External/Ucwa parameter.
You need to have a look at the following diagram.
The Lync 2013 mobile client will need to connect with the external web services. The way Lync is designed this communication is always established using HTTPS/TCP 443, so the traffic
will need to pass through a reverse proxy or similar service that will take this communication and forward it to the server hosting the external web services, now using port 4443 instead.
Best regards,
Eric

Unable to establish AV call with Lync server 2013 from internal to external remote users

Similar Messages

Maybe you are looking for