Common problems

Common problems and fixes

Start with what you can see, learn the first safe check, and avoid shortcuts that can make the problem worse.

129 problemsCheck before changing anythingFull guides included

Start with what you see

Common problems. Safe first checks.

Each problem links to a complete step-by-step guide.

B01

Asterisk · recording cleanup

Recording keeps running after a call

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Stop making changes; preserve the timestamp and recording ID, then have the Asterisk owner trace that one synthetic call's channel cleanup.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B02

VICIdial · call delivery

Live agent receives no calls

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Correlate the browser session, conference, vicidial_live_agents row, hopper and carrier at one timestamp.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B03

Asterisk · Local channels

NO DestChannel mapping race

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Align AGI lookup time with Newchannel, DialBegin and bridge events for the same unique ID.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B04

Asterisk · recording integrity

Recordings merge between calls

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Compare the exact recording ID and filename at recorder start, stop, database update and filesystem close.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B05

SIP · DNS

Carrier hostname stops resolving

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Resolve the hostname from the same namespace and resolver configuration used by Asterisk or OpenSIPS.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B06

Reporting · interval math

Agent time detail overcounts visibility

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Clip every event interval to the agent login and visibility intervals before aggregation.
Compare the before-and-after result using the same filters and time window; retain the evidence and rollback if the result changes unexpectedly.

See the full guide

B07

Dialer · AMD

AMD discards human pickups

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Label representative audio, keep one stable control and alter only one threshold at a time.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B08

VICIdial · agent station

Phone login is not active

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Verify the test agent's separate phone-login record and station assignment in Admin; use the correct credential type and never share passwords.
Compare the before-and-after result using the same filters and time window; retain the evidence and rollback if the result changes unexpectedly.

See the full guide

B09

Operations · capacity

Calls overlap or the dialer slows down

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Pause expansion, capture the active-agent count and timestamp, then have the platform owner compare approved resource monitoring with the call state.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B10

SIP · security boundary

SIP attack traffic reaches Asterisk

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Treat it as a security incident: preserve a sanitized timestamp and receiving interface, then have the firewall and SIP owners verify the intended exposure boundary.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B11

SIP · carrier quality

Dead air or fake answers increase

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Keep campaign settings unchanged and compare approved aggregate results by route and time window; send that evidence to the carrier owner.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B12

SIP · RTP audio

Inbound call has dead air or delayed audio

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Reproduce with an internal test endpoint, then have the network owner verify the negotiated RTP path, NAT policy, and firewall range for that one call.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B13

WebRTC · Asterisk

WebRTC call does not bridge to the ready agent

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Test one approved browser and account, record the build/version, then have the telephony owner compare WebRTC, PJSIP, conference, and TLS/DTLS logs at that timestamp.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B14

Reporting · timezone

Inbound report time is wrong

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the report timezone, VICIdial server time, database time, and browser timezone; correct the one approved source of truth and rerun the same report.
Compare the before-and-after result using the same filters and time window; retain the evidence and rollback if the result changes unexpectedly.

See the full guide

B15

VICIdial · custom fields

Custom fields do not save or display

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Reproduce with one synthetic lead and one field, then have the VICIdial owner verify the field definition, campaign/list scope, permissions, and recorded build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B16

Recording · call metadata

Caller ID is wrong in a recording name

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Use one synthetic call and compare its lead, call, and recording identifiers before changing any filename pattern or recording process.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B17

Inbound · routing

IVR fails on a private-network deployment

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Trace one lab call from DID to inbound group, call menu, extension, and audio path; have the network owner validate the intended NAT and reachable addresses.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B18

Asterisk · migration

Monitoring or whisper breaks after PJSIP migration

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Treat it as a version-specific migration issue: test one lab conference, record the Asterisk/VICIdial versions, and compare supported conference and endpoint settings with the owner.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B19

Database · list maintenance

Lead list work stalls on a database lock

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Pause competing list-maintenance jobs through the approved process, then have the database owner capture a read-only lock snapshot and identify the blocking transaction.
Compare the before-and-after result using the same filters and time window; retain the evidence and rollback if the result changes unexpectedly.

See the full guide

B20

Forum issue index · version-specific

Significant spam flagging

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B21

Forum issue index · version-specific

On-hook agent and manual call acceptance

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B22

Forum issue index · version-specific

Agent Time Detail inconsistency

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Compare the before-and-after result using the same filters and time window; retain the evidence and rollback if the result changes unexpectedly.

See the full guide

B23

Forum issue index · version-specific

Recording storage query

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B24

Forum issue index · version-specific

Carriers versus inbound groups

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B25

Forum issue index · version-specific

Custom date entry in a list

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B26

Forum issue index · version-specific

Removing an agent callback

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B27

Forum issue index · version-specific

External hangup ends an incoming call

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B28

Forum issue index · version-specific

Moving leads from warming to sales campaign

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B29

Forum issue index · version-specific

SSL shutdown

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B30

Forum issue index · version-specific

Inbound dead air or audio starts after 30 seconds

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B31

Forum issue index · version-specific

Changing domain for VICIdial with WebRTC

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B32

Forum issue index · version-specific

SVN repository unavailable

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B33

Forum issue index · version-specific

VICIdial status DEAD on ViciBox 12.0.2

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B34

Forum issue index · version-specific

Transfers recorded as RAXFER instead of XFER

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B35

Forum issue index · version-specific

Agent login as vici_customer_user

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Compare the before-and-after result using the same filters and time window; retain the evidence and rollback if the result changes unexpectedly.

See the full guide

B36

Forum issue index · version-specific

History or detailed report shows deleted user

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Compare the before-and-after result using the same filters and time window; retain the evidence and rollback if the result changes unexpectedly.

See the full guide

B37

Forum issue index · version-specific

List reset recommendation

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B38

Forum issue index · version-specific

ViciBox 12.0.2 install issue

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B39

Forum issue index · version-specific

Download list problem

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B40

Forum issue index · version-specific

No Live Call control remains grey during predictive dialing

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B41

Forum issue index · version-specific

ViciBox 13 WebPhone, DTLS, SELinux and FastAGI gotchas

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B42

Forum issue index · version-specific

Mute agent during a call

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B43

Forum issue index · version-specific

Drop status with agent on inbound call

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B44

Forum issue index · version-specific

Automatic list reset option

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B45

Forum issue index · version-specific

Manual Dial Override on a callback

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B46

Forum issue index · version-specific

Assigning ports in a gateway

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B47

Forum issue index · version-specific

Agent times in stats report

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Compare the before-and-after result using the same filters and time window; retain the evidence and rollback if the result changes unexpectedly.

See the full guide

B48

Forum issue index · version-specific

Reporting database optimization

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Compare the before-and-after result using the same filters and time window; retain the evidence and rollback if the result changes unexpectedly.

See the full guide

B49

Forum issue index · version-specific

Identify outgoing carrier in carrier_log

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Compare the before-and-after result using the same filters and time window; retain the evidence and rollback if the result changes unexpectedly.

See the full guide

B50

Forum issue index · version-specific

WebRTC fails outside the local network

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B51

Forum issue index · version-specific

iOS Call Screening causes false AMD detection

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B52

Forum issue index · version-specific

Report page shows incorrect disk usage

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Compare the before-and-after result using the same filters and time window; retain the evidence and rollback if the result changes unexpectedly.

See the full guide

B53

Forum issue index · version-specific

High CPU load causes call distortion

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Compare the before-and-after result using the same filters and time window; retain the evidence and rollback if the result changes unexpectedly.

See the full guide

B54

Forum issue index · version-specific

Skipped leads in a specific list

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B55

Forum issue index · version-specific

iOS Call Screening detected as AMD

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B56

Forum issue index · version-specific

Blank calls in survey dialing

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B57

Forum issue index · version-specific

Incoming load balancing

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B58

Forum issue index · version-specific

GMT cron affects calling

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B59

Forum issue index · version-specific

Inbound calls configuration

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B60

Forum issue index · version-specific

Session has been disabled

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B61

Forum issue index · version-specific

AMD detection issue

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B62

Forum issue index · version-specific

Customer information collection

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B63

Forum issue index · version-specific

monitor_end_time and monitor_sec missing

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Compare the before-and-after result using the same filters and time window; retain the evidence and rollback if the result changes unexpectedly.

See the full guide

B64

Forum issue index · version-specific

Agent activity record confusion

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B65

Forum issue index · version-specific

Static IP change

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B66

Forum issue index · version-specific

Stereo recordings have separate customer and agent channels

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B67

Forum issue index · version-specific

Australia outbound calls

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B68

Forum issue index · version-specific

Incorrectly loaded leads

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B69

Forum issue index · version-specific

Inbound group HOLD versus WAIT state

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B70

Forum issue index · version-specific

Agent transfer group

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B71

Forum issue index · version-specific

Too many no answers

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B72

Forum issue index · version-specific

VoIP connectivity question

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B73

Forum issue index · version-specific

VoIP service outage

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B74

Forum issue index · version-specific

Managing DROP calls without AMD

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B75

Forum issue index · version-specific

Choosing a SIP provider

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B76

Forum issue index · version-specific

Need a VoIP provider

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B77

Forum issue index · version-specific

Dial timeout in carrier failover dialplan

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Compare the before-and-after result using the same filters and time window; retain the evidence and rollback if the result changes unexpectedly.

See the full guide

B78

Forum issue index · version-specific

STIR/SHAKEN, DID and carrier strategy

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B79

Forum issue index · version-specific

Asterisk 16 and server replacement

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B80

Forum issue index · version-specific

Agent live-call notification delay

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B81

Forum issue index · version-specific

VICIdial Agent Events push

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B82

Forum issue index · version-specific

Reporting for extensions outside the agent portal

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Compare the before-and-after result using the same filters and time window; retain the evidence and rollback if the result changes unexpectedly.

See the full guide

B83

Forum issue index · version-specific

SIP extension closer

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B84

Forum issue index · version-specific

VICIdial server installation issue

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B85

Forum issue index · version-specific

Custom reports example

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Compare the before-and-after result using the same filters and time window; retain the evidence and rollback if the result changes unexpectedly.

See the full guide

B86

Forum issue index · version-specific

Database server without keepalive

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Compare the before-and-after result using the same filters and time window; retain the evidence and rollback if the result changes unexpectedly.

See the full guide

B87

Forum issue index · version-specific

call_log end_time NULL and recording channel remains after disposition

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B88

Forum issue index · version-specific

Add callback to dial status

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B89

Forum issue index · version-specific

Zoiper configuration

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B90

Forum issue index · version-specific

Inbound calls setup

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B91

Forum issue index · version-specific

Unknown VICIdial user attempting a call

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B92

Forum issue index · version-specific

System delay error 2339930-1

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B93

Forum issue index · version-specific

Dead Call Trigger Action does not play audio

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B94

Forum issue index · version-specific

Change VICIdial domain name or FQDN

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B95

Forum issue index · version-specific

ViciBox 9 to ViciBox 12.0.2 migration

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B96

Forum issue index · version-specific

Normalize 11-digit leads to 10 digits

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B97

Forum issue index · version-specific

Limit rings

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B98

Forum issue index · version-specific

Entire call duration recorded as paused

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B99

Forum issue index · version-specific

Realtime panel in-group stats

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Compare the before-and-after result using the same filters and time window; retain the evidence and rollback if the result changes unexpectedly.

See the full guide

B100

Forum issue index · version-specific

VICIdial process consumes high CPU

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Compare the before-and-after result using the same filters and time window; retain the evidence and rollback if the result changes unexpectedly.

See the full guide

B101

Forum issue index · version-specific

Custom routing extension for auto-dial campaign

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B102

Forum issue index · version-specific

VICIdial cluster migration advice

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B103

Forum issue index · version-specific

Dial plan entry for autodial

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B104

Forum issue index · version-specific

Asterisk versions supported by VICIdial

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B105

Forum issue index · version-specific

Manager manual question

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B106

Forum issue index · version-specific

VicidialNOW support prerequisite

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B107

Forum issue index · version-specific

Support posting prerequisite

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B108

Forum issue index · version-specific

IVR not working with private IP

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B109

Forum issue index · version-specific

WebRTC autodial does not bridge to agent conference

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B110

Forum issue index · version-specific

Custom fields bug

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B111

Forum issue index · version-specific

Monitoring and whisper broken after PJSIP migration

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B112

Forum issue index · version-specific

vicidial_lists locked by AST_flush_DBQueue.pl

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Compare the before-and-after result using the same filters and time window; retain the evidence and rollback if the result changes unexpectedly.

See the full guide

B113

Forum issue index · version-specific

Inbound report is two hours off

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Compare the before-and-after result using the same filters and time window; retain the evidence and rollback if the result changes unexpectedly.

See the full guide

B114

Forum issue index · version-specific

Carrier FAS, dead air and answering machines

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B115

Forum issue index · version-specific

SIP attack reaches Asterisk despite firewall rule

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B116

Forum issue index · version-specific

Overlapping calls

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B117

Forum issue index · version-specific

Phone login and password are not active

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Compare the before-and-after result using the same filters and time window; retain the evidence and rollback if the result changes unexpectedly.

See the full guide

B118

Forum issue index · version-specific

Recording does not stop after transfer or hangup

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B119

Forum issue index · version-specific

Agent Time Detail inconsistency follow-up

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Compare the before-and-after result using the same filters and time window; retain the evidence and rollback if the result changes unexpectedly.

See the full guide

B120

Forum issue index · version-specific

Recording storage follow-up

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B121

Forum issue index · version-specific

SSL shutdown follow-up

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B122

Forum issue index · version-specific

CPU call distortion follow-up

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Compare the before-and-after result using the same filters and time window; retain the evidence and rollback if the result changes unexpectedly.

See the full guide

B123

Forum issue index · version-specific

Skipped leads follow-up

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B124

Forum issue index · version-specific

WebRTC outside-network follow-up

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Change one owner-approved telephony setting only, repeat the same test, and verify both call legs before closing the issue.

See the full guide

B125

Forum issue index · version-specific

Inbound drop status follow-up

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B126

Forum issue index · version-specific

Predictive dialing live-call state follow-up

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B127

Forum issue index · version-specific

VICIdial status DEAD follow-up

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B128

Forum issue index · version-specific

High-volume inbound manual acceptance follow-up

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide

B129

Forum issue index · version-specific

Spam flagging follow-up

Solution

Use one approved test, or a read-only aggregate report. Record the exact time and affected scope before changing anything.
Record the VICIdial, Asterisk and OS versions; reproduce only in a lab or approved test scope; then apply the exact owner-approved correction for that build.
Apply the approved correction only to the test fixture, then verify lead state, call outcome, and campaign behavior before a controlled rollout.

See the full guide