automatically answering unwanted calls on the PSTN line on an obi110
tmetro:
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.
Quote
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?
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.
Quote
And 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.
Quote
I 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.
Quote
Its 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).
rob613@gmail.com:
The earlier suggestion was to have this for an inbound call route:
Physical Interfaces -> LINE Port -> InboundCallRoute : {12341234567:sp1(18005551212)},{ph}
It was not clear to me how to parse this, and thus how to extend it. Even more complicated is that I already have a customized entry there I think due to the trusted callers.
By inspection it seems that this is a comma-separated list of curly-brace delimited expressions of (a):(b), and where (a) is an '|' separated list of caller-ID's, an (b) can be "aa" for the Obi auto attendant, "ph" [without an (a) part] to ring through to the phone port, or sp1(nnn) to forward out through service SP1 to some number nnn.
I have been able to make it work to forward calls from a handful of repeat offender telemarketers (having used my own test line) to forward to one of the rejection lines. Unfortunately my home phone does ring while the forwarded call is being initiated, but this should provide some improvement.
If there are any SIP specifications of useful intercept recordings to forward to, especially one to use for telemarketers in violation of my clearly explained preferences, please update them here. I think SIP specifications will be useful since they should initiate faster and remain free to operate.
Ideally an SP2(cid:nnn) syntax could be used to place the SIP call with the actual caller's caller-ID with some special symbol to match the caller's CID info. I hope Obi can add this or tell us how to do it.
RonR:
Quote from: rob613@gmail.com on May 09, 2012, 03:46:29 pm
It was not clear to me how to parse this, and thus how to extend it.tell us how to do it.
See the OBi Device Administration Guide.
rob613@gmail.com:
Based on information in another thread I updated my configuration for this matter by adding two custom digit maps. My one map trust and my other map reject.
My line for handling the incoming calls now references through these maps for lists of numbers to trigger upon.
I have two concerns.
1) it doesn't work yet - I need to comb through the other posting better to see if I did something wrong
2) even if it worked, its still to heavy a solution... any minor change such as adding a new number to my list of numbers to reject, the Obi110 requires a reboot for the change to take effect. A map is probably too heavy for what I want here, just a lightweight list of numbers that can be updated without a reboot.
The other thread brings me to seeing a great feature that I think is worth extending, so I'll post about that in another message on this thread.
rob613@gmail.com:
In this other thread - http://www.obitalk.com/forum/index.php?topic=2327.0 - I see a useful technique for passing on through $1 the caller-ID of the caller whom the auto-attendant should call back.
In my case of wanting to use the Obi110 to answer and dispose of calls that I wish to reject based on CID, I think there is another use for passing an argument of $1, and that is a good case to spoof the caller-ID of the real caller on my PSTN line.
The behavior I want is to generate a custom message with text to voice live on the fly which reminds the caller that they were asked to not call here again in a prior call and that the date and time of the call has been logged for consequences against them.
The behavior I am getting is force-fitting these calls to forward to a rejection hotline using my SP1 call out. Since that is a GV or SIP call I should be able to use the Caller-ID-spoofing technique to just call a special number which speaks the caller-ID of the caller for test purposes even if I cannot customize it to be more scary for the caller. Even better is if I can have a custom scare the caller line set up on some SIP number at some PBX or provider to do that for me and for any others who want this feature.
FEATURE REQUEST:
Obi110 should permit forwarding through sp1 or sp2 not just with a single parameter for the number I wish to forward the call to, but a second parameter for the caller-ID to use when forwarding.
For a trusted caller I might also want this feature so that calls I place for them inherit their caller-ID, and not the caller-ID of my Obi box. The difference would be that they are calling a real number, and not a rejection line.
Navigation
[0] Message Index
[#] Next page
[*] Previous page