Strange "201"call and Oleg method among others

(1/2) > >>

66michael99:
Anveo user. Obi202 purchased Oct. 2012.

I'm re-living a nightmare which I experienced when I first purchased the obi202. No sip scanner nonsense for 2 years using the string "{(?|x|xx|xxx|xxxx|xxxxx|xxxxxx|555xx.|un@@.|anon@@.):},{ph1,ph2}". Now the spam calls have re-emerged with a "201".

I was relieved to find the Oleg method and employed it: {>('Insert your AuthUserName here'):ph}
under Voice Services, X_InboundCallRoutE and a port number somewhere in "xxxxx" range.
I'm shocked to hear the dreaded "201" continues un-abated.

I'm convinced it's me and not Oleg. Where did I go wrong with the setting?

BTW, I can't believe the number of outstanding minds gathered in one place here.

Taoman:
I assume you only want to accept SIP traffic directly from your provider's SIP server? If so, why not give this a try and see what happens:

Voice Services>SPx Service>X_AcceptSipFromRegistrarOnly

OzarkEdge:
Are they perhaps real calls through your provider with spoofed CallerID 201?

Try these Voice Services settings if present in your firmware:

SPn Service - SIP Credentials::X_EnforceRequestUserID = checked ;prohibit anonymous SIP, if supported by the ITSP.

OE

66michael99:
Many thx for the quick replies...will let you know when implemented/tested...

ianobi:
Quote

I'm re-living a nightmare which I experienced when I first purchased the obi202. No sip scanner nonsense for 2 years using the string "{(?|x|xx|xxx|xxxx|xxxxx|xxxxxx|555xx.|un@@.|anon@@.):},{ph1,ph2}". Now the spam calls have re-emerged with a "201".

In the above rule "xxx" will stop "201" from ringing the phones if the CallerId is from a scanner or from your legitimate voip provider.

Check Call History - are you sure that the calls from "201" are coming in via the same SPn that you are applying the scanner prevention measures to?

Navigation

[0] Message Index

[#] Next page