DNC status and DNC list

[karlb]

We have noticed that if we use custom campaign status's and set a status as DNC for the campaign, that same status on another campaign will be sent to the internal DNC list when it is not marked as a DNC status for that campaign.

Example, we have custom status "30" on campaign A set as a DNC status.

We have custom status "30" on campaign B set as just a regular refusal, not DNC.

Every single "30" we disposition on campaign B gets added into our internal DNC list.

This is causing some issues. I was wondering if someone could point me to the script that may be doing this so I can take a look and try to fix it?

Thanks!

----------------------------------------------
VERSION: 2.6-392a
BUILD: 130102-1135
SVN Version: 1915
1x DB
1x Web
2x Dialer
1x Sangoma CPD
Each server is HP DL380 G5, 2x quad core xeon, 16GB RAM.

[williamconley]

Before you try to fix it, you should upgrade and see if it's already been fixed. If you don't want to upgrade your cluster, just test it on a virtual installation. If it has not, you should open an issue in the Vicidial Issue Tracker and post a link to it here.

The code in question could be running in the agent screen or the DB connector responsible for setting the lead's status upon disposition. in the meantime, consider changing your statuses to not coincide like that. LOL