Why do I periodically get several repeated calls from "101"?
RonR:
Quote from: bradwn on June 08, 2011, 02:41:17 pm
Ok, a month later and after changing the port #, and I'm still getting calls occasionally. The latest ones occured on 5/21 and 5/23, from Peer Number "200" and "asterisk" (4 times). How do I make this stop? Can I block any calls that are not from a regular telephone number?
Did you try the suggestion I posted on May 6:?
Voice Services -> SP1 Service -> X_InboundCallRoute : {101:},{ph}
A more general, 3-digit block would be:
Voice Services -> SP1 Service -> X_InboundCallRoute : {(xxx):},{ph}
bradwn:
No, I didn't. So I enter it brackets and all as follows?:
{200:},{ph}
Can I do this to cover the most frequent peers?:
{101:},{200:},{asterisk:},{ph}
What exactly does that do?
RonR:
The InboundCallRoute is used to route incoming calls. It can match CallerID numbers and do something special with them. Since you're getting more than just 101 now and they appear to always be 3-digit numbers, I suggest:
Voice Services -> SP1 Service -> X_InboundCallRoute : {(xxx):},{ph}
This will route any incoming call with a CallerID of a 3-digit number to the bit-bucket. All others will go to the PHONE Port as usual.
bradwn:
I appreciate your help. 2 questions to clarify:
1. Do I enter this into the field exactly as shown (between the quotes) "{(xxx):},{ph}" ? I ask because currently InboundCallRoute is set to default, and the field simply shows "ph". The syntax of what you posted seems different.
2. Is there a way I can do the same with "asterisk"? That is the most frequent call I get.
RonR:
The curly braces can be omitted if there is only one rule in the route, hence the ph instead of {ph}.
If 'asterisk' is being listed as a Peer Number, then a rule for it too can be included:
Voice Services -> SP1 Service -> X_InboundCallRoute : {asterisk:},{(xxx):},{ph}
The InboundCallRoute format is described in detail on page 113 of the OBi Device Administration Guide.
Navigation
[0] Message Index
[#] Next page
[*] Previous page