remote users cannot connect via Edge Server

• Question

• 

  

  0

  Sign in to vote

  Hi all. 

   

  I am configure Edge Server to permit remote users connect via Office Communicator 2007 a internal users, but i get this error.

   

  "Async work item posted for TLS negotiation: this 012B3AB0"

   

  below part of log file of Office communicator 2007

   

  /-------------------------------------------------------------------------------------------------------/

  02/22/2008|14:43:09.453 FC0:FC4 INFO  :: Outgoing 012B5788-<sip:COS.mcaldas@intercorp.com.pe>, local=(null)
  02/22/2008|14:43:09.453 FC0:FC4 TRACE :: SIP_STACK:eleteProviderProfile freed profile at index 0
  02/22/2008|14:43:09.453 FC0:FC4 TRACE :: SIP_MSG_PROCESSOR:nDnsResolutionComplete[012B5788] Entered host sip.intercorp.com.pe
  02/22/2008|14:43:09.453 FC0:FC4 ERROR :: SIP_STACK::MapDestAddressToNatInternalAddress m_pDirectPlayNATHelp is NULL.  Setting *pIsDestExternalToNat to FALSE
  02/22/2008|14:43:09.453 FC0:FC4 INFO  :: CSIPCompressor::Initialize - Compression setting 2, threshold 128000, timeout 5000
  02/22/2008|14:43:09.453 FC0:FC4 TRACE :: Async work item posted for TLS negotiation: this 012B3AB0
  02/22/2008|14:43:09.453 FC0:FC4 TRACE :: ASYNC_SOCKET:endOrQueueIfSendIsBlocking sending sendBuffer 01CE9F90, this 012B3AB0
  02/22/2008|14:43:09.453 FC0:FC4 TRACE :: ASYNC_SOCKET:endHelperFn sendBuffer 01CE9F90 sent, this 012B3AB0
  02/22/2008|14:43:09.453 FC0:FC4 TRACE :: Async work item posted for TLS negotiation: this 012B3AB0
  02/22/2008|14:43:09.453 FC0:FC4 TRACE :: ASYNC_SOCKET:endOrQueueIfSendIsBlocking sending sendBuffer 01CE9F90, this 012B3AB0
  02/22/2008|14:43:09.453 FC0:FC4 TRACE :: ASYNC_SOCKET:endHelperFn sendBuffer 01CE9F90 sent, this 012B3AB0
  02/22/2008|14:43:09.468 FC0:FC4 TRACE :: Async work item posted for TLS negotiation: this 012B3AB0
  02/22/2008|14:44:09.453 FC0:FC4 ERROR :: ASYNC_SOCKET:nTimerExpire - SSL socket still not connected
  02/22/2008|14:44:09.453 FC0:FC4 ERROR :: ASYNC_SOCKET:nConnectError (0x80ee0069) - enter
  02/22/2008|14:44:09.453 FC0:FC4 TRACE :: SIP_MSG_PROCESSOR:nRequestSocketConnectComplete - Enter this: 012B5788, callid=(null), ErrorCode: 0x80ee0069
  02/22/2008|14:44:09.453 FC0:FC4 ERROR :: Releasing socket and notifying transactions
  02/22/2008|14:44:09.453 FC0:FC4 ERROR :: SIP_MSG_PROCESSOR::NotifyRequestSocketConnectComplete - Error: 80ee0069
  02/22/2008|14:44:09.453 FC0:FC4 ERROR :: OUTGOING_TRANSACTION:nRequestSocketConnectComplete - connection failed error 80ee0069
  02/22/2008|14:44:09.453 FC0:FC4 TRACE :: CUccServerEndpoint::UpdateEndpointState - Update state from 1 to 0. Status 80EE0069. Status text (null).
  02/22/2008|14:44:09.453 FC0:FC4 INFO  :: Function: CUccServiceOperationManager:isableServManager
  02/22/2008|14:44:09.453 FC0:FC4 ERROR :: Condition failed with 80ee0061: 'm_fServMgrEnabled'
  02/22/2008|14:44:09.453 FC0:FC4 INFO  :: Function: CUccServerEndpoint::UpdateEndpointState
  02/22/2008|14:44:09.453 FC0:FC4 ERROR :: HRESULT API failed: 80ee0061 = hr. DisableServManager
  02/22/2008|14:44:09.453 FC0:FC4 INFO  :: Function: CUccOperationProgressEvent::get_StatusText
  02/22/2008|14:44:09.453 FC0:FC4 ERROR :: Condition failed with 00000001: 'm_swszText != 0'
  02/22/2008|14:44:09.453 FC0:FC4 TRACE :: SIP_STACK:eleteProviderProfile freed profile at index 0
  02/22/2008|14:44:09.531 FC0:A0 TRACE :: SECURE_SOCKET: stream sizes: header 5 trailer 16 max message 16384 buffers 4 block size 1
  

  /---------------------------------------------------------------------------------------------------------------------------------------------------/

   

   

  Some help , Im not using Director and I using Consolidated Edge Topology.

   

  Monday, February 25, 2008 10:24 PM