Page 1 of 1

JB Warning Output: Resyncing the JB

PostPosted: Fri Oct 26, 2018 3:22 pm
by Leckbush
Hi

Im having a wierd issue with one of our quality agent. First things first on what he do

QA Agent:
-He listen/barging/monitor to all agents whose dialing at the moment (Manual outbound). He using a softphone.
Problem = the blind monitoring call from vici is auto disconnecting. For example, he's gonna barge three agent at the same time and few seconds/minute later all calls will disconnect to softphone. Idk if thats what causing it (multiple barging same time)? Sometime not all call will disconnect.
- When I look at Asterisk CLI I can see that i got this log :
" WARNING[1672]: chan_iax2.c:1184 jb_warning_output: Resyncing the jb. last_delay 0, this delay -10941, threshold 1002, new offset 10923"

and also I got this log when he's softphone/call/barging was disconnected:

"Disconnecting Call (lack of RTP activity in 61 seconds)"

What Did I try:
-Reload command = still the same
-restart his pc = still the same
-reinstall the softphone = still the same

-RTP Debug = found out that vicidial is not recieving any packets from his pc. In other words = Sent Packets - Good but Vici is not getting any "Recieve/Reply/Got Packets" from his PC. Note that its on RTP debugging. So I came up that something has to do with his PC firewall/Blocking etc.

THEN, I check the softphone firewall status (its allowed on all network). Then I came up that I will manually add the SIP Port (5060) on outbound rules on his PC Firewall settings. IT Worked as of now, but Im still monitoring.

Still issue as of that is, Im still receiving the log:
"WARNING[1672]: chan_iax2.c:1184 jb_warning_output: Resyncing the jb. last_delay 0, this delay -10941, threshold 1002, new offset 10923"
I Searched about this problem and find that it was stinky internet? But its local and not using internet.

PLEASE NOTE:
*Vicidial and his PC is behind the firewall
*I Checked all the LAN Cables on his PC to Router including the patch panel, No Problem there.
*Where running on 1Gbps LAN, and bandwidth is fine.
*Only 7 agents are in operation, so there shouldnt have issue with network. Other agents are fine except his line earlier.
*We're using SIP

Re: JB Warning Output: Resyncing the JB

PostPosted: Fri Oct 26, 2018 3:49 pm
by Leckbush
UPDATE: Still the same issue, vici is killing the connection to our QA PC even with no network problem?

here's the log
Disconnect Log = " NOTICE[1677]: chan_sip.c:29325 check_rtp_timeout: Disconnecting call 'SIP/3010-00000856' for lack of RTP activity in 61 seconds"

RTP Debugging while QA agent is connected to Vici :
"[Oct 27 04:45:09] Sent RTP packet to 192.168.1.86:49218 (type 00, seq 023682, ts 486400, len 000160)
[Oct 27 04:45:09] Sent RTP packet to 192.168.1.86:49216 (type 00, seq 022786, ts 524160, len 000160)
[Oct 27 04:45:09] Sent RTP packet to 192.168.1.86:49218 (type 00, seq 023683, ts 486560, len 000160)
[Oct 27 04:45:09] Sent RTP packet to 192.168.1.86:49216 (type 00, seq 022787, ts 524320, len 000160)
[Oct 27 04:45:09] Sent RTP packet to 192.168.1.86:49218 (type 00, seq 023684, ts 486720, len 000160)
[Oct 27 04:45:09] Sent RTP packet to 192.168.1.86:49216 (type 00, seq 022788, ts 524480, len 000160)
[Oct 27 04:45:09] Sent RTP packet to 192.168.1.86:49218 (type 00, seq 023685, ts 486880, len 000160)
[Oct 27 04:45:09] Sent RTP packet to 192.168.1.86:49216 (type 00, seq 022789, ts 524640, len 000160)
[Oct 27 04:45:09] Sent RTP packet to 192.168.1.86:49218 (type 00, seq 023686, ts 487040, len 000160)
[Oct 27 04:45:09] Sent RTP packet to 192.168.1.86:49216 (type 00, seq 022790, ts 524800, len 000160)
[Oct 27 04:45:09] Sent RTP packet to 192.168.1.86:49218 (type 00, seq 023687, ts 487200, len 000160)
[Oct 27 04:45:09] Sent RTP packet to 192.168.1.86:49216 (type 00, seq 022791, ts 524960, len 000160)"

it suppose to have "Got RTP Packet from...." Right?

Re: JB Warning Output: Resyncing the JB

PostPosted: Fri Oct 26, 2018 4:28 pm
by williamconley
lack of RTP activity in 61 seconds


Firewall is blocking the sound in one direction. Presumably the direction you're not listening to anyway so you can't tell. But that's your problem.

Re: JB Warning Output: Resyncing the JB

PostPosted: Fri Oct 26, 2018 4:49 pm
by Leckbush
But everything is behind the firewall and all ports has been allowed thru firewall? I even try turning off firewall but still the same.

UPDATE: So Upon noticing, while our QA agent monitoring 5 agents at the same time(so he receiving 5 sounds from those 5 agents) I notice RTP debugging was fine, "sent" and "Got" packet is there but when I click mute on of those agent he's monitoring... He's RTP log was no have "Got" but when i resume, the normal RTP debug is there. Is that could be the problem lies?

When He mute:
RTP Log:
"Sent RTP Packet to x.x.x.x
Sent RTP Packet to x.x.x.x
Sent RTP Packet to x.x.x.x"

BUT when no barge was muted, its normal:
"Sent RTP Packet to x.x.x.x
Got RTP Packet from x.x.x.x
Sent RTP Packet to x.x.x.x
Got RTP Packet from x.x.x.x"

So if Im right, Theoretically when he mute one barge call from one of those agent he's barging, only sent was showing on RTP debug and the vici is not recieving any packet from his workstation. If thats the scenario, the vici will disconnect to the workstation (QA agent PC) because of there's no RTP Activity (bcoz vici is not getting any packet from QA PC's) Am I right? Please correct me if Im wrong from what I understand on asterisk, as Im still learning. :)

Sorry Im newbie with asterisk/vicidial/linux

UPDATE AGAIN:
I try muting the sip phone with 5 active barging at the same time. If I mute one barge, all are muted (this time RTP Debug log is only "Sent RTP". Then I wait for 60 seconds because that was the RTP timeout set to the vici. And Voila! Vici did kill the connection to the QA Workstation. So I believe that was the thing behind this issue? but I will still monitor his worksation. But I still have problem with the:

" WARNING[1672]: chan_iax2.c:1184 jb_warning_output: Resyncing the jb. last_delay 0, this delay -10941, threshold 1002, new offset 10923"

Re: JB Warning Output: Resyncing the JB

PostPosted: Fri Oct 26, 2018 5:00 pm
by williamconley
Yes. No RTP = dead call. Either change that behavior or set up a keepalive to keep that RTP open and SIP system happy.

Re: JB Warning Output: Resyncing the JB

PostPosted: Fri Oct 26, 2018 5:09 pm
by Leckbush
Thanks William. :) Now I know what to do regarding that kind of things. Many Thanks