Need help on barge blind monitoring warning

Any and all non-support discussions

Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N

Need help on barge blind monitoring warning

Postby richmac2018 » Thu May 14, 2020 10:19 am

Hi All,

I would like to ask help regarding on barge blind monitoring warning. As we try to configure on this feature but it wont work on agent screen.And the customer still able to hear the ring sound though we change already the audio to beep sound only.

Image

Thank you and more power.
richmac2018
 
Posts: 31
Joined: Wed Jan 17, 2018 10:47 am

Re: Need help on barge blind monitoring warning

Postby williamconley » Fri May 15, 2020 9:29 am

1) Welcome to the Party! 8-)

2) As you are obviously new here, I have some suggestions to help us all help you:

When you post, please post your entire configuration including (but not limited to) your installation method (7.X.X?) and vicidial version with build (VERSION: 2.X-XXXx ... BUILD: #####-####).

This IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "manual/from scratch" you must post your operating system with version (and the .iso version from which you installed your original operating system) plus a link to the installation instructions you used. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600

3) Please describe the exact scenario and result. "it wont work" often results in "you did it wrong, but didn't provide any details, and had incorrect expectations of how this feature works". It also happens from time to time that the campaign being configured isn't the one being logged in to by the agent OR the call was inbound instead of outbound, thus controlled by a similar setting in the Ingroup which wasn't changed.

4) To be clear: You are saying "it doesn't work" while showing basic settings. But the feature has been tested and vetted and works. So something is amiss. Providing all the relevant details ... all of them ... is the best way to be sure you're not just pusing the wrong button. Additionally, if your installation method is shared with others, they may have similar issues that were related to their installation method.
Vicidial Installation and Repair, plus Hosting and Colocation
Newest Product: NonDisruptive Lead Loader for Enterprise Vicidial Clusters.
(IE: Keep on dialing even while loading large lists!)
http://www.PoundTeam.com # 352-269-0000 # +44(203) 769-2294
williamconley
 
Posts: 19403
Joined: Wed Oct 31, 2007 4:17 pm
Location: Davenport, FL (By Disney!)

Re: Need help on barge blind monitoring warning

Postby richmac2018 » Fri May 15, 2020 12:05 pm

Hi William,

Here:
Vicibox 8.1.2 from .iso | VERSION: 2.14-718a BUILD: 190902-0839 |Asterisk 13.21.1-vici | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel Corporation Xeon E7 v4/Xeon E5

Also I tried on Vicibox 7 but still theysame. It happen if i click on listen it works the feature it will apply the Blind Monitor Filename and it will show the " Someone is blind monitoring your session". But if I click barge it wont work, its just ring sound then connect barge in it wont apply the Blind Monitor Filename or even show the "Someone is blind monitoring your session"

Image
richmac2018
 
Posts: 31
Joined: Wed Jan 17, 2018 10:47 am

Re: Need help on barge blind monitoring warning

Postby williamconley » Fri May 15, 2020 12:53 pm

barging is not blind monitoring. thus notifying of blind monitoring when barging is not expected.
Vicidial Installation and Repair, plus Hosting and Colocation
Newest Product: NonDisruptive Lead Loader for Enterprise Vicidial Clusters.
(IE: Keep on dialing even while loading large lists!)
http://www.PoundTeam.com # 352-269-0000 # +44(203) 769-2294
williamconley
 
Posts: 19403
Joined: Wed Oct 31, 2007 4:17 pm
Location: Davenport, FL (By Disney!)

Re: Need help on barge blind monitoring warning

Postby richmac2018 » Fri May 15, 2020 1:11 pm

Hi William,

Ok, So is their anyway we can change the barge notification ring to customize sound file? or can we remove the ring sound when we do barging?

As per my research it will do if you dial manually the session id but our client dont want that way. They want the web realtime monitoring listen and barge feature.

Thanks,
richmac2018
 
Posts: 31
Joined: Wed Jan 17, 2018 10:47 am

Re: Need help on barge blind monitoring warning

Postby williamconley » Fri May 15, 2020 1:19 pm

hint: watch the CLI for the extension used for barging. then look in extensions.conf (or whichever included files in that file) for that extension. Note that it may be a pattern and not a literal, so you may need to find one with X's that matches the pattern, or search for what it does to find that pattern quicker).

There are switches included in the diaplan entry that cause or disable entry sounds. Modify the extension in use, but be sure to test all other situations where it may be used in case it turns off the audio indicator somewhere you don't want it to be turned off.
Vicidial Installation and Repair, plus Hosting and Colocation
Newest Product: NonDisruptive Lead Loader for Enterprise Vicidial Clusters.
(IE: Keep on dialing even while loading large lists!)
http://www.PoundTeam.com # 352-269-0000 # +44(203) 769-2294
williamconley
 
Posts: 19403
Joined: Wed Oct 31, 2007 4:17 pm
Location: Davenport, FL (By Disney!)

Re: Need help on barge blind monitoring warning

Postby richmac2018 » Fri May 15, 2020 2:44 pm

Hi William,

Im not sure if this is correct but I tried this I added with q. then I did the "dialplan reload". But still I able to hear the ring sound. unlike listen that their is no ring sound at all.

Image

Please advice. Thanks for the help.
richmac2018
 
Posts: 31
Joined: Wed Jan 17, 2018 10:47 am

Re: Need help on barge blind monitoring warning

Postby williamconley » Fri May 15, 2020 3:56 pm

If it didn't work as expected, we need to take it ... One step at a time. Please provide the CLI output during a test which shows the extension being used.
Vicidial Installation and Repair, plus Hosting and Colocation
Newest Product: NonDisruptive Lead Loader for Enterprise Vicidial Clusters.
(IE: Keep on dialing even while loading large lists!)
http://www.PoundTeam.com # 352-269-0000 # +44(203) 769-2294
williamconley
 
Posts: 19403
Joined: Wed Oct 31, 2007 4:17 pm
Location: Davenport, FL (By Disney!)

Re: Need help on barge blind monitoring warning

Postby richmac2018 » Mon May 18, 2020 6:24 am

Hi William,

I tried also in add in vicidial conference with m or q but it wont work it will just affect the conference with no sound.

With this is their no other solution to make this work theysame as listen feature but in barge way? Why is it not include the barge feature? Is it for paid version?


Barge logs:

Image


Listen logs:

Image


Thanks,
richmac2018
 
Posts: 31
Joined: Wed Jan 17, 2018 10:47 am

Re: Need help on barge blind monitoring warning

Postby williamconley » Mon May 18, 2020 9:55 am

it will just affect the conference with no sound

I interpret this to mean you can hear but not talk (no sound implies not hearing or talking)

In barge, it appears your system is dialing "8600051," which results in "8000,60,"
In monitor, there seems to also be an Fmq not present in barge.

One initiates with 08600051, the other with 68600051. Your previous post indicated you were editing extensions starting with _8 and _99.

I would copy/paste the relevant lines, but they are images so I can't. Seems like you were editing unrelated extensions to your purpose.
Vicidial Installation and Repair, plus Hosting and Colocation
Newest Product: NonDisruptive Lead Loader for Enterprise Vicidial Clusters.
(IE: Keep on dialing even while loading large lists!)
http://www.PoundTeam.com # 352-269-0000 # +44(203) 769-2294
williamconley
 
Posts: 19403
Joined: Wed Oct 31, 2007 4:17 pm
Location: Davenport, FL (By Disney!)

Re: Need help on barge blind monitoring warning

Postby richmac2018 » Tue May 19, 2020 3:24 pm

Hi William,

Barge it goes to 8600052
Listen it goes to 08600052

Can you teach me how set the barge without ring notification? Just like listen.


Barge logs:

-- Executing [038*128*066*005*8600052@default:1] Goto("Local/038*128*066*005*8600052@default-00000008;2", "default,8600052,1") in new stack
[May 19 22:55:40] -- Goto (default,8600052,1)
[May 19 22:55:40] -- Executing [8600052@default:1] MeetMe("Local/038*128*066*005*8600052@default-00000008;2", "8600052,F") in new stack
[May 19 22:55:40] > Channel Local/038*128*066*005*8600052@default-00000008;1 was answered
[May 19 22:55:40] -- Executing [8000@default:1] Dial("Local/038*128*066*005*8600052@default-00000008;1", "SIP/8000,60,") in new stack
[May 19 22:55:40] == Using SIP RTP CoS mark 5
[May 19 22:55:40] -- Called SIP/8000
[May 19 22:55:40] -- SIP/8000-00000003 is ringing
[May 19 22:55:41] == Manager 'sendcron' logged off from 127.0.0.1
[May 19 22:55:44] > 0x7f04b0014000 -- Probation passed - setting RTP source address to 180.232.70.205:26106
[May 19 22:55:44] NOTICE[8061][C-0000000f]: res_rtp_asterisk.c:4519 ast_rtp_read: Unknown RTP codec 95 received from '180.232.70.205:26106'
[May 19 22:55:44] > 0x7f04b0014000 -- Probation passed - setting RTP source address to 180.232.70.205:26106
[May 19 22:55:45] -- SIP/8000-00000003 answered Local/038*128*066*005*8600052@default-00000008;1
[May 19 22:55:45] > 0x7f04b0014000 -- Probation passed - setting RTP source address to 180.232.70.205:26106
[May 19 22:55:45] > 0x7f04b0014000 -- Probation passed - setting RTP source address to 180.232.70.205:26106
===================================================================================================================================

Listen logs:

-- Executing [038*128*066*005*08600052@default:1] Goto("Local/038*128*066*005*08600052@default-00000009;2", "default,08600052,1") in new stack
[May 19 22:57:16] -- Goto (default,08600052,1)
[May 19 22:57:16] -- Executing [08600052@default:1] Dial("Local/038*128*066*005*08600052@default-00000009;2", "IAX2/ASTblind:fhT1I5SiW3H19Hc@127.0.0.1:41569/68600052,55,To") in new stack
[May 19 22:57:16] -- Called IAX2/ASTblind:fhT1I5SiW3H19Hc@127.0.0.1:41569/68600052
[May 19 22:57:16] -- Accepting AUTHENTICATED call from 127.0.0.1:
[May 19 22:57:16] -- > requested format = gsm,
[May 19 22:57:16] -- > requested prefs = (gsm|ulaw),
[May 19 22:57:16] -- > actual format = ulaw,
[May 19 22:57:16] -- > host prefs = (ulaw),
[May 19 22:57:16] -- > priority = mine
[May 19 22:57:16] -- Call accepted by 127.0.0.1 (format ulaw)
[May 19 22:57:16] -- Format for call is (ulaw)
[May 19 22:57:16] -- Executing [68600052@default:1] MeetMe("IAX2/ASTblind-2027", "8600052,Fmq") in new stack
[May 19 22:57:16] -- IAX2/127.0.0.1:41569-7535 answered Local/038*128*066*005*08600052@default-00000009;2
[May 19 22:57:16] > Channel Local/038*128*066*005*08600052@default-00000009;1 was answered
[May 19 22:57:16] -- Executing [8000@default:1] Dial("IAX2/127.0.0.1:41569-7535", "SIP/8000,60,") in new stack
[May 19 22:57:16] -- Executing [h@default:1] AGI("Local/038*128*066*005*08600052@default-00000009;2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16-----ANSWER-----0-----0") in new stack
[May 19 22:57:16] == Using SIP RTP CoS mark 5
[May 19 22:57:16] -- Called SIP/8000
[May 19 22:57:16] -- <Local/038*128*066*005*08600052@default-00000009;2>AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---0-----0 completed, returning 0
richmac2018
 
Posts: 31
Joined: Wed Jan 17, 2018 10:47 am

Re: Need help on barge blind monitoring warning

Postby williamconley » Tue May 19, 2020 3:36 pm

What do you have in the .conf file for those two number patterns?
Vicidial Installation and Repair, plus Hosting and Colocation
Newest Product: NonDisruptive Lead Loader for Enterprise Vicidial Clusters.
(IE: Keep on dialing even while loading large lists!)
http://www.PoundTeam.com # 352-269-0000 # +44(203) 769-2294
williamconley
 
Posts: 19403
Joined: Wed Oct 31, 2007 4:17 pm
Location: Davenport, FL (By Disney!)

Re: Need help on barge blind monitoring warning

Postby richmac2018 » Wed May 20, 2020 10:29 am

Hi William,

for 08600052

; Local blind monitoring
exten => _08600XXX,1,Dial(${TRUNKblind}/6${EXTEN:1},55,To)
exten => _08600XXX,n,Hangup()

for 8600052
; VICIDIAL conferences
exten => _86000[5-9]X,1,Meetme(${EXTEN},F)
exten => _86000[5-9]X,n,Hangup()

Now, I really dont have an idea on how the barge without ring notification to make this work. Please help. Thanks
richmac2018
 
Posts: 31
Joined: Wed Jan 17, 2018 10:47 am

Re: Need help on barge blind monitoring warning

Postby richmac2018 » Fri May 22, 2020 4:31 am

Hi All,

Anybody know how to solve this?

Thank you.
richmac2018
 
Posts: 31
Joined: Wed Jan 17, 2018 10:47 am

Re: Need help on barge blind monitoring warning

Postby williamconley » Fri May 22, 2020 7:50 am

richmac2018 wrote:exten => _08600XXX,1,Dial(${TRUNKblind}/6${EXTEN:1},55,To)
exten => _86000[5-9]X,1,Meetme(${EXTEN},F)


Difference: One uses the "F" switch. The other ... you don't actually have yet, since this redials with "6" instead of "0". So now you'll need to find the "6" version to make your comparison.
Vicidial Installation and Repair, plus Hosting and Colocation
Newest Product: NonDisruptive Lead Loader for Enterprise Vicidial Clusters.
(IE: Keep on dialing even while loading large lists!)
http://www.PoundTeam.com # 352-269-0000 # +44(203) 769-2294
williamconley
 
Posts: 19403
Joined: Wed Oct 31, 2007 4:17 pm
Location: Davenport, FL (By Disney!)

Re: Need help on barge blind monitoring warning

Postby richmac2018 » Fri May 22, 2020 1:01 pm

; quiet monitor-only extensions for meetme rooms (for room managers)
exten => _68600XXX,1,Meetme(${EXTEN:1},Fmq)
exten => _68600XXX,n,Hangup()

6 it will go to listen and I need the barge. I tried Fmq argument in xten => _86000[5-9]X,1,Meetme(${EXTEN},F) but again it will just mute the audio.

Question why if I barge on my softphone with dial directly the session id it will go without ring notification ? But if im using in the browser with barge realtime monitoring admin it will go with ring notification. And they are running on theysame extension exten => _86000[5-9]X,1,Meetme(${EXTEN},F) ?

Direct dial:
Executing [8600051@default:1] MeetMe("SIP/8000-00000002", "8600051,F") in new stack

realtime monitoring admin browser:
Executing [8600051@default:1] MeetMe("Local/038*128*066*005*8600051@default-00000006;2", "8600051,F") in new stack
richmac2018
 
Posts: 31
Joined: Wed Jan 17, 2018 10:47 am

Re: Need help on barge blind monitoring warning

Postby williamconley » Fri May 22, 2020 1:35 pm

The problem, as I see it, is that your troubleshooting methodology involves "try for a bit, then jump around and skip things". 8-) (Yep, I'm a smart ass)

Back to where we were, which was:
Code: Select all
exten => _86000[5-9]X,1,Meetme(${EXTEN},F)

vs
Code: Select all
exten => _08600XXX,1,Dial(${TRUNKblind}/6${EXTEN:1},55,To)


but "Dial" ... that's not accessing the meetme room which would result from 6${EXTEN:1}, so you looked up the actual meetme code that would fire with that "6" prefix and found:
Code: Select all
exten => _68600XXX,1,Meetme(${EXTEN:1},Fmq)


So now we're comparing these two:
Code: Select all
exten => _86000[5-9]X,1,Meetme(${EXTEN},F)
exten => _68600XXX,1,Meetme(${EXTEN:1},Fmq)

Seems like one of these has "Fmq" and the other has "F".
Do you know what the F,m,q options are for the asterisk meetme command?
Vicidial Installation and Repair, plus Hosting and Colocation
Newest Product: NonDisruptive Lead Loader for Enterprise Vicidial Clusters.
(IE: Keep on dialing even while loading large lists!)
http://www.PoundTeam.com # 352-269-0000 # +44(203) 769-2294
williamconley
 
Posts: 19403
Joined: Wed Oct 31, 2007 4:17 pm
Location: Davenport, FL (By Disney!)

Re: Need help on barge blind monitoring warning

Postby richmac2018 » Mon May 25, 2020 11:17 am

Hi William,

F - Pass DTMF through the conference.
m - Set initially muted.
q - Quiet mode (don't play enter/leave sounds).

I already tried those arguments in VICIDIAL conferences and it happen the audio will be muted.
extension exten => _86000[5-9]X,1,Meetme(${EXTEN},F) )

What is the correct way?
richmac2018
 
Posts: 31
Joined: Wed Jan 17, 2018 10:47 am

Re: Need help on barge blind monitoring warning

Postby richmac2018 » Wed May 27, 2020 8:14 am

Hi All,

Do you have update on this?


Thanks
richmac2018
 
Posts: 31
Joined: Wed Jan 17, 2018 10:47 am


Return to General Discussion

Who is online

Users browsing this forum: No registered users and 35 guests