1 / 24

Enrico Marocco enrico.marocco@telecomitalia.it

TELECOM ITALIA GROUP Signalling Systems for Future Telecom Networks Amsterdam – January 2011. Conveying ISDN User-to-user Information in SIP. Enrico Marocco enrico.marocco@telecomitalia.it. ISDN User-to-user Information. 2. Wait. Seriously??. Let's start over. TELECOM ITALIA GROUP

salene
Télécharger la présentation

Enrico Marocco enrico.marocco@telecomitalia.it

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. TELECOM ITALIA GROUP Signalling Systems for Future Telecom Networks Amsterdam – January 2011 Conveying ISDN User-to-user Information in SIP Enrico Marocco enrico.marocco@telecomitalia.it

  2. ISDN User-to-user Information 2

  3. Wait...

  4. Seriously??

  5. Let's start over

  6. TELECOM ITALIA GROUP Signalling Systems for Future Telecom Networks Amsterdam – January 2011 Learning by ExampleTransitioning from PSTN to Future Telecom Networks: The UUI Case Enrico Marocco enrico.marocco@telecomitalia.it

  7. POTS ISDN SIP H.323

  8. What drives transition?

  9. Savings

  10. Scale

  11. Flaws (H.323 anyone?)

  12. Innovation potential

  13. My desktop phone (Has good speaker and mic, why change?) Backward Compatibility

  14. Q.931 ISDN User-to-user information Application-specific information that “is not known and understood by the ISDN network that transports it” Used in call centers, contact centers, public phones…

  15. UUI in SIP – User Agent to User Agent Alice Proxy Bob INVITE (UUI) INVITE (UUI) 100 Trying 200 OK 200 OK ACK ACK

  16. UUI in SIP – Retargeting Alice Proxy Carol INVITE sip:bob (UUI) INVITE sip:carol (UUI) 100 Trying 200 OK 200 OK ACK ACK

  17. UUI in SIP – Redirect Alice Redirector Bob INVITE 302 Moved (UUI) 200 OK ACK INVITE (UUI) 200 OK ACK

  18. UUI in SIP – Referral Alice Referrer Bob REFER (UUI) 202 Accepted Various NOTIFYs INVITE (UUI) 200 OK ACK

  19. ISDN UUI in SIP – Why not in INFO? • SIP INFO Message was introduced specifically for ISUP interworking, but… • UUI needs to be carried at call setup/teardown • Network elements may want to make decisions based on it

  20. ISDN UUI in SIP – Why not in MIME body? • Application data should naturally go in message bodies (just as in HTTP, SMTP), but… • Reality check: very few implementations support multipart MIME • Redirect? Referral?

  21. ISDN UUI in SIP – Why not in URI param? • URI parameter are common in Contact headers to specify user agent characteristics, but… • UUI targets the user, not necessarily the user agent (i.e. 1 user, N UAs) • Retargeting?

  22. ISDN UUI in SIP – New Header Field • Clear syntax and semantic (other than) • Mechanisms for encoding header fields in REFER and 302 messages already exist… and work! User-to-User: 56a390f3d2b7310023a;encoding=hex;purpose=isdn-interwork ;content=isdn-uui Contact: <sip:+12125551212@gateway.example.com? User-to-User=56a390f3d2b7310023a%3Bencoding%3Dhex%3Bpurpose%3D isdn-interwork%3Bcontent%3Disdn-uui> Refer-To: <sip:+12125551212@gateway.example.com? User-to-User=56a390f3d2b7310023a%3Bencoding%3Dhex%3Bpurpose%3D isdn-interwork%3Bcontent%3Disdn-uui>

  23. IETF CUSS Working Group Roadmap • Working group chartered in September 2010 (despite standardization work begun 2/3 years earlier) • Problem statement and requirements • Mechanism specification (exp. in June) • ISDN application usage specification (exp. in June)

  24. Possible Future Applications • Realtime credit information • Payments • ??

More Related