vicidial.org

Iam facing conference issue between two different sip account . both agent can listen each other & customer voice too at time of conference any help will bi highly appreciable. Its inbound server . 1st call come on DID then it route to In GRoup from where it route to Agents that had been logined
____________________
ViciBox_Redux_v.3.1
VERSION: 2.4-329a
BUILD: 110809-1547
NO Sangoma/Digium Card

i have no idea what your problem is. it is not clearly defined at all.

also: Vicibox Redux 3.1.?? (there is a digit, possibly two, missing ...)

oh


sometime conference is happening between two agents during calling


_________________
ViciBox_Redux 3.1.10
VERSION: 2.4-329a
BUILD: 110809-1547
NO Sangoma/Digium Card

between two agents during a call ... so are there prospects involved in this? are agents sharing logins?

how does this show in the real time screen?

Agents told me this thats how i get to know and nothing different appeared on Real time at that time,

else what u said i didnt get

agents hear each other. got that.

when agents hear each other, have there also been prospects in the conference? or just agents that hear each other?

what is your system load when this happens?

is this when agents are logging in or during calls? (or when ONE is in a call and the OTHER is logging in?)

it happened only when both agents on call, both can listen and talk to each other even with customer too having on line with respective agents.

what is your system load when this happens?

did BOTH agents hear 'you are the only person in this conference' when they logged in? or only one of them?

yup man both agent heard this conference msg on login

u mean what appeared on CLI at that time ?

htop, top, uptime, all show "server load". there is also a server load value visible in the real time screen and on the "Admin->Servers" page, but i firmly believe in getting the values directly from the server during use.

the next time this happens, have htop running in a putty screen and be "observing" the load on the processors.

htop has the advantage of showing the 1 minute 5 minute 10 minute "values" in the top right corner (for averages over time) AND the per cpu instant values as well (which can show peaks that may spike up to 100%, which is bad).

But htop command is not working


[root@USSERVER ~]# htop
-bash: htop: command not found

[root@USSERVER ~]# uptime
01:25:54 up 11:14, 3 users, load average: 0.56, 0.32, 0.43
[root@USSERVER ~]# top
top - 01:26:30 up 11:15, 3 users, load average: 0.62, 0.36, 0.43
Tasks: 125 total, 1 running, 123 sleeping, 1 stopped, 0 zombie
Cpu(s): 6.8%us, 1.8%sy, 0.0%ni, 91.2%id, 0.0%wa, 0.0%hi, 0.2%si, 0.0%st
Mem: 1035104k total, 1003264k used, 31840k free, 12804k buffers
Swap: 1044216k total, 9304k used, 1034912k free, 743752k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2326 mysql 15 0 146m 40m 5392 S 3.0 4.1 15:14.01 mysqld
12481 root 18 0 6272 4428 1744 S 2.7 0.4 0:00.08 AST_send_action
3075 root 15 0 53168 18m 5508 S 2.0 1.8 3:54.14 asterisk
3189 root 15 0 12344 6920 2680 S 1.3 0.7 5:10.16 AST_update.pl
12449 root 19 0 6272 4424 1744 S 1.3 0.4 0:00.08 AST_send_action
11800 root 15 0 2332 1112 832 R 0.7 0.1 0:00.07 top
2905 root 15 0 13348 7944 2744 S 0.3 0.8 0:02.65 FastAGI_log.pl
3198 root 15 0 12160 6748 2584 S 0.3 0.7 1:32.72 AST_VDauto_dial
3966 root 15 0 13756 8400 2652 S 0.3 0.8 0:20.02 AST_VDadapt.pl
6782 apache 15 0 63476 21m 14m S 0.3 2.1 0:08.83 httpd
7275 apache 15 0 63628 20m 13m S 0.3 2.0 0:07.23 httpd
7560 apache 15 0 63644 21m 14m S 0.3 2.1 0:07.88 httpd
12975 apache 15 0 63032 19m 13m S 0.3 1.9 0:06.39 httpd
22333 apache 15 0 62900 19m 13m S 0.3 1.9 0:03.66 httpd
22335 apache 15 0 63380 20m 13m S 0.3 2.0 0:03.47 httpd
22336 apache 15 0 62912 19m 13m S 0.3 1.9 0:03.43 httpd
23858 apache 15 0 63600 20m 14m S 0.3 2.0 0:03.27 httpd
23927 root 15 0 13480 6788 1484 S 0.3 0.7 0:00.27 FastAGI_log.pl
24824 root 15 0 10088 2884 2312 S 0.3 0.3 0:00.10 sshd
26455 apache 15 0 63476 19m 13m S 0.3 1.9 0:02.22 httpd
31848 apache 15 0 63504 20m 13m S 0.3 2.0 0:10.81 httpd
1 root 15 0 2072 664 568 S 0.0 0.1 0:00.82 init
2 root RT -5 0 0 0 S 0.0 0.0 0:00.16 migration/0
3 root 34 19 0 0 0 S 0.0 0.0 0:00.01 ksoftirqd/0
4 root RT -5 0 0 0 S 0.0 0.0 0:00.00 watchdog/0
5 root RT -5 0 0 0 S 0.0 0.0 0:00.32 migration/1
6 root 34 19 0 0 0 S 0.0 0.0 0:00.06 ksoftirqd/1
7 root RT -5 0 0 0 S 0.0 0.0 0:00.00 watchdog/1
8 root 10 -5 0 0 0 S 0.0 0.0 0:00.02 events/0
9 root 10 -5 0 0 0 S 0.0 0.0 0:00.02 events/1
10 root 10 -5 0 0 0 S 0.0 0.0 0:00.00 khelper
11 root 10 -5 0 0 0 S 0.0 0.0 0:00.00 kthread
15 root 10 -5 0 0 0 S 0.0 0.0 0:00.04 kblockd/0
16 root 13 -5 0 0 0 S 0.0 0.0 0:00.01 kblockd/1
17 root 10 -5 0 0 0 S 0.0 0.0 0:00.00 kacpid
106 root 14 -5 0 0 0 S 0.0 0.0 0:00.00 cqueue/0
107 root 14 -5 0 0 0 S 0.0 0.0 0:00.00 cqueue/1

Code: Select all

yum install htop

how many processors does your system have?

was THIS uptime load average taken at a time when this problem occurred? (doesn't count if this wasn't taken with in a minute or so ... htop is cool because you can WATCH as the load comes and goes and even seek Peaks when they happen)

its happened during when one agent is in a call and the OTHER is logging in

uptime

02:00am up 8 days 13:00, 3 users, load average: 0.12, 0.21, 0.17

1 15.5%
2 25.2 %

Mem 356/2989 MB

Navdeep,

When this issue is reported could you please check the following things

1. Verify the extension settings on both the agents soft phones carefully (I'm assuming that they're using soft phones).
2. Verify the phone id used by both the agents.

I would suggest going to the agent desktops and checking both these things yourself. You'd be surprised with what you may find.

Thanks crisfurtado for reply


But we are using Analog gateway not soft phones
Telephone hardware :- Grandstream GXW-4024 V0.2C Program-- 1.0.1.8 Bootloader-- 1.0.0.9 Core-- 1.0.0.23 Base-- 1.0.0.66

+----------------+------------------------+-----------+----------+---------+------------+-------+------+------------------
| STATION | USER SHOW ID INFO | SESSIONID | STATUS | MM:SS | CAMPAIGN | CALLS | HOLD | IN-GROUP
+----------------+------------------------+-----------+----------+---------+------------+-------+------+------------------
| SIP/1213 | Ravi Singh + | 8600054 | READY | 1:38 | INTEH | 10 |
| SIP/1212 | Vaibhav Thakur + | 8600058 | READY | 1:41 | INTEH | 40 |
| SIP/1211 | Ankush Kaul + | 8600055 | INCALL I | 3:12 | INTEH | 25 | 0 | INTECH - INTECH PROCESS
| SIP/1209 | Nishant + | 8600060 | PAUSED | 2:49 | INTEH | 135 |
| SIP/1206 | Krishansh + | 8600057 | CLOSER | 1:19 | INTEH | 19 |
| SIP/1205 | Kiransingh + | 8600056 | CLOSER | 25:14 | INTEH | 25 |
| SIP/1208 | Rajive Gognaa + | 8600052 | CLOSER | 21:38 | INTEH | 19 |
| SIP/1210 | Ajit Kumar + | 8600053 | CLOSER | 2:04 | INTEH | 34 |

1) try rebooting your system every night until it happens again (if it never happens again, keep on rebooting nightly forever)

2) Verify the user login and phone login for the agents affected. When they "log out" they will each have a "relogin" screen. Look at this for both agents and be sure they are not accidentally sharing credentials for user or phone.

3) Revalidate your gateway setup, and perhaps reboot it. You may be experiencing rollover (a line is busy, so it rolls to the next one!)