1 / 18

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

SIP services in a distributed architecture : feedback from implementation and trial. emmanuel.bertin@francetelecom.com emmanuel.bury@francetelecom.com pascal.lesieur@francetelecom.com. Agenda. Global feedback Developed services Some issues Next step. Global feedback: SIP engineering.

ronnie
Download Presentation

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

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. SIP services in a distributed architecture : feedback from implementation and trial emmanuel.bertin@francetelecom.com emmanuel.bury@francetelecom.com pascal.lesieur@francetelecom.com

  2. Agenda • Global feedback • Developed services • Some issues • Next step

  3. Global feedback: SIP engineering • SIP is suitable for developing/deploying advanced services • SIP can be implemented in a complex multi-actor environment

  4. Global feedback: current state of industry • Moving towards maturity • Reliable products • Customizable (e.g. for provisioning) • Service creation potential • Good performance • Short duration for call establishment • Even within a fully distributed architecture

  5. Developed services: examples (1) • MediAdd • Add a new medium during a communication • Example : Call with a phone then add video on a PC • Customized Call Routing (CCR) • Callee unavailable • Choices proposed to the caller to join the callee • Call redirection, email, SMS, IM… • Proposed choices • Depend on caller identity • Depend on callee presence and availability • Are set up by the callee

  6. Set up of a rule : • If Caller isMs Durand • And I’m not available • Then indicate : • “I’m sorry but I’m not available now” • And propose : • To forward the call tomy secretary • To leave a voice mail • To send an e-mail • And notify me bye-mail Establish a call Developed services: examples (2) Ms Durand wants to call Ms Dupont CCR Ms Durand Ms Dupont Secretary

  7. 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 Developed services: examples (2) CCR  Present  Not available Ms Durand Presence of Ms Dupont ? Availability of Ms Dupont for Ms Durand ? Which services for Ms Durand ? Ms Dupont Secretary

  8. Developed services: architecture (1) GSP: Global Service Provider USP: Unitary Service Provider NCP: SIP Network Connectivity Provider Common provisionning NCP Complete SIP service execution environment Intranet Internet Common Provisionning * GSP SIP Interconnection Network Complete SIP service execution environment * Unitary provisionning enterprise Unitary SIP service PSTN USP

  9. SP: Serving Proxy EP: Edge Proxy CRP: Core Routing Proxy PP: PSTN Proxy SS: Service Server SS NCP Portal DNS Intranet EP EP SP Internet GSP CRP CRP CRP EP EP EP Enum CRP EP enterprise Web PP GW GW EP SS PSTN services USP Developed services: architecture (2)

  10. SP: Serving Proxy EP: Edge Proxy CRP: Core Routing Proxy PP: PSTN Proxy SS: Service Server SS NCP Portal DNS Intranet EP EP SP Internet GSP CRP CRP CRP EP EP EP Enum CRP EP enterprise Web PP GW GW EP SS PSTN services USP Developed services: architecture (2)

  11. … Some issues • Service triggering • ID/Authentication • Charging & provisioning

  12. Service triggering • Lack of products allowing service triggering in a distributed environment • Implementation: Call redirection to AS based on • CPL scripts in Serving proxies and per user • Triggering criteria = CPL switches • Routing to the corresponding AS • Not optimal : only one AS is invoked • Loop detection • In case of call continuation • Resolved with 2 proxies consulting the same registrar

  13. SP: Serving Proxy EP: Edge Proxy CRP: Core Routing Proxy PP: PSTN Proxy SS: Service Server SS NCP Portal DNS Intranet EP EP SP Internet GSP CRP CRP CRP EP EP EP Enum CRP EP enterprise Web PP GW GW EP SS PSTN services USP Loop detection INVITE sip:DUPONT@enterprise.com LOOP detected INVITE sip:DUPONT@enterprise.com INVITE sip:DUPONT@ss.usp.com

  14. Id / Auth: needs & issues • SIP Network Connectivity Provider level • NCP is close to the Internet Access & Backbone providers • Network Policy requested by the NCP instead of the service providers • Service provider level • Service invocation • Auth. difficult in our implementation • Location of the Registrar server • Trust domains (RFC 3324)

  15. Authentication issue SP: Serving Proxy EP: Edge Proxy CRP: Core Routing Proxy PP: PSTN Proxy SS: Service Server SP SS sip:durand@enterprise.com INVITE sip:dupont@enterprise.com 407 : Proxy Authentication Required INVITE sip:dupont@enterprise.com INVITE sip:dupont@ss.usp.com INVITE sip:secretary@enterprise.com 407 407 407 Authentication error

  16. Provisioning / Charging / OAM • Distributed model • Provisioning • Common GUI • Charging • Breakdown/settlement mechanisms to be defined • OAM • Unified alarms for global CRM

  17. Next step • Today: products • proxies, AS… • Tomorrow: actors • service providers, routing providers, mobile providers, presence providers • Actor interconnection: @Internet at the network level zAt the routing + service level ? peer to peer SLA global infrastructure ?

  18. Thank You !

More Related