SPAM calls on the OBITALK network

<< < (2/3) > >>

drgeoff:
Quote from: Kage on May 19, 2018, 09:30:17 am

In the InboundCallRoute I had used this to ban incoming calls with the less than seven digits:

{(x|xx|xxx|xxxx|xxxxx|xxxxxx):},{ph}

Does anyone know if when you update google voice these settings become non-functional?

There is no change to the functioning of InboundCallRoute.

azrobert:
GV started sending a plus sign with the CallerID after the switch to SIP. You can verify this by looking at the OBi Call History.
http://www.obitalk.com/forum/index.php?topic=13885.0

Try the following:
{(+x|+xx|+xxx|+xxxx|+xxxxx|+xxxxxx):},{ph}

Kage:
Quote from: drgeoff on May 19, 2018, 09:51:18 am

Quote from: Kage on May 19, 2018, 09:30:17 am

In the InboundCallRoute I had used this to ban incoming calls with the less than seven digits:

{(x|xx|xxx|xxxx|xxxxx|xxxxxx):},{ph}

Does anyone know if when you update google voice these settings become non-functional?

There is no change to the functioning of InboundCallRoute.


Then {(x|xx|xxx|xxxx|xxxxx|xxxxxx):},{ph} should work for the OP who was receiving calls from 9001, 8000 etc. If it doesn't will try azrobert's suggestion of adding pluses. Although to be sure enabling X_AcceptSipFromRegistrarOnly and setting a high port number should help to stop it as well.

Taoman:
Quote from: azrobert on May 19, 2018, 10:09:03 am


Try the following:
{(+x|+xx|+xxx|+xxxx|+xxxxx|+xxxxxx):},{ph}



Since the SIP scanner calls are not originating from GV I'm unclear why you would want to do this?

Mango:
Idly:

Does anyone know if X_AcceptSipFromRegistrarOnly rejects unwanted packets or drops them?

The latter is preferable as it gives the hacker no indication VoIP equipment exists.  If packets are rejected, the hacker will likely keep trying to break in.

Navigation

[0] Message Index

[#] Next page

[*] Previous page