OpenSBC Logo

User Manual

[Previous]   [Next]    [Contents]

3. Quick Start


3.1 Basic Configuration

After a successful installation of OpenSBC the HTTP admin should already be accessible via port 9999 of the server where OpenSBC is running.  Figure 1.0 shows the main HTTP admin page.  Pictures speak louder than words!

Figure 1.0

Figure 1.0


For a basic configuration, click on the "OpenSBC General Parameters" link and look for the "SBC Mode" Parameter.
Using the drop-down list box, choose "B2B Only Mode" as shown in Figure 1.1.

Figure 1.1
figure 1.1
We need to change the listener port for OpenSBC to allow us to run a softphone client in the same box.  To do this, we must add a new entry in the "Interface Address" list.   We want to use all available interface bound to port 9000.   Figure 1.2 shows how this is done within the "General Parameters Section"

Figure 1.2
figure 1.2
Make sure you choose "Keep" in the drop down list-box before clicking the [Accept] button.

After this, you MUST RESTART OpenSBC so that the changes would take effect.   Not all parameters in OpenSBC requires a restart.  But these two does!


3.2 Adding User Accounts

The next step would be to add user accounts so that our softphone would be allowed to register and make calls through OpenSBC.   User accounts are added using the "Local Domain Accounts" link.   The format for account entry is using the standard sip URI format "sip:user:password@domain:port".  Let us say our hypothetical account is sip:john:doe@opensbcrocks.org:9000.   This means the authentication user is "john" and his password is "doe" belonging to the domain opensbcrocks.org:9000.   The port is important in this case because OpenSBC is listening at port 9000.
Figure 1.3 shows how this account is added.

Figure 1.3
figure 1.3

Do not forget to choose "Add" from the drop-down list box before clicking the [Accept] button.

opensbcrocks.org is not a real domain with either host or srv records.   OpenSBC will not be able to resolve this domain properly.  Luckily, there is a way around this problem.   You may statically map domains using the "Internal DNS Mapping" section.  In our case we want to map opensbcrocks.org:9999 to the OpenSBC IP address.   Figure 1.4 shows how to add an internal DNS map entry .

Figure 1.4
figure 1.4

3.3 Adding Basic Routes

After the account for John Doe has been added, the next step would be to add routes so that John Doe can start making calls.   Routes are added via "B2BUA Routes" link in the admin page.   Figure 1.5 shows that we want the number 613 be routed to fwd.pulver.com.   sip:613@fwd.pulver.com is a public SIP echo server.

Figure 1.5
figure 1.5

OpenSBC is all set!  You can now start sending traffic and enjoy the sound of your own voice courtesy of the Free World Dialup echo server.


3.4 Sending Traffic

We need to grab a softphone to send test calls to OpenSBC.  For the sake of making life easier, I will be using SJPhone as the test client in this tutorial or else I would be giving you another tutorial on how to compile the equally elegant OSSPhone :-).

First thing, we need to create a new profile in SJPhone and set the proxy and domain to point to OpenSBC.  Figure 1.6 shows a new SJPhone profile pointing to OpenSBC.   192.168.179.129 is the IP address of OpenSBC while the user domain is opensbcrocks.org.  Put a check on Register with Proxy and Proxy is Strict Outbound.

Figure 1.6
1.6

The next step is to provide the user name and password of our hypothetical user John.

Figure 1.7
figure 1.7

Our softphone is all set!   Upon closing the new profile dialog, SJPhone should have already registered with OpenSBC.  Figure 1.8 shows SJPhone is already registered with OpenSBC as sip:john@opensbcrocks.org

Figure 1.8
figure 1.8

You can view the registration details using the "Registration Status" link in the OpenSBC HTTP admin.  Figure 1.9 shows what it the registration detail looks like.

Figure 1.9
figure 1.9

On successful registration, we can now call our FWD echo server route by dialing 613.

Figure 1.10
1.10

OpenSBC can also route calls using just plain DNS resolution without having to enter static routes for the destination.  The following call shows a call to proxy01.sipphone.com which doesn't have a corresponding route.   Since this domain is an actual FQDN, OpenSBC should be able to make this call without routes being statically defined.

Figure 1.11
figure 1.11

There you go!  This concludes the quick start.  Feel free the click the next button for more advanced topics.

[Previous]   [Next]    [Contents]