Troubleshooting Guide for SCOPIA iVIEW Management
Contents
1. page 3 T 3 Resolving User Experience 55 65 2 2 2 244442 22 1 page 6 Resonang adminis SSUES ua RARES page 7 SEU CET cT UNT page 8 Pesonna a Porc S ODE Eois aree VR lites a page 11 Bisnis Raine suae sach EB De UE RN ER page 11 Resolving a Failed Terminal ii page 12 Resolving Meeting Creation Fall te page 13 e Synchronizing SCOPIA Desktop Server with iVIEW Suite page 14 Resolving NO Video page 14 Resolving No Videa OR RP LERRA I eR Epod page 14 Resolving Mo Audio OUEDLIE usce spia e CHER RAI RR page 14 Updating the IP Address on the Streaming 5 page 15 Changing IP Address of the SCOPIA Desktop Server page 15 Recording Does Not Start Automatically page 16 Resolving Browser Authentication Issues Recognizing a Local Intranet Site E Problem The browser does not recognize iVIE2. BADVISION SCOPIA Delivering the Visual Experience 9 MANAGEMENT SCOPIA iVIEW Management Suite Version 7 5 B RADSON R D ISION 1 EET 2000 2010 RADVISION Ltd All intellectual property rights in this publication are owned by RADVISION Ltd and protected by United States copyright laws other applicable copyright laws and international treaty provisions RADVISION Ltd retains all rights not expressly granted This publication is RADVISION confidential No part of this publication may be reproduced in any form whatsoever or used to make any derivative work without prior written approval by RADVISION Ltd No representation of warranties for fitness for any purpose other than what is specifically mentioned in this guide is made either by RADVISION Ltd or its agents RADVISION Ltd reserves the right to revise this publication and make changes without obligation to notify any person of such revisions or changes RADVISION Ltd may make improvements or changes in the product s and or the program s described in this documentation at any time If there is any software on removable media described in this publication it is furnished under a license agreement included with the product as a separate document If you are unable to locate a copy please contact RADVISION Ltd and a copy will be provided to you Unless otherwise indicated RADVISION registered trademarks are registered in the Un
3. csse 13 Resolving No Video OUTPUT e nee em rn ec o na Rn RR aes 14 Resolving Poor Video 2 mmm emen nnn 14 Resolving No Audio QUEDU LU ii rece C a RC Te Yr CCP E 14 Synchronizing SCOPIA Desktop Server with iVIEW Suite 14 Updating the IP Address on the Streaming 15 Changing IP Address of the SCOPIA Desktop Server 15 Recording Does Not Start 222 2 nnn 16 SCOPIA Delivering the Visual Experience Troubleshooting SCOPIA iVIEW Management Suite Version 7 5 RADVISION has your productivity and satisfaction in mind when creating this troubleshooting guide It is meant to provide quick answers to common problems concerning your video conferencing network operations This guide contains answers to problems that SCOPIA iVIEW Communications Manager administrators can utilize with minimal hassle The following sections might help you identify problems with your installation or configuration of iVIEW Communications Manager or related network components Resolving Browser Authentication 155 65 2 222 4 0 0 page 2 Connecting the iCM Microsoft Outlook Add on to
4. Collecting SCOPIA Desktop LOGS erre er nn mre meer em nme ie E eem a 5 Resolving User Experience 15565 2 4 6 6 Enabling Internet Explorer 5 2 6 Navigating Between 6 Configuring Maximum Time Period for Recurring 5 6 Correcting Web Page and Pop up Window Display sss 6 Resolving Administration Issues csse meme een nnns 7 Database 42 tert tr ER EY EXE ERE T dd 7 Using Double Byte Characters the MCU Service Template 7 Configuring Terminal Area Codes ore emen ec eR EE E Ra 7 Assigning DID NUIfDGrs sene toner rex en EE EX E RUE OE EXER EF eee 7 Resolving IVR Issues meme nenne nen nnn nnn 8 Resolving Virtual Service Issue sod ec e o PR Ra eR ERE VETT AAA ed 8 Resolving Video IVR Issue isse seeker ren ber e e E CC RR ERU HR E UC CR Rd 9 Resolving Auto Route Incoming Calls Issue sss 10 Resolving a Port Conflict isses meme meme nnn nnn n 11 Resolving a Sched ling Faillre teer e nr Eye CER ve 11 Resolving a Failed Terminal Invitation cccccccsecceeeeeeee nme 12 Resolving a Meeting Creation Failure
5. Solution If you are using Microsoft Windows XP SP2 or Windows 2003 Service Pack 1 and you enable Internet Explorer Pop up Blocker add the iVIEW Communications Manager site to the list of allowed sites Procedure Step 1 In the Internet Explorer window select Tools Internet Options Privacy Step 2 Select the Block Pop ups check box in the Pop up Blocker area Step 3 Select Settings Step 4 Enter the iVIEW Communications Manager site address and select Add Step 5 Select Close Step 6 Select OK Navigating Between Pages ECCE MM Problem Internet Explorer browser navigation buttons Back Forward and Refresh do not work correctly in the iVIEW Management Suite user interface Solution Use the Next and Back buttons in iVIEW Management Suite to navigate between pages Configuring Maximum Time Period for Recurring Meetings Problem You want to schedule recurring meetings for a period longer than that allowed in the iVIEW Management Suite Web user interface Solution Use the iVIEW Management Suite Configuration Tool to schedule recurring meetings for up to 730 days Correcting Web Page and Pop up Window Display E 0 0 h O CpppO 9A Problem Solution Some Web pages and pop up windows do not display normally Set the screen resolution to a standard resolution such as 800 x 600 pixels or 1024 x 768 pixels The minimum recommende
6. To determine which MCU is actually assigned to the meeting select Admin Resource Management MCU Select the required MCU in the MCU column on the Current tab In the Modify MCU window select Synchronize The MCU profile is updated Make sure the MCU registered gatekeeper is configured correctly Make sure the connection configuration in Admin gt Network Management IP Topology is correct Note TheNetwork Management section is hidden by default in iVIEW Communications Manager Use the iVIEW Communications ManagerConfiguration Tool to change default settings in the user interface Resolving a Failed Terminal Invitation MEME Problem Possible Causes Solution You are not able to invite a terminal to a meeting Incompatible gatekeeper registration The MCU may be registered to a gatekeeper that is different than the one specified in the MCU profile in iVIEW Communications Manager Perform the procedure in this section Step 1 Step 2 Possible Causes Solution Note Possible Causes Step 1 Step 2 Step 3 Step 4 Procedure In the MCU section of the SCOPIA MCU application check that the ECS that is listed is the same asthe one designated in iVIEW Communications Manager If the gatekeeper is not the same then in iVIEW Communications Manager select the same gatekeeper to which the MCU is registered Authorization failure ECS version 4 1 5 0 or later allows multiple iVIEW Communic
7. user so that iVIEW Communications Manager is a local Intranet site iVIEW Communications Manager automatically performs authentication using the domain account password credentials Connecting the iVIEW Microsoft Outlook Add on to iVIEW Communications Manager Problem Solution The iVIEW Communications Manager Microsoft Outlook Add on fails to connect to iVIEW Communications Manager After installing the iVIEW Communications Manager Microsoft Outlook Add on go to Tools Options iVIEW Management Suite Meetings and enter the URL of your server in the Web Site field Collecting Logs Collecting IVIEW Network Manager 1005 iiia eher tkt RR RR E ER ARE ERR E PCR page 3 Collecting SCOPIA Desktop LOGS iui eee cede Eis aud ra ED o EE E t page 5 Collecting iVIEW Network Manager Logs Viewing Logs for Selected Element i essere erre mc err Rente page 3 Defining iVIEW Network Manager Logging 21 n page 4 Element TE 4 Collecting Logs from a Cisco IOS 323 Gatekeeper page 5 Viewing Logs for a Selected Element Step 1 Step 2 Step 3 Step 4 Step 5 The information displayed on the Logs tab is dependent on the type of element that is selected in the tree A log of operations is not available for endpoints supported by the iVIEW Network Manager A log tab is not available
8. 3 If restarting the MCU does not resolve the issue contact your MCU service representative Resolving No Video Output Problem No video is seen during a call Solution In iVIEW Communications Manager Check iVIEW in meeting control and verify that the outgoing video channel is not blocked Check if video packet is sent out to this caller Resolving Poor Video Quality Problem End user computer is sending poor quality video Solution In iVIEW Communications Manager Ensure there is enough bandwidth and the correct codecs in In meeting control For software endpoints Ensure other applications do not occupy much CPU resources Resolving No Audio Output EH Problem No audio is heard during a call Solution In iVIEW Communications Manager First verify the endpoint s self audio For software endpoints play a clip to verify that audio can be heard Or for hardware endpoints play a p2p call to verify each endpoint can hear each other Check iVIEW Management Suite In Meeting Control to verify if the outgoing audio channel is blocked Verify that audio packets are sent out to this caller Check if audio column is very slow Synchronizing SCOPIA Desktop Server with iVIEW Management Suite Problem The Directory Status iVIEW Management Suite tab displays a synchronization error Solution Perform the procedure Procedure Step 1 Select the link on the Directory Status iVIEW Management Suite tab The Direc
9. 99 are free Run the netstat command in the DOS window to determine which applications if any occupy ports 11098 and 11099 Resolving a Scheduling Failure Problem In iVIEW Communications Manager in My Meetings or Meeting Monitoring on the Current tab if Failed appears if you Select Failed the message that opens reads Unableto create the meeting as scheduled Please check your meeting settings Solution A scheduling failure may occur if a meeting type is downloaded and then the meeting type is changed on the MCU but the iVIEW Communications Manager does not update the meeting types Step 1 Step 2 Step 3 Solution Step 1 Step 2 Step 3 Step 4 Step 5 Procedure To confirm that the reason for the failure is an incompatible meeting type select Admin Meeting Types and select Download If the meeting type that you specified appears in the Meeting Types Service Conflicts list the reason for the scheduling failure is at least in part an incompatible meeting type Note meeting is created even though the specified meeting type is incompatible there may be resource calculation errors To resolve the conflict repeat the download of the meeting type you require If actual MCU resources are changed after the MCU is added in iVIEW Communications Manager but iVIEW Communications Manager does not update or synchronize the actual MCU information then the result may be an incompatible MCU Procedure
10. SN is the industry s leading provider of market proven products and technologies for unified visual communications over IP and 3G networks With its complete set of standards based video networking infrastructure and developer toolkits for voice video data and wireless communications RADVISION is driving the unified communications evolution by combining the power of video voice data and wireless for high definition video conferencing systems innovative converged mobile services and highly scalable video enabled desktop platforms on IP 3G and emerging next generation networks For more information about RADVISION visit www radvision com USA Americas EMEA APAC T 1 201 689 6300 T 444 20 3178 8685 T 4852 3472 4388 F 1 201 689 6301 F 444 20 3178 5717 F 4852 2801 4071 infoUSA radvision com infoUK radvision com infoAPAC radvision com This document is not part of a contract of license as may be expressly agreed RADVISION is registered R ADVI S O N trademarks of RADVISION Ltd All trademarks recognized All rights reserved 2010 RADVISION Ltd Delivering the Visual Experience 9
11. W Communications Manager as a local Intranet site and an authentication window appears Solution Provide users with a link to iVIEW Management Suite that includes the necessary fully qualified domain name FDQN rather than only the iVIEW Communications Manager IP address Configure the browser for the user so that iVIEW Communications Manager is a local Intranet site Enabling Single Sign on B B Problem iVIEW Management Suite web pages always require that you enter a user name and password Solution Use Single Sign on SSO SSO enables usersto access iVIEW Management Suite web pages without having to enter a user name or password Users are authenticated transparently using domain account and password credentials To enable Single Sign on during installation select the Single Sign on check box You must also add the iVIEW Management Suite host server to the trusted site of the client browser Configuring Outlook Add on for Single Sign on h 9 Problem iVIEW Communications Manager authentication fails when working with SSO and iVIEW Communications Manager Microsoft Outlook Add on Solution Perform the procedure in this section Procedure Step 1 Select Tools Options iVIEW Management Suite Meeting Settings Step 2 Enter a link to iVIEW Management Suite that includes the necessary fully qualified domain name FDQN rather than only the Resource Manager IP address Step 3 Configure the browser for the
12. ations Manager to connect as authorizer However if multiple iVIEW Communications Manager authorizes a single ECS the iVIEW Communications Manager ECS authorization logic does not work Ensure that each ECS has only one iVIEW Communications Manager as its authorizer If multiple iVIEW Communications Manager authorizes a single ECS remove all other iVIEW Communications Manager authorization connections and then restart ECS Only after this does the remaining iVIEW Communications Manager work with this ECS properly in authorization mode iVIEW Communications Manager initiates the authorization connection to the ECS Ensure that the ECS server SNMP Community names are set correctly in the iVIEW Communications Manager user interface Unconnected IP location at Network Management gt Topology for the MCU and a terminal If a meeting is set up on the MCU that belongs to a specific location defined at Network Management gt IP Topology a terminal is invited to a different location the location to which the MCU is assigned may not be able to connect to the location to which the terminal is assigned Procedure In iVIEW Communications Manager on the IP Topology tab check that there isa link between the two different locations Make sure that if there is a connection that Bandwidth and Location are correctly defined Alternatively assign the MCU and the terminal to the same location Make sure that the gatekeeper that the terminal is a
13. ber Type Phone number Select Upload Navigate to Gatekeeper Services Services tab Select Add Configure settings as follows Prefix Your auto virtual services prefix number Prefix type phone number Description Virtual Services e Conference Hunting Enabled e Global Service No e Allow access for n zone non predefined endpoints enabled Out of zone endpoints enabled Select Upload Resolving Video IVR Issue E J 1 Problem Solution Step 1 Step 2 Step 3 If iVIEW Management Suite is in a standalone mode and a user is configured with an auto attendant number on iVIEW Management Suite only a call to the auto attendant number is not routed to Video IVR Perform the procedure in this section Procedure Login to SCOPIA ECS Gatekeeper Navigate to Gatekeeper gt Endpoints gt Endpoints tab Select Add Predefined Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Configure settings as follows Endpoint type Terminal Registration IP 127 0 0 1 Port 0 Call signaling IP 127 0 01 Port 0 Aliases VR Number Type Name Your auto attendant number Type Phone number Select Upload Navigate to Gatekeeper Services Services tab Select Add Configure settings as follows Prefix Your auto attendant number Prefix type phone number Description End Point e Conference Hunting Enabled Global Service No e Al
14. d resolution is 800 x 600 pixels and the recommended font size is Normal or Large Resolving Administration Issues Database Unavailable Problem Solution No database is available when iVIEW Management Suite is initially started Restart the service when the database is ready If the connection between the database and iVIEW Management Suite is lost after initially starting iVIEW Management Suite iVIEW Management Suite works normally when the database is operating Using Double Byte Characters in the MCU Service Template Problem Solution Unicode and other double byte characters such as Chinese J apanese Korean and Hebrew characters cause device exception in MCU service template Name Description Terminal Name and Gateway Service Prefix fields Use only ASCII text in these fields Configuring Terminal Area Codes Problem Solution Terminal area codes are incorrectly defined Do not include domestic long distance prefixes in terminal area codes Assigning DID Numbers gH h A3 V Problem Solution Step 1 Step 2 Step 3 Step 4 Step 5 Cannot change Direct Inward Dialing DID numbers DID numbers are assigned on a per endpoint basis rather than on a per meeting basis This is an internal configuration that cannot be changed via the Configuration Tool or the iVIEW Management Suite Web interface To manually change the host name perform the fol
15. ect Upload to save your changes Collecting Logs from a Cisco IOS 323 Gatekeeper Element Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Step 11 Step 12 Step 13 Procedure Select Network Tree in the sidebar menu Select the Cisco 105 H 323 Gatekeeper you require in the tree Select Debug Flags Select Add Enter debug ip icmp in the Debug Command field to generate traffic and confirm logging is configured properly Enter Enable ip icmp debugging in the Description field Select Enable Select OK A new alarm appears in the Alarms tab Select Logs Select Save logs Enter a file name and set the log level to Debugging Ping the Cisco IOS H 323 Gatekeeper to generate traffic to capture logs Select Open log view to verify the result Collecting SCOPIA Desktop Logs E LS Step 1 Step 2 Step 3 Procedure Access the SCOPIA Desktop Server Select the Conference Server icon on the taskbar to view the log in the Console window If necessary save the log files located at these locations C Program Files Radvision SCOPIA Desktop ConfSrv cs log e C Program Files Radvision SCOPIA Desktop logs xml e C Program Files SCOPIA Desktop tomcat logs stdout log stderr log Resolving User Experience Issues Enabling Internet Explorer Pop ups 000000 MM Problem Internet Explorer Pop up Blocker blocks pop ups for the SCOPIA iVIEW Communications Manager site
16. for endpoints when selected in the Network Tree view Procedure Select Network Tree in the sidebar menu Select the required network element Select Logs Define the log details for the selected network element Select Open log view to view the logs directory for the selected network element If you are viewing logs for ECS select Open elements logs directory Defining iVIEW Network Manager Logging Activity Procedure Step 1 Select Settings in the sidebar menu Step 2 Select Logging Step 3 Select Network Manager Logs Step 4 Select Save iView Manager log to enable logging Step 5 Optional Define the log file name the maximum file size the number of backup files to maintain and the level of log detail in the relevant fields The maximum log file size is 5 120 KB The maximum number of log files is 50 iVIEW Network Manager Step 6 Select the View log directory link to view a list of links to log files for iVIEW Network Manager and managed network elements Step 7 Select Upload to save your changes Saving Element Logs iVIEW Network Manager can locally save log files for those elements such as MCUs SCOPIA PathFinder Servers and Gateways that do not maintain a log of their own Procedure Step 1 Select Settings in the sidebar menu Step 2 Select Logging Step 3 Select Element Logs Step 4 Define the maximum size of each log file and the number of backup files to maintain in the Step 5 relevant fields Sel
17. ited States and other territories registered trademarks recognized For further information contact RADVISION or your local distributor or reseller Troubleshooting Guide for SCOPIA iVIEW Management Suite Version 7 5 September 2010 http www radvision com F DAIS ON SCCJPIA Delivering the Visual Experience 9 Table of Contents Troubleshooting SCOPIA iVIEW Management Suite Version 7 5 gt Y H eni e M 1 Resolving Browser Authentication 155 65 2 1 2 Recognizing a Local Intranet 51 ene ree kb e 2 Enabling Single qe VER RO EE CQ a 2 Configuring Outlook Add on for Single 519 0 2 Connecting the iCM Microsoft Outlook Add on to 4 4 6 2 2 2 1 3 Collecting LOGS erret ene Yr Peu EE CR Pd vie HE er Aaa 3 Collecting iVIEW Network Manager 1005 2 200100 mn 3 Viewing Logs for a Selected 3 Defining iVIEW Network Manager Logging 4 Saving Element 1005 2 22 memes nnne nn nnn 4 Collecting Logs from a Cisco IOS H 323 Gatekeeper 5
18. low access for n zone non predefined endpoints enabled Out of zone endpoints enabled Select Upload Resolving Auto Route Incoming Calls Issue E i Problem Solution Step 1 Step 2 Step 3 If iVIEW Management Suite is in the standalone mode and a user is configured with auto route incoming calls only on iVIEW Management Suite a call cannot be routed to Video IVR when the user calls an auto route incoming call number Perform the procedure in this section Procedure Login to SCOPIA ECS Gatekeeper Navigate to Gatekeeper gt Endpoints gt Endpoints tab Select Add Predefined Step 4 Configure settings as follows e Endpoint type Terminal Registration IP 127 0 0 1 Port 5 Call signaling IP 127 0 01 Port 5 Aliases Value Routing Number Type Name Value Your auto route incoming calls number Type Phone number Step 5 Select Upload Step 6 Navigate to Gatekeeper Services Services tab Step 7 Select Add Step 8 Configure settings as follows Prefix Your auto route incoming calls number Prefix type phone number Description Virtual Services e Conference Hunting Enabled e Global Service No e Allow access for n zone non predefined endpoints enabled Out of zone endpoints enabled Step 9 Select Upload Resolving a Port Conflict Problem A port conflict occurs when you try to install or run certain applications Solution Ensure that ports 11098 and 110
19. lowing procedure Procedure Go to C Program Files RADVISIONNiVIEW Suite iCM jboss bin where C is the local drive Make a backup copy of the vcs config xml file Open the vcs config xml file with a text editing tool and modify the host url element to the required value Save the file in the text editor Restart iVIEW Management Suite Resolving IVR Issues Resolving Virtual Service ISSUE Lisa eeu eret ebria Reb i E ERR Rr PRO dra page 8 video IVE ISSUE RR DRE page 9 Resolving Auto Route Incoming Calls Issue 1 page 10 Resolving Virtual Service Issue NR nnne Problem Solution Step 1 Step 2 Step 3 If iVIEW Management Suite is in the standalone mode and a user is configured with a virtual services prefix only on iVIEW Management Suite a call cannot be routed to Video IVR when the user calls a virtual conference ID Perform the procedure in this section Procedure Login to SCOPIA ECS Gatekeeper Navigate to Gatekeeper gt Endpoints gt Endpoints tab Select Add Predefined Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Configure settings as follows e Endpoint type Terminal Registration IP 127 0 0 1 Port 1719 e Call signaling IP 127 0 01 Port 1719 Aliases Value Virtual Services Type Name Value Your auto virtual services prefix num
20. sktop Server components with its new IP address Procedure Step 1 Select Start Settings Control Panel Step 2 Double select Add or Remove Programs Step 3 From the list of programs choose SCOPIA Desktop and then Change The Setup Wizard opens Step 4 In the Welcome screen select Next Step 5 In the Program Maintenance screen choose Modify and select Next Step 6 In the Custom Setup screen select Next Step 7 In the SCOPIA Desktop Serial Key screen select Next Step 8 In the SCOPIA Desktop Network Configuration screen select Next Step 9 In the SCOPIA Desktop Hostname Configuration screen select Next Step 10 In the SCOPIA Desktop Recording Configuration screen select Next Step 11 Select Install Recording Does Not Start Automatically Problem iVIEW Management Suite configured to work with the SCOPIA Desktop Server does not record virtual room meetings or scheduled meetings automatically even though iVIEW Management Suite is configured to do so Solution Verify that one of the following problems does not interfere with recording There are not enough available recording ports on the SCOPIA Desktop at the time when the meeting is scheduled The maximum number of simultaneous recordings is reached Make sure that the Allow virtual rooms and scheduled meetings to be recorded automatically option is enabled on the SCOPIA Desktop Administration web user interface About RADVISION RADVISION NASDAQ RV
21. ssigned to is in Authorization Mode Note Cascading is set up in iVIEW Communications Manager in the Network Management section on the IP Topology tab If the IP Topology tab is hidden in the iVIEW Management Suite Configuration Tool in System Configuration gt UI Settings check IP Topology to activate the IP Topology tab Resolving a Meeting Creation Failure Problem A meeting is successfully scheduled but cannot actually be created Procedure Step 1 Make a point to point call Step 2 Ensure that the call is successful from within iVIEW Communications Manager A successful point to point call indicates that the ECS and iVIEW Communications Manager are configured correctly Step 3 Create an endpoint initiated MCU conference If the endpoint connects the MCU ECS and iVIEW Communications Manager are configured properly Schedule a meeting in iVIEW Communications Manager If the meeting is scheduled successfully wait for the meeting to start If the meeting starts successfully dial into the meeting using an endpoint Solution In the event that the troubleshooting procedures in this section do not resolve a meeting creation or meeting invitation issue use the procedure in this section Procedure Step 1 Attempt the same meeting creation or invitation directly on the MCU without using the iVIEW Communications Manager Step 2 If the same meeting creation or invitation does not succeed directly on the MCU restart the MCU Step
22. tory tab opens Step 2 Select the Synchronize button Updating the IP Address on the Streaming Server P iuc aid pM E Problem The SCOPIA Desktop Status tab indicates that the Streaming Server is not connected If you select the Streaming Server indicator this error is displayed 5003 Access denied error from proxy Solution When the Streaming or Recording components of SCOPIA Desktop are installed on their own server separately from the SCOPIA Desktop Server they are configured with the IP address of the SCOPIA Desktop Server which is allowed to connect to them If the IP address of the SCOPIA Desktop Server changes you need to update it on the Streaming and Recording Servers Procedure Step 1 From the Start menu choose Programs SCOPIA Desktop TCP Proxy Configuration Step 2 Run the listServers command to display the address of the SCOPIA Desktop Server which is allowed to access the Streaming or Recording Server Step 3 If the SCOPIA Desktop Server address is incorrect run the removeServer command to remove it Step 4 Run the addServer command to add the correct address Step 5 Follow on screen directions to complete the procedure Changing IP Address of the SCOPIA Desktop Server Problem The SCOPIA Desktop Status tab indicates that the SCOPIA Desktop Server is not connected Solution If the IP address of the server on which the SCOPIA Desktop Server is installed changes you need to update SCOPIA De
Download Pdf Manuals
Related Search