SIP scanners
ianobi:
Quote
If you allow pass through (like calling from soft OBi to your home OBi and than into another trunk) - you have to be very cautious.
Yes, I agree with this. Some of us have complex InboundCallRoutes allowing incoming calls to use outgoing trunks on our OBi. Many users will have "Trusted Callers" giving access to their auto attendant and maybe more. This means that there are still reasons for using CallerID and changing UserAgentPort to increase security.
I see the "oleg approach" as most useful anywhere you have an InboundCallRoute containing the rules like "ph" or "ph,ph2". I will be be changing my "ph" to something like {>('myname'|123456@.):ph}.
lacibaci:
Quote from: oleg on March 21, 2013, 08:03:16 pm
...
>('1777xxxxxxx'):ph1
This should work for Callcentric, but I believe you may remove quotas and even parentheses.
...
I can confirm that for Callcentric following inbound route route works:
>1777XXXXXXX:ph
(replace X with your number)
Lac
RegularJoe:
Ok I seem to be a dummy - How do I implement OLEG method - I have OBI100 and Voip.MS - is there a step by step procedure with Voip.ms service.
Thank you for yor help ahead of time.
Regards
Joe
Shale:
Quote from: RegularJoe on March 29, 2013, 04:31:13 pm
Ok I seem to be a dummy - How do I implement OLEG method - I have OBI100 and Voip.MS - is there a step by step procedure with Voip.ms service.
See http://www.obitalk.com/forum/index.php?topic=5467.0
Method 4 is the Oleg method. Method 3 has a string that you could copy and paste for voip.MS.
giqcass:
Quote
Don't you just hate it when you read something and say, why didn't I think of that!
"why didn't I think of that!" Was going through my head the whole time.
I'm going to try adding a "User Defined Digit Map" and put all the user names in so I can easily edit them. Thanks for a beautiful solution oleg. I just added this topic to my personal OBi library.
Navigation
[0] Message Index
[#] Next page
[*] Previous page