Bridge obi 110 directly to obi 100
grover59:
Yes I thought it should be able to be done, I always set up static ip address if I can, much easier to get to devices that way.
I have ordered the obi 110 so it will be a few days before I can play with it, and try and set it up. If it works as I expect it will it will no doubt solve a somewhat serious problem for one of my customers..we can only hope.
I will post again as to the outcome, or more then likely if I need help..
Steve
ianobi:
Although the post highlighted in Reply #2 above does work, it does make the remote OBi a very dumb terminal, not even able to access its own settings via “***”. Here I’m suggesting a more flexible option, which will still connect directly between the remote OBi and the PSTN line: As always, test by checking Call History to see how calls are routing.
PSTN --- OBi110 ---------- (router subnet) ---------- Remote OBi
PSTN OBi address:port 192.168.1.10:5471
Remote OBi address:port 192.168.1.14:5473
All settings at default if not mentioned below.
PSTN OBi (OBi110):
Service Providers -> ITSP Profile B -> SIP -> ProxyServer : 192.168.1.14
Service Providers -> ITSP Profile B -> SIP -> ProxyServerPort : 5473
Service Providers -> ITSP Profile B -> SIP -> X_SpoofCallerID : checked
Voice Services -> SP2 Service -> Enable : (checked)
Voice Services -> SP2 Service -> AuthUserName : 987654321
Voice Services -> SP2 Service -> X_RegisterEnable : (unchecked)
Voice Services -> SP2 Service -> X_ServProvProfile : B
Voice Services -> SP2 Service -> X_UserAgentPort : 5471
Voice Services -> SP2 Service -> CallerIDName : Anything
Voice Services -> SP2 Service -> MaxSessions : 4
Voice Services -> SP2 Service -> X_InboundCallRoute:
{(123456789)>(xx.):li}
Physical Interfaces -> LINE Port -> InboundCallRoute
{sp2}
If you would like the PSTN OBi’s phone to ring as well as the Remote OBi’s phone use:
Physical Interfaces -> LINE Port -> InboundCallRoute:
{ph,sp2}
Remote OBi (Obi110, but could be any OBi model):
Service Providers -> ITSP Profile B -> SIP -> ProxyServer : 192.168.1.10
Service Providers -> ITSP Profile B -> SIP -> ProxyServerPort : 5471
Service Providers -> ITSP Profile B -> SIP -> X_SpoofCallerID : checked
Voice Services -> SP2 Service -> Enable : (checked)
Voice Services -> SP2 Service -> AuthUserName : 123456789
Voice Services -> SP2 Service -> X_RegisterEnable : (unchecked)
Voice Services -> SP2 Service -> X_ServProvProfile : B
Voice Services -> SP2 Service -> X_UserAgentPort : 5473
Voice Services -> SP2 Service -> CallerIDName : Whatever
Voice Services -> SP2 Service -> MaxSessions : 4
Voice Services -> SP2 Service -> X_InboundCallRoute: ph
Physical Interfaces > PHONE Port > DigitMap:
([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|**0|***|#|**1(Msp1)|**2(Msp2)|**9(Mpp)|(xx.S2))
Physical Interfaces > PHONE Port > OutboundCallRoute:
{([1-9]x?*(Mpli)):pp},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**9:>(Mpp)):pp},{(xx.):sp2}
Using these settings CallerID should be passed both ways. CallerID of the remote OBi is its AuthUserName, although the PSTN line will most likely ignore this.
The above config also allows for the setting up of backup connections using sp1 and the OBiTALK network.
Emergency numbers should be considered. Any number dialled from the remote OBi, 911, 112, 999 etc, will be routed unchanged to the PSTN line connected to the PSTN OBi.
grover59:
Thank you for the post, I just finished the older setup and it works, I came back to this post just now to report my progress and came across your new setup. I will try that set up this evening, unfortunately I can't do it right now. The only problem I have seen so far is, when I hang up the remote phone the other line stays connected, this problem seems to be only with a land line phone, works fine if connected to a cell phone.
So far it is working as I hoped, just some background, this set up will be used at a remote sporting camps here in Maine. I generally set up phone systems using a wireless carrier such as Verizon or US Cellular. I use home phone connects and run wire to where they want the phone or phones, most generally involves climbing trees. The problem at this location is the systems I have set up have gone bad, no signal, can't seem to solve it. So I now have to move the phone connects about a mile away onto some higher ground. Yes I could run some wire it's only a mile and I have done this before at about 1/2 a mile works fine, however I wanted to see if I could make a wireless link.
I have thought about trying this some years ago, but never did, now I more or less have to. If it works in the field as I hope it will add another tool to the tool box in solving these types of problems. I use Ubiquity equipment for radio links mostly for Internet or surveillance cameras, this should not be a problem. And by the way the home phone connect works just fine with this set up. No matter what I do, or how good the technology is I am still going to have to climb some trees, and it ain't getting any warmer here, oh well sucks to be me.
Again thanks for your post on this setup, I am finding people are very helpful on this forum.
Steve
ianobi:
Quote
The only problem I have seen so far is, when I hang up the remote phone the other line stays connected, this problem seems to be only with a land line phone, works fine if connected to a cell phone.
That's interesting. In the old post I did use 127.0.0.1 as the proxy server in each device, effectively looping the devices back to themselves. This has been used in many configurations and seems to work ok, but I wonder if it means that some SIP messages are not passed. Without setting the whole thing up and analysing a call with Wireshark, that's going to be hard to prove. I'll be interested to see if the new set up works differently as each proxy server in the new post points to the other device and seems more logical. Also, the new post is much more flexible and offers other ways for the remote OBi to dial out, but more of that after you have tried the basic setup.
I see the old post is almost three years old - that's a lifetime in OBiWorld :) I guess OBi devices and myself have moved on a bit since then!
Be careful up those trees ;)
grover59:
The new setup seems to work also, however I noticed it takes longer for the outgoing call to go through on the remote unit. Maybe because it has more to process or something, so far so good, I will continue to play with it.
Thanks Again
Steve
Navigation
[0] Message Index
[#] Next page
[*] Previous page