Firstly, get the simple rule detailed above working!
Next, we need to go into OBiNerd mode regarding security and InboundCallRoutes.
A slightly simplified InboundCallRoute rule looks like this:
caller > callee: terminal
In the rule detailed in our previous posts we are only using "terminal" i.e. "ph,ph2" meaning that any call that makes it to the correct ip address/port will ring Phone Ports 1 and 2. To be more selective let's say that certain digits need to arrive to call Phone Port 2. We cannot control the "caller" as we checked SpoofCallerID so that the incoming CallerID is passed along from the OBi110 Line Port to the OBi202 Phone Port 2 . So we first change the call being sent from the OBi110:
OBi110 Physical Interfaces > LINE Port > InboundCallRoute:
{ph,sp2(602@192.168.1.23:5062)}
This means that we are now sending digits 602 to the ip address of the OBi202 and selecting sp3's UserAgentPort. At the OBi202 incoming:
Voice Services > SP3 Service > X_InboundCallRoute:
{>602:ph2}
Where 602 is the "callee". The ">" is required to show that the "caller" is left blank in this rule and so allows any CallerID. Of course 602 could be replaced with a more complex set of digits for added security, so long as it matches in the outgoing OBi110 rule and the incoming OBi202 rule.
Now it is almost impossible for anyone to get a call into your OBi202 sp3, except by dialling in via your PSTN number.
Lots more regarding security here:
http://www.obitalk.com/forum/index.php?topic=5467.msg35387#msg35387I'm guessing that you have more than enough to think about for now! Let us know how you get on.
Edit: Changes made to reflect that CallerID cannot be used for security if it needs to be passed onto Obi202 Phone Port 2.