Setting up an Obi 202 + Obiline in the UK (Draft)
ianobi:
The OBi110 and the OBi202 can work as one combined device with each having access to the others' services. I would not put the OBi110 in the OBi202's network. So long as both devices are in the same router's subnet and both have static subnet ip addresses.
This gives you six spX services and a Line Port. You need to give each spX a unique UserAgentPort and it helps to use unique RTP ports for each service. With this setup calls can be routed to and from any spX or Line Port. All of the routing is done internally within the router subnet.
There are several different ways of routing the calls between the two OBi devices, but I like to dedicate a whole spX on each device to be the two ends of a link between them. However, if there is not a spare spX on each device, then Voice Gateways can be used. The former method makes passing CName and CallerID easy and makes DigitMaps a little more simple.
Comments on the forum would suggest that the OBi110 is a much better link to PSTN than the OBiLINE. I have two OBi110s and have never experienced any echo. I have not tried an OBiLINE, so I'm just judging by the comments of others regarding that.
Mouse:
Quote from: ianobi on July 21, 2015, 09:21:09 am
The OBi110 and the OBi202 can work as one combined device with each having access to the others' services. I would not put the OBi110 in the OBi202's network. So long as both devices are in the same router's subnet and both have static subnet ip addresses.
This gives you six spX services and a Line Port. You need to give each spX a unique UserAgentPort and it helps to use unique RTP ports for each service. With this setup calls can be routed to and from any spX or Line Port. All of the routing is done internally within the router subnet.
There are several different ways of routing the calls between the two OBi devices, but I like to dedicate a whole spX on each device to be the two ends of a link between them. However, if there is not a spare spX on each device, then Voice Gateways can be used. The former method makes passing CName and CallerID easy and makes DigitMaps a little more simple.
Comments on the forum would suggest that the OBi110 is a much better link to PSTN than the OBiLINE. I have two OBi110s and have never experienced any echo. I have not tried an OBiLINE, so I'm just judging by the comments of others regarding that.
Thanks that's very interesting. I have not dug deep enough to know what a user agent port is, and how it could be used, could you maybe explain? (Is it maybe a SIP signalling port?)
Do they dial each other using the Obi number?
ianobi:
Quote
Thanks that's very interesting. I have not dug deep enough to know what a user agent port is, and how it could be used, could you maybe explain? (Is it maybe a SIP signalling port?)
Yes, it is the SIP signalling port. OBi terminology is a bit quirky!
Quote
Do they dial each other using the Obi number?
This is a big question! No, all routing is internal within your router subnet. The DigitMaps would need working out, but you might do something like this:
**1 SP1 OBi202
**2 SP2 OBi202
**3 SP3 OBi202
**4 SP4 OBi202
**6 SP1 OBi110
**7 SP2 OBI110
**8 Line Port OBi110
I've not bothered with OBiTALK for now and you might lose two of the above spXs if they form the link between the two devices.
You have three Phone Ports and with the right DigitMaps say you dial **201234567891 from any of the three Phone Ports, then the number 01234567891 would be routed out of the SIP service on SP2 of the OBi202.
For routing incoming calls it's useful for each phone port to have a number say:
Phone Port 1 OBi202 - 601
Phone Port 2 OBi202 - 602
Phone Port 1 OBi110 - 603
Incoming calls from any service can then be forwarded to any Phone Port(s) which will be identified by its 6xx number. The number will be automatically added by the OBi devices for call routing purposes, the caller just dials in as normal. If needed any of the three ports can call the other ports using it's 6xx number - useful for call transfers etc.
It would be a "project", but similar setups have been done before. I have something similar here using an OBi110 and an OBi1032.
Mouse:
Thanks very much, not sure I am quite understanding. Sorry to be dumb.
How would I specify and where would I put the rule:
"Inbound on Line 1 port of Obi 110 goes out to telephone attached to Ph2 port of Obi 202"
(That would be the most important rule for me .....)
Kind regards
Mike
ianobi:
If the direct link between the two devices had been set up using sp2 in the OBi110 and sp4 in the OBi202, then it could be as simple as this:
OBi110 Physical Interfaces > LINE Port > InboundCallRoute:
{ph,sp2(602)}
All calls coming into the Line Port of OBi110 ring the attached phone of the OBi110 and send digits "602" out via sp2 (anything sent to OBi110 sp2 arrives at OBi202 sp4 via the link). Remove "ph" if it is not required to ring the OBi110 phone.
OBi202 Voice Services > SP4 Service > X_InboundCallRoute:
{>602:ph2}
All calls inbound on sp4 with digits "602" ring Phone Port 2.
The above example is simplified and omits some security measures and other rules to route calls from other inputs to ph2, but I hope that you get the idea.
The link between OBi110 sp2 and OBi202 sp4 would direct all calls between the two using each others' fixed local ip address / SIP port. Too much detail for this example.
An incoming call to any OBi device can be directed to any ip address / port. For instance if I only have an OBi110 and want to direct incoming calls at the line port to a SIP softphone on a PC with address 192.168.10.45:5060, then this would be the rule:
OBi110 Physical Interfaces > LINE Port > InboundCallRoute:
{ph,sp2(1@192.168.10.45:5060)}
This would ring the OBi110 phone and "fork" the call using OBi110 sp2 to the softphone. Whichever answers first takes the call. The "1" in sp2(1@192.168.10.45:5060) can be anything, the softphone does not use it, but it's needed to comply with the required format.
Navigation
[0] Message Index
[#] Next page
[*] Previous page