OmniPCX Office SIP Peering

1. OmniPCX Office SIP Peering 3BN 69070 4143 TCASA Ed.1 July 2007

2. Agenda • Introduction • Architecture & General principles • Supported Topologies • Features List • Remote Management • RFC Compliance

3. 1 Introduction

4. SIP Drivers • Internet technology • Session Initiation Protocol • Signaling protocol for Internet services defined by IETF • Fits into other Internet protocols • IP/TCP/UDP transport, HTTP text encoding, email MIME extensibility. • Standard RFCs are available easily • Implementers that use HTTP understand SIP easily • Many tools are reuseable (Email contents, HTTPS security, etc…). • Beyond VoIP : Multi-Services • Multi-media sessions • Voice, video, Web conferencing, chat • Application driven • Instant messaging, presence based • Notification framework

5. SIP vs H323 SIP H.323 Easy to understandWell known RFC, text encoding ASN1 encodingITU documents Part of the Internet (IETF) ecosystem(HTTP, SMTP, TCP, TLS, IP, RTP,RTSP) Part of the ITU-T ecosystem Internet developers orientedLarge community Telephony service oriented Some legacy phone lack of features Full support of legacy phone features VoIP, security, conferencing, instant messaging, presence, notifications, configuration VoIP, security, conferencing, QoS Flexible Solid but rigid and not extensible Chosen by most carriers, but not easily interoperable with Only few commercial deployments SIP is the most consistent choice for evolutive and future-proof deployments

6. Corporate Private Services Carrier Network Services What is SIP Peering ? • Replacement of PSTN/ISDN trunks connecting private installations (PBXs) • Multi-services connectivity from the enterprise to the network • Permits multiple forms of real-time communication like, voice, video, presence, instant messaging. • Co-operation between IP-PBX and NGN to deliver in future new services • Corporate Private Services + Carrier Services • Users on the IP-PBX can benefit from both Private and Carrier services New Services New Services PSTN Gateway to PSTN OmniPCXOffice NGN SIP-enabled VoIP network SIP Peering

7. Benefits & Business Opportunities • Benefits: • Communication costs reduction • Moving away from distance/minutes based rates to flat-rate plans • Single broadband interface for Voice and Data • IP-PBX ready for IP Telephony and added-value applications • Business opportunities: • Growing acceptance of SIP by Service Providers accelerates commercial roll out of NGN • IP VPN deployments to address enterprises with multiple locations • Launch of new ‘managed communication services’ business models

8. 2 Architecture & General Principles

9. Architecture & Connectivity CPE NETWORK PSTN TGW CE Serving Node (CCS) Access Network SBC NGN OmniPCXOffice SBC CE : Customer Edge router SBC : Session Border Controller TGW : Trunking Gateway CCS : Call Control Server FAX IP Touch

10. NGN Components • CE (Customer Edge) • Router equipment (located in the enterprise) • Sometimes provided by the carrier • SBC (Session Border Controller) : entry door to the network • Gatekeeper & Network access control function • CCS (Call Control Server) : softswitch • Routing of calls • Application management & control (call handling) • TGW (Trunking Gateway) • Gateway to the TDM public network

11. NAT SIP • Translation between • (Private IP@ & Public IP@) or (Domain name & Public IP@) • 2 levels of address translation • Level 3 NAT (IP network level) • translation of address in the header of the IP packet • Level 7 NAT (Application level) : ALG-SIP • Translation of address in the SIP message (payload of the IP packet) • 3 options of architectures • ALG-SIP & L3-NAT in SBC • usually IP VPN topology and incumbent carriers • ALG-SIP in SBC & L3-NAT in CE router • Usually WAN access and alternative carriers • ALG-SIP & L3-NAT in CE router • Usually WAN access and traffic resellers • Important : ALG-SIP function not embedded in OmniPCX Office

12. VoIP parameters (1) • Ethernet LAN connection at 10/100 Mbps • SIP only supported over UDP protocol • Not TCP • Voice codec support : • G711 A-law and –law • G723.1 • G729a (default) • Quality of service • QoS level 3 : IP ToS/DiffServ (RFC 2474) • QoS level 2 : 802.1 p/Q

13. VoIP parameters (2) • VAD • Voice Activity Detection • Silence suppression • Comfort noise generation • Framing (packet size) • Configurable (depending on Codec) and adaptive • 10, 20, 30 (default), 40, 50, 60, 90, 120 ms • Up to 60 ms only with IP Touch phones • Call Admission Control • Static bandwidth management enabling by configuration to set up the maximum number of supported calls • If threshold reached : • OG calls : Release or Call overflow to another carrier (through ARS routing) • IC calls : Release of calls

14. Numbering format • SIP addresses = URI (Uniform Resource Identifier) • Format (for both incoming and outgoing calls) • sip:user@mydomain • ‘user’ is an E164 number, in a canonical/international format for public calls • ex. +33390677012 • Possibility to manage non-E164 numbers if required by SIP carrier (OMC config.) • Non-E164 public number cannot coexist with private SIP numbers • ‘mydomain’ is • a domain name (when calls go through a SIP Proxy) • ex. alcatel-lucent.com • or an IP address in dotted-decimal format • ex. 192.56.98.23

15. Authentication • Outgoing calls • the system sends a global login (name + password) • name (50 characters) / password (50 characters) • OMC configuration • Warning : no multiple-carrier supported with SIP Peering • Incoming calls • No authentication : only check on originating IP@/hostname (via ARS table) • Compliance with RFC 2617 & RFC 1321 • MD5 : Digest authentication scheme • Authentication is optional • Depending on SIP carrier security policy

16. Registration • Authentication information can be used for registration • Registration is performed only at the gateway level • Dynamic registration to a SIP Proxy / Registrar in the network • Registration of the URI corresponding to the installation number • No registration of each URI corresponding to users’ DDI numbers • Users’ DDI numbers must be provisioned in the Softswitch (as for H323) • Registration is optional • Depending on SIP carrier security policy

17. Security • ‘Self-defence’ mechanism provided to protect against hostile attacks • Automatic black list management of hostile IP addresses • Thresholds of identifying these IP addresses are configurable • Content of this table can be read • for Alcatel-Lucent remote support usage only • ‘Connection tracking’ natively provided on VoIP RTP and signalling streams • Thanks to the integrated firewall of Linux • ‘RTP encryption’ not supported

18. Miscellaneous • Dimensioning • Max number of IP trunks : 96 • Max ARS (automatic routing selection) table : 3000 entries • Restrictions • H323 and SIP cannot coexist on the same system • H323 by default Licensing • Each IP trunk requires one ‘IP channel software license’ • Same software license for public IP trunk (H323 or SIP) and private IP trunk

19. 3 Supported Topologies

20. SIP signaling RTP media Voice only supplied by the Service Provider • IP VPN provided by the Service provider • NAT SIP provided by network (SBC) or CE router Service Provider’s Access network NGN IP-VPN CE Softswitch SBC OmniPCXOffice TGW PSTN FAX IP Touch

21. Internet SIP signaling RTP media Voice & Internet supplied by the Service Provider • IP-VPN provided by the Service Provider • NAT SIP (ALG-SIP) for voice provided by network (SBC) or CE router • NAT for Internet provided by CE router • CE router must support QoS priorization Service Provider’s Access network NGN IP-VPN CE Softswitch SBC OmniPCXOffice TGW PSTN Internet FAX IP Touch

22. ISDN/PSTN Back-up • TDM (ISDN or Analog trunk) can be used for SIP back-up • Congestion, SIP trunk down, etc… • Numbering plans (DDI numbers) must remain consistent between TDM and SIP • Only one installation number is provided by OmniPCX Office • Mandatory that TDM carrier accepts SIP installation number T0 PSTN TGW OmniPCXOffice NGN SIP

23. SIP signaling RTP media Voice supplied by the Service Provider via a network access provider • No IP VPN provided by the Service provider • NAT SIP (ALG-SIP) provided by CE router Network Access Provider NGN CE Softswitch SBC OmniPCXOffice TGW PSTN FAX IP Touch

24. 4 Features List

25. Telephony Features supported

26. Telephony Features supported

27. Other VoIP Features

28. Glossary • CLIP Calling Line Identity Presentation • OIP Originating Identity Presentation • CNIP Calling Name Identity Presentation • ONP Originating Name Presentation • CLIR Calling Line Identity Restriction • OIR Originating Identity Restriction • COLP Connected Line Presentation • TIP Terminating Identity Presentation • CONP Connected Name Presentation • TNP Terminating Name Presentation • COLR Connected Line Restriction • TIR Terminating Identity Restriction • TNR Terminating Name Restriction

29. 5 Remote Management

30. Remote Access (1) • SIP Network must support HTTPS flows • Remote Access connections established in HTTPS messages • If HTTPS not supported, ISDN back-up must be provided for remote management • 2 remote access methods • Reverse Proxy method • Requires specific router with Reverse Proxy feature • Analyses content of HTTPS message and identifies ‘Service’ information • Port Forwarding method • Routing based on ‘Port number’ • Available with all routers • Both methods require configuration of router

31. Remote Access (2) • In some cases remote management on SIP trunk is not possible • Commercial offer of the SIP carrier includes one TDM access for remote management • SIP network does not support HTTPS flows • SIP connection is down or no bandwidth available • Traditional remote access methods remain available • ISDN (T0/T2/T1) through BRA/PRA access • Analog trunk through APA access • VPN connection

32. Reverse Proxy Method Router configuration : Routing of HTTPS messages with ‘OXO management’ service To @Priv3 & Port 443 CPE Router with Reverse Proxy feature Application1 @Priv1 / Port x NETWORK Application2 @Priv2 / Port y RSC @Public OmniPCX Office @Priv3 / Port 443 Remote OMC : HTTPS message = @Public + OXO Management service + Port 443

33. Port Forwarding Method Router/FW configuration : Forward of Port 443 To @Priv3 & Port 443 CPE Standard router Application1 @Priv1 / Port x NETWORK Application2 @Priv2 / Port y RSC @Public OmniPCX Office @Priv3 / Port 443 Remote OMC : HTTPS message = @Public + OXO Management service + Port 443

34. 6 RFC Compliance

35. RFC Compliance (1) • RFC 1321 – The MD5 message digest algorithm • RFC 2327 - SDP: Session Description Protocol • RFC 2474 – Definition of the Differentiated Services field • RFC 2617 – HTTP authentication : basic and digest access authentication • RFC 2782 – A DNS RR for specifying the location of services (DNS SRV) • RFC 2822 - Internet message format • RFC 2833 - RTP payload for DTMF Digits, telephony tones and telephony signals • RFC 3261 - SIP: Session Initiation Protocol • RFC 3262 - Reliability of provisional responses in SIP This list of standards should not be interpreted as if OmniPCX Office would be fully compliant with all contents

36. RFC Compliance (2) • RFC 3263 – Locating SIP servers • RFC 3264 - An Offer / Answer model with SDP • RFC 3323- A privacy mechanism for the Session Initiation Protocol • RFC 3324- Short term requirements for network asserted identity • RFC 3325- Private extensions to SIP for asserted identity within trusted networks • RFC 3398 – ISDN User part to SIP mapping • Only mapping to QSIG • RFC 3515 – The SIP Refer method • RFC 3966- The telephone URI for telephone numbers This list of standards should not be interpreted as if OmniPCX Office would be fully compliant with all contents

37. RFC Compliance (3) • RFC 3555- MIME type registration of RTP payload formats • RFC 3389- RTP payload for comfort noise (CN) • RFC 3725- 3rd party call control • 1st scenario only • RFC 4028 – Session timer • RFC 4497 - Interworking between SIP and QSIG • RFC 4733 – RTP payload for DTMF digits, telephony tones and telephony signals • T38 ITU-T Annex D - Procedures for real time Group3 fax / communications over IP This list of standards should not be interpreted as if OmniPCX Office would be fully compliant with all contents

38. www.alcatel-lucent.com This  document  is  for  informational or planning purposes only. It is not intended  to  modify, create or supplement any specifications or warranties relating to the Alcatel-Lucent products or services referenced herein. Information and/or technical specifications supplied within this document do not waive, directly  or  indirectly,  any  rights  or  licenses  on  patents  or other protective  rights  of  Alcatel-Lucent  or others. The specifications mentioned in this document are subject to change without notice.