Connecting a Obi110 to a obi100 without Obitalk?
RonR:
Quote from: earthtoobi on September 07, 2011, 02:24:49 pm
Ronr: isnt there an assumption too that device 1 and 2 have 5061 port forwarded in their own routers to the respective Obi devices for it to work.
also, can DDNS be used instead of Ip address?
When I wrote that, I was thinking in terms of both units being on the same LAN (192.168.?.?). If that's not the case, and there's a router in the loop, then forwarding of SIP and RTP ports is probably required (I'm so used to always having these ports forwarded regardless, I don't have to think about it). There's no problem using hostnames such as Dynamic DNS services instead of IP addresses.
Quote from: earthtoobi on September 07, 2011, 02:24:49 pm
in general:if one of the trunk in each device is configured with same SIP provider, then typically SIP2SIP is provided Free by the provider.
so, if you have callcentric configured on both devices, they can talk to each other for free.
even, if they are configured with different SIP providers, SIP2SIP is free as long as providers support free Sipbroker peering.
That's true assuming the provider allows multiple devices to be registered and you have the necessary sub-accounts set up to handle calling between the units.
Quote from: earthtoobi on September 07, 2011, 02:24:49 pm
As i had mentioned in other posts, what i like about obitalk voice server is that since the protocol is not SIP, it works in countries where ISP blocks SIP completely.
Are you sure the OBiTALK voice server doesn't use SIP protocol? I don't know for sure, but I've always assumed it was mostly vanilla SIP with a few modifications/additions to handle the OBi's specific needs. The ports used may very well be non-standard, which would account for them not being blocked. It would have been a fair amount of work and would take up a lot of space in the OBi to have a totally different protocol in use for the OBiTALK service when SIP is already there and would suffice.
QBZappy:
The OBiTalk portal and the OBiTalk network exhibit similar feature set to the following sip software products: OpenSIPS, SIP Express Router (SER)
OpenSIPS: http://opensips.org/
Main features OpenSIPS can be used as :
SIP registrar server
SIP router / proxy (lcr, dynamic routing, dialplan features) (OBi dial plans???)
SIP redirect server
SIP presence agent (OBi Dashboard has a status feature)
SIP back-to-back User Agent (OBi network can connect OBi to OBi)
SIP IM server (chat and end-2-end IM)
SIP to SMS gateway (bidirectional)
SIP to XMPP gateway for presence and IM (bidirectional) (OBi, Google Chat???)
SIP load-balancer or dispatcher
SIP front end for gateways/asterisk (OBiTALK Portal)
SIP NAT traversal unit (OBi seems to have this ability as well)
SIP application server
SIP Express Router (SER): http://en.wikipedia.org/wiki/SIP_Express_Router
is a SIP server. It can be configured to act as SIP registrar, proxy or redirect server. SER features presence support, RADIUS/syslog accounting and authorization, XML-RPC-based remote control and others. Web-based user provisioning (OBi seems to have this ability as well), serweb, is available.
SER's performance allows it to deal with operational burdens, such as broken network components, attacks, power-up reboots (OBI Expert configuration can reboot the unit) and a rapidly growing user population. SER can be configured for many scenarios including small-office use, enterprise PBX replacements and carrier services.
Some of the other features mentioned in these products might become future enhancements of the OBi.
Just some of my musings about this interesting thread. Anyone see any other similarities?
Navigation
[0] Message Index
[*] Previous page