24 th APAN XiAn China 30 th August

24 th APAN, Xi’An, China 30 th August 2007 SIP Working Group SIP@CNR Sinchai Kamolphiwong http: //cnr. coe. psu. ac. th

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

Interactive Distance Learning based on SIP Under Multimedia Architecture and Applications Based on SIP Project STIC-Asia Project

What can IDL offer? l 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

Design Principles l Collaboration needs sessions, messages and events ¡ l 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 endnodes l Possible to cooperate with Third-party components l ¡ Use open standards at its interfaces.

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

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

Conference Manager (CM( l 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 l Initiate conference using SIP INVITE to mixer and REFER every pre-configured participants l Manage conference repository l

Conference Manager vs. Others l Conference Manager is not try to replace any operations of focus ¡ ¡ l 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

Conference Repository l It is safe to make conference URI from pseudorandom. ¡ l 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 l I want to have some nice talk, here I can see which group of my friends is chatting.

Sample Scenarios l Just conferencing ¡ ¡ ¡ l Group Finding ¡ ¡ l I want to talk to friends now I do not need a complex policy I know exactly who 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

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

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

Application Architecture l 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 l Loosely integrations between ¡ Easy to develop as a team ¡ Easy to test ¡ Easy to change layers

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

IDL on Mobile learning Interactive White Board Power. Point Presentation

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

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

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

Network Scenario : IP Phone connection Abilene

Network Scenario: IDL Connection P SIP SI Abilene

IPv 6 Remote Workshop June 13, 2007 National Ilan University, Taiwan

IPv 6@PSU Side IPv 6 car was running During a participation from both sides

IPv 6@NIU, Taiwan Side Students participated the workshop Students controlled IPv 6 car (from Taiwan to PSU)

SIP Servers@CNR SIP Server (our proprietary stack using Java( l Opern. SER l Asterisk Now l PSU has installed SIP phone system between their 5 campuses

List of CNR Services (Public( l l sip. cnrlab. net. 2001: 3 c 8: 9007: 1: : 201 202. 12. 74. 201 l for voice call ¡ SIP URI: sip: 6674000100@202. 12. 74. 201 or sip: 6674000100@sip. cnrlab. net l for voice + video use Windows Messenger 5. 1. 0701 ¡ SIP URI: sip: cnrsip@202. 12. 74. 201 or sip: cnrsip@sip. cnrlab. net

More workshops done l SIP workshop (Feb 2007) ¡ ¡ l 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.

Other on-going projects SIP-based CRM (Customer Relationship Management( l P 2 P-SIP l Session mobility based on SIP l

Thank You for Your Attentio �� �� ��������� http: //cnr. coe. psu. ac. th/ 29