VoIP

1 readers

1 users here now

Rules

Be civil. Disagreements of varying intensities will happen, but particularly vitriolic attacks will be pruned from the discussion.
Do not promote or advertise for any business, service or product unless responding to a specific request for recommendations. This includes recommending a user change providers when they have not indicated they are interested in doing so.
Do not send private messages to users, or invite users to send you a private message, for the purpose of promoting or advertising a business, service or product.
Do not invite, encourage, or seek help with engaging in unethical or fraudulent activity relating to VoIP, such as call spoofing, robocalling and autodialers, or fraudulent STIR/SHAKEN attestation.

founded 2 years ago

MODERATORS

communick@netheads.online

Digium Switchvox Doing Some Weird Stuff (alien.top)

submitted 2 years ago by Hello-Will@alien.top to c/voip@netheads.online

2 comments fedilink hide all child comments

I'm running a Digium Switchvox 355 physical PBX running Switchvox version 6.3.3 (82427). It has bee rock-solid for the most part, until recently.

Here's some of the issues we're experiencing:

When agents are dialing out, they're still receiving inbound calls
The Digium Switchvox dashboard numbers for received calls / missed calls is not accurate
Agents were still getting calls from the queue, even though they were marked not available or away
Voicemails were being delivered to user's individual mailboxes instead of the main queue shared email box

We were able to fix the last two issues by literally going into the extension queue settings, changing the wait time by 1 second and saving the config. It did manifest again, but the resolution has been to change queue time settings, save and problem resolved.

The other issues (inbound calls while dialing out and incorrect dashboard numbers) are persistent and I'm not sure what could be causing the issue.

The hardware is reporting the drives are not full, and there are two drives (probably in raid 1).

Have you guys encountered these types of issues before? Is there a way I can check the hard drive status to see if they're bad while the server is running?

top 2 comments

sorted by: hot top controversial new old

[–] JohnJimJoeBob@alien.top 1 points 2 years ago (1 children)

The last two issues likely have something to do with individual call rules. You'll want to log in as each user and look at the call rules there. Calls will follow the first set of rules that match both the status and the time frame conditions. Make sure any rule to "send to voicemail" only applies to Direct Calls and not All Calls or Queue Calls. Also note that a user's status is only as good as the call rules it triggers; the only built-in call rule sets are for "Available" and "Do Not Disturb". If users want to stop receiving queue calls, the best option is to make the queue log-in/log-out or use the queue Pause functionality from Switchboard; if you want to tie it to a certain status (Away or otherwise), make a set of call rules to trigger when you set that status and choose to Decline Queue Calls.

Any weirdness you're experiencing could be (and likely is) explained by the version you're running. They're up to Switchvox 8 now, and at the very least, you're several releases behind the latest version of 6. If there's any way for you to get up to date it would be recommended.

Is there something that makes you think the drives are bad? You may able to gather some information on them from the System Information page.

[–] Hello-Will@alien.top 1 points 2 years ago

My thought about the drives is due to the fact that it was working fine, nothing changed config-wise, and then it started having issues. Then, some of the issues are resolved by just making a small tweak and saving the changes. That seems fishy, and my first thought was potential data corruption caused by a failing drive.

What are your thoughts for the inbound calls while dialing out?