automatically answering unwanted calls on the PSTN line on an obi110

(1/3) > >>

rob613@gmail.com:
Is there any feature to automatically answer calls, especially from the PSTN line, that come with Caller-ID information matching say a telemarketer who has been told, under penalties of telephone harassment, to cease calling here?   Some special handling could be to answer and hang up, or answer with a special message, or answer and bridge the call out to the local police or some other appropriate call forwarding destination.

RonR:
To have the caller ignored (they will hear endless ringing):

Physical Interfaces -> LINE Port -> InboundCallRoute : {12341234567:},{ph}

To forward the caller elsewhere:

Physical Interfaces -> LINE Port -> InboundCallRoute : {12341234567:sp1(18005551212)},{ph}

where 12341234567 is the calling number.

MichiganTelephone:
You could always forward such calls to one of the numbers on this page:

http://www.humorhotlines.com/rejectionhotline.asp

fredp:
Very excellent!  I just learned something (very cool bit of programming) and got entertained (again and again - LOL).

rob613@gmail.com:
I see that there are already some entries in this field related to my circle of trust.
Its not obvious to me how to extend what is there to include a list of unwanted caller ID strings.
Could I please see an example configuration for how to add this new capability to the existing capability?

I am also not quite clear on the terminology for the outbound route, such as if I have an Obi110 with a local PSTN line, a SIP provider, and a Google Voice number.  If its an inbound PSTN call I guess the outbound call should go via Google Voice.   What would happen if an inbound PSTN call comes in while I am already using the Google Voice line?

Is there any way to improve this with a level of indirection such as to have a table of unwanted numbers to reference within this rule, but the rule remains static?   Perhaps one of these rejection hotlines will someday add a full SIP specification that the Obi could use regardless of the state of the SIP or Google Voice virtual ports?   And perhaps there is a way to place that SIP call including the true originator's caller-ID, not the Obi's, since its a virtual call?

Navigation

[0] Message Index

[#] Next page