1 / 11

Managing SIP Services

Managing SIP Services. Sumit Dhar Product Manager. Agenda. Managing SIP Services Why Manage Issues of Distributed Networks Service Models Conclusion. SIP Services- Why Manage. Evolution Started as Peer-peer Proxy just a router Service logic in the endpoints

tuan
Download Presentation

Managing SIP Services

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. Managing SIP Services Sumit Dhar Product Manager

  2. Agenda • Managing SIP Services • Why Manage • Issues of Distributed Networks • Service Models • Conclusion

  3. SIP Services- Why Manage • Evolution • Started as Peer-peer • Proxy just a router • Service logic in the endpoints • Application Server introduced • Network-hosted features • Routing-based • Mid-call • Proxies logical, co-located with App-Server • B2BUA became a monster within itself • Is it worthwhile to define networks sans apps • Standardize Vs Leave it open Many Heterogenous Distributed Elements doing Specialized Functions

  4. Service Framework- Complex AS AS Access Network SCIM SIP AS I-CSCF Border Proxy ISC Load Balancer S-CSCF OSA Service Capability Server OSA AS OSA API ISC NAT/Firewall Traversal ISC Sh Cx HSS IM-SSF Si CAP MAP Camel Service Env P-CSCF Outbound Proxy Main Standby

  5. Issue: Network Provisioning • Network Elements are • Heterogeneous • Function • Database requirements • Costly replication • Batch configuration • User CPL activations? • Meta-directory? • Partial exposure of subscriber data across network elements • Notify/Elements fetch on their own • Availability models • Should data be sync-ed between M& S or with Meta-directory

  6. Issue: User Self Provisioning • Terminal/Device Self configuration • Home server coordinates, Preferences etc. • Issues • Lack of Standards • Impact on Device Mobility • “Last mile” causes maximum “outages” • User self-provisioning • CPL based user configuration • Single point of access needed • Should get replicated where ever it needs to

  7. SIP Services- Do your own thing • Feature states/behavior in endpoint • Security Traversal • Availability • Interactions • Network is feature unaware/un-stateful • Proxies are mere routers • May be Basic routing services/ number translation • Benefits • Scalable networks • More flexibility to users • Limitations • Forces homogenous networks/ capabilities • Charging limited to usage only • Endpoints availability for features

  8. SIP Services- Get what you pay for • Network delivers services • Handles feature interactions • Subscriber states/ presence • CPL etc. based routing services • API based Mid-call services • Multi-UA contexts- B2BUA • Limitations • Scalability • Performance • Complexity • Advantages • Choice of charging models • Availability of n/w when endpoint isn’t

  9. Managing SLA • QoS probes • Adjust charging rates viz. Conference • Service probes? • Who Guarantees/Monitors? • Network Provider for access network quality • ASP for the application availability

  10. SIP Services- Summary • Interesting times ahead • Distributed networks tough to provision/manage • Business models yet to mature • May govern how the networks will be deployed • SIP will occupy its right position as an enabler • There may be no killer apps • Integration across various services(web,chat,voice…) • Value sells, not technology

  11. Thank You Sdhar@hss.hns.com

More Related