Capturing traces and logs 225Symptom:The telephone is on Call Forward to another number. When the OfficeCommunicator user who is associated to this telephone logs in (thistelephone is controlled by the Office Communicator user through SIP CTI),the Office Communicator cancels the Call Forward.Possible cause:This is a Microsoft issue that Nortel has escalated to Microsoft.Solution:No solution yet.Office Communicator disconnecting from the networkProblem:Office Communicator user cannot control the telephone after having beendisconnected several times.Symptom:Customers using smart telephones or Mobile Communicators cannot takecontrol of the telephone after having been disconnected abruptly three ormore times. This disconnection could be due to your network (for example,GPRS or WLAN).Possible cause:This problem occurs because the SIP CTI link is disconnected abnormallyand the Association is out of service for 30 minutes (1800 seconds). Thistimer is hard-coded by Office Communicator and cannot be changed.Solution:Increase the Maximum Associations per DN on the Signaling Serverthrough Element Manager. This field is configured to 3 by default. Increasethis parameter to allow more network disconnections.Capturing traces and logsUse the following procedures to capture traces and logs to assistin troubleshooting Converged Office problems. When a problem isencountered, traces and logs can be activated on different components.• Communication Server 1000 traces• MCM logs• OCS logs• OC logsCommunication Server 1000 tracesUse the following procedures for capturing traces.Nortel Communication Server 1000Nortel Converged Office Fundamentals — Microsoft Office Communications Server 2007NN43001-121 01.03 StandardRelease 5.0 30 April 2008Copyright © 2005–2008, Nortel Networks.
