SIP Working Group

1. 24th APAN, Xi’An, China 30th August 2007 SIP Working Group SIP@CNR Sinchai Kamolphiwong http://cnr.coe.psu.ac.th Department of Computer Engineering Faculty of Engineering Prince of Songkla University, Thailand

2. Acknowledgement • NECTEC (National Electronic and Computer Technology) • UniNet (Thai University Network) • STIC-Asia Project • Faculty of Engineering, Prince of Songkla University

3. Interactive Distance Learningbased on SIP Under Multimedia Architecture and Applications Based on SIP Project STIC-Asia Project

4. What can IDL offer? • Interactive distance learning (IDL) offers • much better facility than a normal video conference • For examples, power-point presentations and on-line document sharing • encourage ‘good feeling of teaching and learning’ • More features to come

5. Design Principles • Collaboration needs sessions, messages and events • plus stored context and asynchronous collaboration e.g., Wikis, blog, conference recordings, structured data stores, shared calendars. • Need more than basic presence • automatically derived, not user input • Easy to manage from both servers and end-nodes • Possible to cooperate with Third-party components • Use open standards at its interfaces.

6. IDL Architecture • Complex architecture (but not difficult to implement and manage) • Service & Network Architecture • How IDL interact with other conferencing components • Which protocols need to be used • Application Architecture • How IDL is implement to bridge end-users and conferencing functions • Which application models need to deal with

7. Policy Server Conference Manager HTTP XCAP LDAP Conference Policy Participant SIP Notification Service Subscription SIP Dialog Focus Conference Repository Service & Network Architecture XCAP XCAP XML XCAP

8. Conference Manager (CM) • A Web-based application which users can • Create sip accounts • Configure call services e.g., voice mail, call forward, call transfer • Create & configure conference rooms e.g., open/close conference, member management, sidebar • Use online services e.g., chat, voice mail • Translate user settings to actions and policy • Initiate conference using SIP INVITE to mixer and REFER every pre-configured participants • Manage conference repository

9. Conference Manager vs. Others • Conference Manager is not try to replace any operations of focus • Focus mostly works when conference is in session setup or during session. • Conference Manager mostly works before conference setup or initiate conference establishment. • Conference Manager is an alternative of policy management via Policy Server • Participants do not need XCAP capabilities • Defining policy can be exhausted. • Hard to synchronize GUI on participants with conference servers capabilities

10. Conference Repository • It is safe to make conference URI from pseudo-random. • Drawbacks: hard to remember, book-marking is not possible • Repository is a place to find active conferences • Only open/public conference can be found by anonymous users • Authenticated users can search for authorized conference using conference descriptions • It make sense for daily usages • I want to have some nice talk, here I can see which group of my friends is chatting.

11. Sample Scenarios • Just conferencing • I want to talk to friends now • I do not need a complex policy • I know exactly who I want to talk to • Group Finding • I want to talk to my friends who are my classmates • I feel more comfortable with Web-based interface • Scheduled Conference • A conference can be configured in advance • Participants just wait and talk

12. Scheduled Conference 2.translate 1. create and configure 3. schedule 4. subscribe 5.3 search Policy Server Use web browser for step 1-3 6.1 Initiate 5.2 notify 6.2 consult 6.5 consult 5.1 sign in 6.4 conf. activation Mixer 6.3 join Conf. Conference Group (media exchange) 6.6 conf. gathering IDL Conference Manager Conference Repository Conference server Web browser *Updating conference repository is omitted.

13. Scheduled Conference A participant logon to the website, create and configure a conference 2. Conference info is stored in CR 3. Configurations are translated to policy storing in PS 4. The participant schedule his/her conference 5. X minutes before the conference time, CM subscribes for presence of conference moderator (that can be more than one) 6.1 The moderator sign in 6.2 The moderator’s presence is notified to CM 6.3 CM browse CR for conference info regarding the moderator 7.1 Depends on configurations, CM initiates conference 7.2 CS consults PS for conference policy 7.3 CS invites the moderator to the conference 7.4 If moderator accepts, the conference will be activated. 7.5 Mixer consuls PS for media policy 7.6 Gather all conference members

14. Application Architecture • IDL is a layer-based Application. • GUI Layer: Interacts with end users • Service Layer: Provides necessary functions to GUI • Transport Layer: Delivers signals and media • Loosely integrations between layers • Easy to develop as a team • Easy to test • Easy to change

15. Presentation Main Frame Media Registration Panel ContactList Panel MediaFrame P-Layer Application Architecture Graphics User Interface GUI Layer Media Communication Service File Transfer Service Sip Related Service Media Service Media Manager File Transfer Service File Transfer Agent Service Layer Ctrl & Data JAIN SIP Native Library Media Stream IDLP Raw SIP RTP TCP (+ TLS) UDP (Unicast, Multicast, XCast) Transport Layer IPv4/IPv6 *IDLP is an invented protocol, it is XML-based with target, action and parameters.

16. IDL on Mobile learning Interactive White Board PowerPoint Presentation

17. "Enhancements of IP Conference Scenarios" More information can be found on proceedings of Mobility Conference, September 10-11, 2007, Singapore

18. SIP Interconnection PSU (Thailand) NCNU (Taiwan) NIU (Taiwan)

19. Students visit@NCNU 4 weeks visiting of 3 PG students May 16 to June 10, 2007

20. Abilene Network Scenario : IP Phone connection

21. SIP SIP Abilene SIP Network Scenario: IDL Connection

22. IPv6 Remote Workshop June 13, 2007 National Ilan University, Taiwan

23. IPv6@PSU Side IPv6 car was running During a participation from both sides

24. IPv6@NIU, Taiwan Side Students participated the workshop Students controlled IPv6 car (from Taiwan to PSU)

25. SIP Servers@CNR • CNR SIP Server (our proprietary stack using Java) • OpernSER • Asterisk • Asterisk Now PSU has installed SIP phone system between their 5 campuses

26. List of CNR Services (Public) • sip.cnrlab.net. 2001:3c8:9007:1::201 • sip.cnrlab.net. 202.12.74.201 • for voice call • SIP URI: sip:6674000100@202.12.74.201 or sip:6674000100@sip.cnrlab.net • for voice + video use Windows Messenger 5.1.0701 • SIP URI: sip:cnrsip@202.12.74.201 or sip:cnrsip@sip.cnrlab.net

27. More workshops done • SIP workshop (Feb 2007) • SIP & Call processing (APIs) • Create a simple phone and video application • Asterisk workshop (June 2007) • How to • LDAP & Radius Integration • Conferencing • Voice mail, fix-line phone, GSM phone.

28. Other on-going projects • SIP-based CRM (Customer Relationship Management) • P2P-SIP • Session mobility based on SIP

29. Thank You for Your Attention รศ ดร สินชัย กมลภิวงศ์ http://cnr.coe.psu.ac.th/ Department of Computer Engineering Faculty of Engineering Prince of Songkla University, Thailand