Step 1 Check the network connection between the PC used by the
teller and the UAP. If the network malfunctions, contact the network
administrator.
Step 2 Log in to the UAP and run the show ctinfo command to
check the connection between the UAP and CTI-Link.
If the UAP3300 is used,
run the show ctinfo command to verify the connection between the UAP and
CTI-Link.
If values of CTISTATE are MASTER_SERVER and SLAVE_SERVER, the UAP
is correctly connected to the CTI-Links. (In this example, the CTI-Links are
deployed in active/standby mode.)
[%UAP3300(config)]#show ctinfo
CTI
Information
CTIID GROUPID CTIIP CTIPORT CTISTATE
----- -------
--------------- ------- -------------
0 0 192.165.1.12 5600
MASTER_SERVER
1 0 192.165.1.13 5600 SLAVE_SERVER
If the
U2980 is used, run the DSP MEMLNK: MN=40; command to verify the connection
between the UAP and the CTI-Link. In the command, 40 is the IFM module
ID.
When information similar to the following is displayed, the UAP is
correctly connected to the CTI-Links. (The value of CTI connection status is
Connected as long as the UAP is connected to one of the active and standby
CTI-Links.)
Display the MEM link status
----------------------
MEM link number = 0
Service device ID = 0
IFM module
number = 40
Protocol type = FEP
Service type
= NULL
Support unlimited access codes = Correct
Intess protocol
version = IntessV514
Active connection index = Remote IP1
Socket connection status = Connected
Standby Socket connection status =
Connected
CTI connection status = Connected
(Results = 1)
Step
3 Verify that the eSpace Meeting server is running properly.
1. Log in to the
active and standby nodes of the eSpace Meeting server as the econf user.
2.
Run the ps -ef |grep econf command to check running processes.
− If the
following information is displayed on the active and standby nodes, the eSpace
Meeting server is running properly.
− Active node:
econf 23678 22977 0
14:40 pts/0 00:00:00 grep econf
econf 24447 1 0 11:21 ?
00:01:45 mcsagt
econf 24448 1 1 11:21 ? 00:03:10
mcmgw
econf 24449 1 0 11:21 ? 00:01:26 mccaches
econf
24450 1 1 11:21 ? 00:03:07 mcms
econf 24588 1 0 11:22
? 00:00:32 icdcomm
econf 24645 1 0 11:22 ? 00:00:39
idcenter
econf 24656 1 0 11:22 ? 00:00:39 idagent
econf
24701 1 1 11:22 ? 00:02:46 lom
econf 24742 1 0 11:22
? 00:00:41 configDaemon -d
econf 24758 1 0 11:22 ?
00:00:41 namingDaemon -d
econf 24777 1 0 11:22 ? 00:00:41
toolDaemon -d
econf 24800 1 0 11:22 ? 00:00:41 idlproxy
-d
econf 24887 1 0 11:22 ? 00:00:59 container 0 -d
econf
24997 24887 1 11:22 ? 00:03:30 container 1 -n -d
econf 24998
24887 0 11:22 ? 00:00:43 LicenseService 55 -n -d
econf 24999
24887 0 11:22 ? 00:00:42 CDRServer 303 -n -d
econf 25000 24887 8
11:22 ? 00:16:18 SDU 401 -n -d
econf 25001 24887 0 11:22 ?
00:00:54 eSpaceMeetingLicense 555 -n -d
− Standby node:
econf
1681 1 0 08:42 ? 00:00:21 mcsagt
conf 1683 1 1 08:42
? 00:01:42 mcmgw
econf 1684 1 0 08:42 ? 00:00:32
mccaches
econf 1685 1 1 08:42 ? 00:01:56 mcms
If the
proceeding information is not displayed, perform the following operations as the
econf user:
− On the active node, run the following commands to start the
license management platform and eSpace Meeting server:
start.sh -a
cd
/home/econf/ms/bin
sh run.sh
− On the standby node, run the following
commands to start the eSpace Meeting server:
cd /home/econf/ms/bin
sh
run.sh
3. Run the p command to view the status of the AS process.
The
AS service is started on only one server of the eSpace Meeting two-node cluster.
You only need to check the status of the AS process on the server that has the
AS service started.
If information similar to the following is displayed, the
AS process is running properly.
UID PID PPID C STIME
TTY TIME ALIASNAME
econf 24588 1 0 11:22 ?
00:00:39 icdcomm
econf 24645 1 0 11:22 ?
00:00:49 idcenter
econf 24656 1 0 11:22 ?
00:00:48 idagent
econf 24701 1 1 11:22 ?
00:03:21 lom
econf 24742 1 0 11:22 ?
00:00:51 configDaemon
econf 24758 1 0 11:22 ?
00:00:51 namingDaemon
econf 24777 1 0 11:22 ?
00:00:51 toolDaemon
econf 24800 1 0 11:22 ?
00:00:51 idlproxy
econf 24887 1 0 11:22 ?
00:01:13 container 0
econf 24997 24887 1 11:22 ?
00:04:19 container 1
econf 24998 24887 0 11:22 ?
00:00:53 LicenseService 55
econf 24999 24887 0
11:22 ? 00:00:52 CDRServer 303
econf 25000 24887 8
11:22 ? 00:20:09 SDU 401
econf 25001 24887 0
11:22 ? 00:01:06 eSpaceMeetingLicense 555
econf 25002
24887 0 11:22 ? 00:01:05 eSpaceMeetingCbu 599
econf
25003 24887 0 11:22 ? 00:00:55 eSpaceMeetingCmu 600
econf 25004 24887 0 11:22 ? 00:01:00 eSpaceMeetingFocus
601
econf 25005 24887 6 11:22 ? 00:15:51
eSpaceMeetingCru 602
econf 25006 24887 6 11:22 ?
00:16:03 eSpaceMeetingPtcpt 603
econf 25007 24887 0
11:22 ? 00:01:49 eSpaceMeetingMSRC 604
Step 4 Verify that the MCC
server is running properly.
1. Log in to the active and standby nodes as the
Elpis user.
2. Run the ps -eaf | grep java command to check whether the
Tomcat service is running properly.
If the following information is
displayed, the Tomcat service is running properly:
Elpis 10164 1 0
Nov08 ? 00:51:20
/home/Elpis/tomcat6/../jdk/jre/bin/java
-Djava.util.logging.config.file=/home/Elpis/tomcat6/conf/logging.properties
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Xmx1024m
-XX:MaxPermSize=192m -Xss128k -server -XX:+UseParallelGC
-XX:SurvivorRatio=4
-Djava.library.path=/home/Elpis/tomcat6/native/linux
-Djava.awt.headless=true
-XX:+HeapDumpOnOutOfMemoryError
-Duser.dir=/home/Elpis/tomcat6/bin
-Djava.endorsed.dirs=/home/Elpis/tomcat6/endorsed
-classpath
/home/Elpis/tomcat6/bin/bootstrap.jar
-Dcatalina.base=/home/Elpis/tomcat6
-Dcatalina.home=/home/Elpis/tomcat6
-Djava.io.tmpdir=/home/Elpis/tomcat6/temp
org.apache.catalina.startup.Bootstrap start
Elpis 15816 15772 0 14:24
pts/1 00:00:00 grep java
If the proceeding information is not
displayed, run the following commands as the Elpis user to start the daemon
process for it to start the Tomcat service:
cd
/home/Elpis/tomcat6/bin
./mcc_daemon.sh start &
Step 5 Check whether
the fault is rectified.
If the fault is rectified, the troubleshooting
ends.
If the fault persists, contact Huawei technical
support.
