Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

<?xml version="1.0" encoding="utf-8"?>
<html>
*This document will attempt to provide working OpenSBC configurations for a few commonly used sipxecs calling scenarios. It is a work in progress, so please check back often. For any questions or comments, contact the author (raymund.nones at gmail.com) or post to the OpenSBC forum at http://www.opensourcesip.org.*

NOTE: I'm currently updating this document to give more screenshots for Linux, OSBC and SipXecs to have a more clearer guide.

Scenario # 1: Using OSBC for Far End NAT Traversal(FENT) - Public . This enables remote workers on the WAN to access a sipxecs instance, where SIPX has a public IP address, from behind NAT routers.

Setup:

OS: Fedora 8

No.of NIC: two, both with Public IP Address
SipXecs and OSBC are installed on the same box, each using a separate IP address

UA's: Behind NAT

Note: Dues to a limitation where the gateway configured in sipxecs always uses port 5060, OSBC can not be used for FENT and SIP Trunking simultaneously.*

1.a Registering a NAT'd UA to sipxecs through OSBC with UpperReg(without and with domain rewriting)

In OSBC:

Setting OSBC with UpperReg Mode:

1.) Go to OSBC General Parameters

2.) Select B2BUpperReg Mode

3.) Press Update (Note: After Update you need to restart OSBC)

Setting OSBC to listen to a specific interface:

1.) Go to OSBC General Parameters

2.) Input the interface address at the Interface Address Field and Click Add

3.) Press Update (Note: After Update you need to restart OSBC)

Setting OSBC Upper Registration

1.) Go to Upper Registration

...

this will route all traffic from OSBC to SipX instance at sipx.example.com

Note: For domain rewriting, click the check box for Domain Rewriting (i'll be giving examples regarding the Rewrite Feature on my next update)

If Rewrite-TO-Domain is check, domain of the To-URI will be rewritten and use the domain parameter of the route-uri.

...

Proxy: osbc.example.com <-- tjis domain should resolve to the IP address of your OSBC instance

1.b Calls between UAs behind NAT

Callflow: UA1 ? OSBC ? SIPX ? OSBC ? UA2

In OSBC:

1.) Using the settings for OSBC from Scenario #1, Go to B2BUA Routes

...

Setting OSBC to Register to a Sip Trunk Provider:

1.) Go to OSBC Sip Trunk Config

2.) Paste the XML for the config (sample below)

...

Domain: sipx.example.com <-- your SipXecs instance</html>