call waiting issue

Added by Hari Shankar almost 11 years ago

hello friends,
i am very new to this dialer and having a very tough time while working on it. below is my server configuration:
Asterisk MySql Apache eth0 eth1

System Vital
Canonical Hostname 192.168.1.211
Listening IP 192.168.1.211
Kernel Version 2.6.18-238.9.1.el5.goPAE (SMP)
Distro Name GoAutoDial CE 2.1
Uptime 2 hours 1 minutes
Current Users 2
Load Averages 0.28 0.36 0.37
0%

Network Usage
Device Received Sent Err/Drop
lo 147.74 MB 147.74 MB 0/0
eth0 0.00 KB 0.00 KB 0/0
eth1 182.81 MB 251.26 MB 0/0
usb0 196.28 KB 69.42 KB 0/0
bond0 182.81 MB 251.26 MB 0/0

Hardware Information
Processors 4
Model Intel(R) Xeon(R) CPU E5607 @ 2.27GHz
CPU Speed 2.27 GHz
Cache Size 8.00 MB
System Bogomips 18134.13
PCI Devices
- (2x) Ethernet controller: Broadcom Corporation NetXtreme II BCM5716 Gigabit Ethernet
- Host bridge: Intel Corporation 5520 I/O Hub to ESI Port
- IDE interface: Intel Corporation 82801JI 2 port SATA IDE Controller #2
- IDE interface: Intel Corporation 82801JI 4 port SATA IDE Controller #1
- ISA bridge: Intel Corporation 82801JIB LPC Interface Controller
- PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1
- PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3
- PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7
- PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 8
- PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 9
- PCI bridge: Intel Corporation 5520/X58 I/O Hub PCI Express Root Port 5
- PCI bridge: Intel Corporation 82801 PCI Bridge
- PCI bridge: Intel Corporation 82801JI PCI Express Root Port 1
- PCI bridge: Intel Corporation 82801JI PCI Express Root Port 5
- PCI bridge: Vitesse Semiconductor VSC452 [SuperBMC]
- PIC: Intel Corporation 5520/5500 Physical and Link Layer Registers Port 1
- PIC: Intel Corporation 5520/5500 Routing & Protocol Layer Register Port 1
- PIC: Intel Corporation 5520/5500/X58 I/O Hub Control Status and RAS Registers
- PIC: Intel Corporation 5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers
- PIC: Intel Corporation 5520/5500/X58 I/O Hub System Management Registers
- PIC: Intel Corporation 5520/5500/X58 I/O Hub Throttle Registers
- PIC: Intel Corporation 5520/5500/X58 Physical and Link Layer Registers Port 0
- PIC: Intel Corporation 5520/5500/X58 Routing and Protocol Layer Registers Port 0
- PIC: Intel Corporation 5520/5500/X58 Trusted Execution Technology Registers
- RAID bus controller: LSI Logic / Symbios Logic LSI MegaSAS 9260
- SMBus: Intel Corporation 82801JI SMBus Controller
- (8x) System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device
- USB Controller: Intel Corporation 82801JI USB UHCI Controller #1
- USB Controller: Intel Corporation 82801JI USB UHCI Controller #2
- USB Controller: Intel Corporation 82801JI USB UHCI Controller #3
- USB Controller: Intel Corporation 82801JI USB UHCI Controller #4
- USB Controller: Intel Corporation 82801JI USB UHCI Controller #5
- USB Controller: Intel Corporation 82801JI USB2 EHCI Controller #1
- USB Controller: Intel Corporation 82801JI USB2 EHCI Controller #2
- VGA compatible controller: Matrox Graphics, Inc. MGA G200EV
IDE Devices none
SCSI Devices
- HL-DT-ST DVDROM DH40N (CD-ROM)
- IBM ServeRAID M5014 (Direct-Access)
USB Devices
- (2x) IBM Corp.
- Motorola Semiconductors HK, Ltd

Memory Usage
Type Percent Capacity Free Used Size
Physical Memory 11% 10.60 GB 1.27 GB 11.87 GB
- Kernel + applications 2% 186.55 MB
- Buffers 2% 239.88 MB
- Cached 7% 878.42 MB
Disk Swap 0% 1019.74 MB 0.00 KB 1019.74 MB

Mounted Filesystems
Mount Type Partition Percent Capacity Free Used Size
/boot ext3 /dev/sda1 12% (3%) 82.05 MB 11.57 MB 98.72 MB
/ ext3 /dev/sda2 76% 165.75 GB 687.13 GB 899.29 GB
/dev/shm tmpfs tmpfs 0% (1%) 5.94 GB 0.00 KB 5.94 GB
Totals : 76% 171.76 GB 687.14 GB 905.32 GB ==================================================================================
My main problem is up to this morning calls were landing properly in every campaign, but now calls are not coming. i mean when we log in to any campaign up to 2 - 3 minutes everything is ok after that the call waiting time keeps rising from 3 -6 minutes. when resetting the hoppers and closing the campaign we see this kind of screen continuously. i am in serious shit friends . so please help me and give some advices.

call_issue.JPG (120 KB) call_issue.JPG

call placing screen after 30 minutes of hopper reset and closing the campaign.

Replies (8)

RE: call waiting issue - Added by striker 247 almost 11 years ago

as the screen shots shows that there is no agents while dailling ,, or u force logging out the agent while calls being placed.

more over the details which u provided is not enough to analys ur issue.

1. make sure the hopper level is set to 500 or above based on ur agents availability. as hopper will reload every minute to fill the hopper level.
2. check the asterisk cli , whether the calls are being dialled without any trunk error or any other error ( asterisk -vvvr is the commadn)
3. if u have enabled AMD detection ,then u wil be facing more wait time if the leads has lots of anwering machine nos.

br
striker
www.striker24x7.blogspot.com

RE: call waiting issue - Added by Hari Shankar almost 11 years ago

thanks for your reply. My problem is that after 2-3 minutes of dialing there is a very long wait time of calls like 3-5 minutes but not a single call is placed. And the big problem is that its keep showing the same thing that " calls being placed .. " after closing the campaign and logging off of the agents. i have checked all the logs generated by the asterisk and didn't find any kind of error. suggest me something now today calls are even taking a lot of time to get mature. i have tried your suggestion but it didn't work for me.

RE: call waiting issue - Added by Demian Biscocho almost 11 years ago

Looks like you are using an older version of GOautodial (2.1). Please upgrade to the latest version. Check the Wiki pages for the HOWTOs. Let us know if you still encounter issues after upgrading.

RE: call waiting issue - Added by Hari Shankar almost 11 years ago

ok i will try to upgrade it to the latest one but my only concern is do i have to take back up of present system settings,campaign and leads or after the up gradation only the system files will be changed and all other settings will be untouched . please update me on this thing. thanks for your feedback.

RE: call waiting issue - Added by Demian Biscocho almost 11 years ago

It's always recommended to create a backup of the system before performing the upgrade (in case something wrong happens). The upgrade to GOautodial 3.0 will migrate your existing data and keep your current settings.

RE: call waiting issue - Added by Hari Shankar almost 11 years ago

Thanks for your help. I will try to upgrade my server after backup .

RE: call waiting issue - Added by Hari Shankar almost 11 years ago

but before upgrading the server can you check is there any issue in asterisk ?
below is the log file:

[Jul 3 17:22:26] VERBOSE⁴³⁹³ logger.c: [Jul 3 17:22:26] -- Executing [8600050@defaultlog:2] Goto("SIP/1008-00000000", "default|8600050|1") in new stack
[Jul 3 17:22:26] VERBOSE⁴³⁹³ logger.c: [Jul 3 17:22:26] -- Goto (default,8600050,1)
[Jul 3 17:22:26] VERBOSE⁴³⁹³ logger.c: [Jul 3 17:22:26] -- Executing [8600050@default:1] MeetMe("SIP/1008-00000000", "8600050|F") in new stack
[Jul 3 17:22:26] VERBOSE⁴³⁹³ logger.c: [Jul 3 17:22:26] Parsing '/etc/asterisk/meetme.conf': [Jul 3 17:22:26] VERBOSE[4393] logger.c: [Jul 3 17:22:26] Found
[Jul 3 17:22:26] VERBOSE[4393] logger.c: [Jul 3 17:22:26] Parsing '/etc/asterisk/meetme-vicidial.conf': [Jul 3 17:22:26] VERBOSE⁴³⁹³ logger.c: [Jul 3 17:22:26] Found
[Jul 3 17:22:26] VERBOSE⁴³⁹³ logger.c: [Jul 3 17:22:26] -- Created MeetMe conference 1023 for conference '8600050'
[Jul 3 17:22:26] VERBOSE⁴³⁹³ logger.c: [Jul 3 17:22:26] -- Playing 'conf-onlyperson' (language 'en')
[Jul 3 17:22:36] VERBOSE⁴⁴⁴⁴ logger.c: [Jul 3 17:22:36] Parsing '/etc/asterisk/manager.conf': [Jul 3 17:22:36] VERBOSE[4444] logger.c: [Jul 3 17:22:36] Found
[Jul 3 17:22:36] VERBOSE[4444] logger.c: [Jul 3 17:22:36] Manager 'sendcron' logged on from 127.0.0.1
[Jul 3 17:22:36] VERBOSE⁴⁴⁴⁵ logger.c: [Jul 3 17:22:36] -- Executing [91890318602932774@default:1] AGI in new stack
[Jul 3 17:22:36] VERBOSE⁴⁴⁴⁷ logger.c: [Jul 3 17:22:36] Parsing '/etc/asterisk/manager.conf': [Jul 3 17:22:36] VERBOSE[4447] logger.c: [Jul 3 17:22:36] Found
[Jul 3 17:22:36] VERBOSE[4447] logger.c: [Jul 3 17:22:36] Manager 'sendcron' logged on from 127.0.0.1
[Jul 3 17:22:36] VERBOSE⁴⁴⁴⁸ logger.c: [Jul 3 17:22:36] -- Executing [91890312033744198@default:1] AGI in new stack
[Jul 3 17:22:36] VERBOSE⁴⁴⁴⁸ logger.c: [Jul 3 17:22:36] -- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
[Jul 3 17:22:36] VERBOSE⁴⁴⁴⁸ logger.c: [Jul 3 17:22:36] -- Executing [91890312033744198@default:2] Dial("Local/91890312033744198@default-580b,2", "SIP/vos76/890312033744198||tTor") in new stack
[Jul 3 17:22:36] VERBOSE⁴⁴⁴⁸ logger.c: [Jul 3 17:22:36] -- Called vos76/890312033744198
[Jul 3 17:22:36] VERBOSE⁴⁴⁴⁵ logger.c: [Jul 3 17:22:36] -- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
[Jul 3 17:22:36] VERBOSE⁴⁴⁴⁵ logger.c: [Jul 3 17:22:36] -- Executing [91890318602932774@default:2] Dial("Local/91890318602932774@default-f1a7,2", "SIP/vos76/890318602932774||tTor") in new stack
[Jul 3 17:22:36] VERBOSE⁴⁴⁴⁵ logger.c: [Jul 3 17:22:36] -- Called vos76/890318602932774
[Jul 3 17:22:57] VERBOSE⁴⁴⁴⁵ logger.c: [Jul 3 17:22:57] Spawn extension (default, 91890318602932774, 2) exited non-zero on 'Local/91890318602932774@default-f1a7,2'
[Jul 3 17:22:57] VERBOSE[4445] logger.c: [Jul 3 17:22:57] -- Executing [h@default:1] DeadAGI("Local/91890318602932774@default-f1a7,2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0-----CANCEL----------") in new stack
[Jul 3 17:22:57] VERBOSE[4448] logger.c: [Jul 3 17:22:57] Spawn extension (default, 91890312033744198, 2) exited non-zero on 'Local/91890312033744198@default-580b,2'
[Jul 3 17:22:57] VERBOSE⁴⁴⁴⁸ logger.c: [Jul 3 17:22:57] -- Executing [h@default:1] DeadAGI("Local/91890312033744198@default-580b,2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0-----CANCEL----------") in new stack
[Jul 3 17:22:58] VERBOSE⁴⁴⁴⁸ logger.c: [Jul 3 17:22:58] -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0-----CANCEL---------- completed, returning 0
[Jul 3 17:22:58] VERBOSE⁴⁴⁴⁵ logger.c: [Jul 3 17:22:58] -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0-----CANCEL---------- completed, returning 0
[Jul 3 17:22:59] VERBOSE⁴⁴⁴⁴ logger.c: [Jul 3 17:22:59] Manager 'sendcron' logged off from 127.0.0.1
[Jul 3 17:22:59] VERBOSE[4447] logger.c: [Jul 3 17:22:59] Manager 'sendcron' logged off from 127.0.0.1
[Jul 3 17:23:01] VERBOSE⁴⁷⁰⁸ logger.c: [Jul 3 17:23:01] Parsing '/etc/asterisk/manager.conf': [Jul 3 17:23:01] VERBOSE[4708] logger.c: [Jul 3 17:23:01] Found
[Jul 3 17:23:01] VERBOSE[4708] logger.c: [Jul 3 17:23:01] Manager 'sendcron' logged on from 127.0.0.1
[Jul 3 17:23:01] VERBOSE⁴⁷⁰⁷ logger.c: [Jul 3 17:23:01] Parsing '/etc/asterisk/manager.conf': [Jul 3 17:23:01] VERBOSE[4707] logger.c: [Jul 3 17:23:01] Found
[Jul 3 17:23:01] VERBOSE[4707] logger.c: [Jul 3 17:23:01] Manager 'sendcron' logged on from 127.0.0.1
[Jul 3 17:23:01] VERBOSE⁴⁷⁰⁸ logger.c: [Jul 3 17:23:01] Manager 'sendcron' logged off from 127.0.0.1
[Jul 3 17:23:05] VERBOSE[4707] logger.c: [Jul 3 17:23:05] Manager 'sendcron' logged off from 127.0.0.1
[Jul 3 17:23:06] VERBOSE⁴⁷⁶³ logger.c: [Jul 3 17:23:06] Parsing '/etc/asterisk/manager.conf': [Jul 3 17:23:06] VERBOSE[4763] logger.c: [Jul 3 17:23:06] Found
[Jul 3 17:23:06] VERBOSE[4763] logger.c: [Jul 3 17:23:06] Manager 'sendcron' logged on from 127.0.0.1
[Jul 3 17:23:06] VERBOSE⁴⁷⁶³ logger.c: [Jul 3 17:23:06] Manager 'sendcron' logged off from 127.0.0.1
[Jul 3 17:24:01] VERBOSE[5198] logger.c: [Jul 3 17:24:01] Parsing '/etc/asterisk/manager.conf': [Jul 3 17:24:01] VERBOSE⁵¹⁹⁸ logger.c: [Jul 3 17:24:01] Found
[Jul 3 17:24:01] VERBOSE⁵¹⁹⁸ logger.c: [Jul 3 17:24:01] Manager 'sendcron' logged on from 127.0.0.1
[Jul 3 17:24:01] VERBOSE[5199] logger.c: [Jul 3 17:24:01] Parsing '/etc/asterisk/manager.conf': [Jul 3 17:24:01] VERBOSE⁵¹⁹⁹ logger.c: [Jul 3 17:24:01] Found
[Jul 3 17:24:01] VERBOSE⁵¹⁹⁹ logger.c: [Jul 3 17:24:01] Manager 'sendcron' logged on from 127.0.0.1
[Jul 3 17:24:01] VERBOSE[5198] logger.c: [Jul 3 17:24:01] Manager 'sendcron' logged off from 127.0.0.1
[Jul 3 17:24:05] VERBOSE⁵¹⁹⁹ logger.c: [Jul 3 17:24:05] Manager 'sendcron' logged off from 127.0.0.1
[Jul 3 17:24:06] VERBOSE[5256] logger.c: [Jul 3 17:24:06] Parsing '/etc/asterisk/manager.conf': [Jul 3 17:24:06] VERBOSE⁵²⁵⁶ logger.c: [Jul 3 17:24:06] Found
[Jul 3 17:24:06] VERBOSE⁵²⁵⁶ logger.c: [Jul 3 17:24:06] Manager 'sendcron' logged on from 127.0.0.1
[Jul 3 17:24:06] VERBOSE[5256] logger.c: [Jul 3 17:24:06] Manager 'sendcron' logged off from 127.0.0.1
[Jul 3 17:25:01] VERBOSE⁵⁶⁵⁸ logger.c: [Jul 3 17:25:01] Parsing '/etc/asterisk/manager.conf': [Jul 3 17:25:01] VERBOSE[5658] logger.c: [Jul 3 17:25:01] Found
[Jul 3 17:25:01] VERBOSE[5658] logger.c: [Jul 3 17:25:01] Manager 'sendcron' logged on from 127.0.0.1
[Jul 3 17:25:01] VERBOSE⁵⁶⁶² logger.c: [Jul 3 17:25:01] Parsing '/etc/asterisk/manager.conf': [Jul 3 17:25:01] VERBOSE[5662] logger.c: [Jul 3 17:25:01] Found
[Jul 3 17:25:01] VERBOSE[5662] logger.c: [Jul 3 17:25:01] Manager 'sendcron' logged on from 127.0.0.1
[Jul 3 17:25:02] VERBOSE⁵⁶⁵⁸ logger.c: [Jul 3 17:25:02] Manager 'sendcron' logged off from 127.0.0.1
[Jul 3 17:25:05] VERBOSE[5662] logger.c: [Jul 3 17:25:05] Manager 'sendcron' logged off from 127.0.0.1
[Jul 3 17:25:07] VERBOSE⁵⁷⁰⁹ logger.c: [Jul 3 17:25:07] Parsing '/etc/asterisk/manager.conf': [Jul 3 17:25:07] VERBOSE[5709] logger.c: [Jul 3 17:25:07] Found
[Jul 3 17:25:07] VERBOSE[5709] logger.c: [Jul 3 17:25:07] Manager 'sendcron' logged on from 127.0.0.1
[Jul 3 17:25:07] VERBOSE⁵⁷⁰⁹ logger.c: [Jul 3 17:25:07] Manager 'sendcron' logged off from 127.0.0.1
[Jul 3 17:26:01] VERBOSE[6104] logger.c: [Jul 3 17:26:01] Parsing '/etc/asterisk/manager.conf': [Jul 3 17:26:01] VERBOSE⁶¹⁰⁴ logger.c: [Jul 3 17:26:01] Found
[Jul 3 17:26:01] VERBOSE⁶¹⁰⁴ logger.c: [Jul 3 17:26:01] Manager 'sendcron' logged on from 127.0.0.1
[Jul 3 17:26:01] VERBOSE[6107] logger.c: [Jul 3 17:26:01] Parsing '/etc/asterisk/manager.conf': [Jul 3 17:26:01] VERBOSE⁶¹⁰⁷ logger.c: [Jul 3 17:26:01] Found
[Jul 3 17:26:01] VERBOSE⁶¹⁰⁷ logger.c: [Jul 3 17:26:01] Manager 'sendcron' logged on from 127.0.0.1
[Jul 3 17:26:02] VERBOSE[6104] logger.c: [Jul 3 17:26:02] Manager 'sendcron' logged off from 127.0.0.1
[Jul 3 17:26:05] VERBOSE⁶¹⁰⁷ logger.c: [Jul 3 17:26:05] Manager 'sendcron' logged off from 127.0.0.1
[Jul 3 17:26:07] VERBOSE[6169] logger.c: [Jul 3 17:26:07] Parsing '/etc/asterisk/manager.conf': [Jul 3 17:26:07] VERBOSE⁶¹⁶⁹ logger.c: [Jul 3 17:26:07] Found
[Jul 3 17:26:07] VERBOSE⁶¹⁶⁹ logger.c: [Jul 3 17:26:07] Manager 'sendcron' logged on from 127.0.0.1
[Jul 3 17:26:07] VERBOSE[6169] logger.c: [Jul 3 17:26:07] Manager 'sendcron' logged off from 127.0.0.1
[Jul 3 17:27:01] VERBOSE⁶⁵⁵⁸ logger.c: [Jul 3 17:27:01] Parsing '/etc/asterisk/manager.conf': [Jul 3 17:27:01] VERBOSE[6558] logger.c: [Jul 3 17:27:01] Found
[Jul 3 17:27:01] VERBOSE[6558] logger.c: [Jul 3 17:27:01] Manager 'sendcron' logged on from 127.0.0.1
[Jul 3 17:27:01] VERBOSE⁶⁵⁶² logger.c: [Jul 3 17:27:01] Parsing '/etc/asterisk/manager.conf': [Jul 3 17:27:01] VERBOSE[6562] logger.c: [Jul 3 17:27:01] Found
[Jul 3 17:27:01] VERBOSE[6562] logger.c: [Jul 3 17:27:01] Manager 'sendcron' logged on from 127.0.0.1
[Jul 3 17:27:01] VERBOSE⁶⁵⁶² logger.c: [Jul 3 17:27:01] Manager 'sendcron' logged off from 127.0.0.1
[Jul 3 17:27:04] VERBOSE[6558] logger.c: [Jul 3 17:27:04] Manager 'sendcron' logged off from 127.0.0.1
[Jul 3 17:27:06] VERBOSE⁶⁶¹³ logger.c: [Jul 3 17:27:06] Parsing '/etc/asterisk/manager.conf': [Jul 3 17:27:06] VERBOSE[6613] logger.c: [Jul 3 17:27:06] Found
[Jul 3 17:27:06] VERBOSE[6613] logger.c: [Jul 3 17:27:06] Manager 'sendcron' logged on from 127.0.0.1
[Jul 3 17:27:06] VERBOSE⁶⁶¹³ logger.c: [Jul 3 17:27:06] Manager 'sendcron' logged off from 127.0.0.1
[Jul 3 17:27:17] VERBOSE[3284] logger.c: [Jul 3 17:27:17] Refreshing DNS lookups.
[Jul 3 17:28:01] VERBOSE⁶⁹⁹⁵ logger.c: [Jul 3 17:28:01] Parsing '/etc/asterisk/manager.conf': [Jul 3 17:28:01] VERBOSE[6995] logger.c: [Jul 3 17:28:01] Found
[Jul 3 17:28:01] VERBOSE[6995] logger.c: [Jul 3 17:28:01] Manager 'sendcron' logged on from 127.0.0.1
[Jul 3 17:28:01] VERBOSE⁶⁹⁹⁶ logger.c: [Jul 3 17:28:01] Parsing '/etc/asterisk/manager.conf': [Jul 3 17:28:01] VERBOSE[6996] logger.c: [Jul 3 17:28:01] Found
[Jul 3 17:28:01] VERBOSE[6996] logger.c: [Jul 3 17:28:01] Manager 'sendcron' logged on from 127.0.0.1
[Jul 3 17:28:01] VERBOSE⁶⁹⁹⁶ logger.c: [Jul 3 17:28:01] Manager 'sendcron' logged off from 127.0.0.1
[Jul 3 17:28:05] VERBOSE[6995] logger.c: [Jul 3 17:28:05] Manager 'sendcron' logged off from 127.0.0.1
[Jul 3 17:28:06] VERBOSE⁷⁰⁵⁶ logger.c: [Jul 3 17:28:06] Parsing '/etc/asterisk/manager.conf': [Jul 3 17:28:06] VERBOSE[7056] logger.c: [Jul 3 17:28:06] Found
[Jul 3 17:28:06] VERBOSE[7056] logger.c: [Jul 3 17:28:06] Manager 'sendcron' logged on from 127.0.0.1
[Jul 3 17:28:06] VERBOSE⁷⁰⁵⁶ logger.c: [Jul 3 17:28:06] Manager 'sendcron' logged off from 127.0.0.1
[Jul 3 17:29:01] VERBOSE[7425] logger.c: [Jul 3 17:29:01] Parsing '/etc/asterisk/manager.conf': [Jul 3 17:29:01] VERBOSE⁷⁴²⁵ logger.c: [Jul 3 17:29:01] Found
[Jul 3 17:29:01] VERBOSE⁷⁴²⁵ logger.c: [Jul 3 17:29:01] Manager 'sendcron' logged on from 127.0.0.1
[Jul 3 17:29:01] VERBOSE[7430] logger.c: [Jul 3 17:29:01] Parsing '/etc/asterisk/manager.conf': [Jul 3 17:29:01] VERBOSE⁷⁴³⁰ logger.c: [Jul 3 17:29:01] Found
[Jul 3 17:29:01] VERBOSE⁷⁴³⁰ logger.c: [Jul 3 17:29:01] Manager 'sendcron' logged on from 127.0.0.1
[Jul 3 17:29:01] VERBOSE[7425] logger.c: [Jul 3 17:29:01] Manager 'sendcron' logged off from 127.0.0.1
[Jul 3 17:29:05] VERBOSE⁷⁴³⁰ logger.c: [Jul 3 17:29:05] Manager 'sendcron' logged off from 127.0.0.1
[Jul 3 17:29:06] VERBOSE[7480] logger.c: [Jul 3 17:29:06] Parsing '/etc/asterisk/manager.conf': [Jul 3 17:29:06] VERBOSE⁷⁴⁸⁰ logger.c: [Jul 3 17:29:06] Found
[Jul 3 17:29:06] VERBOSE⁷⁴⁸⁰ logger.c: [Jul 3 17:29:06] Manager 'sendcron' logged on from 127.0.0.1
[Jul 3 17:29:06] VERBOSE[7480] logger.c: [Jul 3 17:29:06] Manager 'sendcron' logged off from 127.0.0.1
[Jul 3 17:30:01] VERBOSE⁷⁸⁹³ logger.c: [Jul 3 17:30:01] Parsing '/etc/asterisk/manager.conf': [Jul 3 17:30:01] VERBOSE[7893] logger.c: [Jul 3 17:30:01] Found
[Jul 3 17:30:01] VERBOSE[7893] logger.c: [Jul 3 17:30:01] Manager 'sendcron' logged on from 127.0.0.1
[Jul 3 17:30:01] VERBOSE⁷⁸⁹⁹ logger.c: [Jul 3 17:30:01] Parsing '/etc/asterisk/manager.conf': [Jul 3 17:30:01] VERBOSE[7899] logger.c: [Jul 3 17:30:01] Found
[Jul 3 17:30:01] VERBOSE[7899] logger.c: [Jul 3 17:30:01] Manager 'sendcron' logged on from 127.0.0.1
[Jul 3 17:30:01] VERBOSE⁷⁸⁹³ logger.c: [Jul 3 17:30:01] Manager 'sendcron' logged off from 127.0.0.1
[Jul 3 17:30:05] VERBOSE[7899] logger.c: [Jul 3 17:30:05] Manager 'sendcron' logged off from 127.0.0.1
[Jul 3 17:30:06] VERBOSE⁷⁹⁵² logger.c: [Jul 3 17:30:06] Parsing '/etc/asterisk/manager.conf': [Jul 3 17:30:06] VERBOSE[7952] logger.c: [Jul 3 17:30:06] Found
[Jul 3 17:30:06] VERBOSE[7952] logger.c: [Jul 3 17:30:06] Manager 'sendcron' logged on from 127.0.0.1
[Jul 3 17:30:06] VERBOSE⁷⁹⁵² logger.c: [Jul 3 17:30:06] == Manager 'sendcron' logged off from 127.0.0.1

RE: call waiting issue - Added by Ashwin krishna over 10 years ago

Hello
I am also facing the CALL WAITING ISSUE. The DROPPED PERCENT IS ONLY 2.22 and in the 8 hours of calling an agent will only get 150 calls to speak. I did not find any solution for this and since we were facing some other problem my we cleared the caches and junks in the asterisk and then it started working good.After doing this the DROPPED PERCENT came to 16 and each agent got 400 calls to speak.. But after few day again the same problem exists...Can any one find a solution for this..We are not able to identify where the error would be...Please guide us ...

thank u
ashwinkm.cadvisor@gmail.com

(1-8/8) Go to top

Project

General

Profile

GOautodial Open Source Omni-channel Contact Center Suite