+ All Categories
Home > Documents > SIP Working Group

SIP Working Group

Date post: 20-Mar-2016
Category:
Upload: azra
View: 54 times
Download: 0 times
Share this document with a friend
Description:
24 th APAN, Xi’An, China 30 th 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. Acknowledgement. NECTEC (National Electronic and Computer Technology) - PowerPoint PPT Presentation
Popular Tags:
29
SIP Working Group 24 th APAN, Xi’An, China 30 th August 2007 Sinchai Kamolphiwong SIP@CNR SIP@CNR http://cnr.coe.psu.ac.th
Transcript
Page 1: SIP Working Group

SIP Working Group

24th APAN, Xi’An, China30th August 2007

Sinchai Kamolphiwong

SIP@CNRSIP@CNR

http://cnr.coe.psu.ac.th

Page 2: SIP Working Group

Acknowledgement

• NECTEC (National Electronic and Computer Technology)

• UniNet (Thai University Network)• STIC-Asia Project• Faculty of Engineering, Prince of Songkla

University

Page 3: SIP Working Group

Interactive Distance Learningbased on SIP

UnderUnderMultimedia Architecture and Applications Multimedia Architecture and Applications

Based on SIPBased on SIP Project ProjectSTIC-Asia ProjectSTIC-Asia Project

Page 4: SIP Working Group

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

Page 5: SIP Working Group

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.

Page 6: SIP Working Group

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

Page 7: SIP Working Group

Service & Network Architecture

NotificationService

Focus

Participant

Policy Server

Conference Policy

SIP Dialog

Subscription

Conference Manager

XCAP

XCAP

XC

AP

XCAP

SIP

HTTP

XML

ConferenceRepositoryLDAP

Page 8: SIP Working Group

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

Page 9: SIP Working Group

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

Page 10: SIP Working Group

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.

Page 11: SIP Working Group

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

Page 12: SIP Working Group

Scheduled ConferenceConference Manager

Conferenceserver

ConferenceRepository

1. create and configure 3. schedule

Conference Group (media exchange)

6.4 conf. activation

6.6 conf. gathering6.3 join Conf.

5.1 sign in

IDL

Web browser

4. subscribe

5.2 notify6.1 Initiate

Use

web

bro

wse

rfo

r ste

p 1-

3

5.3 search

Mixer

Policy Server

2.translate

6.2 consult

6.5 consult

*Updating conference repository is omitted.

Page 13: SIP Working Group

Scheduled Conference

A participant logon to the website, create and configure a conference2. Conference info is stored in CR3. Configurations are translated to policy storing in PS4. The participant schedule his/her conference5. X minutes before the conference time, CM subscribes for presence of

conference moderator (that can be more than one)6.1 The moderator sign in6.2 The moderator’s presence is notified to CM6.3 CM browse CR for conference info regarding the moderator7.1 Depends on configurations, CM initiates conference7.2 CS consults PS for conference policy7.3 CS invites the moderator to the conference7.4 If moderator accepts, the conference will be activated.7.5 Mixer consuls PS for media policy7.6 Gather all conference members

Page 14: SIP Working Group

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

Page 15: SIP Working Group

Application ArchitectureGraphics User Interface

Presentation

P-Layer

Main Frame

Registration Panel ContactList Panel

Media

MediaFrame

CommunicationService

Ctrl & Data

File Transfer Service

FileTransfer

Agent

FileTransferService

Sip RelatedService

JAIN SIP

Media ServiceMedia Manager

NativeLibrary

RTPTCP (+ TLS) UDP (Unicast, Multicast, XCast)

IPv4/IPv6

IDLP Raw

GU

I Lay

erSe

rvic

e La

yer

Tran

spor

t Lay

er SIPMedia Stream

Media

*IDLP is an invented protocol, it is XML-based with target, action and parameters.

Page 16: SIP Working Group

IDL on Mobile IDL on Mobile learninglearning

Interactive White Board

PowerPoint Presentation

Page 17: SIP Working Group

"Enhancements of IP Conference Scenarios"

proceedings of Mobility Conference, September 10-11, 2007, Singapore

More information can be found on

Page 18: SIP Working Group

SIP InterconnectionSIP Interconnection

PSU (Thailand)PSU (Thailand)NCNU (Taiwan)NCNU (Taiwan)

NIU (Taiwan)NIU (Taiwan)

Page 19: SIP Working Group

Students visit@NCNU

4 weeks visiting of 3 PG studentsMay 16 to June 10, 2007

Page 20: SIP Working Group

Network Scenario : IP Phone connectionNetwork Scenario : IP Phone connection

NCNU Network NIU Network

PSU Network

NCNU SIP Server NIU SIP Server

CNR IP PhoneIPv4: 202.12.74.206

IPv6: 2001:3c8:9007:206

NCNU IP PhoneNIU IP Phone

SIP

Asterisk ServerIPv4: 202.12.74.205

PSU PSTNPSU Legacy Phone

GSM

Mobile Phone

Abilene

Page 21: SIP Working Group

Abilene

Network Scenario: IDL Connection

NCNU NetworkNIU Network

PSU Network

CNR SIP ServerIPv4: 202.12.74.201

IPv6: 2001:3c8:9007::201CNR Mixer Server

IPv4: 202.12.74.xxxIPv6: 2001:3c8:9007::xxxIDL at PSU Site

IPv4: 202.12.74.207IPv6: 2001:3c8:9007::207

IDL at NCNU SiteIDL at NIU Site

SIP

SIPSIP

Page 22: SIP Working Group

IPv6 Remote Workshop

June 13, 2007June 13, 2007National Ilan University,National Ilan University,

TaiwanTaiwan

Page 23: SIP Working Group

IPv6@PSU Side

IPv6 car was running During a participation from both sides

Page 24: SIP Working Group

IPv6@NIU, Taiwan Side

Students controlled IPv6 car (from Taiwan to PSU)

Students participated the workshop

Page 25: SIP Working Group

SIP Servers@CNRSIP Servers@CNR

CNR SIP Server (our proprietary stack using Java)

OpernSER Asterisk Asterisk Now

PSU has installed SIP phone system between their 5 campuses

Page 26: SIP Working Group

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:[email protected]

or sip:[email protected]

for voice + video use Windows Messenger 5.1.0701 SIP URI: sip:[email protected] or

sip:[email protected]

Page 27: SIP Working Group

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.

Page 28: SIP Working Group

Other on-going projectsOther on-going projects SIP-based CRM (Customer Relationship

Management) P2P-SIP Session mobility based on SIP

Page 29: SIP Working Group

29

http://cnr.coe.psu.ac.th/

รศ ดร สนิชยั กมลภิวงศ์

Thank You for Your AttentionThank You for Your Attention


Recommended