Ticket #3430 (reopened Feature Requests)

Opened 1 month ago

Last modified 1 month ago

Inbound Routes with Privacy Manager enabled do not check Blacklist

Reported by: marv Assigned to: p_lindheimer
Priority: minor Milestone: 2.6
Component: Core - Trunks/Routing Version: 2.5-branch
Keywords: Cc:
Confirmation: Unreviewed SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description

Inbound Routes with Privacy Manager enabled do not check Blacklist after the caller has entered their CID.

Change History

12/04/08 10:02:00 changed by mickecarlsson

  • status changed from new to closed.
  • resolution set to invalid.

This is not a bug. The call flow for Inbound Routes are: Blacklist check against CID Cidlookup Privacy manager for calls without CID

Closing this as invalid.

12/04/08 10:03:17 changed by mickecarlsson

Enter this again as the formatting was lost:

This is not a bug.

The call flow for Inbound Routes are:
Blacklist check against CID
Cidlookup
Privacy manager for calls without CID

Closing this as invalid

12/04/08 22:46:22 changed by mykroft

Why would this be invalid and not a bug - how are you supposed to check blacklist against privacy manager entry?

12/04/08 23:14:04 changed by mickecarlsson

As explained in the forum. There is nothing preventing the caller to enter a bogus CID in Privacy Manager, and checking Blacklist after that is pointless.

You could use Call Screening defined per extension instead.

12/05/08 10:13:49 changed by mickecarlsson

  • status changed from closed to reopened.
  • type changed from Bugs to Feature Requests.
  • resolution deleted.

After a discussion with other developers we decided to change the ticket to a Feature Request as this is not a bug as the current implementation is valid. However, we do see a use for Blacklist check after Privacy Manager. Comments are welcome.