Barging Not Working

All installation and configuration problems and questions

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

Barging Not Working

Postby Ikram_Ali » Wed May 18, 2022 4:41 am

Hi, I'm facing barging issue where neither listen nor barging working. Extension got registered successfully, even we got a message on Vicidial that extension called but nothing on asterisk CLI, no logs generated there, hence, no ring for extension.

Configuration of our server.

CentOS Linux release 7.9.2009 (Core)

Astguiclient: 2.14b0.5
Asterisk: 13.29.2

I also enabled the Enable Agent Whisper Monitoring: 1 in System Settings

A help will be highly appreciated.
Posts: 24
Joined: Fri Aug 23, 2019 1:21 pm

Re: Barging Not Working

Postby martinch » Wed May 18, 2022 5:00 am

Hey Ikram,

Have you tried enabling allowed API functions on your user profile?

Admin > Users > Your User;

- Agent API Access: 1
- API List Restrict: 0
- API Allow Functions: ALL_FUNCTIONS or blind_monitor (for whispering and barging).

Also, do you have a screenshot of the realtime report with the message? Would help us help you :)

Posts: 49
Joined: Thu Nov 15, 2018 9:14 am

Re: Barging Not Working

Postby williamconley » Wed May 18, 2022 2:52 pm

You posted Vici version but not the FULL version with build. You also should post your installation method (with a link if it's not Goautodial from .iso). And for the record, it's not been "astguiclient" for over a decade. LOL: It's Vicidial.

All that being said:

Extension got registered successfully, even we got a message on Vicidial that extension called but nothing on asterisk CLI.

Extensions don't register. SIP accounts register. So do IAX2 accounts.

Please provide the basic information for the SIP or IAX2 Account in question. And what (specifically) you've put into the Real Time field. Note that the extension (ccxxx?) and context entries may be useful.

You could also try to turn on debug in asterisk cli. It may provide some insight. Some users include an "s" extension in their [default] context to capture invalid dials, but it should notify you of those anyway.

Then there's the API log which may bear fruit, since I believe this is initiated by an API call.
Vicidial Installation and Repair, plus Hosting and Colocation
Newest Product: Vicidial Agent Only Beep - Beta # 352-269-0000 # +44(203) 769-2294
Posts: 19952
Joined: Wed Oct 31, 2007 4:17 pm
Location: Davenport, FL (By Disney!)

Return to Support

Who is online

Users browsing this forum: williamconley and 58 guests