voice wrote:
Hi
Can someone check my logic and setup?
I am using a Cisco ATA-186 in atasip 3.1.0 firmware with a public IPaddr
(69.x.x.x).
I am setting the OutBoundProxy on the ATAs' to my openSBC name/ipaddr ==
sbc.netxxxxxx.net with a public IP Address 69.x.x.50.
The ATA is registered in sipXecs 3.9.x also with a public IPaddr 69.x.x.40.
I am also using but not in this test several Cisco 26xx routers run nat/PAT.
These routers are in front several private networks. The public side of the
NAT are connected to transceivers (69.x.x.x). For testing both boxes are
hanging out on the Internet. No firewalls, Nat nothing to get in the way
etc...
I would like to also have remote Internet (outside my network) ATA/IPPhones
register to the sipXecs.
On the openSBC I have set 'Upper Registration Routes' to point to the
sipxecs. This is my string:
sip:@sbc.network.net sip:sipx.network.net:5060.
Using this approach will local and possibly the remote ATA be able to
register via the openSBC?
This should be possible. The trick is, the domain sip:sbc.network.net
should not resolve as the local address of OpenSBC. If
sip:sbc.network.net is a local address, then OpenSBC would try to be
authoritative over the registrations. The correct format would be:
sip:sipx.network.net* sip:sipx.network.net:5060
Using openSBC in this way do should i set SBC Mode something other then
'Full Mode'?
I am suggesting B2BUpperReg Mode. This would limit the work of OpenSBC
to b2bua and upper reg. Full mode includes the proxy functionality.
When using openSBC using 'Upper registration Routes' is there a basic set
of setting i should be concerned with at the exclusion of other settings?
No. B2BUpperReg routes are just static routes for OpenSBC to follow in
case the remote domain is not resolvable via DNS. In B2BUpperReg mode,
you don't even have to put anything in the routes as long as the To-URI
resolves to a remote domain.
Are there any sipXecs folks on this list with similar issues' to mine?
I would be willing to open my test sipxecs and opensbc box's to further
development challenges in exchange for help setting up both boxes to
intergrate sipXecs and openSBC....
Solegy (Sponsor Company of OpenSBC) has a similar setup. In fact
B2BUpperReg mode came into life when we started to evaluate sipXecs.
r
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>
http://get.splunk.com/
_______________________________________________
opensipstack-devel mailing list
opensipstack-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>
http://get.splunk.com/
_______________________________________________
opensipstack-devel mailing list
opensipstack-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensipstack-devel