18
D1 - SIP’03 SIP services in a distributed architecture : feedback from implementation and trial emmanuel.bertin@francetelecom .com [email protected] om pascal.lesieur@francetelecom. com

SIP services in a distributed architecture : feedback from implementation and trial

  • Upload
    ronnie

  • View
    15

  • Download
    0

Embed Size (px)

DESCRIPTION

SIP services in a distributed architecture : feedback from implementation and trial. [email protected] [email protected] [email protected]. Agenda. Global feedback Developed services Some issues Next step. Global feedback: SIP engineering. - PowerPoint PPT Presentation

Citation preview

Page 1: SIP services in a distributed architecture : feedback from implementation and trial

D1 - SIP’03

SIP services in a distributed architecture : feedback from implementation and trial

[email protected]

[email protected]

[email protected]

Page 2: SIP services in a distributed architecture : feedback from implementation and trial

France Telecom R&D D2 - SIP’03

Agenda

s Global feedback

s Developed services

s Some issues

s Next step

Page 3: SIP services in a distributed architecture : feedback from implementation and trial

France Telecom R&D D3 - SIP’03

Global feedback: SIP engineerings SIP is suitable for developing/deploying advanced

services

s SIP can be implemented in a complex multi-actor environment

Page 4: SIP services in a distributed architecture : feedback from implementation and trial

France Telecom R&D D4 - SIP’03

s Moving towards maturityQReliable productsQCustomizable (e.g. for provisioning)QService creation potential

s Good performanceQShort duration for call establishment QEven within a fully distributed architecture

Global feedback: current state of industry

Page 5: SIP services in a distributed architecture : feedback from implementation and trial

France Telecom R&D D5 - SIP’03

Developed services: examples (1)

s MediAddQAdd a new medium during a communication

–Example : Call with a phone then add video on a PC

s Customized Call Routing (CCR)QCallee unavailable

–Choices proposed to the caller to join the callee– Call redirection, email, SMS, IM…

QProposed choices–Depend on caller identity–Depend on callee presence and availability–Are set up by the callee

Page 6: SIP services in a distributed architecture : feedback from implementation and trial

France Telecom R&D D6 - SIP’03

CCR

Developed services: examples (2)Ms Durand wants to call Ms Dupont

Ms Durand

Ms Dupont Secretary

Establish a call

Set up of a rule :

If Caller is Ms Durand

And I’m not available

Then indicate :

“I’m sorry but I’m not available now”

And propose :

-To forward the call to my secretary

-To leave a voice mail

-To send an e-mail

And notify me by e-mail

Page 7: SIP services in a distributed architecture : feedback from implementation and trial

France Telecom R&D D7 - SIP’03

CCR

Developed services: examples (2)

Ms Durand

Ms Dupont Secretary

Present Not available

Presence of Ms Dupont ? Availability of Ms Dupont for Ms Durand ?Which services for Ms Durand ?

I’m sorry but I’m not available now.

You can :

-forward the call to my secretary

-leave me a voice mail

-send me an e-mail

Page 8: SIP services in a distributed architecture : feedback from implementation and trial

France Telecom R&D D8 - SIP’03

Developed services: architecture (1)

PSTN

NCP

GSP

USP

enterprise

InternetIntranet

SIP Interconnection

Network

Complete SIP serviceexecution environment

Common provisionning

Unitary provisionning

Unitary SIP service

Complete SIP serviceexecution environment *

Common Provisionning *

GSP: Global Service Provider

USP: Unitary Service Provider

NCP: SIP Network Connectivity

Provider

Page 9: SIP services in a distributed architecture : feedback from implementation and trial

France Telecom R&D D9 - SIP’03

Developed services: architecture (2)

EP

CRP

CRP CRP

CRP

EP

EP

EPPP

PSTN

EP SP

Portal

DNSEP

GW GW

Enum

EP SS

Web

SSNCP

GSP

USP

enterprise

InternetIntranet

SP: Serving Proxy

EP: Edge Proxy

CRP: Core Routing Proxy

PP: PSTN Proxy

SS: Service Server

services

Page 10: SIP services in a distributed architecture : feedback from implementation and trial

France Telecom R&D D10 - SIP’03

EP

CRP

CRP CRP

CRP

EP

EP

EPPP

PSTN

EP SP

Portal

DNSEP

GW GW

Enum

EP SS

Web

SSNCP

GSP

USP

enterprise

InternetIntranet

SP: Serving Proxy

EP: Edge Proxy

CRP: Core Routing Proxy

PP: PSTN Proxy

SS: Service Server

services

Developed services: architecture (2)

Page 11: SIP services in a distributed architecture : feedback from implementation and trial

France Telecom R&D D11 - SIP’03

… Some issues

s Service triggering

s ID/Authentication

s Charging & provisioning

Page 12: SIP services in a distributed architecture : feedback from implementation and trial

France Telecom R&D D12 - SIP’03

Service triggering

s Lack of products allowing service triggering in a distributed environment

s Implementation: Call redirection to AS based onQCPL scripts in Serving proxies and per userQTriggering criteria = CPL switchesQRouting to the corresponding ASQNot optimal : only one AS is invoked

s Loop detectionQIn case of call continuationQResolved with 2 proxies consulting the same registrar

Page 13: SIP services in a distributed architecture : feedback from implementation and trial

France Telecom R&D D13 - SIP’03

Loop detection

EP

CRP

CRP CRP

CRP

EP

EP

EPPP

PSTN

EP SP

Portal

DNSEP

GW GW

Enum

EP SS

Web

SSNCP

GSP

USP

enterprise

InternetIntranet

SP: Serving Proxy

EP: Edge Proxy

CRP: Core Routing Proxy

PP: PSTN Proxy

SS: Service Server

services

INVITE sip:[email protected]

INVITE sip:[email protected]

INVITE sip:[email protected]

LOOP detected

Page 14: SIP services in a distributed architecture : feedback from implementation and trial

France Telecom R&D D14 - SIP’03

Id / Auth: needs & issues

s SIP Network Connectivity Provider levelQNCP is close to the Internet Access & Backbone providersQNetwork Policy requested by the NCP instead of the service providers

s Service provider levelQService invocation

s Auth. difficult in our implementationQLocation of the Registrar serverQTrust domains (RFC 3324)

Page 15: SIP services in a distributed architecture : feedback from implementation and trial

France Telecom R&D D15 - SIP’03

Authentication issue

SP SS

SP: Serving Proxy

EP: Edge Proxy

CRP: Core Routing Proxy

PP: PSTN Proxy

SS: Service Server

sip:[email protected]

INVITE sip:[email protected]

407 : Proxy Authentication Required

INVITE sip:[email protected] sip:[email protected]

INVITE sip:[email protected]

407407

407

Authentication error

Page 16: SIP services in a distributed architecture : feedback from implementation and trial

France Telecom R&D D16 - SIP’03

Provisioning / Charging / OAM

s Distributed model

s ProvisioningQCommon GUI

s Charging QBreakdown/settlement mechanisms to be defined

s OAMQUnified alarms for global CRM

Page 17: SIP services in a distributed architecture : feedback from implementation and trial

France Telecom R&D D17 - SIP’03

Next steps Today: products

Qproxies, AS…

s Tomorrow: actors Qservice providers, routing providers, mobile providers, presence providers

s Actor interconnection:

@ Internet at the network level

z At the routing + service level ?peer to peer SLAglobal infrastructure ?

Page 18: SIP services in a distributed architecture : feedback from implementation and trial

France Telecom R&D D18 - SIP’03

Thank You !