Best way to connect 2 Obis on Local Network
hwittenb:
Quote from: azrobert on January 27, 2013, 05:44:04 pm
ianobi and I are getting one way audio with 2 OBi110s.
In my case the firmware levels were the same, but the hardware versions were different.
Any ideas?
Thanks
Edit: ianobi's worked when SP2 was unregistered.
I don't have two OBi110's to test out. Just an OBi110, an OBi100, and an OBi202. I don't know why you would get the one-way audio between the two OBi110's. One way audio usually occurs because one adapter doesn't communicate correctly the ip address or port number to be used for the rtp data stream.
Edit: See http://www.obitalk.com/forum/index.php?topic=5141.msg33309#msg33309
In my tests I was calling from SP2 to SP2, both were registered to a voip provider but I don't think that makes any difference, one way or the other. In fact I just ran a test with both unregistered and the result was the same. It worked between the OBi100 and the OBi110. Now I moved the OBi100 to some other ip address and now it gets one-way audio. Flakey
If it doesn't work it is due to some setting or environment factor we haven't discovered. I think this method of direct ip communication is something that really isn't supported or tested by OBi and that's why we get flakey results.
The units appear to accept calls from unregistered sources. The OBi202 has a setting to stop unregistered calls but the default allows it. If fact I tried the setting the OBi202 to stop unregistered calls and it does just that. A voice comes on to scold me.
mrjoe:
For 2 way Audio you must us an Outbound Proxy.
Trust me, I've tried all types of Configurations..
azrobert:
You can also use this method to define an OBi as a trunk on PBX in a Flash.
I'm a total novice with PIAF, but this Trunk definition works:
type=friend
username=PIAF
host=192.168.1.10
port=5061
fromuser=PIAF
canreinvite=no
insecure=invite,port
qualify=yes
nat=yes
I wonder if putting PIAF between the 2 OBi's would correct the audio problems.
Point a VG on OBi#1 to a PIAF extension and route the call out the OBi#2 trunk.
I can't do any testing until my dead OBi gets replaced.
Has anyone tried mrjoe's outbound proxy suggestion?
ianobi:
I have consistant results in my setup as follows:
Using two OBi110s both with Hardware Version 2.8 and Software Version 1.3.0 (Build: 2274). (R) = registered to a Service Provider. (U) = unregistered using 127.0.0.1 etc.
OBiA sp(U) > < LAN > < OBiB sp(U)
Call routing and audio ok in both directions. CallerID passed ok in both directions.
vg > OBiA sp(U) > LAN > OBiB sp(U)
Call routing and audio ok. CallerID passed ok.
vg > OBiA sp(R) > LAN > OBiB sp(U)
Call routing and audio ok. CallerID passed ok.
vg > OBiA sp(U) > LAN > OBiB sp(R)
Call routing ok. no audio tx or rx. CallerID passed ok.
vg > OBiA sp(R) > LAN > OBiB sp(R)
Call routing ok. no audio tx or rx. CallerID passed ok.
In this setup Outbound Proxy makes no difference for the unregistered calling. I accept that it may well be needed in some setups. If you are using an sp with a registered service provider, then you cannot mess with the Outbound Proxy without affecting that voip service.
hwittenb:
I finally got my wireshark packet trace more or less working correctly and I now see what is happening with the one-way audio when I call the OBi110 from the OBi202 over my local network. When the OBi110 starts up its rtp voice packet stream instead of sending the packet stream to the OBi202 local network address it sends its rtp packet stream to the (correct port number) at the local network's external ip address. The router discards the packet and you have one-way audio. To circumvent the problem, I setup a unique rtp port range for the OBi202 and in my router forwarded that unique port range to the OBi202 and the call works correctly.
Navigation
[0] Message Index
[#] Next page
[*] Previous page