IMS Service Creation with Ericsson Service Development Studio and BEA WebLogic SIP Server
Pages: 1, 2

Configure Initial Filter Criteria (IFC)

Open the HSS tab and select the Initial Filter Criteria sub-tab (Figure 3). Here you have to define a filter for your test requests (the requests that will trigger your application):

  • Select the Definition panel.
  • Click the Add button.
  • Fill the Name field with your filter name (SDS will set a default for you, but you can choose any).
  • Fill the Server Address field with the IP address or host name of your WLSS and the port number on which it is listening.
  • Leave everything else as it is. (There is more functionality that can be used but it is out of the scope of this article.)
  • You can add as many filters as you require. Just click the Add button as needed. Note that each filter you add can be directed to a different WLSS.
  • Click the save button.

The configuration screen
Figure 3. The IFC configuration screen

Configure the Service Point Trigger

  • Select the Service Point Trigger panel.
  • Click the Add button.
  • Fill the Name field with a valid name for your trigger point. (SDS will set a default for you, but you can choose any.)
  • Fill your Trigger Definition fields (Figure 4). They are a set of conditions that SDS will check in order to know if a received request has to be forwarded to your application. If the request matches the trigger point(s), then the request will be forwarded to the application. For more information on how to specify these fields, see the SDS documentation.
  • You can add as many trigger points as required. Just click the Add button as needed. Be aware that all of them will be considered by SDS when receiving a request to decide whether to trigger your application or not.
  • Leave everything else as it is. (There is more functionality that can be used but it is out of the scope of this article.)
  • Click the Save button.
  • You need to repeat all these steps for every filter you created (on the Definition panel).

The configuration screen
Figure 4. The Trigger Definition fields

Configure the Service Profile

Open the HSS tab and select the Service Profile sub-tab (Figure 5). Here you have to define a profile to attach your filters to. In other words, any user id (later we'll see how to define user ids) registered on SDS could be linked to this Service Profile so that any request received from that specific user id will trigger your application. In this example, we will create a Service Profile named helloWorldUser, which includes the filter criteria triggeringMyBEA.

  • Click the Add button.
  • Fill up the Name field with a valid name for your Service Profile (SDS will set a default for you, but you can choose any).
  • SDS will show on this panel a list of available Initial Filter Criterion (those you defined on previous steps). Select the one(s) you want to be attached to this specific Service Profile.
  • You can add as many Service Profiles as required. Just click the Add button as needed.
  • Click the Save button.

The configuration screen
Figure 5. The Service Profile configuration screen

Configure the user profile

Open the HSS tab and select the User Profile sub-tab (Figure 6). Here you have to define the user id(s) that can register and send requests through your SDS.

  • Click the Add button.
  • Fill up the Public User ID field with the correct value. This is related to the SIP-URI of your user. For more information on how to specify this field, see the SDS documentation.
  • Fill up the Private User ID field with the correct value. For more information on how to specify this field, see the SDS documentation's Developers guide.
  • Define the Password for the user id.
  • On the Service Profile field, SDS will drop a list of available Service Profiles (those you defined on previous steps). Pick one for the user id.
  • You can add as many user profiles as required. Just click the Add button as needed.
  • Click the Save button.

The configuration screen
Figure 6. The User Profile configuration screen

Start the network simulator

You are now ready to start up your IMS Core network simulator. Go to the Main menu under the SDS sub-menu and select the CSCF/Start CSCF option. Make sure it has been successfully started by checking the console at the bottom of your SDS (Figure 7).

The simulator console
Figure 7. The simulator console

Now you can register from any device (SIP hard phones, SIP soft phones, or any other SIP terminal or device) by using one of the user id(s) that you have previously created as long as they are reachable on your LAN and they belong to the same domain (make sure to specify the correct domain name and proxy). It is possible to see if registration has been successful if you go to the Registrar tab of your SDS. In Figure 8, you can see a registration using the user-id Intech@myDomain.com by using a SIP soft-terminal.

The registration screen
Figure 8. The registration screen

Summary

This article describes the Ericsson Service Development Studio 4.0 and how it can be used with BEA WebLogic SIP Server 3.1. Together, they enable operators and ISV developers to design and end-to-end test their own IMS applications.

To find out more about how the Ericsson Mobility World Developer Program can help you plan, develop, verify, and get IMS applications to operators and end users, go to Ericsson Mobility World (membership is free). In addition, when an IMS application is approaching commercial launch, it can be tested with Ericsson's live IMS test environment in Montreal, which can be accessed remotely.

Acknowledgments

The authors would like to thank Francois Deza, Senior Manager, Business Development BEA Systems, and Stefano Gioia, EMEA Principal Technology Specialist, BEA Systems, Abid Qureshi, SDS Software Developer, and Alain Bergevin, Software Developer and SDS Specialist, for their contribution in the article.

Download

References

Amin Daya is a Technical Product Manager at Ericsson Canada.

Marco Rodriguez is a Test Configuration Manager at Intelligent Network Technologies S.A. de C.V.