How to check on your Avaya CRM Connector
This article will show you how to verify that your Avaya CRM connector is functioning and healthy

Description

This article assumes that you have a root-level login or a login that has permissions to run the commands outlined in this article. These are commands are meant to give you a snapshot of the type of data you should see on your Avaya CRM Connector server.

Steps

Below are the Linux commands used in this article

docker ps
docker exec -it avayacrmconnector_iec-app_1 netstat -natp | grep 8483 | grep ESTABLISHED
echo | openssl s_client -connect 127.0.0.1:8484 | openssl x509 -text | head
/opt/avaya/avayacrmconnector ; docker-compose logs --tail=1500 iec-app | grep -i MakeCallCommand | less

Output of docker ps we should see output similar to the following.

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

f7b6cd983b6e rabbitmq:3-management "docker-entrypoint..." 4 months ago Up 6 weeks 4369/tcp, 5672/tcp, 15671/tcp, 25672/tcp, 0.0.0.0:5673->5671/tcp, 0.0.0.0:15673->15672/tcp avayacrmconnector_rabbitmq2_1

c644998fefb2 aa4salesforce "/bin/sh -c 'echo ..." 4 months ago Up 6 weeks 5701/udp, 8084/tcp, 0.0.0.0:8484->8484/tcp avayacrmconnector_aa4salesforce-app_1

b00cf225bc77 aes3pcc "/bin/sh -c 'echo ..." 4 months ago Up 6 weeks 5701/udp, 8082/tcp avayacrmconnector_aes3pcc-app_1

a971054b6177 jkarlos/git-server-docker "sh /git-server-mo..." 4 months ago Up 6 weeks 0.0.0.0:2222->22/tcp avayacrmconnector_git-server_1

9917cd008341 consul:0.9.3 "docker-entrypoint..." 4 months ago Up 6 weeks 0.0.0.0:8300->8300/tcp, 8301-8302/udp, 0.0.0.0:8500->8500/tcp, 0.0.0.0:8600->8600/tcp, 8301-8302/tcp, 8600/udp avayacrmconnector_consul_1

a47ecbc80cf1 rabbitmq:3-management "docker-entrypoint..." 4 months ago Up 6 weeks 4369/tcp, 5672/tcp, 0.0.0.0:5671->5671/tcp, 15671/tcp, 25672/tcp, 0.0.0.0:15672->15672/tcp avayacrmconnector_rabbitmq1_1

d798c7ddf8a4 jhipster/consul-config-loader:v0.2.2 "sh /config/load-c..." 4 months ago Up 6 weeks avayacrmconnector_consul-config-loader_1

9566b5d20000 iec "/bin/sh -c 'echo ..." 4 months ago Up 6 weeks 5701/udp, 8083/tcp, 0.0.0.0:8483->8483/tcp avayacrmconnector_iec-app_1


Verify java processes are running

docker exec -it avayacrmconnector_iec-app_1 netstat -natp | grep 8483 | grep ESTABLISHED here we are looking for several connected Java processes as shown below.

tcp 0 0 ::ffff:10.18.0.2:8483 ::ffff:10.2.224.131:59955 ESTABLISHED 1/java

tcp 0 0 ::ffff:10.18.0.2:8483 ::ffff:10.2.224.40:55871 ESTABLISHED 1/java

tcp 0 0 ::ffff:10.18.0.2:8483 ::ffff:10.2.224.131:59952 ESTABLISHED 1/java

tcp 0 580 ::ffff:10.18.0.2:8483 ::ffff:10.2.13.181:57717 ESTABLISHED 1/java

tcp 0 0 ::ffff:10.18.0.2:8483 ::ffff:10.2.224.56:57065 ESTABLISHED 1/java

tcp 0 0 ::ffff:10.18.0.2:8483 ::ffff:10.2.10.33:57963 ESTABLISHED 1/java

tcp 0 0 ::ffff:10.18.0.2:8483 ::ffff:10.2.224.70:53104 ESTABLISHED 1/java

tcp 0 0 ::ffff:10.18.0.2:8483 ::ffff:10.2.224.224:60551 ESTABLISHED 1/java

tcp 0 0 ::ffff:10.18.0.2:8483 ::ffff:10.2.13.181:57700 ESTABLISHED 1/java

tcp 0 729 ::ffff:10.18.0.2:8483 ::ffff:10.2.13.181:57698 ESTABLISHED 1/java

tcp 0 0 ::ffff:10.18.0.2:8483 ::ffff:10.2.10.33:57844 ESTABLISHED 1/java

tcp 0 0 ::ffff:10.18.0.2:8483 ::ffff:10.2.224.224:60103 ESTABLISHED 1/java


Verifying our Certificate

Output of the echo | openssl s_client -connect 127.0.0.1:8484 | openssl x509 -text | head command below checking the product certificate to ensure it has not expired.

root@avayacrm ~]# echo | openssl s_client -connect 127.0.0.1:8484 | openssl x509 -text | head
depth=0 C = US, ST = Massachusetts, L = Boston, O = Acme Corp, CN = avayacrm.acmecorp.com
verify error:num=20:unable to get local issuer certificate
verify return:1
depth=0 C = US, ST = Massachusetts, L = Boston, O = Acme Corp, CN = avayacrm.acmecorp.com
verify error:num=21:unable to verify the first certificate
verify return:1
DONE
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
5f:00:00:40:00:7d:37:89:0a:63:ed:c8:e9:00:01:00:00:40:00
Signature Algorithm: sha512WithRSAEncryption
Issuer: DC=acmecorp, DC=corp, DC=ops, CN=CAISSUE-SRV
Validity
Not Before: Jan 19 17:51:05 2019 GMT
Not After : Jan 18 17:51:05 2021 GMT


Viewing the logs for call attempts

Running the docker-compose logs --tail=1500 iec-app | grep -i MakeCallCommand first run cd /opt/avaya/avayacrmconnector this will show the extension number and the number they tried to call using the CRM connector.

docker-compose logs --tail=1500 iec-app | grep -i MakeCallCommand
iec-app_1 | 2020-07-31 15:30:22.559 INFO 1 --- [tp1232204889-80] c.a.e.c.a.i.a.c.c.e.MakeCallCommand : MakeCallCommand: station 8509 - numberToDial 917487865098
iec-app_1 | 2020-07-31 15:33:35.013 INFO 1 --- [tp1232204889-78] c.a.e.c.a.i.a.c.c.e.MakeCallCommand : MakeCallCommand: station 8509 - numberToDial 917489218860
Was this article helpful?
Cancel
Thank you!