Setting up an Obi 202 + Obiline in the UK (Draft)
ianobi:
For this to work:
OBi110 Physical Interfaces > LINE Port > InboundCallRoute:
{ph,sp2(192.168.1.23:5068)}
You are using sp2 in the OBi110 to send the call to the address/port within the parentheses. So if OBi110 sp2 is not already in use with a voip service provider, then it needs to be set up as a "fake" service provider as detailed above.
In the OBi202 the default UserAgentPorts are sp1 5060; sp2 5061; sp3 5062; sp4 5063. Assuming that the OBi202 ip address is 192.168.1.23, then you can "aim" the call at any one of them assuming that the InboundCallRoute is at default "ph,ph2" and the service is enabled:
Voice Services -> SPx Service -> Enable : (checked)
Both phone ports will ring. This does not stop the spX service in the OBi202 being used for other
things.
So if you are aiming at say OBi202 sp3, then in the OBi110 the rule would be:
OBi110 Physical Interfaces > LINE Port > InboundCallRoute:
{ph,sp2(192.168.1.23:5062)}
This means it's really easy to aim SIP calls at any OBi spX. This can be a bad thing! After you get the above example working I'll pass on some advice regarding security to stop the dreaded sip scanners calling you every five minutes in the middle of the night. However, let's keep it simple for now.
Mouse:
Quote from: ianobi on July 22, 2015, 06:41:10 am
For this to work:
OBi110 Physical Interfaces > LINE Port > InboundCallRoute:
{ph,sp2(192.168.1.23:5068)}
You are using sp2 in the OBi110 to send the call to the address/port within the parentheses. So if OBi110 sp2 is not already in use with a voip service provider, then it needs to be set up as a "fake" service provider as detailed above.
In the OBi202 the default UserAgentPorts are sp1 5060; sp2 5061; sp3 5062; sp4 5063. Assuming that the OBi202 ip address is 192.168.1.23, then you can "aim" the call at any one of them assuming that the InboundCallRoute is at default "ph,ph2" and the service is enabled:
Voice Services -> SPx Service -> Enable : (checked)
Both phone ports will ring. This does not stop the spX service in the OBi202 being used for other
things.
So if you are aiming at say OBi202 sp3, then in the OBi110 the rule would be:
OBi110 Physical Interfaces > LINE Port > InboundCallRoute:
{ph,sp2(192.168.1.23:5062)}
This means it's really easy to aim SIP calls at any OBi spX. This can be a bad thing! After you get the above example working I'll pass on some advice regarding security to stop the dreaded sip scanners calling you every five minutes in the middle of the night. However, let's keep it simple for now
Thanks very much I had misunderstood the 'sp2'. I thought it referred to the service on the remote machine. The admin manual sections on VGs, which have a somewhat similar syntax, seem to me very misleading in this respect.
I think I can have a go at this now. Probably tomorrow if my wife is out - ringing of the phones during testing drives her mad!
(I'd intend to deal with the scanners by ensuring the router port forward rules refer to the source server IP - will that suffice?)
Kind regards
Mike
drgeoff:
Quote from: Mouse on July 22, 2015, 02:15:07 pm
(I'd intend to deal with the scanners by ensuring the router port forward rules refer to the source server IP - will that suffice?)
A typical home router doesn't have that functionality.
ianobi:
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#msg35387
I’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.
NoelB:
Quote from: ianobi on July 22, 2015, 06:41:10 am
So if you are aiming at say OBi202 sp3, then in the OBi110 the rule would be:
OBi110 Physical Interfaces > LINE Port > InboundCallRoute:
{ph,sp2(192.168.1.23:5062)}
Taking this a little bit further I have an obi202 and an obi110 working independently but rather than call out from the 202 line port I would like to direct the call to the 110 and use its line port to call out.
So would this work. In the 202 phone OBCR I have ,{(Mli):li}, change this to ,{(Mli):sp2(192.168.1.103:5061)} where this is the ip addr of the 110 and sp2 of obi110 is already configured with a sip voip provider.
Now comes my dilemma as to what to use as the incoming call route on 110 sp2 first to send the dialled number to the obi110 line port and secondly not to obstruct any call coming in on sp2 from the voip provider coming in to the phone port. Maybe I have to remove everything and set it up with a dummy and drop the voip provider on sp2.
Navigation
[0] Message Index
[#] Next page
[*] Previous page