SIP scanners
dial.tone:
Quote from: dial.tone on June 07, 2013, 05:27:08 am
When I did the Oleg setup, the AuthUserName I put in the InboundCallRoute string was "GVxxxxxxxxxx" where the x's are my GV number. When I look in Expert Configuration, I don't see any AuthUserName associated with the ST part of the setup. Does this help or just muddy the water?
I just realized that the InboundCallRoute string (GVxxxxxxxxxx) I found in Expert Configuration for SP1 is the SimonTelephonics username for that GV/ST setup. I have a different, standalone GV number coming in on SP2, so I compared its InboundCallRoute string with the one on SP1 and they are totally different. The InboundCallRoute string on SP2 is the GV email address associated with that number. So ST used my SP1 GV number to construct its username and Obi202 used ST's username for its InboundCallRoute. Doesn't solve the mystery but helps clear up that point. Actually, now that I think about it, it only deepens the mystery. Now I know that I have properly implemented the Oleg method on the ST-configured SP1 and yet Private Caller calls are still getting through. At least the middle-of-the-night 100/1000/1001 calls have stopped.
Quote from: Shale on June 07, 2013, 07:25:55 am
Maybe on of the other methods such as method 2 or 3 (port number or IP number) would work for you. If not, I would give up on CNAME until there was a solution.
At this point, that's about all I have left. I hate to pull the plug on SimonTelephonics caller ID name service -- the 80% of the time it works it is pretty cool! Any additional ideas would be more than welcome!
ianobi:
The question here is do these calls come in via the ST servers? If so, then methods 2,3 & 4 will not work because as far as the OBi knows the calls are genuine with the correct UserAgentPort, correct ip address and correct AuthUserName.
While researching further you might try a version of method 1, combined with the oleg method such as:
Voice Services > SP1 Service > X_InboundCallRoute:
{(Priv@@.):},{>(GVxxxxxxxxxxx):ph}
This will block all calls with a CallerID / Peer Number of “Priv” followed by anything. Make sure you get the upper/lower cases correct for “Priv” exactly as shown in Call History > Peer Number.
If you get genuine calls with the CallerID / Peer Number “Private Caller” that you wish to receive, then this will block those, so may not be a good method for you. In that case we are out of ideas for now ???
dial.tone:
Quote from: ianobi on June 08, 2013, 07:44:13 am
The question here is do these calls come in via the ST servers? If so, then methods 2,3 & 4 will not work because as far as the OBi knows the calls are genuine with the correct UserAgentPort, correct ip address and correct AuthUserName.
While researching further you might try a version of method 1, combined with the oleg method such as:
Voice Services > SP1 Service > X_InboundCallRoute:
{(Priv@@.):},{>(GVxxxxxxxxxxx):ph}
This will block all calls with a CallerID / Peer Number of “Priv” followed by anything. Make sure you get the upper/lower cases correct for “Priv” exactly as shown in Call History > Peer Number.
If you get genuine calls with the CallerID / Peer Number “Private Caller” that you wish to receive, then this will block those, so may not be a good method for you. In that case we are out of ideas for now ???
I haven't gotten any of these Private Caller calls for a couple of days now, but it looks like some are still coming into the Obi202. Here's why I say that. I compared the caller ID log on my phone with the Obi Call History log on the Obi web portal. The Obi Call History shows a bunch of calls labeled "PH1" that don't correspond to any calls we have received, nor do they correspond to any calls that show up on the phone's caller ID log. The phone's time stamp on the Private Caller calls we were getting a few days ago DO, however, correspond with the time stamp on the Obi Call History for some of the older calls that are labeled "PH1." So I assume (yes, I know) that the PH1-labeled calls are the calls that used to get through as Private Caller calls but are now being stopped by the Oleg settings. At least most of them are -- I know some of them got through the first/second day after I made the Oleg change. The biggest thing that concerns me now is that the duration of these PH1 calls, according to the Obi Call History, is anywhere from 20 seconds to over nine minutes. These calls never make it to our desktop phone, so what the heck are they doing on my system for nine minutes. Do I need to be concerned?
Shale:
Do the calls you are concerned with say "From PH1" or "To PH1" in the call history?
dial.tone:
Quote from: Shale on June 09, 2013, 03:23:56 pm
Do the calls you are concerned with say "From PH1" or "To PH1" in the call history?
Argh, NO, imanidiot! I had to go back and look and the "To" data on all those calls and they all had numbers associated with them. . .they looked like phone numbers. . .familiar numbers. . .I wondered why the Frisbee was getting larger, then it hit me. . .those were our OUTGOING calls. Sorry about that!
Navigation
[0] Message Index
[#] Next page
[*] Previous page