Quote from: rob613@gmail.com on March 27, 2012, 04:13:17 PM
Is there any feature to automatically answer calls...that come with Caller-ID information matching say a telemarketer...? Some special handling could be to answer and hang up, or ... forward.
Why bother with forwarding? If it is a junk caller, just hang up. (That's what the blocking software on my cell phone does, and what my Callcentric rules do.) At best, if you were unsure, you'd send them to voice mail.
QuoteIs 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?
You are looking for functionality that is going to be painful - if even possible with the current firmware - to implement in an OBi. If they specifically added support for user-friendly call routing rules, then yes.
The easy solution would be to use Callcentric, which provides a web UI for creating rules like you want. If you want to "firewall" more than just your inbound SIP calls, then maybe the solution is to have your OBi forward everything to Callcentric, and then have it proxy it back to you. (Obviously this could reduce reliability and quality, as Callcentric's servers will remain in the middle of all calls.)
Aside from various approaches where you outsource things to Callcentric or Google Voice, the only other option that comes to mind is to have the OBi do a SIP hand-off to a SIP proxy that you run on a local server, where you can then implement rules to drop the call, or forward it to someplace where you have voice mail. (In this case you could use SIP forwarding - like an HTTP redirect - so your proxy doesn't have to remain in the middle. But a POTS or GV inbound call would still keep your OBi tied up until the caller is done leaving voice mail.) I'm also not sure where you'd terminate "normal" calls. I don't think you could bounce them back to the originating OBi, so you'd need a 2nd one or another SIP phone.
QuoteAnd perhaps there is a way to place that SIP call including the true originator's caller-ID, not the Obi's...
Should be no problem with SIP forwarding. Any SIP proxy should handle this.
QuoteI see that there are already some entries in this field related to my circle of trust.
Doesn't that also imply that the field is being managed by the Obitalk web UI? And if you are going to customize it, you'd have to uncheck the default checkbox and break the link? Probably not what you want to do if the circle of trust feature depends on that and you are using that functionality.
QuoteIts not obvious to me how to extend what is there to include a list of unwanted caller ID strings.
Post what you currently have (anonymize the numbers as necessary).