![]() ![]() WLSS is in the HSS table list and the authorization of Repository Data for WLSS is set to readable.The Base DIAMETER Stack is configured to communicate with the HSS.The WLSS is connected to the Bridgewater HSS.The preconditions for a positive test result are summarized below: Show UDR behavior (click the image for a full-size screen shot) The following diagram shows the behavior of the UDR:įigure 6. Going the other way, the application should be able to read the response: Each of them should match. The CEA is used to determine what diameter applications are supported by each peer.Īfter it has established the connection WLSS could send a User-Data-Request (UDR) request to the HSS Server: The HSS should correctly read the request and send a response User-Data-Answer (UDA). In this case, WLSS should send a Capability-Exchange-Request (CER) to the configured HSS server: The HSS must return with a Capability-Exchange-Answer (CEA). Just before the real connection, WLSS should be able to connect to an HSS server. Step 1: Testing Connect Disconnect from the HSS Show a simple PUR response (click the image for a full-size screen shot) In addition, the Web application prints out the ResultCode, the XML response generated by the HSS, and eventually the exception, as showed in Figure 5:įigure 5. Once the connection with the HSS is established you can use those pages to query the HSS. These parameters are read at startup and you can change them to meet your requirements. serviceName - used to query the HSS with UDR and PUR and correspond with ServiceIndication.serverName - used to query for InitialFilterCriteria.In the web.xml you can find two parameters: All you have to do is to insert the username in the field, and submit the form. There is another special page, the profileViewer.jsp, which is used to query the HSS and get the full user profile. There are three simple JSP pages: The Sh-Pull.jsp is used to test Sh-Pull request, the Sh-Update.jsp is used to test Sh-Update, and the Sh-Subs-Notif is used to test Sh-Subs-Notif. Show the home page of the Web application used to test Sh This application shows that WLSS can successfully communicate with an HSS and conforms to 3GPP Technical Specification documents for the Sh interface.įigure 4. You can choose the user name, the type of request, the service name, in case of Sh-Pull, and the service data and service value in case of Sh-Update. It's possible to send out Sh-Pull, Sh-Update, and Sh-Subs-Notify requests using a simple Web interface. The application lets you query and update the data stored in the HSS. The sample application presented in this article is a simple example built for testing in an easy way the message flow described in this article. Refer to the documentation on how to configure a diameter domain. ![]() The Configuration Wizard includes a DIAMETER domain template that creates a domain with four WebLogic SIP Server instances: Download and deploy the application on a diameter Sh client node.Configure a DIAMETER domain using the Configuration Wizard.If you don't have a real HSS, you can download WLSS and use our HSS Simulator. The other DIAMETER node is running on the other server, as showed in Figure 3: On one server two instances of WLSS will be running, one acting as an Admin Server, one as a DIAMETER node. The system under test consists of two servers running the WLSS 2.2 instances, acting as a DIAMETER node, connected with the Bridgewater HSS. We start by presenting how we configure the environment, then we briefly discuss the Web application used in the test and a description of the messages exchanged between WebLogic SIP Server and the HSS. ![]() This section examines how we set up the test environment and how we drive the test with Bridgewater Systems. Sh Interoperability Tests with Bridgewater Systems HSS ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |