MeetMe Beep - remove it on customer side

[phil_discount]

Hey Guys,

i know that the meetme beep is a code and not a sound file and it's very difficult to change the sound cause of recomping asterisk with a correct file.

is it possible to prevent the beep on customerside?
everytime a customer gets a call, first he hears "beep"
furthermore if the callcenter manager will observe agents, customer and agent hear a beep again...

Thanks
regards
philip

[mflorell]

you could change the meetme extensions in the dialplan to remove the enter/leave sounds, but this would remove it from the agent as well.

Are you using the standard Asterisk meetme sounds or the ViciDial droplet/swish sounds?

[phil_discount]

on both sides it's very difficult cause agents don't look the whole time on the screen.

i think i use standard vicidial sounds (vicibox installation)

Code: Select all

exten => _86000[0-4]X,1,Meetme,${EXTEN}|q
exten => _86000[5-9]X,1,Meetme,${EXTEN}|F
exten => _8600[1-2]XX,1,Meetme,${EXTEN}|F

q means "quiet", so no sounds were played or?

is there any other solution?
i think some callcenters who uses vicidial ask if there is any possibility to prevent the beep sound.

[jayboo876]

Was anyone able to find a workaround for this?

[mflorell]

As we are working on an integration with ConfBridge for Asterisk 18(as a replacement for MeetMe, since it is slated to be removed from Asterisk), this will be one of the features we are working on, since it has been requested for so long. We don't have an ETA on this yet, but it is under development.

[williamconley]

Vicidial Agent Only Beep - Beta

Change the meetme room entry to remove the beep. Implement an agi script which activates upon entry to the room. The agi script determines the agent's channel and uses chanspy to play the beep sound ONLY to the agent.

[carpenox]

nice addition

[williamconley]

nice addition

Apparently this feature was started and then abandoned at some point. We piggybacked some of the existing code. Still in Beta because nobody wants to pay for it to be cleaned up (ie: change the names of the functions/etc away from the sample code we found online for near-hit functionality). But it seems to hold solid on single server or massive clusters. So far nobody has had a failure they've told us about.