DTMF Beep Sound

[hunter2009]

HI ,

Outbound and incoming calls Agents Getting Beep sound on call also its repeat same With Customer But customer not hear any beep sound only agents can hear the beep. When i check with CLI showing Some DTMF Entry but agents not pressed any keys ..Any one faced the issues


My carrier Entry
[DWG-001T]
type=friend
host=192.168.0.200
disallow=all
allow=ulaw
allow=alaw
fromhost=192.168.0.200
port=5060
qualify=yes
dtmfmode=auto -- [I have Tried RFC2833, inband info,also]
nat=force_rport,comedia
insecure=invite,port
canreinvite=no
context=trunkinbound

My Server Details : Cento-OS-7 | Version: 2.14-812a | BUILD: 210429-1624 | Asterisk 13.29.2 | Viciphone2.1 |


In asterisk CLI

using SIP RTP CoS mark 5
> 0x7f946c020660 -- Strict RTP learning after remote address set to: 192.168.0.200:8000
-- Executing [61610@trunkinbound:1] AGI("SIP/DWG-001T-00000051", "agi-DID_route.agi") in new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/agi-DID_route.agi
-- <SIP/DWG-001T-00000051>AGI Script agi-DID_route.agi completed, returning 0
-- Executing [99909*2***DID@default:1] Answer("SIP/DWG-001T-00000051", "") in new stack
> 0x7f946c020660 -- Strict RTP switching to RTP target address 192.168.0.200:8000 as source
-- Executing [99909*2***DID@default:2] AGI("SIP/DWG-001T-00000051", "agi-VDAD_ALL_inbound.agi") in new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/agi-VDAD_ALL_inbound.agi
-- <SIP/DWG-001T-00000051> Playing 'sip-silence.gsm' (escape_digits=) (sample_offset 0) (language 'en')
-- <SIP/DWG-001T-00000051> Playing 'sip-silence.gsm' (escape_digits=) (sample_offset 0) (language 'en')
-- <SIP/DWG-001T-00000051> Playing 'welcomes.slin' (escape_digits=) (sample_offset 0) (language 'en')
== Manager 'sendcron' logged on from 127.0.0.1
-- Called 58600051@default
-- Executing [58600051@default:1] MeetMe("Local/58600051@default-0000005e;2", "8600051,Fmq") in new stack
-- Local/58600051@default-0000005e;1 answered
-- Executing [8309@default:1] Answer("Local/58600051@default-0000005e;1", "") in new stack
[Oct 10 19:06:15] DTMF[12318][C-000000e7]: channel.c:4152 __ast_read: DTMF begin '1' received on SIP/DWG-001T-00000050
[Oct 10 19:06:15] DTMF[12318][C-000000e7]: channel.c:4163 __ast_read: DTMF begin passthrough '1' on SIP/DWG-001T-00000050
-- Executing [8309@default:2] Monitor("Local/58600051@default-0000005e;1", "wav,919944176993_10001_Y0101906120000009148_1007") in new stack
== Manager 'sendcron' logged on from 127.0.0.1
-- Executing [8309@default:3] Wait("Local/58600051@default-0000005e;1", "3600") in new stack
-- Called 192*168*0*200*78600051@default
-- Executing [192*168*0*200*78600051@default:1] Goto("Local/192*168*0*200*78600051@default-0000005f;2", "default,78600051,1") in new stack
-- Goto (default,78600051,1)
-- Executing [78600051@default:1] MeetMe("Local/192*168*0*200*78600051@default-0000005f;2", "8600051,Fq") in new stack
-- Local/192*168*0*200*78600051@default-0000005f;1 answered
-- Executing [83047777777777@vicidial-auto:1] Answer("Local/192*168*0*200*78600051@default-0000005f;1", "") in new stack
-- Executing [83047777777777@vicidial-auto:2] Playback("Local/192*168*0*200*78600051@default-0000005f;1", "ding") in new stack
-- <Local/192*168*0*200*78600051@default-0000005f;1> Playing 'ding.gsm' (language 'en')
-- Executing [83047777777777@vicidial-auto:3] Hangup("Local/192*168*0*200*78600051@default-0000005f;1", "") in new stack
== Spawn extension (vicidial-auto, 83047777777777, 3) exited non-zero on 'Local/192*168*0*200*78600051@default-0000005f;1'
[Oct 10 19:06:15] WARNING[12341][C-000000ef]: func_hangupcause.c:140 hangupcause_read: Unable to find information for channel
-- Executing [h@vicidial-auto:1] AGI("Local/192*168*0*200*78600051@default-0000005f;1", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16--------------------)") in new stack
-- <Local/192*168*0*200*78600051@default-0000005f;1>AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ----------) completed, returning 0
== Spawn extension (default, 78600051, 1) exited non-zero on 'Local/192*168*0*200*78600051@default-0000005f;2'
[Oct 10 19:06:15] WARNING[12342][C-000000ee]: func_hangupcause.c:140 hangupcause_read: Unable to find information for channel
-- Executing [h@default:1] AGI("Local/192*168*0*200*78600051@default-0000005f;2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16--------------------)") in new stack
-- <Local/192*168*0*200*78600051@default-0000005f;2>AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ----------) completed, returning 0
[Oct 10 19:06:15] DTMF[12318][C-000000e7]: channel.c:4066 __ast_read: DTMF end '1' received on SIP/DWG-001T-00000050, duration 261 ms
[Oct 10 19:06:15] DTMF[12318][C-000000e7]: channel.c:4107 __ast_read: DTMF end accepted with begin '1' on SIP/DWG-001T-00000050
[Oct 10 19:06:15] DTMF[12318][C-000000e7]: channel.c:4136 __ast_read: DTMF end passthrough '1' on SIP/DWG-001T-00000050

[jamiemurray]

Just out of curiosity, does the agent continue to hear the tone in their conference until they logout and back in?
I had this randomly happen on many installations on ast 13 and never got to the bottom of it (agents would always report it AFTER logging out and back in but there was nothing of interest in the logs and it happened so infrequently in my case for the number of agents we look after, we never really put any focus on finding the cause), but it hasn't happened to my knowledge since upgrading to asterisk 16.
The DTMF tone from what I can see is coming from the carrier side, not the agent side.
Have you made some test calls yourself to see if it still happens on the calls you make in to the system? If it is, I'd be having a word with the carrier.

[williamconley]

1) How often does this happen? Can you predict it? If so, make sure you do so when YOU are on both ends of the call to categorically remove the possibility that the Lead is pushing a button

2) jamiemuarry: Are you also on CentOS? Is your system similar to OPs?

3) What method of installation was used? If in fact you are both on CentOS, it's possible that this is an installation-specific ... feature. While I'd like to say that's not possible, I've been using Vicidial/Linux far too long to use that word. Ever since the day a client "darked" my fiber and the ISP couldn't figure out why (several days in a row, put him on his own circuit). Still don't know if the NSA was after him for something.

4) Is it possible that this is a "delayed" key press from a prior menu or other feature? Bad scripts happen.

[hunter2009]

Just out of curiosity, does the agent continue to hear the tone in their conference until they logout and back in?
I had this randomly happen on many installations on ast 13 and never got to the bottom of it (agents would always report it AFTER logging out and back in but there was nothing of interest in the logs and it happened so infrequently in my case for the number of agents we look after, we never really put any focus on finding the cause), but it hasn't happened to my knowledge since upgrading to asterisk 16.
The DTMF tone from what I can see is coming from the carrier side, not the agent side.
Have you made some test calls yourself to see if it still happens on the calls you make in to the system? If it is, I'd be having a word with the carrier.

In My case Of after agent logout and login also same Beep sound repeat .Also i have tried with Registering the extension with Directly in soft phone same beep is coming every few min once

[hunter2009]

1) How often does this happen? Can you predict it? If so, make sure you do so when YOU are on both ends of the call to categorically remove the possibility that the Lead is pushing a button

2) jamiemuarry: Are you also on CentOS? Is your system similar to OPs?

3) What method of installation was used? If in fact you are both on CentOS, it's possible that this is an installation-specific ... feature. While I'd like to say that's not possible, I've been using Vicidial/Linux far too long to use that word. Ever since the day a client "darked" my fiber and the ISP couldn't figure out why (several days in a row, put him on his own circuit). Still don't know if the NSA was after him for something.

4) Is it possible that this is a "delayed" key press from a prior menu or other feature? Bad scripts happen.

Hi williamconley

Agents Called outbound and inbound calls Customer cant hear the beep but Agents agents hear that beep sound random repeat .Also Am using Centos-7 other Servers not having issues only in this server Beep sound issues
CentOS 7 - Bit asterisk 13.29.2 , Processor Quad core 3.x Ghz With 8GB ram : Agents 10 only max Inbound calls system load normal
VERSION: 2.14-812a
BUILD: 210429-1624

[jamiemurray]

I've been using Vicibox for all my installations for a number of years, been some time since I used CentOS.
I don't think the issue I saw is the same as the OP.
It was once in a blue moon it would happen, there would be a constant DTMF sound playing the in the meetme conference until the agent logged out and back in, and always seemed co-incided with an answer machine call if the agent hung up around the "beep" of the machine (when I think about it this only happened on UK campaigns, never US or Canadian ones although don't quote me on that).
I looked after receiving the first few reports for hours at a time in my case and tried to reproduce but never could, I gave up looking in the end and any time we received reports of it, the only advice we gave was "log out and back in when it happens". Like I say, volume of this was so low it just wasn't worth the time trying to find the cause in my case.
As mentioned above, to AFIK we haven't had a single report of this happening since upgrading all boxes to Ast 16.