1 / 17

An IMS testbed for SIP applications

An IMS testbed for SIP applications. Cosmin Caba José Soler {cosm,joss}@fotonik.dtu.dk. Networks Technology and Service Platforms. Agenda. Problem background + solutions IMS service composition and triggering SIP Servlet Design decisions Implementation Testing methodology

rivka
Télécharger la présentation

An IMS testbed for SIP applications

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. An IMS testbed for SIP applications Cosmin Caba José Soler {cosm,joss}@fotonik.dtu.dk Networks Technology and Service Platforms

  2. Agenda • Problem background + solutions • IMS service composition and triggering • SIP Servlet • Design decisions • Implementation • Testing methodology • Conclusions

  3. Problem background • The work has been done as a MSc thesis project. • Started during a course in programming services for NGN. The students should execute their SIP applications within a realistic network context.

  4. Possible solutions for app. testing • SIPp testing tool (SIP user agent) • Good UA: custom SIP requests. • Limited: test single application, no service composition, no network context. • Open IMS Core • Complete implementation of IMS CSCFs. • Increased complexity, out of scope of the intented course.

  5. Proposed solution • Build a simple emulation for the IMS core entities. • Requirements: • Simple to use (collocated with the dev. environment). • Deploy SIP applications. • Set up network triggers (i.e. iFC, SPTs). • Execute SIP applications (composition if necessary). Emulate the IMS service composition and triggering using the SIP Servlet API!

  6. IMS service composition HSS contains the initial Filter Criteria (iFC) for each subscriber S-CSCF: service composition according to the iFC • Allow for iFC configuration. • Perform service execution and composition according to the iFC.

  7. SIP Servlet API • IMS service development. • Emulation implementation. Servlet object -> processing of SIP messages (Route headers). Application router -> applicationselection. Servlet object + Application router == S-CSCF

  8. Design decisions • Applications not tied to a single SIP Servlet Container. • Handling special cases (What if the target app. does not exist?). • Registration possibility. • Persistenttriggers (configuration maintained over server restarts). • Intuitive user interface.

  9. Implementation • CSCF: • Retrieves the iFC set from the database. • Creates the service chain. • Adds the Route headers to the SIP request. • IMS Application Router: • Selects the application to be executed.

  10. A short scenario Server1 Server2 IMS Core (CSCF) Call Blocking Voice Mail INVITE Route:<sip:callblock@server1;lr> IMS AR AR Route:<sip:cscf@server1;lr> Route:<sip:voicemail@server2;lr> Route:<sip:cscf@server1;lr>

  11. Testing methodology (I) • Functional testing. • Inspect messages at the end-points and at the application server. Message log from the UA client

  12. Testing methodology (II) Message log from the application server

  13. Conclusions • Simple yet realistic tesbed for SIP applications. • Implementation based on the SIP Servlet API. • Requirements: • Configure network triggers. • Perform IMS-like service composition. • Features: • Integrated with the development environment. • Intuitive work flow. • Easy to set up and run. • Testing methodology: message log investigation.

  14. Thank you!

  15. Backup 1

  16. Backup 2

  17. Backup 3

More Related