[BUG?] Customer HangUp while Call Park

[covarrubiasgg]

Hey everyone,

i am not sure if this is a bug or i mess with something, recently I upgrade a cluster to the latest SVN 2848

On admin Interface it shows: VERSION: 2.14-639a BUILD: 171028-0913
On agent Interface it shows: VERSION: 2.14-538c BUILD: 171026-0109

We have a cluster 1 x DB , 1 x Web, 3 x Dialers for 75 Outbound agents all installed with Vicibox 7.0.4 with no zypper updates, but updated Vicidial via svn update.


The problem is, that if i send a call to park, on the agent screen goes from LIVE CALL to CUSTOMER HANGUP, and real time show agent as DEAD.

The customer is actually on Hold listening music, and agent is able to recover the call when GRABBED PARK, but agent will remain DEAD / CUSTOMER HANGUP, it wont affect the call at all, i made some test i was able to stay on the line with the customer for 30 minutes without dropping the call or even showing the green screen that says "Customer hang up, hang up and dispo" the call controls remain active all the time but real time show DEAD and agent time report show DEAD.


Here is the asterisk output

Code: Select all

[Nov 12 19:51:05] Connected to Asterisk 11.25.1-vici currently running on phone1 (pid = 1476)

//HERE I PRESSED PARK CALL
[Nov 12 19:51:16]     -- Executing [8301@default:1] Answer("DAHDI/i1/045XXXXXXXXXX-a", "") in new stack
[Nov 12 19:51:16]     -- Executing [h@default:1] AGI("Local/8600051@default-00000013;1", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16-----ANSWER-----28-----21") in new stack
[Nov 12 19:51:16]     -- Executing [8301@default:2] AGI("DAHDI/i1/045XXXXXXXXXX-a", "park_CID.agi") in new stack
[Nov 12 19:51:16]     -- Launched AGI Script /usr/share/asterisk/agi-bin/park_CID.agi
[Nov 12 19:51:16]     -- <DAHDI/i1/045XXXXXXXXXX-a> Playing 'sip-silence.gsm' (escape_digits=) (sample_offset 0) (language 'en')
[Nov 12 19:51:16]     -- <DAHDI/i1/045XXXXXXXXXX-a> Playing 'sip-silence.gsm' (escape_digits=) (sample_offset 0) (language 'en')
[Nov 12 19:51:16]     -- <DAHDI/i1/045XXXXXXXXXX-a> Playing 'sip-silence.gsm' (escape_digits=) (sample_offset 0) (language 'en')
[Nov 12 19:51:16]     -- <DAHDI/i1/045XXXXXXXXXX-a> Playing 'sip-silence.gsm' (escape_digits=) (sample_offset 0) (language 'en')
[Nov 12 19:51:16]     -- Started music on hold, class 'default', on DAHDI/i1/045XXXXXXXXXX-a
[Nov 12 19:51:17]     -- <Local/8600051@default-00000013;1>AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16-----ANSWER-----28-----21 completed, returning 0
[Nov 12 19:51:17]   == Spawn extension (default, 9XXXXXXXXXX, 2) exited non-zero on 'Local/8600051@default-00000013;1'
[Nov 12 19:51:17]   == Spawn extension (default, 8600051, 1) exited non-zero on 'Local/8600051@default-00000013;2'
[Nov 12 19:51:17]     -- Executing [h@default:1] AGI("Local/8600051@default-00000013;2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0---------------") in new stack
[Nov 12 19:51:17]     -- <Local/8600051@default-00000013;2>AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0--------------- completed, returning 0


// HERE I PRESSED GRAB PARK
[Nov 12 19:53:00]     -- Stopped music on hold on DAHDI/i1/045XXXXXXXXXX-a
[Nov 12 19:53:00]     -- <DAHDI/i1/045XXXXXXXXXX-a>AGI Script park_CID.agi completed, returning 4
[Nov 12 19:53:00]   == Spawn extension (default, 8600051, 1) exited non-zero on 'DAHDI/i1/045XXXXXXXXXX-a'
[Nov 12 19:53:00]     -- Executing [8600051@default:1] MeetMe("DAHDI/i1/045XXXXXXXXXX-a", "8600051,F") in new stack


In case it is relevant here is my dialplan

Code: Select all

exten => _9XXXXXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _9XXXXXXXXXX,2,Dial(DAHDI/g0/045${EXTEN:1},,ToI)
exten => _9XXXXXXXXXX,3,Hangup


We are using DAHDI E1 channels via a Sangoma A200 card

i will try to test on a different enviroment to verify if it is a bug.

[mflorell]

The Sangoma A200 is for FXO interfaces, how are you using an E1 through it?

Unfortunately, we haven't been using or recommending Sangoma cards for years now, mostly due to poor support from Sangoma for recent kernel versions, and the lack of having clients that use those cards either, so we don't typically do testing using them. So, it's possible there is a bug, but we don't have interfaces set up to test using Sangoma cards, so it's difficult for us to troubleshoot these kind of issues.

[covarrubiasgg]

My mistake Sangoma A102, and yes i hate Sangoma cards but for some reason there is a client which "requires" that brand, i don't know why if they don't manage the servers what the difference for them, but i'm the one who has to deal with the problems

Thank you Matt, BTW i don't know any other open source projects that has a developer as active as you , great value for the Vicidial brand

[arunkooods]

I have many of my clients using Sangoma without these kind of issue.install latest wan-pipe version for better results.Also check what is your Kernel version and check if it matches your wan-pipe version.
what is your kernel version ?
what is your wan-pipe version ?