Presentation is loading. Please wait.

Presentation is loading. Please wait.

Call Routing Application #1

Similar presentations


Presentation on theme: "Call Routing Application #1"— Presentation transcript:

1 Call Routing Application #1
System Topology vms/applications on WAS#2-lab. vms/applications on WAS#1-lab. Call Routing Application #1 6*AESconncter is working on WAS#2-lab 9*AESconncter is working on WAS#1-lab TBM TAI 6 BUC vms/applications TBM TAI 9 BUC AESC TBM AESC TAI AESC BUC AESC AESC TBM AESC TAI AESC BUC AESC AESC AESconnecter 9 6 Primary Tlink for AESConnectors failover Tlink for AESConnectors AES1-lab. AES2-lab. c-lan c-lan c-lan c-lan CM-duplex, server1 CM-duplex, server2

2 events in our test 2. test-call 3. test-call 5. test-call TBM TAI VISA
BUC TBM TAI VISA BUC 4. reboot 4. reboot AESC TBM AESC TAI AESC VISA AESC BUC AESC TBM AESC TAI AESC VISA AESC BUC vms/applications on WAS1-lab. vms/applications on WAS2-lab. 7. Stop 6. Stop c-lan c-lan 8. Start 9. Start AES1-lab. AES2-lab. c-lan c-lan 1. outage CM-duplex, server1 CM-duplex, server2 20:00-21:00 9/27, 5-10 minutes cm outage 9:20-11:50 9/28, Incoming calls which played BUC application completed cti-blindcall but the calls were disconnected 3 seconds later. DDSESSIONID=Nn6i_d-fiQaZYTRLodRBnal, Session ID=kccspi2f , Start Time=9/28/16 11:08:01 AM 9:20-19:50 9/28, Incoming calls which played TBM application completed cti-blindcall. Caller heard ring-back-tone little time but the call received no audio later. Caller continued to have silent-call. DDSESSIONID=qTNeQODId95ks5-u-WULAGu, Session ID=kccspi2f , Start Time=9/28/16 7:34:30 PM 11:50-12:30 9/28, Rebooting BUC-vms on WAS1/WAS2. 12:30-19:50 9/28, Incoming calls which played BUC application couldn’t completed cti-blindcall. It started and completed cti-hold, pre-action for cti-blindcall, but next action didn’t start later. Caller continued to hear hold-music. DDSESSIONID=uFjx9zhqUHvYU5Tg7OrhNiA, Session ID=kccspi1f , Start Time=9/28/16 1:52:23 PM 19:51:30 9/28, System Platform Web Console > Virtual Machine Management > Manage > Application Enablement Services > Stop in AES2. 19:54:30 9/28, System Platform Web Console > Virtual Machine Management > Manage > Application Enablement Services > Stop in AES1. 20:01:30 9/28, System Platform Web Console > Virtual Machine Management > Manage > Application Enablement Services > Start in AES1. 20:06:00 9/28, System Platform Web Console > Virtual Machine Management > Manage > Application Enablement Services > Start in AES2. 20:10 and later 9/28, All calls which played BUC and TBM application had no error. CTI-blindcalls were completed normaly.

3 # of ACS stream on AES Management Console
During CM outage After AES restart

4 Attached Files aes1: log.20160928 sec.20160928
/opt/mvap/logs/common/trace.out (trace.out.old *.gz) /opt/mvap/logs/TSAPI/csta_trace (csta_trace-129.trace.out.old *.gz) /opt/mvap/logs/TSAPI/g3trace (g3trace-cmr16-1.trace.out.old *.gz) beforerebooting_aes1.png (screenshot fo opend streams) afterrebooting_aes1.png (screenshot fo opend streams) aes2: beforerebooting_aes2.png (screenshot fo opend streams) afterrebooting_aes2.png (screenshot fo opend streams) od-trace: TBM-OD-trace.log.gz BUC-OD-trace.log.gz aesconnector-trace: TBM-aescon-trace.log.gz BUC-aescon-trace.log.gz jtapi-trace: tsapi_trace.txt.CCSWebServer11*.gz (trace for TBM application) tsapi_trace.txt.CCSWebServer14*.gz (trace for BUC application) epm: contactdetail.xls sessiondetail.xls


Download ppt "Call Routing Application #1"

Similar presentations


Ads by Google