[Asterisk-Dev] Block caller ID patch submitted

[Martin Pycko]

Why don't you use the PRES_PROHIB_NETWORK_NUMBER instead of 35 (0x23) ?

regards
Martin

On Mon, 4 Aug 2003, John Todd wrote:

>
> I've submitted a patch to the bugs.digium.com system (#48) that I believe will make Asterisk "legal" to use in situations where blocked caller ID data is sent to Asterisk with a "block" flag set.  This apparently is the mode of choice for some CLECs, but sending the caller ID data along to the end station is illegal (at least, here in the US it is.)  All you CLECs should be very interested in this patch.  :)  While sending caller ID data even if blocked seems noble (thwart those telemarkters!) it is still undesired, since there are situations where this could be very bad for the caller (think of spousal abuse cases, or workplace whistleblowers.)
>
> As I mention in the bug/feature request, someone with more zapata.conf clue should make this a per-PRI configurable switch instead of always-on or always-off.
>
> JT
>
>
>
> --- q931.c~     Sat Jul 26 15:14:44 2003
> +++ q931.c      Mon Aug  4 17:49:08 2003
> @@ -741,6 +741,7 @@
>
>         q931_get_number(cnum, sizeof(cnum), ie->data + 2, len - 4);
>         pri_message("%c Calling Number (len=%2d) [ Ext: %d  TON: %s (%d)  NPI: %s (%d)\n", prefix, len, ie->data[0] >> 7, ton2str((ie->data[0] >> 4) & 0x07), (ie->data[0] >> 4) & 0x07, npi2str(ie->data[0] & 0x0f), ie->data[0] & 0x0f);
> +       if ((ie->data[1] & 0x7f) == 35) cnum[0] = '\0';
>         pri_message("%c                           Presentation: %s (%d) '%s' ]\n", prefix, pri_pres2str(ie->data[1]), ie->data[1] & 0x7f, cnum);
>  }
>
> _______________________________________________
> Asterisk-Dev mailing list
> Asterisk-Dev at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-dev
>