7510 product description

3FZ 08014 AAAS DEZZA Edition 02

3FZ 08014 AAAS DEZZA Edition 02

Status Released

Change Note

Short Title MGW Product Description

All rights reserved. Passing on and copyingof this document, use and communicationof its contents not permitted without writtenauthorization from Alcatel-Lucent.

Contents

3 / 2123FZ 08014 AAAS DEZZA Edition 02

Contents

About this Document 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 Product Overview 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1 Introduction 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 Network Solutions 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3 Alcatel-Lucent 7510 MGW Key Benefits 20. . . . . . . . . . . . . . . . . . . . . . . . . .

1.3.1 General Features 22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.2 System Robustness and Stability 24. . . . . . . . . . . . . . . . . . . . . . 1.3.3 Geographic Redundancy 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.4 Versatile Platform; Combining TGW, BGW and SGW 25. . . . . 1.3.5 Density and Scalability/Performance 27. . . . . . . . . . . . . . . . . . . . 1.3.6 Performance 28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.7 System Management and OAM Overview 28. . . . . . . . . . . . . . .

2 Features and Services – Platform 29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1 Introduction 30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2 Interfaces 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3 Signaling Protocols Supported 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3.1 H.248.1 Version 2 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4 Multi-Vendor Interoperability 34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5 Virtual Media Gateways 35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6 Voice Codecs 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.6.1 G.711 Codec 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6.2 G.729A/B Codec 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6.3 G.723.1 Codec 37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6.4 G.726 Codec 37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6.5 AMR2 Codec 37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6.6 AMR-WB (G.722.2) Codec 37. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6.7 GSM-FR Codec 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6.8 GSM-EFR Codec 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6.9 GSM-HR Codec 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6.10 G.728 Codec 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6.11 EVRC Codec 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.7 Voice-Band and Voice-Band Data Services 40. . . . . . . . . . . . . . . . . . . . . . . 2.7.1 Voice Activity Detection 40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7.2 Comfort Noise Generation 41. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7.3 Packet Loss Concealment 42. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7.4 Echo Cancellation 42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7.5 Adaptive Jitter Buffer 42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7.6 Fax Modem / T.38 43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7.7 Voice Band Data Mode 43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Contents


2.7.8 Media Inactivity Detection 44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7.9 Media Replication 44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.8 Inband Signaling Based Call Services – Platform 45. . . . . . . . . . . . . . . . . . 2.8.1 DTMF Packet Relay 45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.8.2 Inband Signaling Processing 45. . . . . . . . . . . . . . . . . . . . . . . . . . 2.8.3 Digitmap 46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.9 Quality of Service 47. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.10 Secured IP-Interfaces (OAM and MGC) 50. . . . . . . . . . . . . . . . . . . . . . . . . .

2.10.1 IPsec 50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.10.2 Telnet/SSH 50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.11 Tones and Announcements 52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.12 Redundancy, Reliability, and Availability 54. . . . . . . . . . . . . . . . . . . . . . . . . .

2.12.1 System Control Module and Switch Fabric Module 55. . . . . . . 2.12.2 Packet Interface Module 56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.12.3 Circuit Interface Module 57. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.12.4 Media Conversion Module 57. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.12.5 Signaling 58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.12.6 Power 58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.12.7 Cooling 59. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.13 IP Services and Resilience 60. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.13.1 Gratuitous ARP 60. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.13.2 Bi-directional Forwarding Detection – BFD 61. . . . . . . . . . . . . .

2.14 Switching and Interworking Modes 62. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.14.1 TDM To/From RTP 62. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.14.2 TDM Hairpinning 63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.14.3 Border Gateway 65. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.15 Switched Connection Types 68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3 Features and Services – TGW Application 69. . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1 Circuit–Mode Data Services 70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.1 Monorate 64k Unrestricted Digital Information 70. . . . . . . . . . . 3.1.2 Multirate Nx64k Wide-Band Data Services 70. . . . . . . . . . . . . . 3.1.3 Digital Circuit Multiplication Equipment – DCME 71. . . . . . . . . .

3.2 Inband Signaling Based Call Services – TGW Application 72. . . . . . . . . . 3.2.1 TDM to TDM Hairpinning with Media Processing 72. . . . . . . . . 3.2.2 FSK 72. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3 Semi-Permanent Connections 73. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.1 SPC without Media Processing 73. . . . . . . . . . . . . . . . . . . . . . . . 3.3.2 SPC without Media Processing with DCME 73. . . . . . . . . . . . . . 3.3.3 SPC with Media Processing 73. . . . . . . . . . . . . . . . . . . . . . . . . . .

4 Features and Services – SGW Application 75. . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1 Embedded Signaling Gateway 76. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Contents


5 Features and Services – BGW Application 79. . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.1 Introduction 80. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.1 Context Admission Control 82. . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.2 Dynamic Media Firewall and Gate Management 83. . . . . . . . . . . . . . . . . . . 5.3 Traffic Policing 84. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4 Address Translation, Hosted NAT Traversal, and Connectivity 85. . . . . . . 5.5 IP Version Interworking 86. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.6 Media Aware Mode (Transcoding and Media Resource Functions) 87. . . 5.7 QoS Tagging and QoS Statistics 88. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.8 Peering Partner Monitoring 89. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.9 Multimedia Support 90. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.10 BGW Specific H.248 Packages 91. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6 Features and Services – SFW Application 93. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.1 SIP Firewall Overview and Main Features 94. . . . . . . . . . . . . . . . . . . . . . . . 6.2 SIP Firewall Features 97. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.2.1 SIP Parser Attack Prevention 97. . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.2 Protection Against SIP DoS and Dstributed DoS Attacks 97. .

6.3 IP Filtering and Classifier 99. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4 IP/UDP/ICMP/TCP DoS Attacks Mitigation 100. . . . . . . . . . . . . . . . . . . . . . . . 6.5 Networking Features 101. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6 Redundancy 102. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7 SIP Firewall Capacity 103. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7 Functional Architecture and Software 105. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.1 Introduction 106. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1.1 Scalable Capacity 106. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1.2 Usage 107. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1.3 Efficiency 107. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1.4 Quality of Service – QoS 108. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1.5 Redundancy, Reliability and Availability 108. . . . . . . . . . . . . . . . .

7.2 Media Gateway Functional Architecture 110. . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.1 Functional Architecture 110. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.2 System Control Module 111. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.3 Switch Fabric Module 113. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.4 Circuit Interface Module 115. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.5 Packet Interface Module 117. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.6 Media Conversion Module – VBMCMxE 118. . . . . . . . . . . . . . . . 7.2.7 Capacity, Scaleability and Redundancy 121. . . . . . . . . . . . . . . . . 7.2.8 Summary of Module Functions 123. . . . . . . . . . . . . . . . . . . . . . . .

7.3 Backplane Structure 124. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.3.1 TDM Bus 124. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.3.2 Data Bus 124. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Contents


7.3.3 Redundant Bus 124. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.3.4 Clock Distribution Bus 124. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.4 Clock Generator 126. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5 Software 128. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.5.1 Kernel Software 129. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5.2 Network Layer Software 130. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5.3 Application Layer Software 132. . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5.4 Voice Processing 134. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5.5 Software Redundancy 134. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8 System Management and OAM 137. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.1 Overview 138. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2 Chassis Management 139. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3 Configuration Management 140. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4 Fault Management 141. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.4.1 Fault Management Application Manager 141. . . . . . . . . . . . . . . . 8.4.2 Monitoring and Alarms 142. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4.3 Alarm Classifications 143. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.5 Diagnostic Test – BERT 144. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.6 System Logging and Debugging 145. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.7 Performance Management 147. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.7.1 Performance Counters 147. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.7.2 Threshold Crossing Alarms 148. . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.7.3 Call-Related Performance Counters – H.248.xnq 148. . . . . . . . .

8.8 Security Management 149. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.8.1 Transport Layer Security 149. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.8.2 User Account Security 149. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.9 OAM Interfaces 151. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.9.1 Command Line Interface 152. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.9.2 GUI-Based Interface 152. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.9.3 RADIUS User Account Management 158. . . . . . . . . . . . . . . . . . .

8.10 Software Upgrade Management 160. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9 Physical Architecture and Hardware 161. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.1 Introduction 162. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1.1 Single Alcatel-Lucent 7510 MGW Configuration 162. . . . . . . . . . 9.1.2 Rack Configuration 166. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.2 Chassis Internal and External Features 167. . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.1 Chassis 167. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.2 Cooling 169. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.3 Power Source and Distribution 172. . . . . . . . . . . . . . . . . . . . . . . . . 9.2.4 EMC 173. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.3 Functional Description of Hardware Modules 174. . . . . . . . . . . . . . . . . . . . . . 9.3.1 System Control Module 176. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Contents


9.3.2 Switch Fabric Module 179. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3.3 Circuit Interface Module 181. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3.4 Packet Interface Module 189. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3.5 Media Conversion Module 192. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Abbreviations 195. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendix A Specifications 199. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendix B Standards 201. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendix C Components and Part Numbers 207. . . . . . . . . . . . . . . . . . . . . . . . . .

Appendix D Revision History 211. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Contents


Figures

Figure 1 Network Solutions 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 2 Multiple Virtual MGW Function 26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 3 Interfaces Supported 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4 IP Header for ToS and DiffServ 48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 5 Forwarding Voice Packets using Backbone Routers 49. . . . . . . . . . . . . . . . . Figure 6 TDM To/From RTP 62. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 7 TDM Hairpinning Without DSP Involvement 63. . . . . . . . . . . . . . . . . . . . . . . . Figure 8 TDM Hairpinning With DSP Involvement 64. . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 9 TDM Hairpinning With DSP and PIM Involvement 65. . . . . . . . . . . . . . . . . . Figure 10 BGW Without DSP Involvement 66. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 11 BGW With DSP Involvement 67. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 12 BGW Application 80. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 13 BGW Features List 82. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 14 SFW Application 94. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 15 SIP Firewall Functionality 96. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 16 SIP Firewall Capacity 103. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 17 Logical Interconnections of the Functional Modules 110. . . . . . . . . . . . . . . . Figure 18 Functional Architecture of the System Control Module 112. . . . . . . . . . . . . . . Figure 19 Functional Architecture of the Switch Fabric Module 113. . . . . . . . . . . . . . . . Figure 20 External Switch Fabric Module Connections 114. . . . . . . . . . . . . . . . . . . . . . . Figure 21 Functional Architecture of the Circuit Interface Module 116. . . . . . . . . . . . . . Figure 22 Functional Architecture of the Packet Interface Module 118. . . . . . . . . . . . . . Figure 23 Runtime Architecture 129. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 24 Element Management Architecture and Interfaces 151. . . . . . . . . . . . . . . . . . Figure 25 MGEM: Example of Main Window 154. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 26 MGEM: Example of E1 Links Display 155. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 27 Alarm Manager: Example of a Main Active Alarm Window 157. . . . . . . . . . . Figure 28 Alarm Manager: Example of an Alarm Archive View 157. . . . . . . . . . . . . . . . . Figure 29 Alcatel-Lucent 7510 MGW Front View 163. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 30 Alcatel-Lucent 7510 MGW Rear View 164. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 31 Alcatel-Lucent 7510 MGW Chassis, Side View 165. . . . . . . . . . . . . . . . . . . . . Figure 32 Rack Configuration 166. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 33 Alcatel-Lucent 7510 MGW Chassis, Front View 168. . . . . . . . . . . . . . . . . . . . Figure 34 Alcatel-Lucent 7510 MGW Chassis, Rear View 169. . . . . . . . . . . . . . . . . . . . . Figure 35 Air Flow through an Alcatel-Lucent 7510 MGW 170. . . . . . . . . . . . . . . . . . . . . Figure 36 Fan Tray (VS3FU) Physical View 171. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 37 Position of the Air Filter 172. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 38 Alcatel-Lucent 7510 MGW Power Connections 173. . . . . . . . . . . . . . . . . . . . . Figure 39 Generic View of a Processor Board 174. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 40 Generic View of an I/O Board 175. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 41 Front View and Location of the VBSCM 177. . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 42 Rear View and Location of the VMSCM/VMSCMA 178. . . . . . . . . . . . . . . . . . Figure 43 Front View and Location of the VBSFM 179. . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 44 Front View and Location of the VBC4S1 181. . . . . . . . . . . . . . . . . . . . . . . . . . .

Contents


Figure 45 Rear View and Location of the VM4S1SS 182. . . . . . . . . . . . . . . . . . . . . . . . . . Figure 46 Rear View and Location of the VMCIM 184. . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 47 Front View and Location of the VB32E1T1 185. . . . . . . . . . . . . . . . . . . . . . . . . Figure 48 Rear View and Location of the VM32E1T1/VMRED1 186. . . . . . . . . . . . . . . . Figure 49 Front View and Location of the VB12DS3 187. . . . . . . . . . . . . . . . . . . . . . . . . . Figure 50 Rear View and Location of the VM12DS3 188. . . . . . . . . . . . . . . . . . . . . . . . . . Figure 51 Front View and Location of the VBPI4GE / VBPIxGES 190. . . . . . . . . . . . . . Figure 52 Rear View and Location of the VMPIM 191. . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 53 Front View and Location of the VBMCMxE 192. . . . . . . . . . . . . . . . . . . . . . . . .

Contents


Tables

Table 1 Related Documents 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 2 Alcatel-Lucent 7510 MGW Key Benefits 20. . . . . . . . . . . . . . . . . . . . . . . . . . . Table 3 Alcatel-Lucent 7510 MGW General Features 22. . . . . . . . . . . . . . . . . . . . . . . Table 4 Alcatel-Lucent 7510 MGW Performance 28. . . . . . . . . . . . . . . . . . . . . . . . . . . Table 5 Interfaces Supported 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 6 Echo Cancellation Supported 42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 7 Hardware Redundancy 54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 8 System Control Module Functions 112. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 9 Switch Fabric Module Functions 115. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 10 Circuit Interface Module Functions 117. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 11 Packet Interface Module Features 118. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 12 VBMCMxE Features 120. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 13 Capacity and Redundancy of the VBMCMxE 120. . . . . . . . . . . . . . . . . . . . . . . Table 14 Overview of Capacity and Redundancy per Module 122. . . . . . . . . . . . . . . . . Table 15 VoIP Functions Processed by the Modules 123. . . . . . . . . . . . . . . . . . . . . . . . Table 16 Software Redundancy 135. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 17 Alcatel-Lucent 7510 MGEM Hardware Requirements 158. . . . . . . . . . . . . . . Table 18 Alcatel-Lucent 7510 MGEM Software Requirements 158. . . . . . . . . . . . . . . . Table 19 SDH CIM I/O Card: Transmitter Performance 183. . . . . . . . . . . . . . . . . . . . . . Table 20 SDH CIM I/O Card: Receiver Performance 183. . . . . . . . . . . . . . . . . . . . . . . . Table 21 Alcatel-Lucent 7510 MGW Physical Specifications 199. . . . . . . . . . . . . . . . . . Table 22 Alcatel-Lucent 7510 MGW Compliances and Requirements 200. . . . . . . . . . Table 23 Components and Part Numbers 207. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 24 Reason for Revision 211. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Scope

Reason forRevision

Readership

Contents in Brief

About this Document


About this Document

This Product Description introduces the Alcatel-Lucent 7510Media Gateway (MGW) and describes how it connects circuitswitched telephone networks to Ethernet packet switchingnetworks. Its capabilities as Border Gateway (BGW), ensuringnetwork security, service interworking and accounting in anexclusive Internet Protocol (IP) network, is described as well.

The document provides an overview of theAlcatel-Lucent 7510 MGW, focusing on the general systemarchitecture and the applications: Trunking Gateway (TGW),Time Division Multiplex (TDM)-switch and Border Gateway.

Descriptions of the changes for this document are provided inAppendix D.

This document is intended to be used by network planners, andothers desiring to gain an overview of theAlcatel-Lucent 7510 MGW as a Voice over IP (VoIP) or Fax overIP (FoIP) Trunking Gateway, a Border Gateway, and a SignalingGateway.

This document contains the following chapters:

Chapter 1Product Overview gives an overview of the features andkey benefits of an Alcatel-Lucent 7510 MGW, as well asgateway management and applications.

RelatedDocuments

About this Document


Chapter 2Features and Services – Platform describes features andservices supported by the Alcatel-Lucent 7510 MGW withregard to the MGW platform.

Chapter 3Features and Services – TGW Application describesfeatures and services supported by theAlcatel-Lucent 7510 MGW with regard to the MGW trunkinggateway application.

Chapter 4Features and Services – SGW Application describesfeatures and services supported by theAlcatel-Lucent 7510 MGW with regard to the MGWsignaling gateway application.

Chapter 5Features and Services – BGW Application describesfeatures and services supported by theAlcatel-Lucent 7510 MGW with regard to the MGW bordergateway application.

Chapter 7Functional Architecture and Software describes thearchitecture and software system components of anAlcatel-Lucent 7510 MGW.

Chapter 8System Management and OAM describes thecomprehensive set of system management and OAM toolsand features.

Chapter 9Physical Architecture and Hardware describes thephysical architecture of the Alcatel-Lucent 7510 MGW andits related hardware.

Table 1 lists other Alcatel-Lucent 7510 MGW related documents.

Frequently UsedAbbreviations

Trademarks

About this Document


Table 1 Related Documents

Title Part Number

Alcatel-Lucent 7510 MGW:Installation and Configuration Guide

3FZ 08012 AAAx PCZZA

Alcatel-Lucent 7510 MGW:Safety Guidelines and Agency Approvals

3FZ 08013 AAAA PCZZA

Alcatel-Lucent 7510 MGW Reference Guide: Gateway Specific Commands


Alcatel-Lucent 7510 MGW Reference Guide: IP Specific Commands


Alcatel-Lucent 7510 MGW Reference Guide: Signaling Commands


Alcatel-Lucent 7510 MGW Reference Guide: TDM Specific Commands


Alcatel-Lucent 7510 MGW Reference Guide:Performance Statistics Commands


Alcatel-Lucent 7510 MGW Element ManagerUser Guide


Alcatel-Lucent 7510 MGW Alarm Manager UserGuide


Circuit Interface Module (CIM)

Media Conversion Module (MCM)

Packet Interface Module (PIM)

System Control Module (SCM)

Switch Fabric Module (SFM)

The Alcatel-Lucent word and Alcatel-Lucent logo are registeredtrademarks and service marks of Alcatel-Lucent. All othertrademarks are the property of their respective owners.

About this Document


1 Product Overview


1 Product Overview

This chapter presents an overview of theAlcatel-Lucent 7510 MGW.

The following sections are presented:

Introduction

Network Solutions

Alcatel-Lucent 7510 MGW Key Benefits

Alcatel-Lucent 7510 MGW Key Features

System Management

Efficient andReliable

Networks

Single Platform

IndustryStandards

Key NGNBuilding Block

1 Product Overview


1.1 IntroductionAs one of the key components of Alcatel-Lucent’s NextGeneration Network (NGN) and IP Multimedia Subsystem (IMS)portfolio, the Alcatel-Lucent 7510 MGW provides seamlessinterworking of media streams between the Public SwitchedTelephone Network (PSTN) and IP networks, as well as betweenIP networks.

More and more service providers are transforming their networksinto all-IP networks. The Alcatel-Lucent 7510 MGW todayprovides a cost effective solution for PSTN to IP conversion, anda smooth evolution to a Border Gateway guarding the interfaceto other IP-network providers.

The Alcatel-Lucent 7510 MGW combines the reliability andsimplicity of voice with the speed and efficiency of data networks.It features an advanced architecture and interfaces optimized forpacket voice applications, together with carrier-class reliability,availability and quality.

A single platform, the Alcatel-Lucent 7510 MGW supportsmultiple media gateway applications and facilitates the evolutionof the PSTN towards a Voice over Packet (VoP) network andsmooth evolution to an all-VoIP network. Based on its modularconcept the Alcatel-Lucent 7510 MGW supports simultaneousoperation as TGW, BGW and SGW in one chassis. All modulesof the TGW, except the Circuit Interface Modules (CIM), can bereused for the BGW application.

Using open and standardized signaling and control protocolssuch as Megaco/H.248 and Signaling Transport (SIGTRAN), itcan be deployed with Alcatel-Lucent softswitch and MediaGateway Controller (MGC) platforms as well as integrated intoany multi-vendor next generation network.

An NGN contains three main building blocks: softswitches, mediagateways and a packet-based transport network. TheAlcatel-Lucent 7510 MGW is the key element for Alcatel-Lucent’sNGN solutions, setting the foundation for voice quality, reliability,scalability and performance in the high-density segment. Itprovides VoIP capabilities and serves as a key transitionalelement between today’s circuit-switched and packet-switchedtelephony networks, and serves as a Border Gateway between

1 Product Overview


packet networks to ensure network security, service interworkingand accounting.

Combined with the Alcatel-Lucent 5020 Softswitch Platform and5450 IMS Session Controller, the Alcatel-Lucent 7510 MGWenables multifold NGN solutions.

1 Product Overview


1.2 Network SolutionsAs shown in Figure 1, the Alcatel-Lucent 7510 MGW offers thefollowing network solutions:

Figure 1 Network Solutions

TrunkingGateway

Centralized AGW

Border Gateway

1 Product Overview


Trunking Gateway

Centralized AGW

Border Gateway

The Alcatel-Lucent 7510 MGW offers the highest port density inVoIP trunking on a true carrier grade platform, thereby enablingreliable and cost-efficient utilization of IP network for transit voicetraffic.

By supporting TDM hairpinning (native TDM switching) andavoiding burdening IP network with local calls, theAlcatel-Lucent 7510 MGW enables efficient treatment of localcalls while migrating to an NGN Class 4 solution.

The Centralized Access Gateway (CAGW), under the control ofsignaling compatible MGC like Alcatel-Lucent 5020 MGC,supports the following Local EXchange (LEX) bypasses:

PBX AccessBy allowing direct Private Branch Exchange (PBX) accessto IP-based NGN platforms, bypassing TDM localexchanges, the Alcatel-Lucent 7510 MGW providescost-efficient Primary Rate Access (PRA) lines forconnecting corporate PBX systems.

The Alcatel-Lucent 7510 MGW interworks with theAlcatel-Lucent 5020 MGC as Alcatel-Lucent Border Gateway.The Alcatel-Lucent 7510 Border Gateway Function (BGF) is toadapt, police and switch media streams.

The Alcatel-Lucent 7510 integrated SIP Firewall is to adapt,police and switch the SIP control stream to the InterconnectionBorder Control Function (IBCF), e.g., the Alcatel-Lucent 5020MGC.

1 Product Overview


1.3 Alcatel-Lucent 7510 MGW Key BenefitsAn Alcatel-Lucent 7510 MGW, featuring a carrier-grade platformand a highly scalable distributed switching architecture, isspecifically designed to meet stringent operator requirementsdemanded by Next Generation media gateway applications.Table 2 lists key benefits uniquely distinguishing theAlcatel-Lucent 7510 MGW in the media gateway market.

Table 2 Alcatel-Lucent 7510 MGW Key Benefits

Key Benefits Feature Description

Versatile platform – TGW

– BGW

– SGW

Leveraging common media resourcesand multihoming (virtualized MediaGateway) in one chassis.

Smooth transition TGW ––> BGW.

Full PSTN-network conversion.

Density/Scalability User-configurable number of VoiceAccess Modules [Digital SignalingProcessors (DSPs)]

Available in multiple configurations,each Alcatel-Lucent 7510 MGW DSPmodule has a maximum capacity toserve 7,000 DS0s simultaneously or

20-slot chassis with a 14 U x 18 inchx 19 inch size (1 U = 44.45 mm)

serve 7,000 DS0s simultaneously or32,000 DS0s per gateway for VoIP(64,000 DS0s per gateway forservices w/o media processing).

High Capacity SwitchingArchitecture

Pool of DSP resources shared by allports and interfaces

The Alcatel-Lucent 7510 MGWarchitecture efficiently and

Provides native-mode switching andadaptation of different media typesincluding TDM and VoIP

economically increases DSP powerand packet forwarding rates withoutrequiring major system upgrades.

Features a non-blocking 16 Gbit/spacket switch fabric and anon-blocking 10 Gbit/s TDM switchfabric, as well as a variety ofhigh-speed broadband and TDMinterfaces

The gateway uses an NGNconnection control model to maintaincall processing, independent of otherfunctions, e.g., DSP resourcemanagement.

Carrier-Class Reliabilityand Availability

Designed with numerous redundancyand fault tolerance features to providea very high level of availability andreliability

All control, interfaces, and voiceprocessing hardware modules are1+1 or N+1 (active + standby)redundant and hot swappable,allowing any module to be removedand replaced without shutting downthe system. TheAlcatel-Lucent 7510 MGW includesredundant power interfaces.

All optical interfaces support LinkProtection Switching (LPS). Switchingfrom an active to a standby line doesnot result in lost packets.

1 Product Overview


Key Benefits DescriptionFeature

Latest DSP Technology A pool of high-density DSP-basedmodules offering several VoiceCodecs and G.168 compliant echocancellation is used.

Alcatel-Lucent 7510 MGW DSPs offerdynamic access to any port orinterface to connect to voicecompression and packetization,silence suppression, echocancellation, and other packet voiceprocessing facilities.

Packet to Packet transcoding. Any to any codec.

Packet Loss Concealment PLC is an algorithm used to minimizedistortion in output voice, caused bypacket loss or excessively latespeech packets.

Silence Suppression The voice activity detection in theAlcatel-Lucent 7510 MGW stopstransmission of packets when periodsof silence occur during aconversation.

Adaptive Jitter Buffer The adaptive jitter buffercompensates for delay variations inpacket transmission times during aVoIP call.

Open Standard Protocols Supports the industry-standardH.248.1 Version 2 signaling protocolto seamlessly interwork with multiplesoftswitches.

An Alcatel-Lucent 7510 MGWsupports an open control interface,e.g., to connect to:

MGCs using the H.248 protocol

TISPAN NGN R1 (TGW profile)or ETSI TS 123 002 Mn profile(IMS-MGW)

ETSI ES 283 018 H.248 Ia pro-file version (BGW profile)

an Alcatel-Lucent 5020 MGCF

multi-vendor NGN networks.

Multicore/MultithreatMIPS64 Technology

Multicore CPUs for high performancecall-processing.

Enables flexible application on theHardware, network processing, traffic

General Purpose ThroughputProcessing.

management, performancemonitoring, encryption and SGW.

Industry LeadingManagement Solution

Alcatel-Lucent 7510 Media GatewayElement Manager (MGEM)

The Alcatel-Lucent 7510 MGEMoffers Simple Network ManagementProtocol (SNMP) controlledGraphical User Interface (GUI)management of allAlcatel-Lucent 7510 MGW units,supporting configuration, fault,performance, and securitymanagement.

1 Product Overview


1.3.1 General Features

Table 3 summarizes the Alcatel-Lucent 7510 MGW generalfeatures.

Table 3 Alcatel-Lucent 7510 MGW General Features

Features Description

Switching Capacity 10 Gbit/s TDM switch fabric

16 Gbit/s packet switch fabric

PSTN Interfaces Up to 32 OC-3/STM-1 [Synchronous OpticalNetwork (SONET)/Synchronous DigitalHierarchy (SDH) single-mode or multi-modewith 32*(1+1) redundancy)].

Up to 72 Digital Signal 3 (DS3) electricalinterfaces.

Up to 15x32 T1/E1 Plesiochronous DigitalHierarchy (PDH) interfaces.

NOTE: The interfaces are protected in 1+1redundancy even if N+1 redundancy isselected for module protection.

Packet Interfaces Up to 8 Gigabit Ethernet with additional8*(1+1) redundancy.

NOTE: The interfaces are protected in 1+1redundancy even if N+1 redundancy isselected for module protection.

Management Interfaces Fast Ethernet

1+1 redundancy

RS-232

Local and remote Command LineInterface (CLI)

SNMP agent

Telnet/Secure SHell (SSH)

IP Services IPv4/IPv6 dual stack for GigE–interface(media).

IPv4/IPv6 dual stack for Fast Ethernetinterface (MGC).

IPv4 for Fast Ethernet interface (OAM).

Domain Name Service (DNS) client service.

Network Time Protocol (NTP) v.4 support.

IP security (IPsec) using the EncapsulatingSecurity Protocol (ESP) with Tunnel Mode.

1 Product Overview



Signaling and Call Control H.248.1 Version 2

TISPAN NGN R1 (TGW profile)

ETSI TS 123 002 Mn profile (IMS-MGW)

ETSI ES 283 018 H.248 Ia profile version(BGW profile)

Stream Control TransmissionProtocol (SCTP)

SIGTRAN IUA

SIGTRAN M2UA

SIGTRAN M3UA

SPC (TDM-TDM) for signal linkconcentration (e.g. SS7)

SPC (TDM-IP) for signal link forwarding (e.g.user network signaling, e.g. RSU/CSNsignaling)

NOTE: To forward/concentrate signalinglinks, bundled in the same physical link asthe bearer channels, the Alcatel-Lucent 7510MGW provides the opportunity to configureSPCs per UI.

Clock Synchronization Internal Stratum 2 or 3 clock available

Any TDM Line Timing interface

External clock interfaces:

Building Integrated TimingSource (BITS)

Synchronization Supply Unit (SSU)

Timing Redundancy (1+1)

VLAN Support Virtual Local Area Network (VLAN) taggingbased on provisioned IP addresses or byH.248 control

H.248.11Overload

Robustness

H.248.gri

1 Product Overview



Reliability & Redundancy Event log, performance management faultmonitoring and alarm generation

CLI and GUI based SNMP management

1+1 / n+1 redundancy of each module,power, fan tray

Total availability >99,999 %

Quality of Service IP Type Of Service (TOS) packet markingfor voice, signaling, Operations,Administration and Maintenance (OAM), andother packets set by the User Interface (UI)or by H.248 control.

Interoperability Alcatel-Lucent softswitch, 3rd partysoftswitches, VoIP Gateways and VoIPterminals.

The physical specifications can be found in Appendix A

1.3.2 System Robustness and Stability

The Alcatel-Lucent 7510 MGW supports the following robustnessand stability feature.

The H.248.11 overload feature is based on a load thresholdwhich is set by using the relevant OAM command. The MGWload is measured in terms of “processor occupancy”.When theMGW load exceeds the threshold value, the MGW sends anoverload event to the softswitch. As a result, the softswitchshould reduce the load on the MGW.

1.3.3 Geographic Redundancy

The Alcatel-Lucent 7510 MGW supports geographic redundancyin a network.

To enable call server (MGCF, IBCF or SPDF) to synchronizecall-context related information via the MGW, the H.248.gripackage is supported. Therefore the call server , establishingnew call contexts, provides the MGW call-context records percontext. At failover the redundant call server obtains theserecords from MGW, required for further call processing, while thebearer-path is kept up.

1 Product Overview


1.3.4 Versatile Platform; Combining TGW, BGW and SGW

The 7510 MGW is capable to operate simultaneously as TGWwith TDM interfaces and BGW providing media and SIP firewallto secure packet-networks. Therefore the 7510 MGW can besplit into multiple virtual entities, each providing a separateinterface to a control function, either multiple MGCF, IBCF or amix of MGCF and IBCF.

Each virtual media gateway can be configured with an MGCspecific profile.

Furthermore the 7510 MGW supports a mixed TGW/BGW profiletogether with Alcatel–Lucent MGCF/IBCF that allows to addressTDM terminations and BGW realms within one context togenerate a cost and operation optimized configuration of TGWand BGW in one instance.

TDM resources can be assigned via user interface to thecorresponding MGCF.

Up to 512 IP realms with unique VLAN ID each, are supported toconnect packet networks (carriers) to the BGW. The IP realmscan be assigned individually to a virtual BGW entity controlled bythe corresponding IBCF. IP realms can be assigned to a uniqueGigabit Ethernet interface or can be distributed over multipleGigabit Ethernet interfaces. Each IP realm is characterized by amedia profile.

Each VBPIxGES PIM module hosting the Gigabit Ethernetinterface supports up to 1024 IP addresses.

Figure 2 shows the Multiple Virtual MGW Function:

1 Product Overview


Figure 2 Multiple Virtual MGW Function

1 Product Overview


1.3.5 Density and Scalability/Performance

The Alcatel-Lucent 7510 MGW chassis supports 20 slots andcan be configured with five types of application-specific modules:

The System Control Module (SCM) performs allmanagement functions and houses the SIP firewall.

The Switch Fabric Module (SFM) performs all routingfunctions (TDM and packet).

The Circuit Interface Module (CIM) includes OC-3/STM-1,DS3 or T1/E1 interfaces to receive or forward PSTN traffic.

The Packet Interface Module (PIM) includes a GigabitEthernet port to receive and forward packet traffic.

The Media Conversion Module (MCM) contains a pool ofDSPs that convert TDM traffic to packet, or packet traffic toTDM traffic. Additionally the MCM performs VoiceCompression and Echo Cancellation.

1 Product Overview


1.3.6 Performance

Table 4 lists the Alcatel-Lucent 7510 MGW performancecharacteristics.

Table 4 Alcatel-Lucent 7510 MGW Performance

Function Value

Mean Time Between Failures (MTBF) > 12 years

Context Attempts Per Second (CoAPS) perGateway [Call Hold Time (CHT) is 120seconds]

270

Maximum Busy Hour Call Attempts (BHCA)per Gateway

972,000

1.3.7 System Management and OAM Overview

Note Details of the system management and OAM toolsand features are available in chapter 8.

The Alcatel-Lucent 7510 MGW contains a comprehensive set ofsystem management and OAM tools and features, namely:

Chassis Management

Configuration Management

Fault Management

Diagnostic Test – BERT

System Logging and Debugging

Performance Management

Security Management

OAM Interfaces

Software Upgrade Management

2 Features and Services – Platform



This chapter describes features and services supported by theAlcatel-Lucent 7510 MGW platform. The following sections arepresented:

Introduction

Interfaces

Signaling Protocols Supported

Multi-Vendor Interoperability

Virtual Media Gateways

Voice Codecs

Voice-Band and Voice-Band Data Services

Inband Signaling Based Call Services

Quality of Service

Secured IP-Interfaces (OAM and MGC)

Tones and Announcements

Redundancy, Reliability, and Availability

IP Services and Resilience

Switching and Interworking Modes

Switched Connection Types



2.1 IntroductionThe Alcatel-Lucent 7510 MGW has been optimized to operate inthe Next Generation convergence switch market; it is installed onthe boundary between PSTN and packet networks to convertTDM voice, facsimile signals or Integrated Services DigitalNetwork (ISDN) data into packetized data traffic, which is thentransported over a packet network, and vice-versa. This Gatewayfunctions as a high-capacity Trunking Media Gateway to serviceVoIP or FoIP calls.

The Alcatel-Lucent 7510 MGW multiplexes DS0 channels intoOC-3/STM-1 or T1/E1 structured data transmission streams, andin the reverse transmission direction demultiplexes thesestreams into individual DS0 channels.

The gateway operates together with a softswitch (a MediaGateway Controller or BCG), and can employ theH.248.1 Version 2 and the SIGTRAN XUA signaling protocols toexchange control messages. The softswitch performs call controlto set up a call context, release a call context, and manageenhanced services.



2.2 InterfacesThe Alcatel-Lucent 7510 MGW supports the narrowband,broadband, and management interfaces shown in Figure 3.

1 Gigabit Ethernet

Craft Console

Softswitch

Alcatel-Lucent 7510 MGW

RS–232

OC–3/STM–1or

T1/E1PSTN Packet

OC–3PSTNSDHSONETSTM–1

: Optical Carrier 3: Public Switched Telephone Network: Synchronous Digital Hierarchy: Synchronous Optical Network: Synchronous Transport Module – Level 1

UPD_0173_fig20b_ed02

MGEM

MGAM

(using SNMP)

Fast EthernetH.248 SIP

1 Gigabit Ethernet

SIP

Media

SFW

SFW : SIP Firewall

Figure 3 Interfaces Supported

Table 5 lists the interfaces supported by the Alcatel-Lucent 7510MGW.



Table 5 Interfaces Supported

Interface Description

PSTN Channelized OC-3/STM-1 SONET/SDH, optical, fullduplex, single-mode and multi-mode

T1/E1 electrical – 100/120 Ω

DS3 electrical – BNC

RTP (VoIP) Gbit/s Ethernet, full duplex, 1+1 redundant

Signaling H.248: 10/100 Mbit/s Fast Ethernet, 1+1 redundant

SIGTRAN/SCTP: Gbit/s Ethernet, full duplex, optical,1+1 redundant

SIP (firewall): Gbit/s Ethernet, full duplex, electrical,1+1 redundant

Management Redundant 1+1 Fast Ethernet, 10/100 Mbit/s link usedfor management. Full duplex, auto-sensing port withunique Medium Access Control (MAC) address.

CLI interface via RS-232, RJ-45 type connector

Alarm Cut Off (ACO) switch on an alarm panel,external alarm interface.



2.3 Signaling Protocols SupportedThe following signaling types are supported:

Megaco

2.3.1 H.248.1 Version 2

The H.248.1 Version 2 protocol is an industry-standard mediagateway control protocols which address the relationshipbetween a media gateway and a softswitch (which is also calleda media gateway controller). The softswitch directs anAlcatel-Lucent 7510 MGW to dynamically establish and releasevoice and data (e.g., fax, modem transparent channel)connections over a packet network using the H.248.1 Version 2protocol.

Megaco FeaturesThe Alcatel-Lucent 7510 MGW implementation of the Megacov1.0 protocol includes Text Encoding and supports the use of theUser Datagram Protocol (UDP) or the Transmission ControlProtocol (TCP) as transport protocol.

TDM termination ID strings are configurable to guarantee thebest possible inter-operability with softswitches.

For detailed descriptions of the supported Megaco features, referto the document: “Protocol Implementation ConformanceStatement”.



2.4 Multi-Vendor InteroperabilityOpen standard-based solutions are the key to promoteinteroperability among vendors, and are crucial to serviceproviders deploying multivendor services. Alcatel-Lucent iscommitted to deliver open, standard-based solutions.

The Alcatel-Lucent 7510 MGW allows service providers to deployequipment from multiple vendors and reduce risks that stem fromrigid, single-service systems.

The Alcatel-Lucent 7510 MGW supports the industry standardprotocol Megaco and operates together with multivendorsoftswitch and gateway systems.

TGW application for PSTN Emulation Subsystem as TrunkingMGF, according to ”TISPAN NGN Release 1 (TGW profile)”identical to the IMS–MGW defined in TS 123 002 (Mn Interface),is located at the boundary between an IP core network and thePSTN/ISDN.

BGW application, also called Border Gateway Function, with IaInterface (ETSI ES283 018 H.248 Ia profile version 1), is locatedat the boundary between two IP core networks.



2.5 Virtual Media GatewaysThe Alcatel-Lucent 7510 MGW can be partitioned into multipleVirtual Media Gateways (VMGs) allowing multiple Controllers tointeract simultaneously with disjoint sets ofContexts/Terminations within the same MGW.

This MGC multi-homing capability provides functionality forgeographical redundancy in case of catastrophic outages at thecall control layer (1 MGW is controlled by 2 MGCs at differentlocations) as well as for efficiency (multiple MGC-entities canshare resources of an Alcatel-Lucent 7510 MGW).

The Alcatel-Lucent 7510 MGW allows the assignment ofresources to each VMG entity without service interruption.

The main configuration properties of VMGs in anAlcatel-Lucent 7510 MGW are the following:

The VMG implementation is according to ITU–T H.248.1chapter 11.1.

The maximum number of VMGs in a physical MGW is 128.

All the VMGs can be controlled by different MGCs.

The granularity per virtual media gateway set is E1.



2.6 Voice CodecsIn IP networks, where bandwidth efficiency and compatibility todifferent VoIP clients have top priority, the Alcatel-Lucent 7510MGW supports compressed and un-compressed voice codecscomplying to different requirements. Transcoding for each codec,supported by the 7510 MGW, is supported in scope of the BGWapplication.

The voice codecs supported by the Alcatel-Lucent 7510 MGWare listed and explained in the following sections.

G.711 Codec

G.729A/B Codec

G.723.1 Codec

G.726 Codec

AMR2 Codec

AMR-WB Codec

GSM-FR Codec

GSM-EFR Codec

GSM-HR Codec

G.728 Codec

EVRC Codec

2.6.1 G.711 Codec

The Alcatel-Lucent 7510 MGW supports the A-law and µ-lawvariants of the un-compressed codec G.711.

2.6.2 G.729A/B Codec

The G.729A/B codecs are becoming accepted standards forvoice compression. They use only 8Kbit/s of bandwidth and,therefore, offer significant bandwidth gain, while still producinghigh voice quality. These properties make G.729A/B the de factostandard for ,Wide Area Network (WAN) connections running IPtelephony.

The G.729A/B codecs use packet sizes of 10 to 60 ms in steps of10 ms.

The basic codec is the G.729A. The G.729B is the extendedversion comprising the following additional features:



VAD

Discontinuous Transmission (DTX)

CNG

2.6.3 G.723.1 Codec

The G.723.1 codec is used in networks that require maximumbandwidth efficiency. The supported packet sizes are 30 and60 ms. The following codec variants are used:

G.723.1 - ACELP (5.3 kbit/s)

G.723.1 - MPMLQ (6.3 kbit/s)

2.6.4 G.726 Codec

The G.726 codec has an extended inter-operability with VoIPequipment and is, therefore, widely used. The supported packetsizes are 10, 20 and 30 ms.

The G.726 codec is configurable in four different bitrate variantsas follows:

G.726 variant with 16 kbit/s




2.6.5 AMR2 Codec

Adaptive Multi-Rate (AMR) is an Audio data compressionscheme optimized for speech coding. AMR is adopted as thestandard speech codec in wireless networks.

The codec has eight bit rates:12.2, 10.2, 7.95, 7.40, 6.70, 5.90,5.15 and 4.75 kbit/s. The bitstream is based on frames whichcontain 160 samples and are 20 milliseconds long.

The Alcatel-Lucent 7510 MGW supports the RTP payload formatfor AMR encoded speech signals according to RFC3267.

2.6.6 AMR-WB (G.722.2) Codec

G.722.2 is an ITU–T standard wideband speech codec, alsoknown as AMR Wide Band (AMR–WB), offers even lower bit ratecompressions, as well as the ability to quickly adapt to varyingcompressions as the network topography mutates. In the latter



case, bandwidth is automatically conserved when networkcongestion is high. When congestion returns to a normal level, alower-compression, higher-quality bit rate is restored.

The codec provides the bit rates: 23.85, 23.05, 19.85, 18.25,15.85, 14.25, 12.65, 8.85 and 6.60 kbit/s.

G.722 and its variants sample audio data at a rate of 16 kHz,double that of traditional telephony interfaces, which results insuperior audio quality and clarity.

2.6.7 GSM-FR Codec

The Full Rate (FR) speech codec is defined by the ETSIspecification GSM 06.10. The GSM-FR speech codec uses theRegular Pulse Excitation – Long Term Prediction (RPE-LTP)algorithm and operates at 13 kbit/s.

2.6.8 GSM-EFR Codec

The Enhanced Full Rate (EFR) speech codec is defined by theETSI specification GSM 06.60. The GSM-EFR speech codecuses the Algebraic Code Excited Linear Prediction (ACELP)algorithm. Working at 12.2 kbit/s the EFR codec provides wirelikequality in any noise free and background noise conditions. TheEFR 12.2 kbit/s speech coding standard is compatible with thehighest AMR-mode.

2.6.9 GSM-HR Codec

The Half Rate (HR) speech codec is defined by the ETSIspecification GSM 06.20. The GSM-HR speech codec operatesat 5.6 kbit/s and thus requires half the bandwidth of the GSM-FRspeech codec.

2.6.10 G.728 Codec

The G.728 speech codec operates at 16 kbit/s and uses theLow–Delay Code Excited Linear Prediction (LD–CELP)algorithm.

2.6.11 EVRC Codec

EVRC(A) and EVRCB with header-free packet format accordingto RFC 4788.

Discontinuous Transmission;



EVRCB is an extension of EVRC(A) and provides a fourth datarate (1/4) in comparison to EVRC(A) to reduce average datarate.



2.7 Voice-Band and Voice-Band Data ServicesVoice-band and Voice-band data services supported by theAlcatel-Lucent 7510 MGW include the following:

Voice Activity Detection

Comfort Noise Generation

Packet Loss Concealment

Echo Cancellation

Adaptive Jitter Buffer

Fax Modem / T.38

Voice Band Data Mode

Media Inactivity Detection

Media Replication

2.7.1 Voice Activity Detection

The Voice Activity Detection (VAD) in the Alcatel-Lucent 7510MGW stops transmission of speech data when periods of silenceoccur during a conversation by monitoring the traffic stream atthe transmitting end (to detect audio silence based on audiopower falling below a certain threshold). During such periods, noaudio payload packets are sent, increasing transmissionefficiency.

Silence suppression can be enabled or disabled for eachindividual channel; it is often undesirable when the channel iscarrying facsimile or modem traffic.



VAD can be configured in four different modes:

offno VAD, i.e., packets are always sent.

transparentis an alternative to the “off” mode, but with an adaptivethreshold that will not rise above –62 dBm).

conservativeis the best compromise between voice quality and bandwithconsumption; the adaptive threshold will not rise above–42 dBm).

aggressiveThe aggressive mode is suitable for voice with verylow-level background noise: the adaptive threshold will notrise above –36 dBm).

2.7.2 Comfort Noise Generation

The Alcatel-Lucent 7510 MGW uses Comfort Noise Generationto supply a non-silent audio signal to a listener (person) duringintervals of silence suppression. This comfort noise masks theaudible clipping effects of activating and de-activating the voicechannel.

Comfort noise also avoids uncomfortable, total silence that wouldotherwise be experienced by a listener during periods of silencesuppression. Characteristics of the source silence are used togenerate the comfort noise, making the silence suppression lessnoticeable to a listener.

CNG can have the following settings:

offgenerates absolute silence.

whiteall frequencies have the same power level (flat spectrum).

pinkuses a spectrum with high frequency roll-off; more closelymatched to typical background noise conditions (compliantto ITU-T standard P.800).

spectralCNG according to G.711 – Appendix II (described in theITU-T G.711 specification).



2.7.3 Packet Loss Concealment

PLC is an algorithm used to minimize distortion in output voice,caused by packet loss or excessively late speech packetsaccording to:

G.711 – Appendix I.

Embedded PLC algorithm in all compressed codecs.

2.7.4 Echo Cancellation

An echo is commonly introduced at the four-wire (PSTN switch)to two-wire (local loop) hybrid interface in a circuit-switchednetwork due to impedance mismatch. The Alcatel-Lucent 7510MGW suppresses this echo before it propagates to the VoIPnetwork by implementing an integrated echo canceller thatcomplies with G.168. This echo canceller delivers up to 128milliseconds tail length of cancellation (see Table 6).

Table 6 Echo Cancellation Supported

Echo Cancellation Features Description

Standards Supported ITU G.168

Maximum Tail Length usingMCM board: VBMCMxE:

128 ms

Echo cancellation can be enabled or disabled for each individualchannel; it is desired on a channel when voice is beingtransmitted, but is often undesirable when a channel is carryingother types of information, like tones, facsimile, or modem traffic.

2.7.5 Adaptive Jitter Buffer

The Alcatel-Lucent 7510 MGW provides an adaptive jitter bufferhaving a configurable upper limit of 135 milliseconds. This jitterbuffer compensates for delay variations in packet transmissiontimes during a VoIP call, which causes jitter. The jitter bufferstores received packets for the configured amount of time, andafterward forwards them to the G.711 codec at a more stablerate. To achieve a minimum of delay, the buffer adapts to theactual network jitter.

T.38 withParameter

Negotiation



2.7.6 Fax Modem / T.38

The Alcatel-Lucent 7510 MGW supports different types of Faxtransmission through the IP network, namely:

Fax Relay over T.38

Fax Pass Through (i.e. transport of fax-signal in VBD-mode)

Fax Relay over T.38This is the recommended version for efficient, economic andreliable Fax transport and includes additional services.

Fax relay over T.38 using UDP/IP

Support of transferred Training Check Frame (TCF)

Support of redundant UDP error correction

support of all rates of V.17, V.27 and V.29

Bandwidth limitation by setting maximum bit rate for Faxtransfer

Support of up to 20% port capacity for simultaneous Faxrelays

This option provides inter-operability with existing VoIP networks,independent of the used protocol (H.323, SIP, H.248, etc.). Oninterworking with an Alcatel-Lucent softswitch, full compatibility toT.38 is offered. The relevant parameters can be exchanged viathe signaling protocol.

Fax Pass ThroughFax pass through is used when endpoints are not T.38compatible. The Fax transmission with Fax pass through isbased on G.711.

On recognition of Fax events, the Alcatel-Lucent 7510 MGW willswitch to Voice Band Data (VBD) mode to provide a completelytransparent transport layer for Fax transmission. About VBDmode see section 2.7.7.

2.7.7 Voice Band Data Mode

The Alcatel-Lucent 7510 MGW supports the VBD-mode formodem calls according to the V.152 standard. On recognition ofmodem tones, a switch to VBD-mode is performed to speed upthe support for modem calls.

V.32ext

Text-Phone

Robust VBD



Additionally, the Alcatel-Lucent 7510 MGW supports tonedetection to switch to VBD-mode of the following modemstandards: V.21, V.22(bis), V.23, V.32, and V.34.

The Alcatel-Lucent 7510 MGW supports the V.32ext specificmodem detection and, the procedure to switch autonomously toVBD-mode, which guarantees the data transport.

The Alcatel-Lucent 7510 MGW supports“Text-phone-pass-through”, i.e., the text-phone protocol. Thisprotocol allows a mixed mode communication, i.e., low bitratetext messages can be forwarded during a voice call.

VBD stimuli criteria for the text telephony applications areaccording to V.152.

Optionally the robust VBD mode, according RFC2198, can beenabled, sending redundant packets to prevent distortion ofmodem/fax transmission, caused by packet loss.

2.7.8 Media Inactivity Detection

The Media Inactivity Timer enables the Alcatel-Lucent 7510MGW to monitor VoIP calls. If no RTCP packets are receivedwithin a configurable time period a notification is sent towards theMGC. This allows call control to disconnect media sessions thatwere not properly released on the part of signaling.

2.7.9 Media Replication

To supervise each bearer session, processed by theAlcatel-Lucent 7510 MGW, it provides media replication for voicemedia traffic towards mediation device at packet networkcontrolled by MGC using topology and stream descriptor.

The media replication can be used to implement special serviceswhich could be requested by local law.

Digit CollectionService

Digit Map StateMachine



2.8 Inband Signaling Based Call Services – PlatformInband signaling based call services supported by theAlcatel-Lucent 7510 MGW, in TGW application as well as forBGW application in media aware mode, include the following:

DTMF Packet Relay

Inband Signaling Processing

Digitmap

2.8.1 DTMF Packet Relay

The Alcatel-Lucent 7510 MGW supports the transmission ofDTMF tones to forward Named Telephone Events (NTEs)according to the RFC2833 and RFC4733 standard. By defaultthe payload type is negotiated dynamically Optionally, thepayload type can be configured to ensure compatibility withH.323 VoIP networks.

In BGW application the Alcatel-Lucent 7510 MGW maytranscode DTMF digits received inband in IP-realm A toNTE-messages in IP-realm B. By media profile the mediacapabilities per IP-realm are configurable.

2.8.2 Inband Signaling Processing

The following Inband Signaling Processing features are availablewith the Alcatel-Lucent 7510 MGW:

Digit Collection Service

Digit Map State Machine

Digit Outpulsing Service

The Alcatel-Lucent 7510 MGW collects DTMF and MultiFrequency (MF) tones. These tones are analyzed and stored asdigits. Notification about the received digits to the softswitch isrealized by a Digitmap-state machine.

The Alcatel-Lucent 7510 MGW uses a Digitmap-state machineto realize extended digit collection services. The followingextended digit collection services are available:

Interaction on each detected digit (no post dial delays)

Credit/calling card calls

Triggering the re-origination of special functions

Digit Outpulsing



The Digitmap-state machine can be adapted to customerrequirements by simply adapting the eXtended MarkupLanguage (XML)-style configuration file.

With each call, the digitmap and its relevant parameters can beprovided. These parameters are:

Maximum amount of digits

First digit timer

Fast inter-digit timer

Remaining inter-digit timer

International inter-digit timer

Up to 48 digit can be buffered by the Alcatel-Lucent 7510 MGW,without receiving a valid digitmap from the softswitch.

The Digitmap-state machine can perform the following actions:

Reset dialing

Collect digits

Ignore digits

Notification of invalid actions

Activate/reset timer

Switch Digitmap-state machine

Additionally to the detection, storing and analyzing of digits, theAlcatel-Lucent 7510 MGW also supports the outpulsing of digits.

2.8.3 Digitmap

A Digit Map is a dialing plan resident in the Media Gateway andused to detect and report digit events received on a termination.A Digit Map and its name is loaded into the Media Gateway byan MGC. Digit Maps are implemented according to the H.248standard, i.e. maximum 195 bytes per termination.



2.9 Quality of ServiceDue to the delay-sensitive nature of packet voicecommunications, service providers require well engineered,end-to-end IP networks to successfully deploy high quality VoIPservices. Service providers can use three fundamentaltechniques to support QoS across their IP networks:

Providing excess network bandwidth Static and dynamic bandwidth reservation Traffic prioritization.

Of these three techniques, traffic prioritization is the mosteconomical and powerful way to support differentiated services.Fine-tuning IP networks to adequately support QoS involvesDiffServ and IP ToS features, which are used to mark packets toachieve prioritization. Traffic prioritization features are widelydeployed in core backbone routers and switches; they can worktogether with media gateways that support the same techniques.

The Alcatel-Lucent 7510 MGW is able to prioritize different typesof traffic, depending on the priority of a given traffic stream; ittags voice packets with a priority value that backbone switchesand routers then use to prioritize traffic. Once a packet has beentagged with a priority value, subsequent switches and routersalong the transmission path use the tag to identify traffic that is toreceive preferential treatment.

There are two standards enabling end-to-end traffic prioritizationacross IP networks, the IP ToS, and DiffServ; the Alcatel-Lucent7510 MGW supports both of them. For both IP ToS and DiffServ,routing decisions in the IP network are based on the same sixbits in the IP v.4 header (see Figure 4). Values of these bits arein accordance with the IP ToS or DiffServ core networkarchitecture.

With the H.248.52 package (ex H.248.QoS) a property to controlthe setting of the DiffServ field of the IP header, as defined inIETF RFC 2474 is available. The MGC can set the quality ofservice for egress media flows without having to provision theMGW with a default Differentiated Services Code Point (DSCP)value.

This enables individual marking per IP termination to specify theproper QoS level per IP realm and media stream.



0193_qos_ed01

Type of Service Field RFC 1349 Defines:1000 – Minimize Dely0100 – Maximize Throughput0010 – Maximize Reliability0001 – Minimize Monetary Cost0000 – Normal Service

IPv4 TOS Byte

IP TOS

IPv4 Packet Header

0 2 3 6 7

Precedence MBZ

TOS

Recommended DSCP: RFC 2597001010 (low), 001100 (medium), 001110 (high) – AF Class 1010010 (low), 010100 (medium), 010110 (high) – AF Class 2011010 (low), 011100 (medium), 011110 (high) – AF Class 3100010 (low), 100100 (medium), 100110 (high) – AF Class 4

DS Byte

DiffServ

IPv4 Packet Header

0 5 6 7not

usedDSCP

DiffServDSDSCPIPRFCTOS

: Differentiated Service: DiffServ: Differentiated Services Codepoints: Internet Protocol: Request for Comments: Typ of Service

Figure 4 IP Header for ToS and DiffServ

The Alcatel-Lucent 7510 MGW simply marks the packetsaccordingly and sends them to the core network (IP Backbone(see Figure 5). The core network routers must be able to identifyToS-packets or DiffServ-packets, as well as be able to associatepriorities with service levels, to forward these voice packetsacross the core network using packet prioritization andcongestion control techniques.



ClassificationMarkingTraffic PolicingScheduling

ClassificationMarkingTraffic PolicingScheduling

BackboneRouters

Per Hop BehaviourPrecedence queuingWeighted schedulingPriority dropping

7510Media Gateway

7510Media Gateway

0208_forvoipack_ed01

Figure 5 Forwarding Voice Packets using Backbone Routers

The following list summarizes the IP ToS and DiffServ typessupported by the Alcatel-Lucent 7510 MGW:

User-configurable IP header ToS/DiffServ bits for voicepackets

User-configurable IP header ToS/DiffServ bits for signalingpackets

User-configurable IP header ToS/DiffServ bits for OAM&P

User-configurable IP header ToS/DiffServ bits for otherpackets.

IPsec Features



2.10 Secured IP-Interfaces (OAM and MGC) IPsec

Telnet/SSH

2.10.1 IPsecThe IETF has developed a method of ensuring secured datatransmission in packet networks that use the IP protocol, calledIPsec.

IPsec uses powerful new encryption technologies to add securityservices to the IP layer of data transmission, allowing networkoperators to secure communications in their network.

IPsec is compatible with the existing IP standard, IP v.4, which isplanned to become mandatory in the succeeding IP standard,IP v.6.

The IPsec implementation in the Alcatel-Lucent 7510 MGWcontains the following features:

The encryption mechanism is Encapsulating SecurityPayload (ESP). The following encryption/authenticationmethods are supported:

DES (maximum 56 bit)

3DES (maximum 168 bit)

MD5 (maximum 20 bit)

SHA1 (maximum 16 bit)

NULL

Tunnel Mode

Manual Key Exchange

Supported IPsec interfaces are:

Signaling Interface (see Table 5)

Management Interface (see Table 5)

2.10.2 Telnet/SSH

A secured Telnet session can be established between a remoteclient and the Alcatel-Lucent 7510 MGW using SecureSHell (SSH). It uses public-key cryptography, to authenticate theremote computer, and data encryption .

SSH Features



The SSH implementation in the Alcatel-Lucent 7510 MGWcontains the following features:

The following encryption/authentication methods aresupported:

DES

3DES

AES

MD5

SHA-1

Key exchange methods:

DH group1

DH group14

Public key algorithms:

RSA

DSS

Supported SSH interfaces are:

Management Interface (see Table 5)

Supported Tones



2.11 Tones and AnnouncementsThe Alcatel-Lucent 7510 MGW offers tones and announcementsgeneration.

The following DTMF/MFR1/MFR2F tones are supported on TDMor RTP terminations:

Basic call progress tones

Dial tone

Ringing tone

Busy tone

Congestion tone

Special info tone

Payphone recognition tone

Call waiting tone

Caller waiting tone

Expanded call progress tones

Comfort tone

Vacant number tone

Special condition dial tone

Basic services tones

Recall dial tone

Confirmation tone

Held tone

Expanded services tones

Call transfer dial tone

Call forward tone

Intrusion tones

Intrusion tone

Continuity test tones

Continuity check tone (2010 Hz)

Continuity check response tone

Note The corresponding Megaco package and signal ID toplay the tones are supported by the Alcatel-Lucent7510 MGW.

SupportedAnnouncement

Features



The following announcement features are supported:

Announcements can be played on all TDM terminationssimultaneously.

Announcements and tones can be enabled at RTP or TDMterminations

Generic Announcement Package (H.248.7)

“SCC” dial tone (tone that has to be played out as anannouncement)

Multiple recorded announcements

Calling card confirmation tone (tone that has to be playedout as an announcement)

Total Announcements (48 Announcements with varied lengthof 4s – 8s, total 360 sec

Announcements Repeat Count (number of times to play theannouncement; value “0” means play the announcementcontinuously; default = 0)

Note The Alcatel-Lucent 7510 MGW can start/restart theannouncements at any phase of the call set-up.



2.12 Redundancy, Reliability, and AvailabilityAs NGN technologies progress toward offering expansionalternatives to PSTN networks, softswitches and media gatewaysmust guarantee the highest level of reliability and availability tomeet the most stringent exchange deployment requirements.The Alcatel-Lucent 7510 MGW has been designed with severalredundant and fault tolerance features to provide the highestlevel of availability and reliability.

An Alcatel-Lucent 7510 MGW supports three hot-swappable fantrays and as many as 20 modules having 1+1 or N+1redundancy. The unit is designed to support continuousoperations and have no single point of failure.

Table 7 summarizes redundant components in an Alcatel-Lucent7510 MGW.

Table 7 Hardware Redundancy

Hardware Redundancy (active + standby)

Fan tray Three fan trays, load-sharing, only two required foroperation.

Media ConversionModule

Pooled architecture scheme in 1+1 or n+1 redundantconfigurations.

Circuit InterfaceModule

SDH CIM: 1+1 or n+1

PDH CIM (E1/T1): n+1

PDH CIM (DS3): 1+1 or n+1

Packet InterfaceModule

1+1 or n+1

System ControlModule

1+1

Switch FabricModule

1+1

Power A+B power feed, 1+1

Timing Two sources of external SSU or BITS network timingsignals and line timing source

Signaling Port Two Fast Ethernet ports, 1+1.

The following operational processes have been optimized toprevent adverse effects to service availability:



Software upgrades Fault management Route establishment Service expansion.

The Alcatel-Lucent 7510 MGW chassis was designed to supporthot-swappable, redundant power sources and cooling devices.All control modules and TDM and packet interfaces, as well asvoice processing modules, are fully redundant andhot-swappable. This allows each module to be removed andreplaced during operation (without shutting down the gateway).

The Alcatel-Lucent 7510 MGW also offers fully redundantsoftware applying to system control, call processing, signaling,and routing. The Alcatel-Lucent 7510 MGW Fault TolerantApplication Manager (FTAM) software detects internal andexternal outages, and restores services automatically whenpossible.

The Alcatel-Lucent 7510 MGW is designed for a 99.999 %availability.

The following sections describe how each module in theAlcatel-Lucent 7510 MGW operates in a fault-tolerant mode.

2.12.1 System Control Module and Switch Fabric Module

The System Control Module and the Switch Fabric Moduleredundancy feature applying to the Alcatel-Lucent 7510 MGWallows a standby System Control Module to provide backup, ifthe active System Control Module fails. It also allows systemsoftware upgrades to be performed without incurring downtime.

The System Control Module copies all configuration informationstored in the active System Control Module into the standbySystem Control Module. In the event of active System ControlModule failure, the standby System Control Module reads itsconfiguration file, re-starts the appropriate routing protocol, andrebuilds the routing tables and Address ResolutionProtocol (ARP) entries. The standby System Control Moduleassumes communication with the softswitch without effecting thestate of current calls.

The System Control Module also houses the SIP Firewall (SFW),located on an Advanced Mezzanine Card (AMC). Purpose of thisSFW is to protect IBCF from SIP signaling attacks by filtering theunprotected SIP traffic on the interface to a peer network, beforeit will pass to the IBCF. This SFW is also redundant like the

EquipmentProtection

Switching – EPS

Link ProtectionSwitching – LPS



System Control Module, and also provides link protection for thetrusted and the untrusted transmission links.

The packet switch fabric (c-PSF) on each System ControlModule connects to all modules in the system using tworedundant 10/100 Mbit/s Ethernet MAC controllers. This providesredundant backplane connectivity to the rest of the system. Allmodules can receive backplane traffic on either bus. If a faultoccurs on the packet switching fabric of the active SystemControl Module, the Alcatel-Lucent 7510 MGW immediatelyswitches all traffic to the packet switching fabric on the standbySystem Control Module.

2.12.2 Packet Interface Module

If an active Packet Interface Module fails, the System ControlModule designates the standby Packet Interface Module as theactive module, and informs all other modules of the statechanges made. An ARP broadcast response is sent using thenewly enabled Packet Interface Module ports to ensure thatsubsequent data sent to the corresponding IP interface isdirected toward its new new port.

The System Control Module can also switch over the functions ofone Packet Interface Module to another Packet Interface Modulewithout disrupting traffic; this is done for maintenance purposes.Each link or channel state is monitored individually. If a link orchannel failure is detected and reported, the FTAM informs allother modules. When a ’link down’ message is received, eachmodule clears address database and ARP entries pointing to thefailed channel, ensuring that the information in the forwardingtables is current and correct.

PIM protection groups can be configured in an Alcatel-Lucent7510 MGW, when two Media Interface Modules (MIMs) areinstalled in adjacent slots, both being connected to one activeand one standby PIM of an active and standby PIM pair. In thissituation, when the active PIM experiences a fault, an EPS in theactive MIM automatically switches over to the standby PIM. Thisaction is known as Equipment Protection Switching (EPS).

Similarly, if a data line connected to a PIM experiences a faultcondition, the on-board Central Processing Unit (CPU) in the PIMcontrols a Link Protection Switch (also part of the PIM) toperform a line change from the defective line to an alternate line,ensuring continued data transmission. This action is known asLink Protection Switching.

EquipmentProtection

Switching – EPS

AutomaticProtection

Switching – APS

Multiplex SectionProtection



In addition the 7510 MGW supports Bi–directional ForwardingDetection as described in section 2.13.

2.12.3 Circuit Interface Module

If an active Circuit Interface Module fails, the System ControlModule designates the standby Circuit Interface Module as theactive module, and informs all other modules. The newlyactivated Circuit Interface Module sends a signal through theTDM fabric to indicate its change of status. When the MediaConversion Modules detect this TDM signal, they switch over tothe new TDM fabric. Since all TDM connections are identicallyset on the newly activated Circuit Interface Module, this transitionhas no impact on current calls.

CIM protection groups can be configured in an Alcatel-Lucent7510 MGW, when two MIMs are installed in adjacent slots, bothbeing connected to one active and one standby CIM of an activeand standby CIM pair. In this situation, when the active CIMexperiences a fault, an Equipment Protection Switch in the activeMIM automatically switches over to the standby CIM. This actionis known as Equipment Protection Switching.

If a data line connected to a CIM experiences a fault condition,the on-board CPU in the CIM controls an Automatic ProtectionSwitch to perform a line change from the defective line to analternate line, ensuring continued data transmission. This actionis known as Automatic Protection Switching (APS) in SONETbased networks.

The MGW 7510 supports APS 1+1 for bidirectional non–revertiveand unidirectional non–revertive mode.

As part of an SDH network the 7510 MGW supports MultiplexSection Protection (MSP). The MSP link protects the connectionto an other network similar to an APS protection.

2.12.4 Media Conversion Module

By default, all Media Conversion Module operate in an N+1redundant mode. All control messages to the Voice managerserver in the MCM are forwarded transparently via thesynchronization manager. The synchronization manager isresponsible for distributing the data of all registered calls in theactive MCMs to the standby MCM. The standby MCM is always



synchronized with the data of all active MCMs and ready totakeover the function of one of these modules.

The Alcatel-Lucent 7510 MGW can also assign thenon-redundant mode to MCM modules.

If an active Media Conversion Module fails, the System ControlModule designates the standby Media Conversion Module as theactive module, and informs all other modules of these changes.The Circuit Interface Module immediately swaps the TDM datastreams connected to the failed Media Conversion Module to thenewly activated Media Conversion Module. The Packet InterfaceModule and the System Control Module update their forwardingtables, to allow all entries in their tables to point to the correctDSP in the newly activated Media Conversion Module.

2.12.5 Signaling

The Megaco or SIGTRAN signaling links between a softswitchand an Alcatel-Lucent 7510 MGW are fully redundant. TheAlcatel-Lucent 7510 MGW terminates the Megaco or SIGTRANsignaling links on the 10/100 Mbit/s Ethernet ports of a pair offully redundant System Control Modules. From the 10/100 Mbit/sEthernet port of the System Control Module, each Megaco orSIGTRAN signaling connection can be transmitted from theAlcatel-Lucent 7510 MGW over the IP network using differentphysical routes, and terminate on two physically redundantinterfaces in the softswitch. This configuration avoids any singlepoint of failure for Megaco or SIGTRAN signaling traffic. TheAlcatel-Lucent 7510 MGW also provides a ’keep alive’ functionserving the signaling links to ensure correct communication.

The control software in the Alcatel-Lucent 7510 MGW maintainsa database of all call termination IDs and call contexts, and canmanage queues to process all pending messages to be sent tothe softswitch. The control software maintains this database andthe corresponding message queues on the standby SystemControl Module. If the active System Control Module fails, theAlcatel-Lucent 7510 MGW automatically switches over to thestandby System Control Module, which then automaticallycommunicates with the softswitch without effecting the states ofactive calls.

2.12.6 Power

Each module in an Alcatel-Lucent 7510 MGW uses one of twoparallel power sources that are connected to the backplane of



the chassis to provide power redundancy. The two powersources are either both –48 V, or both –60V DC. If the activepower source fails, the system automatically switches to thestandby power source.

The Alcatel-Lucent 7510 MGW hardware manages power sourcestatus, low voltage, and corrective action if a power source fails.The voltage available to all modules is also monitored; if thevoltage provided to a board falls below the level required forreliable operation, the affected board executes a fault-initiatedhard reset.

2.12.7 Cooling

There are three fan trays in an Alcatel-Lucent 7510 MGW and allare active.

Each fan tray contains three fans.

Fan status and overall chassis temperature are continuouslymonitored. The chassis management software issues commandsto the fan trays to adjust fan speeds. If the temperature isdetermined to be above the limit allowed, the fan speeds areincreased to reduce the temperature.

The system also sends appropriate traps to the networkmanagement software when a change in fan status occurs.

During maintenance, the Alcatel-Lucent 7510 MGW can beoperated with two fan trays.

Network TimeProtocol – NTP



2.13 IP Services and ResilienceThe Alcatel-Lucent 7510 MGW features comprehensive IProuting using a complete IPv4 protocol set.

IPv6 support is restricted on media plane.

In addition, the Alcatel-Lucent 7510 MGW supports NTP tosynchronize its system time with various network time servers inaccordance with RFC 1305 (see below).

The Alcatel-Lucent 7510 MGW supports NTP version 4 inaccordance with RFC 2030, to synchronize the localAlcatel-Lucent 7510 MGW system time with one or more networktime servers. This provides a reliable and precise timingreference for all logging services. The Alcatel-Lucent 7510 MGWperiodically sends NTP messages to the time server and adjustsits local system time with the time stamp embedded in the replymessages.

The Daylight Saving Time (DST)switchover/switchback isconfigurable per calendar function for the next years.

2.13.1 Gratuitous ARP

Gratuitous ARP is a layer-2 redundancy mechanism for IP links.

In case of a link or I/O-board failure, the old IP address ispreserved, but a new / different MAC address is assigned to theredundant Ethernet-interface.

In practice this means that the PIM will send out, via the newIP-interface (i.e., via the new active link), a gratuitousARP-request (according to the IP mobility RFC2002), advertisingthe new MAC address in conjunction with the old IP address.

Based on the new MAC address information, included in theARP-request, all layer 3 (IP) terminating network elements in thesame IP-subnet have to update their ARP-table. The ARP-tableupdate function, in the terminating network elements, has aself-learning capability, documenting a new route (new HW port,new MAC@), leading to the fail-over MIM.



2.13.2 Bi-directional Forwarding Detection – BFD

Bi–directional Forwarding Detection (BFD) – Version 1 is alow-overhead, short-duration detection of failures in the pathbetween two systems.

If a system stops receiving BFD messages for a long enoughperiod (based on the configuration), it is assumed that a failurealong the path has occurred and the associated application isnotified.

BFD provides on interoperability with a BFD capable router (e.g.7750) comprehensive IP network resilience.

Typically two BFD sessions are configured per IP-interface tosupervise the availability of two redundant packet-edge routers. Ifone session is failing, the packet-routing is forwarded to analternative packet-edge router. If both BFD sessions fail, anIP-interface takeover is initiated.

Towards IP core-network the packet-edge router advertisesavailability of the MGW dependent on the BFD session state.

The BFD feature is available on the Gigabit Ethernet interfaces(VoIP) and the Fast Ethernet interface (Signaling).



2.14 Switching and Interworking ModesThe Alcatel-Lucent 7510 MGW features the following switchingand interworking modes:

TDM To/From Real-time Transport Protocol (RTP)

TDM Hairpinning

TDM Hairpinning Without DSP Involvement

TDM Hairpinning With DSP Involvement

TDM Hairpinning With DSP and PIM Involvement

Border Gateway

BGW Without DSP Involvement

BGW With DSP Involvement

The following sections present the Alcatel-Lucent 7510 MGWswitching and interworking modes.

2.14.1 TDM To/From RTP

The interworking mode: TDM to/from RTP is a standardAlcatel-Lucent 7510 MGW feature, see Figure 6.

SFMCIM PIM

MCM

DSP

MCM

DSP

Figure 6 TDM To/From RTP

Definition of TDMHairpinning

TDM HairpinningWithout DSPInvolvement



2.14.2 TDM Hairpinning

TDM Hairpinning is a scenario whereby a call is made betweentwo TDM endpoints on a single Media Gateway. The mediacomes in on one TDM channel and goes out on another TDMchannel through the use of an internal loop in the MediaGateway.

The Alcatel-Lucent 7510 MGW features three TDM-hairpinningmodes, namely:

TDM Hairpinning Without DSP Involvement

TDM Hairpinning With DSP Involvement

TDM Hairpinning With DSP and PIM Involvement

The switching mode: TDM-hairpinning without DSP involvementcreates a loop in the SFM using the native TDM switch withoutvoice quality degradation, see Figure 7.

SFMCIM PIM

MCM

DSP

MCM

Figure 7 TDM Hairpinning Without DSP Involvement

TDM HairpinningWith DSP

Involvement



The interworking mode: TDM-hairpinning with DSP involvementcreates a loop in the SFM using the native packet switch withoutvoice quality degradation. Before and after the switching, themedia is converted using a DSP in the MCM, see Figure 8.

This interworking mode is generally used in case of TDM-basedvoice processing, e.g., echo cancelling, gain control, etc.

SFMCIM PIM

MCM

DSP

MCM

DSP

Figure 8 TDM Hairpinning With DSP Involvement

TDM HairpinningWith DSP and

PIM Involvement

Definition ofBorder Gateway



The interworking mode: TDM-hairpinning with DSP and PIMinvolvement applies in the cases where two different H.248contexts are two call legs of the same call (the MGC is not awarethat these two “calls” are in fact one and the same call). The twocall legs are joined in the PIM, see Figure 9.

This interworking mode is required with supplementary serviceslike, e.g., call forwarding or call transfer.

SFMCIM PIM

MCM

DSP

MCM

DSP

Figure 9 TDM Hairpinning With DSP and PIM Involvement

2.14.3 Border Gateway

Border Gateway is a function whereby a call is made betweentwo RTP session endpoints located typically in different IP realms(packet Interfaces in different packet networks) on a single MediaGateway. The media comes in on one RTP/RTCP session andgoes out on another RTP/RTCP session through the use of aninternal loop in the Media Gateway.

All other media streams, not negotiated via signaling interface,are rejected and the BGW acts as dynamic firewall.

The Alcatel-Lucent 7510 MGW features two stream modes withinBGW application, namely:

MediaAgnostic (w/o DSP involvement)

MediaAware (with DSP involvement)

BGW WithoutDSP Involvement



Both stream modes are supported within a virtual BGW instance.Even in one H.248 call context a mixture of stream modes issupported.

The media stream mode MediaAgnostic (without DSPinvolvement) is typically used for pure pinholing with NetworkAddress Translation (NAT), see Figure 10.

If the RTP/RTCP sessions are on different PIMs, the IP-packetsare switched via SFM. This is not needed if both sessions end onthe same PIM.

SFMCIM PIM

MCM

DSP

MCM

DSP

PIM

Figure 10 BGW Without DSP Involvement

BGW With DSPInvolvement



The media stream mode MediaAware (with DSP involvement) isused with media processing functions like voice transcoding(codec conversion), service transcoding (FAX/DTMF to VBD),traffic policing and enhanced media statistics.

A packet to packet loop is created in the SFM switch andincludes media processing using a DSP, see Figure 11.

SFMCIM PIM

MCM

DSP

MCM

DSP

Figure 11 BGW With DSP Involvement

DynamicStandard

Connections

Dynamic TestConnections

Semi PermanentConnections



2.15 Switched Connection TypesThe Alcatel-Lucent 7510 MGW features the following switchedconnection types:

A dynamic connection is the Alcatel-Lucent 7510 MGW standardconnection type. Dynamic connections are established usingH.248 connection control.

Dynamic test connections include:

Continuity tests

Loopback tests

SPCs have the following properties:

They are established using OAM Commands.

A self-healing mechanism restores an SPC in case of loss ofconnection.

An alarm is generated in case the link goes down.

3 Features and Services – TGW Application



This chapter describes features and services which apply to theAlcatel-Lucent 7510 Trunking Gateway application. The followingsections are presented:

Circuit–Mode Data Services

Inband Signaling Based Call Services – TGW Application

Semi-Permanent Connections



3.1 Circuit–Mode Data ServicesISDN monorate bearer services (e.g., ITU–T I.231.1, I.231.3) arebased on 1x64 kbit/s bearer channels, whereas ISDN multiratebearer service are defined by Nx64 kbit/s structures.

Circuit mode data services supported by the Alcatel-Lucent 7510MGW include the following:

Monorate 64 kbit/s Unrestricted Digital Information

Multirate Nx64K Wide-Band Data Services

3.1.1 Monorate 64k Unrestricted Digital Information

In digital, circuit-switched networks, bearer capabilities arerequested by ISDN call control signaling during the call set-upphase. This information is passed by the softswitch in thegateway control protocol (Megaco/H.248) to the gateway.Through this trigger, the Alcatel-Lucent 7510 MGW is capable ofswitching to ”Clear mode” (on IP side, according IETF RFC4040) in order to transmit a bearer with 64 kbit/s UDI (e.g., videotelephony, G.722 wideband telephony, or digital datatransmission).

3.1.2 Multirate Nx64k Wide-Band Data Services

ISDN multirate bearer services are emulated by theAlcatel-Lucent 7510 MGW in the IP transport domain in general,using a Circuit Emulation Service over IP (CESoIP) approach.The Alcatel-Lucent 7510 MGW principally supports CESoIP onan extension of RTP Clearmode (IETF RFC 4040).

ISDN multirate bearer service traffic is encapsulated on a Nx64basis in the RTP payload. Control of this modes of operation areidentical to monorate bearer services.

ISDN multirate bearer services are used e.g., for X.25 dataservices, leased line services, PBX-to-PBX interconnection,video conferencing systems based on ITU–T H.320.



The following ISDN multirate bearer services are defined:

N = 2 (ITU-T I.231.5)

N = 6 (ITU-T I.231.6 384 kbit/s unrestricted,8 kHz structured)

N = 24 (ITU-T I.231.x 1536 kbit/s unrestricted,8 kHz structured)

N = 30 (ITU-T I.231.x 1920 kbit/s unrestricted,8 kHz structured)

Note Other values of N are not excluded e.g., for use in“fractional E1/T1” based network applications.

3.1.3 Digital Circuit Multiplication Equipment – DCME

Digital Circuit Multiplication Equipment (DCME) is often used infront of International Switching Centers (ISCs) to enhanceefficiency on long distance TDM links.

The Alcatel-Lucent 7510 MGW can convert these ISCs to NGNusing the Alcatel-Lucent 7510 MGW as InternationalGateway (IGW).

The Alcatel-Lucent 7510 MGW can interface with DCMEaccording to Q.50A or Q.50B and supports the H.248.42 DCMEpackage for communication with the corresponding MGC.



3.2 Inband Signaling Based Call Services – TGWApplication

Inband signaling based call services supported by theAlcatel-Lucent 7510 MGW, in TGW application, include thefollowing:

TDM to TDM Hairpinning with Media Processing

FSK

3.2.1 TDM to TDM Hairpinning with Media Processing

In addition to native TDM hairpinning, the Alcatel-Lucent 7510MGW offers media processing for future applications. For thispurpose, a DSP is involved. Media processing can beenabled/disabled by the softswitch on a per call basis, using theH.248 protocol.

The following media processing features with TDM to TDMhairpinning are available:

Echo Cancellation

Tone Detection

A-law/µ-law conversion (planned for next release)

3.2.2 FSK

For the centralized access gateway application theAlcatel-Lucent 7510 MGW supports Frequency ShiftKeying (FSK) to realize the Calling Line IdentificationPresentation (CLIP) service for analog lines connected viaanalog line concentrator.

The MGC provides CLIP relevant data via the H.248.23 packageto the 7510 MGW.



3.3 Semi-Permanent ConnectionsThe Alcatel-Lucent 7510 MGW supports various types ofsemi-permanent connections:

SPC without Media Processing

SPC without Media Processing with DCME

SPC with Media Processing

3.3.1 SPC without Media Processing

An SPC without media processing connects either 2 TDM-ports,or one RTP-port and a TDM-port. This type of SPC could beused to concentrate signaling links associated to bearer linkswithin a PCM link and forward to an signaling end-point.

An SPC without media processing can connect two entire PCMlinks (E1/T1) as well.

3.3.2 SPC without Media Processing with DCME

An SPC without media processing with DCME connects 2TDM-ports and supports additionally the DCME protocol toextract signaling links out of PCM links connected to DCMEequipment.

3.3.3 SPC with Media Processing

An SPC with media processing connects either 2 TDM-ports, orone RTP-port and a TDM-port, and involves a DSP for mediaprocessing. This type of SPC is usually used for long-term bearerconnections with echo cancellation or compression.

Note The Alcatel-Lucent 7510 MGW supports maximum4096 SPCs.

4 Features and Services – SGW Application



This chapter describes features and services which apply to theAlcatel-Lucent 7510 Signaling Gateway application. Thefollowing sections are presented:

Embedded Signaling Gateway

SIGTRAN IUA

SIGTRAN M2UA

Entry M2UACapacity on SFM

Large M2UACapacity on PIM2



4.1 Embedded Signaling GatewayWithin NGN VoIP Networks, when signaling information istransferred within a packet switched network, a signalinggateway function is required to transform the TDM-signals usedin a PSTN to signals used in the packet switched network, andvice-versa. In the Alcatel-Lucent 7510 MGW, the SIGTRANprotocol family is used to perform this required embeddedsignaling gateway function.

The SIGTRAN IUA protocol is used between a softswitch and anAlcatel-Lucent 7510 MGW to transport Q.931 via IP and toterminate it at the softswitch.

A maximum of 256 (IUA) signaling links are supported.

The SIGTRAN M2UA protocol is used to transport the SS7signaling over IP networks on layer 2, using SCTP.

The M2UA function can be realized in two different ways, eitheron SFM or on PIM2 module. The realization on an SFM modulecan be done without additional hardware. It allows a realizationbased on software and data adaptation only. Using this capabilityon the SFM module the introduction of M2UA protocol in anetwork can be done very fast.

For large M2UA capacity the SGW can be configured on a PIM(VBPIxGES) module.

A maximum of 16 (M2UA) signaling links with 0.1 Erlang aresupported.

Note The IUA and M2UA function is available at the basichardware platform and don’t need specific hardwaremodules. The capacity varies on resources requiredfor MGW call processing. The maximum capacity canonly be reached in exclusive IUA/M2UA mode. Byrealization of M2UA on PIM2 module the full IUAcapacity can be used in any case.

For extended capacity the M2UA application could be operatedw/o internal redundancy at the VBPIxGES PIM module.

Maximum M2UA capacity: 64 SS7-links at 0.2 Erlang perVBPIxGES-module (max 2 modules per chassis). The capacityper chassis is 128 SS7 links at 0.2 Erlang.

SIGTRAN M3UA



The SIGTRAN M3UA protocol enables the 7510 MGW to operateas SGW and forward the SS7 protocol’s User Parts to MGC overIP. The system provides the backhauling mode and is capable torun in ETSI or ANSI environment. The SGW module is based onthe VBPIxGES PIM module running a specific software-packageon it.

The SGW application supports up to 128 logical SS7 networks.

Maximum M3UA capacity: 64 SS7-links at 0.2 Erlang perVBPIxGES-module (max 2 modules per chassis). The capacityper chassis is 128 SS7 links at 0.2 Erlang.

5 Features and Services – BGW Application



This chapter describes features and services which apply to theAlcatel-Lucent 7510 Border Gateway application. The followingsections are presented:

Introduction

Dynamic Media Firewall and Gate Management

Traffic Policing

Address Translation, Hosted NAT Traversal, andConnectivity

IP Version Interworking

Media Aware Mode (Transcoding and Media ResourceFunctions)

QoS Tagging and QoS Statistics

Peering Partner Monitoring

Multimedia Support

BGW Specific H.248 Packages



5.1 IntroductionIn Alcatel-Lucent’s NGN and IMS solutions the 7510 MGW actsas decomposed BGW function including the I–BGF to managepeering with other carriers and A–BGF to manage accessIP–networks. For the BGW application the 7510 MGWinter–works with:

IBCF/SPDF using the Ia–interface in the role of I–, C– andA–BGF according IMS TISPAN

IMS–ALG using the Iq–interface in the role of an IMS AccessGateway according 3GPP 23.228, Annex G

IBCF using the Ix–interface in the role of a Transit Gatewayaccording 3GPP 23.228, Annex I

The feature set allows operating the 7510 BGW as well asGSMA IPX media–node for IP–interconnect.

Alcatel-Lucent’s approach of embedding BGW functions intothese widely deployed MGW platform has been well received bymany customers as the ideal solution for evolving their networksfrom TDM towards IP. The Alcatel-Lucent 7510 MGW savesCAPEX/OPEX through re–use, scalability and IMS compliance.Because it provides simultaneous session connectivity for anymix of TDM and IP on a single platform, the solution boostsdeployment flexibility and enables economy–of–scale savings byaggregating more traffic per node.

Figure 12 BGW Application



The Border Gateway Function controls the transport boundary atlayers 2, 3 and 4 between service provider networks. It controlsaccess by packet filtering on IP-media address/port andopening/closing gates (pinholes) into the network and usesNetwork Address and Port Translation (NAPT) to hide the IPaddresses/ports of the service elements in the IMS/NGN core.Quality of Service (QoS) packet marking, bandwidth rate policing,usage metering and QoS measurements for the media flows areadditional features supported by the BGW. Optionally the BGWincludes media aware functions. It supports the media typesaudio and video on UDP and multiple streams within one H.248context.

The 7510 MGW configurations support up to 32.000 mediasessions in media agnostic mode, where BGW features realizedat the VBPIxGE PIM module. Optionally the BGW may bedeployed in media-aware mode requiring DSP capacity.

The BGW features supported by the Alcatel-Lucent 7510 MGWare listed in the following sections.

An overview on those features is given in Figure 13.



Figure 13 BGW Features List

5.1.1 Context Admission Control

Per IP realm (access or peering) a max-bandwidth threshold canbe defined. New context creations are accepted as long as thecumulated bandwidth of all streams stays below the threshold.The reserved bandwidth per stream is derived from b-line in theSession Description Protocol.



5.2 Dynamic Media Firewall and Gate Management Acts as a media firewall: does not allow any media through

unless it has been negotiated via a signaling session. Amedia pinhole is not opened until directed by the signalingcontroller, based on a negotiated session.

Latching for C(A)BGF function to learn address and port ofaccess–device.

Prevention of Denial of Service (DoS) attacks.



5.3 Traffic Policing Limit the traffic bandwidth for each session instructed via

traffic management package

The peak data rate or sustainable data rate, maximum burstsize and delay variation tolerance per stream could beinstructed individually per session.

Call Admission Control: max. bandwidth configurable forGigabit Ethernet interface, IP realm or VLAN. * Realized inMedia agnostic mode from R3.1 onwards



5.4 Address Translation, Hosted NAT Traversal, andConnectivity

Provides topology hiding: hides data that exposes internalnetwork information outside the provider’s network. This isachieved for the media path with network address translation(NAT) / network address port translation (NAPT).

Support of different or overlapping IP address realms of theinterconnected networks including VLAN support.

Multiple IP realms could be assigned to GigE interface. It’srecommended to distribute the IP realms via multiple GigEinterfaces to enable flexible capacity extension by addingfurther GigE interfaces vs. exclusive IP realm assignment tospecific GigE interfaces. Per chassis up to 1024 IP realmsare supported and the “system realms“ feature allows theusability of IP realms across multiple VGW instances.

VLAN tagging provisionable per IP realm or signaled viaH.248 for VPN bridging.



5.5 IP Version Interworking The introduction of IPv4/IPv6 dual stack enables an

IP-version translation across IP realms controlled bysignaling. Per IP realm you may assign either a uniqueIP–protocol version (IPv4 or IPv6) or both versions, i.e., anIPv4 and an IPv6 address could be assigned to one IPrealm.



5.6 Media Aware Mode (Transcoding and MediaResource Functions)

For media aware services MCM modules with DSP arerequired for media processing

Transcoding (any to any within supported codec–set) ofmedia streams to fulfill the peer network’s media standardslike default codec, packetization time, voice activity detectionand more.

Media profiles per realm to define Inter–working for Fax andDTMF per carrier.

RTCP Extended Report (RTCP XR) filter could be enabledper realm to avoid incompatibility with non–compatiblepeer–networks.

Media Resource Functions for tones and announcements

Media replication for Lawful Intercept

Media Inactivity Detection

Extended Media Statistics (please refer to QoS statistics forfurther details)



5.7 QoS Tagging and QoS Statistics Dynamic packet marking per stream, Differentiated

Services (DiffServ). or TOS and VLAN to guarantee QoS inIP–backbone, transition to MPLS pipes by packet edgenetwork element

Provides key performance voice metrics on a per-sessionbasis; using Real-time Transport Control Protocol (RTCP)data (used as well for call accounting records)

Media usage statistics like duration of session andsent/received packets/octets

Media quality statistics like round trip delay, packet–lossand jitter

Extended Media (H.248.XNQ) quality statistics in mediaaware configuration for:

Time degraded by network problems

Network Degraded Seconds Count

Network Severely Degraded Seconds Count

Time degraded by jitter buffer adaptations

Maximum IPDV range within RTCP cycle

Global Maximum Jitter range

IPDV Sum

IPDV Cycles

Jitter buffer adaptation events

RTP cumulative packet loss

Max/xMinimum round trip delay

Provides network quality and volume metrics per realm todifferentiate QoS figures per connected network:

Maximum and average used Bandwidth, packet andoctets received/sent

Discarded packets due to traffic policing, closed ports

Maximum and average delay, jitter, packet loss

Monitoring an threshold crossing alarms for qualitymetrics

Bandwidth and Error statistics per GigE–Interface to monitorphysical connection.



5.8 Peering Partner Monitoring The peering partner or rather the IP-connectivity could be

supervised and reported to the controller (IBCF) via theH.248 protocol. On notification the IBCF has the opportunityto select an alternative route to the peering partner.

To signal the peering partner service degradation, the BGWdoes not respond to supervision heartbeat if registration tothe controller (IBCF) is lost.



5.9 Multimedia SupportThe C–BGF and IBGF supports multiple media types typicallyused in scope of IMS:

Media type Audio and Video over UDP

Multiple streams (max. 4) within one call context

Packet size up to 1522 byte

Message Session Relay Protocol (MSRP) over TCP.

Instant Messaging (IM) clients use for enhanced messagingthe MSRP protocol in ’session mode’, e.g., in scope of RichCommunication Suite (RCS) within IMS for video sharing, filesharing ...

Note For instant messaging the ’page mode’ defined inMSRP is used, i.e., transport via control plane. Mediaplane and BGF is not involved.

Further media and protocol types are planned in futurereleases..



5.10 BGW Specific H.248 Packages H.248.37; IP NAPT traversal package

H.248.41; IP domain connection package + IP Realmavailabilty package

H.248.43; Packages for Gate Management and Gate Control

H.248.52; Quality of Service Package (diffserv)

H.248.53; TMAN TrafficMgmt

H.248.56; (VPN package) includes vlan–tag(802.1q) and802.1p.

6 Features and Services – SFW Application



This chapter describes features and services which apply to theAlcatel-Lucent 7510 SIP Firewall application. The followingsections are presented:

SIP Firewall Overview and Main Features

SIP Firewall Features

IP Filtering and Classifier

IP/UDP/ICMP/TCP DoS Attacks Mitigation

Networking Features

Redundancy

SIP Firewall Capacity



6.1 SIP Firewall Overview and Main FeaturesAlcatel-Lucent provides a peering border architecture consistingof:

An IBCF that supports SIP signaling interworking

A BGW that supports the RTP bearer functionality

An organic SIP signaling firewall to protect the IBCF fromSIP signaling attacks

Figure 14 SFW Application

Figure 14 shows the Alcatel-Lucent border solution. The SFW(SIP Signaling Firewall) is located on the edge of the network infront of the IBCF.

The Alcatel-Lucent 7510 BGW has internal firewall functionalityto protect the bearer network from external attacks, butadditionally a signaling firewall is needed to protect the IBCFfrom SIP signaling attacks.



The SIP firewall is located in the Alcatel-Lucent 7510 MGW onthe System Control Module (SCM). Only the SIP signalingmessages pass through the SFW; bearer packets pass throughthe BGW media layer.

High–level functionality of the SFW is:

Network Address/Port Translation

Load Sharing among IBCF CCS

n–tuple Filtering

SIP Support

Malicious Attack Prevention

IP Realm Separation

Per SIP Method Rate Limiting

IBCF Geographic Redundancy Support

Overlapping IP Address Support

Most firewalls provide SIP firewalling by implementing anApplication Layer Gateway (ALG) . From a networking standpointthey can operate either in transparent mode or routed mode withor without performing NAT. The Alcatel-Lucent 7510 MGW SIPfirewall does not follow that model.



Figure 15 SIP Firewall Functionality

The SIP firewall is built around a SIP stateless Record–RouteProxy that has been enhanced to be able to track dialogs andtransactions. For that purpose that SIP firewall inserts itself in theroute (inserts via and record–route headers) and providesTopology Hiding for the IBCF it protects. It is the next SIP hop forthat IBCF.

Since it operates as a stateless Proxy, it owns one IP interfaceon the trusted side and one IP interface on the untrusted sidedepending on the deployment model.

In its first version the SIP firewall supports IPv4 networks only.



6.2 SIP Firewall Features

6.2.1 SIP Parser Attack Prevention

Only the SIP header is analyzed by the SIP Firewall, the SDP isnot analyzed:

only accepts SIP messages which are properly formatted

only mandatory SIP headers are parsed

provides a limit for SIP message sizes (header and totalmessage size)

6.2.2 Protection Against SIP DoS and Dstributed DoSAttacks

Rate limits per types of messages

This is the first level of protection. When the untrusted SIPmessage is out of its rate, it is dropped by the SIP firewall.

Transaction tracking

The SIP firewall is aware of the transactions and can dropout of sequence messages as well as the duplicatemessages.

Dialog tracking

Dialog tracking is provided for INVITE dialog only. It permitsto track transaction inside a dialog. Transactions that are outof sequence are blocked, for example it may block blindCANCEL or BYE attacks.

Initial Request Flooding attack detection

The SIP firewall is able to detect a transaction flooding attackand to isolate SIP messages that correspond to thesignature of the attacker.



DDOS attack mitigation on initial INVITE

When all the fields uses for flooding detection changes oneach SIP message the SIP firewall is not able to detect thesource of the attack by just analysing the SIP message. Thedetection is based on a threshold of bad response for agiven signature by tracking the behavior of the transaction.When that threshold is reached, all the initial INVITEsmatching that signature have their rate downgraded. Thatdowngrading remains until the bad response counters dropbelow the normal threshold. That mechanism will impactlegitimate traffic that match the same signature, but avoidssetting up the source IP address in quarantine and by theway blocking an entire peer. Typically, in case of IP spoofingattack if the SIP firewall puts the source IP in quarantines theattack is successful, because the SIP firewall blocks thelegitimate source.



6.3 IP Filtering and ClassifierThe SIP firewall performs a 5–tuple classification on theuntrusted side to accept or reject an IP frame:

Protocol

Source IP address

Destination IP address

Destination port

IEEE 802.1Q tag



6.4 IP/UDP/ICMP/TCP DoS Attacks Mitigation IPv4

Any packet with an invalid/malformed IP header is dropped.This includes the control of IP checksum, Time to live, IPversion and IP header length.

UDP, TCP and ICMP are supported only (SCTP is plannedfor the future).

IP re–assembly of fragmented packages

The IP reassembly is provided for UDP and TCP protocols.The SIP firewall provides protection against most of thethreats resulting from fragmentation, e.g. Overlapping,Buffer Full, and others.

UDP

The SIP firewall provides protection against UDP shortheader, flood prevention or packets with incorrect checksum.

ICMP

The SIP firewall supports the necessary ICMP types, likeecho request/response. Others will be dropped.

TCP

The SIP firewall is protected against threats on TCP, whichincludes SYN flood, TCP RST attack, TCP sequenceprediction attack or Sockstress attacks .



6.5 Networking Features Remote SIP ports replication on trusted side

The SIP firewall is configured with a routing table thatpermits to perform the mapping between the trusted SIP portand the SIP port of the remote IBCF on the untrusted side.This is 1:1 mapping.

Single Point of Contact

On the untrusted side the SFW can be configured to be thesingle point of contact for the remote peers while operatingin a networking environment that provides separation amongthe peer networks.

Transparent to forking

When the local I-BCF decides to fork, the SIP firewall istransparent.

L2/L3/L4 SIP-aware firewalling

The SIP firewall provides L2/L3/L4 firewalling which is SIPaware on the untrusted side and thus does not require anyexternal firewall. That solution provides better performancesversus a solution with a separate L2/L3/L4 firewall. In case ofoverloading, the drop is performed at SIP level and not at L3or L4 level. This avoids dropping legitimate SIP traffic.

IPv4 address overlapping / VPN separation

VPN separation and IP address overlapping is supported onthe untrusted side by usage of IEEE 802.1Q VLAN tagging.

Reliable Transport

Beside UDP only TCP is supported in that release. TCPconnections are terminated at SIP firewall level.



6.6 RedundancyThe SIP firewall operates in 1+1 redundancy mode. It providesredundancy for the established calls but not for the transactioninside or outside a dialog.

Also the Gigabit Ethernet links carrying the SIP streams (trustedand untrusted) are 1+1 redundant.



6.7 SIP Firewall Capacity

Figure 16 SIP Firewall Capacity

7 Functional Architecture and Software



This chapter provides information concerning the Alcatel-Lucent7510 MGW architecture and hardware.


Introduction

Media Gateway Functional Architecture

Backplane Structure

Clock Generator

Alarms

Software



7.1 IntroductionThe Alcatel-Lucent 7510 MGW was specifically designed to meetthe requirements applying to a carrier-grade media gateway thatcan connect TDM circuit-switched networks to IPpacket-switched networks. It employs a highly flexible dualswitching architecture that permits large scale TDM and packetswitching operations. TDM and packet switching operationsoccur in this gateway simultaneously.

Some important considerations that were involved whendeveloping the Alcatel-Lucent 7510 MGW were:

Scaleability, regarding the ease with which the systemcapacity can be increased to meet the demands of growingfuture traffic requirements

Usage, i.e., network integrated and stand-alone installations

Efficiency in terms of components that can be shared toreduce overall production costs

Reliability.

7.1.1 Scalable Capacity

The Alcatel-Lucent 7510 MGW possesses dedicated bandwidthto support native transport of high capacity packet voice trafficwithin the gateway.

The Alcatel-Lucent 7510 MGW supports up to 30,240simultaneous VoIP sessions in a single chassis, using thefollowing interfaces per module:

PSTN interfacesThree PSTN interface types:

4 optical OC-3/STM-1 interfaces per module (up to 8active modules per Alcatel-Lucent 7510 MGW)

9 electrical DS3 interfaces per module (up to 8 activemodules per Alcatel-Lucent 7510 MGW)

32 T1/E1 interfaces per module (up to 15 activemodules per Alcatel-Lucent 7510 MGW)

Packet interfacesOne optical Gigabit Ethernet IP interface (up to 8 activemodules per Alcatel-Lucent 7510 MGW)

DSP Architecture

DynamicResource

Management

Shared Memory



DSP moduleUp to 6K VoIP ports and 6 active DSP modules perAlcatel-Lucent 7510 MGW (allows high capacity; also whencompressed codecs are used)

7.1.2 Usage

The Alcatel-Lucent 7510 MGW can be deployed in standaloneconfigurations in a distributed network topology, or in a rackconfiguration in centralized installations. The Alcatel-Lucent 7510MGW is designed to be a VoIP Trunking Gateway that can befurther optimized to operate in future gateway applications.

7.1.3 Efficiency

Efficiency is guaranteed by using a DSP architecture and sharedmemory.

Flexible switching and a pooled DSP architecture are employedto allow application-specific optimization. The Alcatel-Lucent7510 MGW architecture ensures maximum versatility andreliability by pooling DSP resources and assigning themdynamically.

Note The dynamic allocation of DSPs is very efficient andflexible in case of TDM hairpinning, because DSPscan be inserted or removed in mid-call.

Forwarding resources and DSPs are physically available to eachport on any TDM or packet interface. Distributed forwarding andresource pooling in the Alcatel-Lucent 7510 MGW serve tooptimize the cost of the Alcatel-Lucent 7510 MGW – the mostexpensive components, DSP resources and forwarding engines,are shared by all ports and interfaces.

Using Dynamic Resource Management (DRM), the efficiency ofthe DSP pools can be increased by the configuration of thecodec profiles. The capacity of the DSP pool then depends onthe percentage allocated per codec type, and not on the capacityof the most resource consuming codec type.

The memory used for classification, buffering, and to storerouting tables is also shared by all modules, further reducing thetotal cost of the gateway.

Redundancy

RedundancyGroups

AdditionalRedundancy



7.1.4 Quality of Service – QoS

The Alcatel-Lucent 7510 MGW offers advanced QoS servicelevels pertaining to packet voice traffic, from best effort toguaranteed delivery; the gateway implements DiffServ and IPTOS to differentiate QoS priorities that are maintained for allmodules (see also section 2.9).

7.1.5 Redundancy, Reliability and Availability

As NGN technologies begin to offer an alternative to PSTNnetworks, softswitches and media gateways must guarantee thehighest level of reliability and availability to meet the moststringent deployment requirements applicable to exchangeenvironments. The Alcatel-Lucent 7510 MGW has beendesigned incorporating numerous redundancy and fault tolerancefeatures to provide the highest level of gateway availability andreliability.

The Alcatel-Lucent 7510 MGW supports as many as 20 moduleshaving 1+1 or N+1 redundancy. It is designed to supportcontinuous operations without any point of failure. Consistentconfiguration information and replicated call data are maintainedin each standby module; this prevents losing active calls when anAlcatel-Lucent 7510 MGW switches from an active to a standbymodule, e.g., to perform maintenance or upgrade actions.

Each module contains complete software copies to ensure thatthe Alcatel-Lucent 7510 MGW remains online while softwareupgrades are being performed or should a module fail.

Communication between the Alcatel-Lucent 7510 MGW and asoftswitch is also fully redundant (see also section 2.12).

To combine software and hardware redundancy theAlcatel-Lucent 7510 MGW is configured as a set of redundancygroups. Every 1+1 redundancy group contains a pair of physicalmodules, the related interfaces and software. An n+1redundancy group consists of n+1 physical modules and thecorresponding interfaces and software. These logical groupsallow the access to other modules and resources using logicaladdresses, while hiding their physical presence.

Additionally, the Alcatel-Lucent 7510 MGW offers full softwareredundancy:

System control functions



Call processing

Call signaling

Routing

Memory.



7.2 Media Gateway Functional ArchitectureThe Alcatel-Lucent 7510 MGW is a multi-purposehardware/software platform.

A short description of the functional architecture, as well asindividual functional descriptions of the modules involved follow.

7.2.1 Functional Architecture

Each Alcatel-Lucent 7510 MGW simultaneously interfaces to aTDM network and an IP network.

Logical interconnections of the functional modules inside of anAlcatel-Lucent 7510 MGW are shown in Figure 17.

0198_loinhm_ed02

DSPF EthG EthTDM

: Digital Signal Processor: Fast Ethernet: Gigabit Ethernet: Time Division Multiplex

SwitchFabricModule

CircuitInterfaceModule


Multi–DSP System

Media ConversionModule

SystemControlModule

Circuit–Oriented Functions Packet–Oriented Functions

Fast Ethernet Link to MGC

F Eth

G Eth

F Eth

G Eth

F Eth

G Eth

TDM

TDM

TDM

F Eth

PacketInterfaceModule


Circuit(TDM)

Packet

SIP

FirewallG Eth

Figure 17 Logical Interconnections of the Functional Modules

The functional architecture shown involves the followingmodules:



System Control Module

The system control software and the optional SIP firewallsoftware are stored in the SCM.

Switch Fabric Module

The Switch Fabric Module contains the packet switches andcircuit switches.

Media Conversion Module

The Media Conversion Module provides pooled DSPresources.

Circuit Interface Module

The Circuit Interface Module contains channelizedOC-3/STM-1 and T1/E1 interfaces. It provides the time stageof TDM switching, which, e.g., is used together with thespace stage switch on the SFM, to perform TDM hairpinning.

Packet Interface Module

The Packet Interface Module contains the optical GigabitEthernet uplink ports, and provides the first stage of packetswitching (tier 1 switching).

7.2.2 System Control Module

The System Control Module uses a Packet SwitchingFabric (PSF) (the c-PSF) to provide dedicated 100 Mbit/sEthernet links to manage and communicate with every othermodule in the Alcatel-Lucent 7510 MGW. The System ControlModule initializes, configures, resets, and performs run-timemanagement of the system; it also gathers system statistics andperforms diagnostic testing.

The System Control Module also provides out-of-bandmanagement ports (Ethernet and RS-232) to connect to a craftsport, and an alarm manager that supervises external alarms.

The SCM provides a forwarding server to forward traffic from aMedia Conversion Module, and from the packet switch fabric,which is part of the Switch Fabric Module. It also includes theSystem Route Server (SRS) and System ManagementServer (SMS) functions.

The SRS calculates routes and performs route distribution.

The SMS provides overall system control (e.g., resetting andmonitoring the status of different modules) and downloads copiesof software (software images) that are to be stored in otherhardware modules.



The SCM also houses the SIP firewall on an AMC sub-card,including the dedicated GE connections for the SIP traffic.

The functional architecture of the System Control Module isshown in Figure 18.

0200_fumoscm_ed02

PhysicalBlock

To Media Conversion Module

To Packet Interface Module

To Craft

To Fast Ethernet

To AlarmsTo FansTo FusesTo Status

Flash

PROM

SDRAM

NVRAM

CentralProcessing

Unit

ChassisManagement

Modules

Packet SwitchFabric

Controller

Controller

Memory

Figure 18 Functional Architecture of the System ControlModule

Table 8 lists the functions performed by the System ControlModule.

Table 8 System Control Module Functions

Feature Description

Functions System Management

Megaco/H.248 application software

Control of media switching

OAM

SIP signaling firewall application

Redundancy 1+1 redundant – one active, the second a hot standby

EPS and LPS for Fast Ethernet interface (signalingand OAM)

Circuit (TDM)Switch Fabric



7.2.3 Switch Fabric Module

To maximize performance, the Alcatel-Lucent 7510 MGWincorporates two types of switches on the Switch Fabric Module.Each switch, called a switch fabric, is optimized to process aspecific type of traffic, i.e., TDM traffic (in the circuit switch) orpacket traffic (in the packet switch, d-PSF). The Switch FabricModule is a high capacity module that simultaneously processesTDM- and packet-switching.

The functional architecture of the Switch Fabric Module is shownin Figure 19.

0209_sfm_ed01

ControllerManagerTarget

PacketSwitchFabric

Flash

PROM

SDRAM

NVRAM

CircuitSwitchFabric

Controller

CentralProcessing

Unit

Memory

Figure 19 Functional Architecture of the Switch Fabric Module

The Alcatel-Lucent 7510 MGW incorporates a fully redundantpair of non-blocking 16 Gbit/s packet switch fabrics and a fullyredundant pair of non-blocking 10 Gbit/s circuit (TDM) switchfabrics on the Switch Fabric Module.

Each one of the 32 circuit (TDM) switch fabric carries 9000 DS0circuits, and performs all TDM distribution, switching, andgrooming functions.

The distributed TDM switching architecture of the Alcatel-Lucent7510 MGW supports termination of DS0s. It also supports 100 %TDM hairpinning by providing a full DS0-level cross-connect

Packet SwitchFabric

ExternalConnections



inside of the gateway. This avoids any kind of TDM formatconversions and associated transfer delays that occur whensending TDM traffic across a non-circuit (TDM) switch fabric.

The packet switch fabric (the d-PSF) on the SFM maintains thedata plan and provides interconnections between the MCM andPIM modules, allowing VoIP packets to be exchanged betweenthem. The packet switch fabric provides a dedicated bandwidthof multiple Fast Ethernet/Gigabit segments to each module.

Figure 20 shows the connections between the Switch FabricModule and other modules.

0199_conramo_ed02

SwitchFabricModuleStandby





MediaConversion

Module

MediaConversion

Module

SystemControlModule

3SwitchFabricModule

Circuit(TDM)

Packet

1/2/3

11

11

2

2

2

2

1 TDM 1.25 Gbit/s2 Gigabit Ethernet 1 Gbit/s3 Fast Ethernet 100 Mbit/s

TDM : Time Division Multiplex

Figure 20 External Switch Fabric Module Connections

The Switch Fabric Module uses dedicated 1.25 Gbit/s TDM-linksto communicate with every Circuit Interface Module and theMedia Conversion Module, as well as dedicated 1 Gbit/sGigabit-Ethernet-links to communicate with every PacketInterface Module and the Media Conversion Module within theAlcatel-Lucent 7510 MGW to process signaling information andtransport voice-traffic.

Summary ofFunctions



The Switch Fabric Module possesses out-of-band managementports (Ethernet and RS-232) to connect to a crafts port, and analarm manager that supervises external alarms.

Table 9 lists the functions of the Switch Fabric Module.

Table 9 Switch Fabric Module Functions

Feature Description

Functional Performs switching of Ethernet packets

Performs forwarding of packets that originate fromMedia Conversion Modules

Scalability &Performance

The packet switch fabric supports scalability throughtwo generations of density evolution

Redundancy 1+1 redundant – one active, the second is a hotstandby

Capacity Packet switch: 16 Gbit/s

Circuit switch: 10 Gbit/s


Two types of CIMs are available:

SDH CIMContains 4 OC-3/STM-1 ports, supporting either a SONETor SDH network

PDH CIMContains 32 T1/E1 ports, supporting a PDH network

All PSTN functions, including signaling, monitoring, timing, andalarm processing, are managed by processors on the CIM. TheCIM also performs TDM switching, (e.g., to perform hairpinning),and distributes traffic to the Media Conversion Module.

A SDH–CIM module could be configured in n+1 or 1+1redundancy group (EPS). The PDH–CIM runs always in n+1configuration.

The EPS configuration protects the CIMs and the APS takes careof the link protection. The active CIM performs line interfacing,timing recovery, framing, and TDM switching and grooming. Afully equipped Alcatel-Lucent 7510 MGW can carry more than32,000 DS0s protected in this manner (4 active and one standbySDH–CIM).



In case of a pure TDM switching configuration, theAlcatel–Lucent 7510 MGW can carry up to 64,512 DS0s (i.e., 2redundancy groups each with 4 active and one standbySDH–CIM).

Figure 21 shows the functional architecture of the CircuitInterface Module.

0211_famocim_ed02

SDRAM

PROM

CentralProcessing

UnitController

ClockRecovery

TDMInterface a.Multiplexor

To Switch Fabric ModuleTo Line

BITSPROMTDM

: Building Integrated Timing Source: Programmable Read Only Memory: Time Division Multiplex

To SSU or BITS Input

SSU : Synchronization Supply Unit

Figure 21 Functional Architecture of the Circuit InterfaceModule

Table 10 lists the functions of the Circuit Interface Module.



Table 10 Circuit Interface Module Functions

Feature Description

Functional Provides a TDM receive and transmit interface,performing full DS0-level extraction.

Provides up to two timing domains; each domain canbe synchronized to any TDM interface.

Provides up to two TDM switches, which are fullDS0-level capable.

Plugable SFP module with multiple laser modes.


The TDM switch supports distribution to all MediaConversion Modules.

The TDM switch supports DS0 switching locally on theCircuit Interface Module.

Redundancy SDH supports 1+1 or n+1 EPS and 1+1 APSredundancy for an SDH or SONET configuration.

PDH supports n+1 EPS redundancy for a T1/E1configuration.


The Packet Interface Module possesses a high-speed IPinterface in the form of an optical Gigabit Ethernet interface. ThePacket Interface Module accepts and forwards packets to andfrom the core packet network.

The Packet Interface Module provides the backbone packetnetwork interface using an optical multimode Gigabit Ethernetinterface. In addition, the Packet Interface Module functionsinclude:

Line termination

Framing

Packet buffering on input

Fairness policing on input

Forwarding Buffering on output

Rate shaping on output.

The EPS configuration protects the PIMs and the APS takes careof the link protection.

Figure 22 shows the functional architecture of the PacketInterface Module.



0201_fumopim_ed02

CentralProcessing

Unit

To Packet Network

MemoryController

Memory

To Switch Fabric Module

LineBlock

BackplaneBlockSDRAM

PROM

CentralProcessing

Unit

Figure 22 Functional Architecture of the Packet InterfaceModule

Table 11 lists the features of the Packet Interface Module

Table 11 Packet Interface Module Features

Feature Description

Functional Provides the backbone line receive interface

Supports buffering and shaping

Supports packet-level marking using appropriatelevels of QoS

Provides routed packets to the packet switch

Plugable SFP module for 1000 Base SX/LX


A PIM card provides a full duplex Gigabit Ethernetinterface.

A PIM can handle up to 8 k ephemeral terminations(designed to cover maximum 8064 RTP streams usingG.711 codecs without VAD and 5 % RTCP)

Redundancy n*(1+1) or n+1

7.2.6 Media Conversion Module – VBMCMxE

The enhanced MCM board (VBMCMxE) provides the latest DSPtechnology.

The Alcatel-Lucent 7510 MGW can be pre-configured to supportup to 6 Media Conversion Modules.

The two variants of the new MCM board are:



Large MCM (VBMCM7E)Conversion of up to 6,048 DS0 voice channels (usingG.711) to packet format, and vice versa.

Small MCM (VBMCM3E)Conversion of up to 3,024 DS0 voice channels (usingG.711) to packet format, and vice versa.

A Media Conversion Module consists of a pool of DSPresources, several high-speed microprocessors, memory, andbuses to support a large number of voice over IP connections.

The DSPs, part of the Media Conversion Module, perform voiceprocessing statistics collection, traffic policing, and signalrecognition to discriminate between voice and data signals, e.g.,fax, modem, or DTMF signals. The DTMF signals are transmittedin-band in the packet network using the G.711 Codec oraccording to RFC2833 and RFC4733. On detection of FAX ormodem tones, the DSP automatically switches over toFAX-modem bypass (G.711) or T.38, depending on theconfiguration used.

Table 12 lists the features of the VBMCMxE.



Table 12 VBMCMxE Features

Feature Description

Functional Provides a pool of DSPs that process voice, fax ordata

Codec G.711 App. I & II (packet size: 10...30 ms)

Codec G.729AB (packet size: 10...60 ms)

Codec G.723.1 (packet size: 30 & 60 ms)

Codec G.726.1 (packet size: 10, 20 & 30 ms)

Codec AMR2 (packet size: 20 ms)

Codec GSM-FR (packet size: 20 ms)

Codec GSM-EFR (packet size: 20 ms)

RTCP

T.38

RFC2833/RFC4733

VBD and V.152

Tones

Echo Cancellation (tail length up to 128 ms)

Adaptive Jitter Buffer (maximum value is 135 ms)


Supports scalability of up to 6,048 G.711 channels permodule (VBMCM7E) and, up to 3,024 channels permodule (VBMCM3E).

Redundancy Pooled architecture scheme in 1+1 or n+1 redundantconfigurations

Table 13 presents an overview of the VBMCMxE capacities andredundancy.

Table 13 Capacity and Redundancy of the VBMCMxE

Module Capacity Active/Standby

VBMCM7E with G.711 codecs 1 to 6,048 DS0s 1+1

... to ... ...+...

Up to 36,288 DS0s 6+1

VBMCM3E with G.711 codecs 1 to 3,024 DS0s 1+1

... to ... ...+...

Up to 18,144 DS0s 6+1



Module Active/Standby

Capacity

VBMCM7E with G.729/G.726 1 to 3,456 DS0s 1+1codecs and T.38 ... to ... ...+...

Up to 20,736 DS0s 6+1

VBMCM3E with G.729/G.726 1 to 1,728 DS0s 1+1codecs and T.38 ... to ... ...+...

Up to 10,368 DS0s 6+1

VBMCM7E with 1 to 2,592 DS0s 1+1G.723/AMR/GSM-FR/GSM-EFR ... to ... ...+...codecs

Up to 15,552 DS0s 6+1

VBMCM3E with 1 to 1,296 DS0s 1+1G.723/AMR/GSM-FR/GSM-EFR ... to ... ...+...codecs

Up to 7,776 DS0s 6+1

7.2.7 Capacity, Scaleability and Redundancy

Capacity, scalability and redundancy are the most importantcharacteristics applicable to carrier-class media gateways.Service providers desiring to expand their networks in aconverging market must be able to add subscribers quickly,easily and as cost-effectively as possible.

A single Alcatel-Lucent 7510 MGW provides an entry-levelconfiguration capable of managing a packet switching capacity of16 Gbit/s , and a circuit switching capacity of 10 Gbit/s.

The VoIP call capacity in the Alcatel-Lucent 7510 MGW isdetermined by the number and the redundancy configuration ofthe Media Conversion Modules.

Using DRM, the efficiency of the DSP pools can be increased bythe configuration of the codec profiles. The capacity of the DSPpool then depends on the percentage allocated per codec type,and not on the capacity of the most resource consuming codectype.

Note The MCM is not required in a TDM hairpinningconfiguration without media processing.

Note Up to 3*(N+1) redundancy groups for PIM/CIM(SDH)modules are supported within one Alcatel-Lucent 7510MGW chassis, but only 2 groups of each type.



Table 14 presents an overview of the gateway capacities permodule, and redundancy.

Table 14 Overview of Capacity and Redundancy per Module

Module Capacity Active/Standby

SCM2 270 CoAPS 1+1

SCM 135 CoAPS 1+1

MCM with G.711 codecs 1 to 6,048 DS0s 1+1

... to ... ...+...

30,241 to 36,288 DS0s 6+1

Compressed codecs See Table 13 –

CIM (SDH ANSI config.) 1 to 8,064 DS0s 1+1

... to ... ...+...

24,193 to 32,256 4*(1+1)or 4+1

...

CIM (SDH ETSI config.) 1 to 7,812 DS0s 1+1

... to ... ...+...

23,437 to 31,248 4*(1+1)or 4+1

...

CIM (PDH ANSI config.) 1 to 768 DS0s 1+1

... to ... ...+...

10,753 to 11,520 15+1

CIM (PDH ETSI config.) 1 to 992 DS0s 1+1

... to ... ...+...

13,889 to 14,880 15+1

PIM 1 to 8,000 RTP terminations 1+1

8,001 to 32,000 RTPterminations

4*(1+1)or 4+1

...

SFM All configurations 1+1



7.2.8 Summary of Module Functions

Table 15 summarizes the VoIP functions managed by each of theapplication-specific Alcatel-Lucent 7510 MGW modules.

Table 15 VoIP Functions Processed by the Modules

VoIP Functionality SystemControlModule

SwitchFabricModule



MediaConversion Module

Overall System Initialization andManagement

X

Call and Connection Management X

Packet Forwarding and IP Routing X

Packet Switching X

(control)

X X X

(optional)

TDM Switching X X X

(optional)

PSTN Interface X

Packet Interface X

Media Processing X

Clock Recovery and Distribution X X

Silence Detection/Suppression, ComfortNoise Generation, and Echo-Cancellation

X

Operations Interface X

NarrowbandClock

Distribution



7.3 Backplane StructureThe Alcatel-Lucent 7510 MGW backplane structure includes aTDM Bus, two Data Buses, one Redundant Bus, and a ClockDistribution Bus.

7.3.1 TDM Bus

The TDM bus on the Switch Fabric Module provides TDM linkswhich carry DS0 bit streams from TDM input ports to digitalmodems.

TDM links carry traffic between the PSTN interface and the voiceprocessing modules. Each TDM stream has an input line and anoutput line. The voice processing modules take data from inputstreams and deliver it to output streams. The PSTN interfacemodules place received data into input streams, and send datareceived from output streams back into the line.

7.3.2 Data Bus

The data bus on the Switch Fabric Module provides GigabitEthernet links and Fast Ethernet links to transfer traffic betweenhardware modules. These data links carry internal protocol andcontrol messages, using advanced multicast circuitry. The datalinks interconnect all Alcatel-Lucent 7510 MGW modules; theyoperate on a load-sharing basis, and act as a redundant pair forbackup purposes.

7.3.3 Redundant Bus

The Alcatel-Lucent 7510 MGW uses a dedicated Redundant Busconcept to detect failures in the system; redundant busesoperate in a load-sharing mode, and act as a redundant pair forbackup purposes.

7.3.4 Clock Distribution Bus

This section explains the narrowband clock distribution and thebroadband clock generator.

Clock signals are distributed using two distribution branches in aramifying tree structure, employing the Circuit Interface Module

Broadband ClockGenerator



in two hierarchical levels serving as many as 20 boards. Eachboard can select one of the two distribution branches.

The broadband clock generator is an internal 19.44 MHz CrystalOscillator that is synchronized to an 8 kHz clock signal takenfrom one of the two distribution branches.



7.4 Clock GeneratorThe Alcatel-Lucent 7510 MGW can be deployed in serviceprovider networks that use a clock distribution system that wasestablished according to the hierarchical source-receivermethod.

The Alcatel-Lucent 7510 MGW includes a redundant clockgeneration and distribution subsystem that are located on theCircuit Interface Module. Each clock module can use one ofthree modes to generate a reference clock signal:

External clock timing modeUses an external SSU or BITS source clock signal

TDM Line timing modeUses a TDM (from CIM) interface, 8 kHz line timing signal.

Internal timing modeUses a local crystal oscillator that is Stratum 3 Clockcompatible. A variant with Stratum 2 clock is also available.

The Alcatel-Lucent 7510 MGW internally distributes two clocksignals, a primary and a secondary, to all modules. Thesecondary clock signal provides a backup if the primary fails.Each of the two clock signals is generated by two independentclock, recovery, synthesis, and distribution systems (each asingle chip) on the SCM modules.

For synchronisation of further network elements at the samelocation the Alcatel-Lucent 7510 MGW provides an externalclock-output connector.

Clock features supported by the Alcatel-Lucent 7510 MGW:

Two internal clock distribution systems, one primary and onesecondary.

SSU (2.048 MHz) port

T1-BITS (1.544 Mbit/s) or E1-BITS (2.048 Mbit/s) port

Alternative clock source can be derived from a TDM link (linetiming).

User-selected clock source with configurable prioritysettings.

To ensure clock quality, Synchronisation StatusMessages (SSMs) are monitored and evaluated.

Revertible clock source selection (the primary clock source isre-selected after an outage).



Internal Stratum 3 Clock to be used if all external timing inputfails.

Clock recovery and clock generation from configurableinterfaces.



7.5 SoftwareThe Alcatel-Lucent 7510 MGW contains a distributed softwaresystem. The following description of the software architectureinvolves each node in the system, as well as the model used torealize communication between these nodes.

The Alcatel-Lucent 7510 MGW uses a layered, modular softwarearchitecture (see Figure 23). This architecture is based on anopen, programmable call control model that performs callprocessing independent of other functions, like resourcemanagement, routing, or forwarding.

The software consists of the following modules:

Kernel Software

Network Layer Software

Application Layer Software.



0169_rtimearch_ed01

FTAMIPMGCPOSPFRIPSCTP

SNMPTCPTFTPUDPUI

: Fault Tolerant Application Management: Internet Protocol: Media Gateway Control Protocol: Open Shortest Path First: Routing Information Protocol: Stream Control Transmission Protocol

: Simple Network Management Protocol: Transmission Control Protocol: Trivial File Transfer Protocol: User Datagram Protocol: User Interface

Hardware Layer

HdS

Network Layer

Routing Table

ARPFunction,

TableMARP

Function

IPStack, Cache, Filter

High SpeedIP Forwarder

Generic Forwarding Interface

Application Layer

SIGTRAN

SCTP

MegacoMGCP

RIP TFTP SNMP Mast Agent

SNMP Sub Agent

On–Line Diagnostics

UI Subsystem

Telnet

TCP UDP

IP Management Interface

OSPF

KernelSoftware

File System

TTYDriver

FlashFile

Driver

Kernel

Protocol Demux

FTAM

RedundancyManager

MultiCastManager

TDM

ResourceManager

ConfigManager

Voice Port

Figure 23 Runtime Architecture

7.5.1 Kernel Software

The Kernel software contains limited but efficient scheduling andcommunication services. All software modules, with few

RedundancyManager

MulticastManager

ResourceManager



exceptions, use the tasking model provided by the kernelsoftware.

The packet processing modules (e.g., the Generic ForwardingInterface (GFI) and the high speed forwarder) do not use thekernel tasking model; this minimizes performance overheadwhen forwarding packets.

7.5.2 Network Layer Software

The network layer software consists of the following modules:

Redundancy Manager

Multicast Manager

Resource Manager

Configuration Manager

Routing Server/Packet Forwarding

TDM Manager Software

FTAM

Voice Port Software

Routing Tables

Protocol Demux

GFI Software.

The Redundancy Manager manages switchover operations andother system reactions to failures. It also provides services toother modules in the system, allowing them to synchronize andregister the current configuration of the system, should a failureoccur. Additionally, this module maintains the currentconfiguration of the system regarding the active and standbymodes of all software modules, as well as other parameters thateffect the entire system.

The Multicast Manager software lists ports that can be used tomulticast packets internally. Applications running in the SystemControl Module can dynamically create or delete multicast lists.Once a multicast list has been created, it can be accessedglobally by all applications running in all modules.

The Resource Manager software allocates and releases DSPresources that can be assigned to voice channels. The ResourceManager software stored in each DSP module tracks the status

ConfigurationManager

RoutingServer/Packet

Forwarding

TDM Manager

FTAM



and availability of all DSPs. When a dedicated line is configured,or when a switched call is received, a request is broadcast toeach DSP module. The Resource Manager software in eachDSP module receives the request and determines whichresources are required to set up a TDM circuit, beginning at theinput port to the pooled DSPs.

The Configuration Manager software is responsible for:

managing all configuration requests received from thesoftware using it.

managing the configuration database.

distributing configuration information to various accessmodules.

The Configuration Manager software provides a service to allother modules, distributing configuration information across allboards, but it does not register configuration parameters. It alsostores and retrieves configuration information received from theConfiguration database, which is stored in the System ControlModule flash memory. These modules run as a task on eachboard.

The Routing Server/Packet Forwarding software forwards IPpackets according to information stored in the module cachememory, forwarding tables, and a central forwarding table.

The TDM Manager software sets up and releases TDMconnections (DS0 paths). This software consists of severalsub-modules. The major sub-modules are the:

TDM Call Control Manager

TDM Driver

TDM Server.

The FTAM software monitors the Alcatel-Lucent 7510 MGWsoftware components to ensure non-stop operation. The FTAMuses microprocessor-based module managers (located in eachmodule) to control system start-up, sense hardware status, andmeasure internal temperatures. It provides services toapplication tasks that require fault tolerance observation. It alsocommunicates with FTAM tasks running in all other accessmodules, ensuring that application tasks operate correctly, andprovides switch-over capabilities if an application fails.

Voice Port

Routing Tables

Protocol Demux

GFI

Telnet



The Voice Port software supervises the establishment of voicechannels; this primarily consists of configuring and managingDSP resources that were previously allocated by the resourcemanager. The Voice Port software consists of the Voice PortClient / Server.

Routing Tables are stored in the Configuration DatabaseManager (CDBM) software, which collects, distributes, andstores configuration information applying to the entire gateway.

The Protocol Demux software provides a demultiplex function toroute packets from the Layer 2 interface to higher layerprotocols. This module is responsible for all packets received orsent as Media. In co-ordination with the Port Interface (PIF)software, this module de-encapsulates IP packets beforesending them to the IP forwarder software, thereby supportingthe Ethernet.

The GFI software provides a uniform interface to the forwardingfunctions; this interface hides the details of transmitting andreceiving packets over interfaces of different types. It alsodefines an interface that the driver software uses to deliverpackets they received, and to transmit packets from the gateway.

7.5.3 Application Layer Software

The application layer software consists of the following modules:

Telnet

TCP

User Datagram Protocol (UDP)

SIGTRAN/SCTP

Megaco

TFTP

FTP Server

SNMPv3

UI Module

IP Management Interface.

Support of Telnet applies only to incoming Telnet requests asdescribed in the initial Telnet release. Users can use Telnet to

TCP

UDP

SIGTRAN/SCTP

Megaco/H.248

TFTP

FTP Server



reach an Alcatel-Lucent 7510 MGW; this applies to any interfacethat is configured for IP. Outgoing Telnet functions are only usedinternally in the system to implement the remote console feature;this feature allows a user working at the System Control Moduleconsole to connect to the ‘console’ of any other access module.

The TCP software implements RFC 793 and RFC 1122. TheTCP ports transport Telnet.

The UDP software implements RFC 768. The UDP portstransport RTP, Megaco/H.248 and SNMP.

The SIGTRAN/SCTP represents the architecture used totransport real-time signaling data over IP networks. TheSIGTRAN protocol uses the SCTP as a transport layer, insteadof using TCP and a set of user adaptation layers. TheSIGTRAN/SCTP supports communication between anAlcatel-Lucent 7510 MGW and a softswitch.

The Megaco protocol represent the application in anAlcatel-Lucent 7510 MGW that services requests from an MGCand returns responses to that MGC. Communication between theAlcatel-Lucent 7510 MGW and an MGC follows theindustry-standardized Megaco protocol.

When the Megaco protocol is used, the software is acombination of the Megaco stack and the adaptation layersaround it that are used to integrate Megaco functionally into anAlcatel-Lucent 7510 MGW.

The TFTP complies with the standard RFC 1350. The TFTP onthe System Control Module consists of two components: theclient and the server tasks.

The client task is used to initiate file transfers from anAlcatel-Lucent 7510 MGW, using user commands.

The server task responds to TFTP requests received from thenetwork.

The FTP server application allows FTP clients to get and put filesusing the File Transfer Protocol (FTP). An FTP client accessingthe FTP server requires an FTP account and password. Onlyone file directory-level is supported and only one FTP user canbe active at a time.

SNMPv.3

UI Module

IP ManagementInterface



The SNMPv.3 agent implements the standard RFC 1157. SNMPrequests received on any interface in an Alcatel-Lucent 7510MGW are directed to the master agent task, a process that runsin the System Control Module.

The master agent in the System Control Module responds tothese requests by making calls to access functions in itssub-agent.

The sub-agent implements all standard Management InformationBases (MIBs) that are relevant, as well as enterprise MIBs thatcontain Alcatel-Lucent 7510 MGW specific MIB extensions (seeAppendix B.4).

The master agent either communicates with MIB objects storedin the System Control Module, or it sends messages tosub-agent processes in access modules to communicate withMIB objects that are stored in other modules.

The UI Module implements the CLI specified to configure andmonitor an Alcatel-Lucent 7510 MGW. This software controls asmany as four simultaneous sessions. The UI is a table driversoftware; it allows additions and changes to be easilyaccomplished.

The IP Management Interface makes all forwarding decisionsapplying to IP packets. This software maintains a cache memorycontaining currently active destinations, as well as informationrequired to forward a packet to a required destination; it alsoperforms quick lookup and forwarding tasks to accelerate packettransmission.

7.5.4 Voice Processing

The Alcatel-Lucent 7510 MGW provides maximum density, usinga modular, pooled DSP resource design. The DSPs use G.711,G.729A/B and G.723.1 Codecs that are available to any interfaceto perform voice compression, packetization, silencesuppression, echo cancellation, and adaptive Jitter Buffer packetvoice-processing services.

7.5.5 Software Redundancy

The Alcatel-Lucent 7510 MGW offers full software redundancyfor:

System control functions



Call processing

Call signaling

Routing

Memory

Voice path.

These functions are designed to provide high service availability,continuous administration and hitless voice connections with:

Failing Hardware (HW) or module (provided by EPS)

Failing interface connections; provided by AutomaticProtection Switch (APS)

Administrative operations like software upgrades orconfiguration updates.

MGC fail-over

Application Server (AS) fail-over (SIGTRAN)

Table 16 summarizes the redundant software components in theAlcatel-Lucent 7510 MGW.

Table 16 Software Redundancy

System Software Redundancy

Dual copies(images) of eachsoftware component

All software modules within the Alcatel-Lucent 7510MGW are copied, i.e., have a dual software image,allowing software upgrades to occur without losingactive calls. Redundant components include thefollowing:

System and management software

Signaling and gateway control software

8 System Management and OAM



This chapter describes the comprehensive set of systemmanagement and OAM tools and features.


Overview

Chassis Management

Configuration Management

Fault Management

Diagnostic Test – BERT

System Logging and Debugging

Performance Management

Security Management

OAM Interfaces

Software Upgrade Management



8.1 OverviewThe Alcatel-Lucent 7510 MGW contains a comprehensive set ofsystem management and OAM tools and features, namely:

Chassis ManagementThe Alcatel-Lucent 7510 MGW contains a high-levelchassis management system that operates from the activeSystem Control Module.

Configuration ManagementThe configuration database, which is stored in files in theFlash Memory of the System Control Module, maintains allAlcatel-Lucent 7510 MGW configuration information.

Fault ManagementFault management concerns detection, isolation, andcorrection of abnormal operations in an Alcatel-Lucent 7510MGW.

Diagnostic Test – BERTThe BERT generates and evaluates bit patterns to verifythe proper functioning of all equipped modules.

System Logging and DebuggingIn addition to monitoring extensive statistical data, theAlcatel-Lucent 7510 MGW supports a complete set ofdiagnostic features.

Performance ManagementThe Alcatel-Lucent 7510 MGW assesses its ability to carryout all activities by continuously collecting and analyzingstatistical data related to key functions.

Security ManagementThe Alcatel-Lucent 7510 MGW contains transport layer anduser account security mechanisms.

OAM InterfacesThe Alcatel-Lucent 7510 MGW can be managed using thetext-based CLI or the GUI-based Alcatel-Lucent 7510MGEM.

Software Upgrade ManagementThe Alcatel-Lucent 7510 MGW incorporates a hitlesssoftware upgrading process.



8.2 Chassis ManagementThe Alcatel-Lucent 7510 MGW contains a high-level chassismanagement system that operates from the active SystemControl Module. When power is applied to an Alcatel-Lucent7510 MGW, both the active System Control Module and thestandby System Control Module are powered up simultaneously.The System Control Module in slot 10 becomes the activemodule and the System Control Module in slot 11 becomes thestandby module.

Information concerning static IP configurations, routing protocolconfigurations, static routes, and Address Resolution Protocolentries are stored in a configuration file in the System ControlModule. The active System Control Module is able to reset,reboot, or power down any module. When changes or softwareupdates occur, the System Control Module informs all othermodules and registered application programs about the changein state of an active module. The System Control Module alsodetects fan or power supply fault indications, and generatesappropriate alarms.

When power is applied to an application-specific module in anAlcatel-Lucent 7510 MGW, it sends a request to be identified tothe active System Control Module, which responds by sending acopy of application software (image) back to the requestingmodule. The application-specific module connects to the packetswitch fabric (c-PSF) of the active System Control Module, loadsthe runtime application software, initializes the runtimeapplication, and changes to a runtime state. After reaching theruntime state, each module reports its hardware configuration tothe System Control Modules using the packet switch fabric.

Information sent from each module to the active System ControlModule is duplicated in the standby System Control Module. If afault condition should occur, a module can be hard or soft reset.Each module failure is processed in a manner that minimizes itsimpact on active calls and overall system performance.



8.3 Configuration ManagementThe configuration database, which is stored in files in the FlashMemory of the System Control Module, maintains allAlcatel-Lucent 7510 MGW configuration information. Theconfiguration database is maintained by a software processcalled CDBM, that is stored and runs in the System ControlModules. The CDBM is responsible for collecting, storing, anddistributing configuration information inside of an Alcatel-Lucent7510 MGW; the CDBM is also able to save and restore theconfiguration of the entire Alcatel-Lucent 7510 MGW, or anyindividual module in the gateway.

During power-up, the CDBM stored in the active System ControlModule restores the entire Alcatel-Lucent 7510 MGWconfiguration; it sends global configuration and module-specificconfiguration information to each module, as the modulesbecome operational.

The CDBM stored in the active System Control Module supportsread and write access to the configuration file stored in Flashmemory; it also ensures that the CDBM stored in the standbySystem Control Module synchronizes with the latest configurationat all times. If the active System Control Module fails, the standbySystem Control Module immediately takes over.



8.4 Fault ManagementFault management concerns detection, isolation, and correctionof abnormal operations in an Alcatel-Lucent 7510 MGW. Inaddition to reporting functions, fault management performs faultcorrection, as well as alarm surveillance, during whichcontinuous monitoring occurs to detect failures.

Fault localization is performed when the root cause of a failurehas been isolated.

Testing procedures are also used to validate reports or verifyrepair actions after they have been completed.

8.4.1 Fault Management Application Manager

The FTAM software performs fault detection, fault notification,fault isolation, and service restoration in an Alcatel-Lucent 7510MGW. The FTAM is a collection of hardware and softwarecomponents that are distributed throughout the Alcatel-Lucent7510 MGW, comprising microprocessor-controlled modulemanagers on each application-specific module. These modulemanagers control system start-up, sense hardware status, andmeasure internal temperatures.

The FTAM software performs fault detection and managementpertaining to the following situations:

Module management, tracking module state Non-revertive, hitless switchover to backup module, if

required Power failure Fan failure Module above temperature.

Each Alcatel-Lucent 7510 MGW software component registerswith the FTAM to identify events to be monitored. When a fault isdetected, the FTAM notifies all applications that have registeredfor that type of event. The FTAM and application programs theninitiate corrective actions. The FTAM software in the activeSystem Control Module generates alarms to the networkmanagement system when faults occur.



8.4.2 Monitoring and Alarms

The Alcatel-Lucent 7510 MGW issues alarms when detectingfaults, or when thresholds have been exceeded; it also clearsalarms when fault conditions cease to exist.

Alcatel-Lucent 7510 MGW alarms can be caused by physicalconditions (e.g., alarm of a physical link) or by environmentalconditions (e.g., high temperature alarm).

Alarm forwarding is done using SNMP traps (generated basedon fault localization principles). In parallel, the Megaco protocol isused to report erroneous resources.

The Alcatel-Lucent 7510 MGW alarm priorities are minor, major,or critical. Depending on the alarm type, the alarms can bepresented in a textual, audible or visual way.

The alarm system supported by the Alcatel-Lucent 7510 MGWincludes:

Visual alarms, displayed on Light Emitting Diodes (LEDs)

Alarms reported using an internal audible alarm speaker

Alarms reported using a remote audible alarm speaker

A mechanical ACO switch

All SONET/SDH interface alarms

Power feed failure alarms

SNMP trap to send Alcatel-Lucent 7510 MGW related alarmsto the remote alarm manager [Convergent networkManagement Center (CMC), Alarm View].

Alarms indicating a loss of synchronization at the broadbandor narrowband interface

Service change messages reported to a softswitch using theMegaco protocol.



8.4.3 Alarm Classifications

The Alcatel-Lucent 7510 MGW supports the following alarmseverity classification (in accordance with X.733):

Critical

Major

Minor

Warning

Information

The severity of alarms is configurable to adapt to customerclassification.

Additionally, the Alcatel-Lucent 7510 MGW supports the followingalarm types (in accordance with X.733):

Communication

Quality of Service

Processing Error

Equipment

Environmental

The visualization and management of alarms is performed by theElement Management System (for details, see Section 8.9.2).



8.5 Diagnostic Test – BERTThe Alcatel-Lucent 7510 MGW provides internal Bit Error RateTest (BERT) capabilities. The BERT generates and evaluates bitpatterns to verify the proper functioning of all equipped modules.All the components of the data path are covered by the test. Toidentify potential defects, the BERT can be focused on specificfunctions or modules.

SYSLOG

Megaco DebugLogging

SIGTRAN DebugLogging



8.6 System Logging and DebuggingFor logging purposes, event, message and UI-interface loggingcan be enabled per UI for Megaco or SIGTRAN.

To record user interface activities at the command line interface(CLI) events are reported to a pre-configured syslog server. Thesyslog format is complaint to IETF RFC 3164 and includes:

The user responsible for the event

The system hostname

The date and time of the event

Following events are reported:

Enabling and disabling of the auditing process

Any changes to the type of events logged by the audit trail

Start-up parameters and any changes to them

System or application start-up and shut-down

Login attempts (e.g., wrong userid or password) and loginpatterns

Rejected access attempts because of insufficient authority

All usage by privileged users (e.g., users with powerfulaccess to system utilities or applications)

Use of selected transactions

Use of sensitive resources (e.g., access to highly sensitivedata)

Changes to user privileges

ACL violations.

Furthermore all alarms (per default reported by SNMP to thealarm manager) can be forwarded to the syslog-server.

The logging provides following details using Megaco:

physical trunk number

termination id

events

incoming/outgoing message ID for Megaco

The logging provides following details using SIGTRAN:

D–channel number

User InterfaceLogging



interface–ID

incoming/outgoing message ID for SIGTRAN

User Interface (UI) logging has two variants

Command Line Interface (CLI) logging

Simple Network Management Protocol (SNMP) logging

A circular (FIFO) buffer is used. The maximum buffer sizecan be allocated according to the size of the flash disk(up to 1 GB).



8.7 Performance ManagementThe performance of the Alcatel-Lucent 7510 MGW is monitoredusing a comprehensive set of performance-statistic counters (fordetails of the list of performance counters, see Section 8.7.1).

A historical view of the Alcatel-Lucent 7510 MGW performance isprovided by monitoring the performance counters over a periodof time. Events are allocated to ”buckets” where each bucketrepresents an interval of time. For each performance value 96buckets are provided. These 96 buckets represent a 24 hourperiod with 15 minute default intervals. After post processing, thisdata can be used, e.g., at network management level.

Separate tables are kept for the current interval, the historyintervals, and the total aggregates (RFC3593). This data can bedisplayed at the MGEM (GUI) or can be obtained via SNMP(MIB).

8.7.1 Performance Counters

The following performance counters are available in theAlcatel-Lucent 7510 MGW:

System Performance Counters:

CPU load (Media Gateway and Signaling Gateway)

Memory usage (Media Gateway and Signaling Gateway)

Internal Resource Counters (busy/idle/out ofservice/disabled)

DSP Capacity utilization

PIM utilization (Packet-interface))

TDM link utilization

Service utilization (type of Codec used)

IP-Interface statistics (packet sent/received)

Signaling Interface (H.248 and Sigtran command statistic)

TDM Performance Counters according to G.826/828

EB (Errored blocks)

BBE/CV (Background Block Error/Coding Violation)

ES (Errored Second)

ESB/BES (Errored Second Typ B, only T1)

SES (Severely Errored Second)



UAS (Unavailable Second)

FC (Failure Count)

SEFS (Severely Errored Framed Second)

PSC (Protection Switching Count)

8.7.2 Threshold Crossing Alarms

To indicate critical conditions at the Network Management level,the Alcatel-Lucent 7510 MGW generates alarms (SNMP traps) ifa configurable threshold for a performance counter is exceededor has fallen below.

8.7.3 Call-Related Performance Counters – H.248.xnq

Performance monitoring data, on a per-call basis, can beretrieved from the H.248 interface for further processing and asan extension of the Call Detail Record (CDR).

The usage metrics: packets sent/received, Jitter andPacket-Loss are provided by the H.248 network and RTPpackages. For enhanced quality metrics, theAlcatel-Lucent 7510 MGW provides H.248.xnq(IP-Delay-Variation, Round-Trip-Delay, Jitter buffer adaptions)based on the RTCP–XR (RFC3611) Block-type 8. Furthermore,with H.248.xnq one system can provide the metrics for itself andthe corresponding peer.

Access ControlList – ACL

EncryptedAccess

PasswordSecurity

User AccountLocking



8.8 Security ManagementThe following security mechanisms are implemented in theAlcatel-Lucent 7510 MGW:

Transport Layer Security

User Account Security

8.8.1 Transport Layer Security

The following transport-layer security mechanisms are available:

The Alcatel-Lucent 7510 MGW provides (per IP-filtering) apowerful feature limiting access to OAM functions per remoteIP-address-range.

Encrypted user access is available via a built-in IPsec functionfor the CLI interface and SNMPv3 for the MGEM.

Alternatively SSH can be used for the CLI interface. SSH usesdata encryption and Message Authentication Codes (MACs) toprovide confidentiality of data. It uses public-key cryptography forauthentication.

8.8.2 User Account Security

The main user account security features are:

Password Security

User Account Locking

Command Privileges

Password management features include:

Forced change of default passwords

Strong password syntax (using special characters)

User account locking features are:

User account locking after a configurable amount of faultylog-ins (including logging of all faulty log-ins)

User account locking after expiry of a configurable passwordage

An admin user can set an immediate user account lock.

User AccountPrivileges



The following user account privileges are available:

viewDefault privilege

codeFile handling privilege

updateBoot, save & upgrade privilege

systemConfigure & change settings privilege

passwordUser account management privilege



8.9 OAM InterfacesThe Alcatel-Lucent 7510 MGW can be managed using thetext-based CLI or the GUI-based Alcatel-Lucent 7510 MGEM.The Alcatel-Lucent 7510 MGW host software contains anembedded SNMP agent and supports a complete list ofstandards-compliant MIBs (including an Alcatel-Lucent MIB, seeAppendix B.4). SNMPv3 or SNMPv1 compliance is configurableusing the SNMP agent.

The SNMP protocol is used for communication between theAlcatel-Lucent 7510 MGW host software and the Alcatel-Lucent7510 MGEM. With SNMP, a standardized interface for a thirdparty SNMP browser is offered to report the status of theAlcatel-Lucent 7510 MGW.

The Network Management Layer (NML) integration can be madeusing, either the GUI-based Alcatel-Lucent 7510 MG ElementManagement System or native access to the SNMP objects (seealso Figure 24).

1300 CMC SmartDesktop Based Integration

1300 CMCUnix

3rd Party SNMPBrowser

7510 MGW EMS (GUI-based)

SyslogsCLIInterface

SNMPTraps

SNMPobjectsaccess

SNMPTraps

SNMPobjectsaccess

NML

EML

NE

TelnetSession

7510MGEM

7510MGAM

7510 Media GatewaySNMP v1/v3 Engine

TelnetIP/RS232

SNMPTraps

Figure 24 Element Management Architecture and Interfaces



8.9.1 Command Line Interface

The user-friendly CLI supports access to all the configurationoptions and the diagnostic, performance, fault and securityfunctions. Intuitive handling is supported by offering availableoptions at all command/parameter levels, including help texts foreach command.

The Alcatel-Lucent 7510 MGW CLI can be accessed using IPTelnet sessions or a local console (connecting a craft terminal tothe asynchronous RS-232 port of the Alcatel-Lucent 7510MGW). Additionally, out-of-band connections can be establishedusing either modems or terminal servers to realize remote serialconnections.

The Alcatel-Lucent 7510 MGW supports a maximum of eightsimultaneous logins to the CLI (using a craft terminal or Telnet) .The CLI offers password protection when accessing the networkmanager level or, when performing system administrationactions.

8.9.2 GUI-Based Interface

The GUI-based Alcatel-Lucent 7510 MGEM software provideselement management for the Alcatel-Lucent 7510 MGW EMS.The Alcatel-Lucent 7510 MGW EMS communicates with theSNMP agent to realize comprehensive, remote elementmanagement of the Alcatel-Lucent 7510 MGW.

The Alcatel-Lucent 7510 MGW EMS features Java-basedsoftware that runs on Microsoft NT and Sun Solaris UNIXplatforms. The Alcatel-Lucent 7510 MGW EMS supplies theflexible service capabilities that large and growing networkservice providers require, while reducing network managementcomplexity; it offers an easy-to-use GUI and a comprehensivesuite of element management applications to facilitate:

Real-time utilization and traffic monitoring Performance monitoring Alarm surveillance and reporting System and Interface configuration Services.

The Alcatel-Lucent 7510 MGW EMS includes the followingapplications:

Media Gateway Element Manager (MGEM) Media Gateway Alarm Manager (MGAM)



MGEMThe main application window of the MGEM is the Gateway View(see Figure 25). The Gateway View is the starting point for allAlcatel-Lucent 7510 MGEM applications and utilities. The mainwindow displays the Alcatel-Lucent 7510 MGW being managed,complete with real-time updates of hardware modules,connectors, and status LEDs. The menu bar and tool bar provideaccess to all Alcatel-Lucent 7510 MGEM applications. MGEMfeatures include the following:

Display system and Interface status information

Display system and Interface statistics:

H.248 commands and errors

IP and Ethernet statistics

SNMP statistics

SIGTRAN statistics

Hardware and software version upgrade management

Configuration options for each interface, SNMP and systemparameters

Monitoring and logging of the following information on a pergateway basis (for an example, see Figure 26):

Resource use:

Number of busy/idle/down/disabled DSP, UDP andTDM ports

Media Gateway: CPU load and memory usage

Signaling Gateway: CPU load and memory usage

Chassis management data

Power supply data

User account management with three levels of authority:

Administrator (full access)

Operator (read and write access)

Viewer (read access only)

On-line help



Figure 25 MGEM: Example of Main Window



Figure 26 MGEM: Example of E1 Links Display

MainActive-Alarm

Window



MGAMThe MGAM displays and acknowledges SNMP alarms generatedby the SNMP agent in an Alcatel-Lucent 7510 MGW and sent bySNMP traps.

MGAM features include:

Manual alarm management

Alarm filtering

Optional alarm resource hierarchy

Storage option of Alarm View profiles

Storage option of Alarm Log-files

On-line help

There are multiple alarm views, including:

Main Active-Alarm Window, containing operator-definedfiltered/non-filtered active alarm views. The following filteroptions are available:

Date and time range

Source

Alarm severity

Event type

Probable cause

Trap ID

Alarm Archive View, containing the cleared andacknowledged alarms

The Main Active Alarm Window shows the active alarms (seeFigure 27). Active alarms are received only for configured hosts.Active alarms are sorted in the order given by the time-stamp ofthe alarm. Alarms are shown in the active alarms table until theyare acknowledged and cleared or until they are purged.

Alarm ArchiveView



Figure 27 Alarm Manager: Example of a Main Active Alarm Window

The acknowledged and cleared or purged alarms can be viewedin the Alarm Archive View window (see Figure 28). The alarmhistory is a static table that can be updated by a manual refresh.The alarms are displayed in the sequence they were received.

Figure 28 Alarm Manager: Example of an Alarm Archive View



System RequirementsThe Alcatel-Lucent 7510 MGEM runs on PC and UNIX platforms.System hardware and operating system requirements are listedin Table 17 and Table 18.

Table 17 Alcatel-Lucent 7510 MGEM HardwareRequirements

PC Hardware UNIX Hardware

200 MHz Pentium II processor SUN Sparc 10 or higher model

64 MB RAM, 20 MB hard disk space 128 MB RAM, 20 MB hard diskspace

Super Video Graphics Array (SVGA)monitor with 256 colors minimum withscreen resolution set to at least800 x 600

Network card or modem card Network card or modem card

Table 18 Alcatel-Lucent 7510 MGEM Software Requirements

PC Software UNIX Software

Microsoft NT Workstation or Server4.0 with Service Pack 5 or later

Sun Solaris 2.5.1 or later

Installed TCP/IP client software

8.9.3 RADIUS User Account Management

To realize centralised administration of user accounts theAlcatel-Lucent 7510 MGW supports the Remote AuthenticationDial In User Service (RADIUS) protocol, to performauthorisation/authentication/accounting by support of a remoteserver (RFC2865, RFC2866). For authorization six privileges canbe signaled by use of the “vendor specific attribute” withinRADIUS protocol.

In case no RADIUS server is availabel the system providesemergency user accounts stored in the 7510 MGW’s local userdatabase.

The RADIUS protocol, used between the RADIUS client, locatedin the 7510 MGW, and the remote RADIUS server does nottransmit passwords in cleartext, but in hidden, using a rather



complex operation instead, which involves MD5 hashing andshared secret.



8.10 Software Upgrade ManagementThe Alcatel-Lucent 7510 MGW incorporates a hitless softwareupgrading process. A hitless software upgrade is a mechanismwhich ensures compatibility of inter-board data exchangebetween entities having different Software (SW) versions.

Note The following restrictions must be taken intoconsideration:

Hitless software upgrading is not applicable forSIGTRAN and CAS configurations, and for E1/T1interfaces.

For configurations operating in n+1 redundancy,before the actual hitless software upgrading, theconfiguration has to be modified to 1+1redundancy, and around 50% of the MediaGateway resources have to be gracefully takenout of service.

It is recommended to start a hitless softwareupgrade during a low traffic period (maximum30% of the nominal load).

9 Physical Architecture and Hardware



This chapter provides information concerning the physicalarchitecture of the Alcatel-Lucent 7510 MGW and its relatedhardware.


Introduction

Chassis Internal and External Features

Functional Description of Hardware Modules



9.1 IntroductionThis section describes a single Alcatel-Lucent 7510 MGW, aswell as a rack configuration containing as many as threeAlcatel-Lucent 7510 MGWs in one rack.

The configuration and hardware modules installed in anAlcatel-Lucent 7510 MGW are described separately in theremainder of this chapter.

9.1.1 Single Alcatel-Lucent 7510 MGW Configuration

A single Alcatel-Lucent 7510 MGW consists of the followingcomponents:

One NEBS Level 3 compliant chassis, designed to meetinternational power, grounding, and shielding requirements

A high-speed midplane that interconnects all Alcatel-Lucent7510 MGW modules

Three fan trays

One air filter

As many as 16 application-specific modules which provideinterface or media processing services; these modules are:

Circuit Interface Module Media Conversion Module Packet Interface Module.

The two duplicated system modules provide managementand switching services ; these modules are:

System Control Module Switch Fabric Module.

The chassis is fitted with 20 vertical slots, which are divided bythe midplane. Each application-specific module consists of aprocessor board that is installed from the front of the chassis,and an I/O board that is installed from the rear of the chassis.

Figure 29 shows a front view of the Alcatel-Lucent 7510 MGW.



Processor Board

UPD_0254_7510_front_view_ed01

Fan Trays

Figure 29 Alcatel-Lucent 7510 MGW Front View

Figure 30 shows a rear view of the Alcatel-Lucent 7510 MGW.



UPD_0264_7510_rear_view_ed01

I/O Boards

Figure 30 Alcatel-Lucent 7510 MGW Rear View

Of the 20 slots available, four slots are dedicated to hold twoSwitch Fabric Modules, and two System Control Modules. Tomaximize the Alcatel-Lucent 7510 MGW port density, theremaining 16 generic slots can be filled using Media ConversionModules, Packet Interface Modules, or Circuit Interface Modules.

Each board that is inserted into the Alcatel-Lucent 7510 MGWchassis has a fully redundant Ethernet MAC connection.Connections to the System Control Module switch fabrics (thec-PSFs) allow communication with the control plane, whileconnections to the packet switch fabrics on the Switch FabricModules (the d-PSF) provide the packet switch used to transferdata in the data plane; these connections are made at themidplane.

Each module has its own power circuit and distribution, supplied,for example, by the distributed –48 V or –60 V DC exchangepower sources.

Figure 31 shows a side view of the Alcatel-Lucent 7510 MGW.



0271_chassis_side_ed01

Fan Trays

Processor Boards

Air Deflector Air Filter Power Supply Cage

Cable Trays

I/O Boards

Front Rear

Midplane

Figure 31 Alcatel-Lucent 7510 MGW Chassis, Side View



9.1.2 Rack Configuration

The Alcatel-Lucent 7510 MGW is rack-mountable in standard19 inch, 23 inch, or 600 mm equipment racks.

The chassis height, 14 U (7 feet = 43 U), is designed to achievemaximum packing per Telco frame. As many as threeAlcatel-Lucent 7510 MGWs can be installed in a 7 foot Telco rack(see Figure 32). The remaining space is used to install extraequipment, like fuse panels or cabling brackets. All connectorsare accessible from the front of the gateway.

Figure 32 Rack Configuration

Side View

Front View



9.2 Chassis Internal and External FeaturesThe Alcatel-Lucent 7510 MGW chassis can be characterized bydescribing its internal and external features. Following adescription of the chassis, the following features will be describedin detail:

Cooling Power Source and Distribution Electro Magnetic Compatibility (EMC).

9.2.1 Chassis

The Alcatel-Lucent 7510 MGW is a powerful, compact,standalone media gateway designed to comply with NEBS,Level-3 requirements.

The chassis contains a midplane that connects processor boardsinstalled in the front of the chassis to I/O boards installed in therear of the chassis.

Figure 31 shows a side view of the chassis.

The chassis supports 20 processor boards and 20 I/O boards.The processor boards are plugged into the midplane from thefront, the I/O boards from the rear. The I/O boards have to beplugged into the midplane as an extension of the processorboard, i.e., in the same slot from the rear of the chassis.

All processor boards are accessible from the front of the chassis,which has no doors or cover panels. There are 18 slots having awidth of 21 mm, and 2 slots in the middle having a width of30 mm to accept the System Control Modules.

Figure 33 shows a front view of the chassis.

Rear View



0261_chassis_front_view_ed01

Fan AlarmLED

FANConnector

Midplane

Figure 33 Alcatel-Lucent 7510 MGW Chassis, Front View

All I/O boards are accessible from the rear of the chassis, whichhas no doors or cover panels. There are 18 slots having a widthof 21 mm, and 2 slots in the middle having a width of 30 mm.

Figure 34 shows a rear view of the chassis.

Air Flow



Power Connections

0265_chassis_rear_view_ed01

Midplane

Figure 34 Alcatel-Lucent 7510 MGW Chassis, Rear View

9.2.2 Cooling

The Alcatel-Lucent 7510 MGW chassis is fitted with threefan-trays, which are located at the top of the chassis. The threefan-tray design provides redundant fans and reduces noiselevels.

The gateway draws air from the bottom front and sides of thechassis toward the top of the chassis, and exhausts air throughvents located at the top front and rear of the chassis.

Figure 35 shows the air flow though an Alcatel-Lucent 7510MGW.



Air Intake

Air Filter

Fan Units

Air Output

0268_air_flow_ed01

Figure 35 Air Flow through an Alcatel-Lucent 7510 MGW

Fan Trays



Each fan-tray (VS3FU) consists of three DC fans, see Figure 36.

Alarm Board Fan Unit

AlarmConnector

PowerConnector

Guide Pin

0263_vs3fu_ed01

Metallic Grid

Figure 36 Fan Tray (VS3FU) Physical View

Two of the fans in each of the three fan trays operate at variablespeed. They operate only at maximum speed if one of the traysis not operational. The Alcatel-Lucent 7510 MGW can runindefinitely with only two of the three fan-trays operational. If afan fails, an alarm is sent using the network managementinterface.

Air Filter

Power SourceConnection



An air filter is located at the lower front of the chassis, just underthe slides used to hold the processor boards (see Figure 37).

Air Filter

Filter Fixing Screws Removable Front Plate Air Inlet Holes

0252_air_filter_ed01

Figure 37 Position of the Air Filter

The air filter can be replaced while the system is running.

9.2.3 Power Source and Distribution

The Alcatel-Lucent 7510 MGW supports dual-feed power inputs(A and B). If either the “A” source or the “B” source fails, allAlcatel-Lucent 7510 MGW functions continue to operate from theremaining power source.

The power source must be in the range from –48 V DC to –60 VDC within standard tolerances (–38.4 V to –72 V DC). Thisallows –48 V or –60 V DC distributed exchange power sources tobe used.

Figure 38 shows the power source connections, located on therear of the Alcatel-Lucent 7510 MGW chassis.



GroundConnection

Switch BPower Terminal

Block

Switch A

0270_power_connection_b_ed01

ESD Wrist Strap

Figure 38 Alcatel-Lucent 7510 MGW Power Connections

9.2.4 EMC

The Alcatel-Lucent 7510 MGW chassis is designed to form aFaraday cage around the entire active electronic circuitry. ThisFaraday cage is realized by the metal chassis construction andthe use of continuous frontplane gasket material for theprocessor and I/O boards. All cables passing through the faradaycage are manufactured with the required shielding.

The main chassis (creating the faraday cage) is grounded usinga mounted ground cable located at the rear of the chassis.

Processor Board



9.3 Functional Description of Hardware ModulesFunctionally, hardware modules consist of two different types ofboard, i.e., the:

Processor Board I/O Board.

The processor boards contain all components required toperform functional tasks, e.g., the Packet Interface Modulefunctions.

Electrical or optical interfaces are not located on processorboards, instead, they are located on their corresponding I/Oboards.

Processor boards are always inserted from the front of thechassis, while their corresponding I/O boards are inserted fromthe rear of the chassis.

Figure 39 provides a generic view of a processor board.

LEDs

Metallic Frontplate

Handle with Fastener

Vertical Stiffener

0267_process_view_ed01

Locking Screw

Guide

Figure 39 Generic View of a Processor Board

I/O Board

General BoardFeatures



Figure 40 provides a generic view of an I/O board.

Vertical Stiffener

Metallic Frontplate

I/O Connectors

Handle with Fastener

0266_io_board_view_ed01

Locking Screw

Guide

Figure 40 Generic View of an I/O Board

The boards are held in position by two handles having metalfasteners at their ends. When the boards are inserted, thehandles are moved into place, and afterward fixed by screws tolock the fasteners in place.

The frontplane of the boards has an EMI gasket on its bottomside that ’closes’ the faraday cage.

A guide supports each board as it is inserted into its correctlocation in the midplane.



9.3.1 System Control Module

The System Control Module consists of the following hardware:

Processor boardVBSCM / VBSCM2 (VBSCM2 with or without SFW)

I/O boardsVMSCM

The VMSCM board can access the external SSU, whichprovides an external signal used to support network timingsynchronization when the gateway is being operated withanalog synchronization (i.e., a 2,048 MHz clock signal), or itcan access the external BITS which provides an externalsignal used to support network timing synchronization whenthe gateway is being operated with digital synchronzation(i.e., a clock with 1,544 Mbit/s DS1 signal or 2,048 Mbit/s).

VMSCMA

The VMSCMA board not only accesses the SSU or BITS towork with different external network timing systems; it alsocontains alarm processing circuitry that operates an LED(which shows green or red, red indicating an alarm) and anacoustic buzzer, which buzzes when an alarm is set.

Because an Alcatel-Lucent 7510 MGW is always equipped withtwo System Control Modules, one VBSCM must be associatedwith the VMSCM and the other with the VMSCMA.

Processor Board



Figure 41 shows a front view of the VBSCM, and its location inan Alcatel-Lucent 7510 MGW.

UPD_0308_scm_in_chassis_ed01

Figure 41 Front View and Location of the VBSCM

I/O Boards



Figure 42 shows a rear view of the VMSCM and VMSCMA, andtheir locations in an Alcatel-Lucent 7510 MGW.

0261_vmscm_a_in_chassis_ed01UPD_

ACO

External alarm interface

Figure 42 Rear View and Location of the VMSCM/VMSCMA

The SCM I/O board has the following interface connections (seealso document “Installation and Configuration Guide” – Section:“Connecting the Network Cables”)

Alarm connectorExternal alarms

External reference clockExternal BITS or SSU clock (RJ48 connector)

MGC and OAM connectorEthernet connection 10/100 BaseT to MGC and OAMterminal (RJ45 connector)

Serial interface connectorSerial interface (e.g. Telnet on a Personal Computer)

Processor Board



9.3.2 Switch Fabric Module

The system Switch Fabric Module consists of the followinghardware:

Processor boardVBSFM

AND

Filler panel I/O boardVMDMY20

OR

Maintenance I/O boardVMCDA

Figure 43 shows a front view of the VBSFM, and its location in anAlcatel-Lucent 7510 MGW.

UPD_0255_sfm_in_chassis_ed01

Figure 43 Front View and Location of the VBSFM

I/O Board



The SFM can be equipped with a filler panel or a maintenanceI/O board, i.e., a VMCDA board.

The VMCDA provides a serial port for those processor boards(SFM and MCM) which do not have a corresponding I/O board. Itis required for maintenance operations, e.g., to upgrade firmwareand for enhanced debugging. The VMCDA provides the sameport as the I/O boards of SCM, CIM and PIM.

It is recommended to equip each chassis with one VMCDA boardfor fast access in case a maintenance operation is required, butnot necessary for normal operation.

Processor Board




The Circuit Interface Module has two variants:

SDH Circuit Interface Module (STM–1/OC3)

PDH Circuit Interface Module (E1/T1 and DS3)

SDH Circuit Interface ModuleThe SDH Circuit Interface Module consists of the followinghardware:

Processor boardVBC4S1

I/O boardVM4S1SS / VMCIM

Figure 44 shows a front view of the VBC4S1, and itsrecommended locations in an Alcatel-Lucent 7510 MGW.

UPD_0258_cim_in_chassis_ed01

Figure 44 Front View and Location of the VBC4S1

CIM I/O Board fora 1+1

configuration



Figure 45 shows a rear view of the VM4S1SS, and its locationsin an Alcatel-Lucent 7510 MGW.

UPD_0260_vm4s1ss_in_chassis_ed01

Figure 45 Rear View and Location of the VM4S1SS

The SDH CIM I/O board for a 1+1 configuration has the followinginterface connections (see also document “Installation andConfiguration Guide” – Section: “Connecting the NetworkCables”)

Four duplex T-SC connectors (single-mode fiber)Four STM-1/OC-3 interfaces (compliant to ITU-T G957)with APS (bi-directional, linear and non-revertible)



Table 19 and 20 show the transmitter and receiver performanceof the SDH CIM I/O card.

Table 19 SDH CIM I/O Card: Transmitter Performance

Parameter Symb Conditions Min. Type Max. Unit

Output mean Power Po –15 –11 –8 dBm

Center wavelength 1261 1310 1360 nm

Extinction Ratio ER 10 dB

Eye diagram According to ITU-TG957 mask

Power supply current lcct 85 130 mA

Table 20 SDH CIM I/O Card: Receiver Performance

Parameter Symb Conditions Min. Type Max. Unit

Sensitivity (beginning of life) Pin PRBS 223-1 NRZ BER< 10–10

–29 31 dBm

Maximum input Power Pmax PRBS 223-1 NRZ BER< 10–10

–7 0 – dBm

Signal detect switching threshold:–> Increasing light

–29 dBm

Signal detect switching threshold:–> Decreasing light

–45 dBm

Link detect hysteresis Pmax PRBS 223-1 NRZ BER< 10–10

1 dB

Power supply current lccr PRBS 223-1 NRZ BER< 10–10

70 100 mA

CIM I/O Board foran n+1

configuration



Figure 45 shows a rear view of the VMCIM, and its locations inan Alcatel-Lucent 7510 MGW.


Figure 46 Rear View and Location of the VMCIM

The SDH CIM I/O board for an n+1 configuration has thefollowing interface connections:

Eight SFP SlotsEight slots) with APS (bi-directional, linear andnon-revertible or revertible).

SFP ModulesTwo SFP modules for single-mode laser with a wavelengthof 1,310 nm and LC connector: intermediate range(IR-1/S-1.1 (15km)) and long range (LR-1/L-1.1 (40km)).

Processor Board



PDH Circuit Interface ModuleThe PDH Circuit Interface Module consists of the followinghardware:

Processor boardVB32E1T1

I/O boardTwo variants:

VM32E1T1

VMRED1 (with relay to protect PDH processor card)

Figure 47 shows a front view of the VB32E1T1, and itsrecommended locations in an Alcatel-Lucent 7510 MGW.


Figure 47 Front View and Location of the VB32E1T1

I/O Board



Figure 48 shows a rear view of the VM32E1T1/VMRED1, and itslocations in an Alcatel-Lucent 7510 MGW.


Figure 48 Rear View and Location of theVM32E1T1/VMRED1

The PDH CIM I/O board has the following interface connections(see also document “Installation and Configuration Guide” –Section: “Connecting the Network Cables”)

T1/E1 connectorsTwo T1/E1 interfaces

PDH Circuit Interface Module (CIM2) for DS3The PDH Circuit Interface Module for DS3 consists of thefollowing hardware:

Processor boardVB12DS3

Processor Board



I/O boardTwo variants:

VM12DS3 (in current release supporting 9 DS3 electricalinterfaces)

VM12DS3R (with relay to protect PDH processor card)

Figure 49 shows a front view of the VB12DS3, and itsrecommended locations in an Alcatel-Lucent 7510 MGW.


Figure 49 Front View and Location of the VB12DS3

I/O Board



Figure 50 shows a rear view of the VM12DS3, and its locations inan Alcatel-Lucent 7510 MGW.

Figure 50 Rear View and Location of the VM12DS3

The PDH CIM I/O board has the following interface connections(see also document “Installation and Configuration Guide” –Section: “Connecting the Network Cables”)

Eighteen DS3 connectorsNine DS3 interfaces

Processor Board




The Packet Interface Module consists of the following hardware:

PIM Processor boardVBPI4GE

OR

PIM Processor boardVBPIxGES

Features supported by the VBPIxGES board and theVBPI4GE board:

BGW application

Multiple IP addresses per ethernet port

Advanced BGW features (e. g., for video streams)

IPv4/IPv6 dual stack

Features supported by the VBPIxGES board:

Can be configured to operate as SGW for M2UA orM3UA protocol.

Features supported by the VBPI4GE board:

Is ready to support up to 4 GE ports with futuresoftware releases.

I/O boardVMPIM

Figure 51 shows a front view of the VBPI4GE / VBPIxGES, andits recommended locations in an Alcatel-Lucent 7510 MGW for aTrunking Gateway configuration.



UPD_0256_pim_in_chassis_ed01

Figure 51 Front View and Location of the VBPI4GE /VBPIxGES

In a BGW configuration the VBPI4GE / VBPIxGES boards can belocated in all slots except in those slots reserved for SCM andSFM boards.

PIM I/O Board forn+1 or 1+1

Configuration



Figure 52 shows a rear view of the VMPIM, and its locations inan Alcatel-Lucent 7510 MGW.

UPD_0259_vm1gem_in_chassis_ed01

Figure 52 Rear View and Location of the VMPIM

The PIM I/O board provides the following interface connections:

Two SFP SlotsTwo SFP slots with LPS (non-revertible)

SFP ModulesTwo different SFP modules for single or multi-mode laserwith a wavelength of 850 or 1310 nm and LC or T-SCconnectors.

1000 Base SX modules (850 nm)

1000 Base LX modules (1310 nm)

Processor Board



9.3.5 Media Conversion Module

The MCM consists of the following hardware:

MCM-2 Processor boardVBMCM7E / VBMCM3E

AND

Filler panel I/O boardVMDMY20

OR

Maintenance I/O boardVMCDA

Figure 53 shows a front view of the VBMCMxE, and itsrecommended locations in an Alcatel-Lucent 7510 MGW.

UPD_0257_mcm_in_chassis_ed01

Figure 53 Front View and Location of the VBMCMxE

I/O Board



The MCM can be equipped with a filler panel or a maintenanceI/O board, i.e., a VMCDA board.

The VMCDA provides a serial port for those processor boards(SFM and MCM) which do not have a corresponding I/O board. Itis required for maintenance operations, e.g., to upgrade firmwareand for enhanced debugging. The VMCDA provides the sameport as the I/O boards of SCM, CIM and PIM.

It is recommended to equip each chassis with one VMCDA boardfor fast access in case a maintenance operation is required, butnot necessary for normal operation.

Abbreviations


Abbreviations

ACELP Algebraic Code Excited Linear Prediction

ACO Alarm Cut Off

ALG Application Layer Gateway

AMC Advanced Mezzanine Card

AMR Adaptive Multi-Rate

AMR–WB AMR Wide Band

APS Automatic Protection Switching

ARP Address Resolution Protocol

AS Application Server

BERT Bit Error Rate Test

BFD Bi–directional Forwarding Detection

BGF Border Gateway Function

BGW Border Gateway

BHCA Busy Hour Call Attempts

BITS Building Integrated Timing Source

CAGW Centralized Access Gateway

CDBM Configuration Database Manager

CDR Call Detail Record

CESoIP Circuit Emulation Service over IP

CHT Call Hold Time

CIM Circuit Interface Module

CLI Command Line Interface

CLIP Calling Line Identification Presentation

CMC Convergent network Management Center

CoAPS Context Attempts Per Second

CPU Central Processing Unit

DCME Digital Circuit Multiplication Equipment

DiffServ Differentiated Services

DNS Domain Name Service

DoS Denial of Service

DRM Dynamic Resource Management

Abbreviations


DS3 Digital Signal 3

DSCP Differentiated Services Code Point

DSP Digital Signaling Processor

DST Daylight Saving Time

DTX Discontinuous Transmission

EFR Enhanced Full Rate

EMC Electro Magnetic Compatibility

EPS Equipment Protection Switching

ESP Encapsulating Security Protocol

ESP Encapsulating Security Payload

ETSI European Telecommunications Standards Institute

FoIP Fax over IP

FR Full Rate

FSK Frequency Shift Keying

FTAM Fault Tolerant Application Manager

FTP File Transfer Protocol

GFI Generic Forwarding Interface

GUI Graphical User Interface

HR Half Rate

HW Hardware

IBCF Interconnection Border Control Function

IGW International Gateway

IM Instant Messaging

IMS IP Multimedia Subsystem

IP Internet Protocol

IPsec IP security

ISC International Switching Center

ISDN Integrated Services Digital Network

LD–CELP Low–Delay Code Excited Linear Prediction

LED Light Emitting Diode

LEX Local EXchange

LPS Link Protection Switching

MAC Medium Access Control

Abbreviations


MACs Message Authentication Codes

MCM Media Conversion Module

MF Multi Frequency

MGC Media Gateway Controller

MGEM Media Gateway Element Manager

MGW Media Gateway

MIB Management Information Base

MIM Media Interface Module

MSP Multiplex Section Protection

MSRP Message Session Relay Protocol

MTBF Mean Time Between Failures

NAPT Network Address and Port Translation

NAT Network Address Translation

NEBS Network Equipment Building System

NGN Next Generation Network

NML Network Management Layer

NTEs Named Telephone Events

NTP Network Time Protocol

OAM Operations, Administration and Maintenance

PBX Private Branch Exchange

PDH Plesiochronous Digital Hierarchy

PIF Port Interface

PIM Packet Interface Module

PRA Primary Rate Access

PSF Packet Switching Fabric

PSTN Public Switched Telephone Network

QoS Quality of Service

RADIUS Remote Authentication Dial In User Service

RCS Rich Communication Suite

RPE-LTP Regular Pulse Excitation – Long Term Prediction

RTCP Real-time Transport Control Protocol

RTCP XR RTCP Extended Report

RTP Real-time Transport Protocol

Abbreviations


SCM System Control Module

SCTP Stream Control Transmission Protocol

SDH Synchronous Digital Hierarchy

SFM Switch Fabric Module

SFW SIP Firewall

SIGTRAN Signaling Transport

SMS System Management Server

SNMP Simple Network Management Protocol

SONET Synchronous Optical Network

SRS System Route Server

SSH Secure SHell

SSM Synchronisation Status Message

SSU Synchronization Supply Unit

SVGA Super Video Graphics Array

SW Software

TCF Training Check Frame

TCP Transmission Control Protocol

TDM Time Division Multiplex

TGW Trunking Gateway

TOS Type Of Service

UDP User Datagram Protocol

UI User Interface

VAD Voice Activity Detection

VBD Voice Band Data

VLAN Virtual Local Area Network

VMG Virtual Media Gateway

VoIP Voice over IP

VoP Voice over Packet

WAN Wide Area Network

XML eXtended Markup Language

Appendix A Specifications



This Appendix summarizes physical specifications and regulatorycompliance information about the Alcatel-Lucent 7510 MGW.

A.1 Physical Specifications

Table 21 shows the Alcatel-Lucent 7510 MGW physicalspecifications.

Table 21 Alcatel-Lucent 7510 MGW Physical Specifications

Specification Description

Dimensions Height: 62.2 cm (14 RU) (1 RU = 44.45 mm)

Width: 45.7 cm (18 inch)

Depth: 53.3 cm (21 inch)

Weight 68 kg (150 lbs.) fully configured

Supported Racks Up to three Alcatel–Lucent 7510 MGWs canbe installed in one of these racks:

7 feet x 19 inch Network EquipmentBuilding System (NEBS) standardscompliant rack

2200 mm (H) x 600 mm (W) x 600 mm(D) European TelecommunicationsStandards Institute (ETSI) rack

Operating TemperatureRange

0 C to 40 C (32 F to 104 F)

Storage Temperature Range –20 C to 65 C (–4 F to 149 F)

Operating Humidity 0 to 80 %, noncondensing

Power –48 V DC, –60 V DC

redundant A and B power feeds

1300 W (typically loaded)

1800 W (fully loaded)



A.2 Compliances and Requirements

Table 22 shows the compliances and requirements of theAlcatel-Lucent 7510 MGW:

Table 22 Alcatel-Lucent 7510 MGW Compliances andRequirements

Compliance / Requirement Description

Regulatory Compliance World Market:

EMC : Emission: CISPR 22 class B

EMC : Immunity: IEC 61000-4-2 to -4-6

Safety : IEC 60950-1 (2001)

Eurpean Market (CE Marking):

EMC : EN 300 386 (2001)

Safety : EN 60950-1 (2001)

North American Market:

EMC : FCC Part 15

Safety : UL 60950/ CSA C22.2No.60950-00

NEBS Requirements NEBS level 3 certification

EMC and Safety : GR1089

Environmental conditions : GR63

Environmental Conditions Climatic, Mechanic and Seismic :

Operating conditions : EN 300 019-2-3(2003) [class 3.1 and 3.1E forclimatic tests]

Storage : EN 300 019-2-1 class 1.1

Transportation : EN 300 019-2-2class 2.1

Acoustic :

ETS 300 753

BellcoreSpecifications

TelcordiaSpecifications

Appendix B Standards



Each of the following sections lists the standards supported bythe Alcatel-Lucent 7510 MGW, which include:

Bellcore/Telcordia Specifications ITU Standards ANSI/EIA/IEEE Standards MIBs IETF RFCs.

B.1 Bellcore / Telcordia Specifications

The Alcatel-Lucent 7510 MGW supports the following Bellcorespecifications:

Bellcore GR-63-CORE Bellcore GR-246-CORE Bellcore GR-253-CORE Bellcore GR-472-CORE Bellcore GR-474-CORE Bellcore GR-1089-CORE Bellcore GR-1244-CORE Bellcore GR-1248-CORE Bellcore GR-1275-CORE Bellcore GR-2914-CORE Bellcore SR-3645.

The Alcatel-Lucent 7510 MGW supports the following Telcordiaspecifications:

Telcordia GR-3054-CORE: Voice over Packet, NGN TrunkGateway Generic Requirements

Telcordia GR-3059-CORE: NGN Network PerformanceRequirement

Telcordia GR-3060-CORE: Framework Generic Requirement

Telcordia GR-3070-CORE: NGN Element ManagementSystem Requirement

Telcordia SR-4717: Voice over Packet in Next GenerationNetworks, An Architecture Framework.



B.2 ITU Standards

The Alcatel-Lucent 7510 MGW supports the following ITUstandards:

G.703: Physical/electrical characteristics of hierarchical digitalinterfaces

G.704: Synchronous frame structures used at 1544, 6312, 2048,8448 and 44 736 kbit/s hierarchical levels

G.706: Frame alignment and cyclic redundancy check (CRC)procedures relating to basic frame structures defined inRecommendation G.704

G.711: Pulse code modulation (PCM) of voice frequencies

G.168: Digital network echo canceller

G.3: Universal protocol for sending facsimile

H.248: Series H, Audiovisual and Multimedia Systems, GatewayControl Protocol

B.3 ANSI / EIA / IEEE Standards

The Alcatel-Lucent 7510 MGW supports the followingANSI/EIA/IEEE standards:

ANSI T1.231: Digital Hierarchy – Layer 1 In-Service Digital TransmissionPerformance Monitoring

ANSI T1.107: Digital Hierarchy – Format Specifications

IEEE 802.3: Standard for Carrier Sense Multiple Access with CollisionDetection (CSMA/CD) Access Method and Physical LayerSpecifications

IEEE 802.3u:100BaseT Fast Ethernet System



B.4 MIBs

The Alcatel-Lucent 7510 MGW supports the following MIBsdescribed in SMIv1 according to RFC 1155 & RFC 1212, and,additional definition of traps according RFC1215 :

Alcatel-Lucent MIBenterprise MIB for 7510 specific extensions

RFC 1213Management Information Base (MIB–II) for use withnetwork management protocols in TCP/IP– based internets

RFC 1253OSPF Version 2 Management Information Base

RFC 1389RIP Version 2 MIB Extensions

RFC 1406 Definitions of Managed Objects for the DS1 and E1Interface Types

RFC 1650 Definitions of Managed Objects for the Ethernet–likeInterface Types

RFC 1907 Management Information Base for Version 2 of the SimpleNetwork Management Protocol

RFC 2233 The Interfaces Group MIB

RFC 2558 Definitions of Managed Objects for the SONET/SDHInterface Type

RFC 2571 SNMP–FRAMEWORK–MIB DEFINITIONS

RFC 2572 Message Processing and Dispatching for the SimpleNetwork Management Protocol

RFC 2573nDefinitions of MIB modules for specifying targets ofmanagement operations, for notification filtering, and forproxy forwarding

RFC 2573t ”



RFC 2574 User–based Security Model (USM for version 3 of theSimple Network Management Protocol)

RFC 2575 View–based Access Control Model (VACM) for the SimpleNetwork Management Protocol

B.5 IETF RFCs

The Alcatel-Lucent 7510 MGW supports the following IETFRFCs:

RFC 768: User Datagram Protocol (UDP)

RFC 791: Internet Protocol

RFC 792: Internet Control Message Protocol

RFC 793: Transmission Control Protocol

RFC 826: Ethernet Address Resolution Protocol: Or convertingnetwork protocol addresses to 48 bit Ethernet address fortransmission on Ethernet hardware

RFC 854: Telnet Protocol Specification

RFC 950: Internet Standard Subnetting Procedure

RFC 951: Bootstrap Protocol

RFC 1034: Domain names – concepts and facilities

RFC 1058: Routing Information Protocol

RFC 1122: Requirements for Internet hosts – communication layers.

RFC 1157: Simple Network Management Protocol

RFC 1305: Network Time Protocol (Version 3) Specification,Implementation



RFC 1338: Supernetting: an Address Assignment and AggregationStrategy

RFC 1350: TFTP Protocol (Revision 2)

RFC 1519: Classless Inter-Domain Routing

RFC 1583: Open Shortest Path First Protocol, Version 2

RFC 1780: Internet Official Protocol Standards

RFC 1812: Requirements for IP Version 4 Routers

RFC 2833 / RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, andTelephony Signals

RFC 2598: An Expedited Forwarding PHB

RFC 3015: Megaco Protocol Version 1

Appendix C Components and Part Numbers



This appendix provides a list with Alcatel-Lucent 7510 MGWcomponents and part numbers (see Table 23).

Table 23 Components and Part Numbers

Part Number Description

3FZ 60028 AAXX Chassis Kit for Alcatel-Lucent 7510 MGW

- includes chassis (3FZ 50010 AAXX) plus

one (1) Backpanel (3FZ 40000 AAXX)

and three (3) Fan Tray Units (3FZ 50012 AAXX)

3FZ 60028 ABXX Chassis Kit for Alcatel-Lucent 7510 MGW

- NEBS compliant

- includes chassis (3FZ 50010 AAXX) plus

one (1) Backpanel (3FZ 40000 AAXX)

and three (3) Fan Tray Units metal (3FZ 50012 ABXX)

3FZ 30084 AAXX System Control Module 2 (SCM)

- processor board with Stratum 3 - VBSCM2S3

3FZ 30084 BAXX System Control Module 2 (SCM)

- processor board with Stratum 2 - VBSCM2S2

3FZ 30084 DAXX System Control Module 2 (SCM)

- processor board with Stratum 3, FW - VBSCM2S3-FW

3FZ 30084 EAXX System Control Module 2 (SCM)

- processor board with Stratum 2, FW - VBSCM2S2-FW

3FZ 30017 AAXX System Control Module (SCM)

- I/O board with management, timing interface - VMSCM

3FZ 30021 AAXX System Control Module (SCM)

- I/O board with management, timing and alarm interface - VMSCMA

3FZ 30002 AAXX Switch Fabric Module (SFM)

- processor board - VBSFM

3FZ 30003 AAXX Circuit Interface Module (CIM)

- processor board for 4-port OC-3/STM-1 - VBC4S1


- I/O board with 4-port OC-3/STM-1 interface (optical) - VM4S1SS


- MIM board for 16 optical transceivers (not included) - VMMIM





- processor board for 32-port E1/T1 - VBC32E1

3FZ 30025 ABXX Circuit Interface Module (CIM)

- I/O board with 32-port E1 or T1 interface (electrical) - VM32E1T1


- I/O board without interface for redundancy - VMRED

3FZ 30102 AAXX Circuit Interface Module (CIM2)

- processor board for 12–board DS3


- I/O board with 9–port DS3 interface (electrical)


- I/O board without DS3 interface for redundancy

3FZ 30009 AAXX Packet Interface Module (PIM)

- processor board for 1-port GigEthernet - VBPI1GE

3FZ 30012 AAXX Packet Interface Module (PIM)

- I/O board with 1-port GigEthernet interface (optical) - VM1GEM

3FZ 30086 BAXX Packet Interface Module (PIM)

- MIM board for 4 optical transceivers (not included) - VMPIM

1AB 23890 0002 Optical Transceiver, SFP

- 1310 nm single wavelength - OE-TRX

1AB 23890 0004 Optical Transceiver, SFP

- 850 nm multi-mode - OE-TRX

3FZ 30079 AAXX Media Conversion Module (MCM)

- with 36 DSP (TI C5) - VBMCM7E

3FZ 30079 ABXX Media Conversion Module (MCM)

- with 18 DSP (TI C5) - VBMCM3E

3FZ 30035 AAXX Filling board for Alcatel-Lucent 7510 MGW

- processor board 20 mm - MA-VBDMY20


- processor board 30 mm - MA-VBDMY30


- I/O board 20 mm - MA-VMDMY20


- I/O board 30 mm - MA-VMDMY30

3FZ 30019 AAXX System debug module (SFM, MCM)

- I/O board with craft and debug interface - VMCDA




3FZ 50012 AAXX Fan Tray Unit for Alcatel-Lucent 7510 MGW - EMA-VS3FU

3FZ 50012 ABXX Fan Tray Unit for Alcatel-Lucent 7510 MGW - metal - EMA-VS3FU

1AD 01636 0002 Quadrafoam Air Filter

3FZ 03551 AAXX 7510 SW RTU per VoIP/TDM HP GW session (Min. 32 E1/T1; 1STM-1/OC-3)

including Gateway Element Manager (GUI) - (7510 SW RTU - VoIP)

3FZ 03551 ABXX 7510 SW RTU per MTP2 link

including Gateway Element Manager (GUI) - (7510 SW RTU - M2UA)

3FZ 03551 ACXX 7510 SW RTU per Peering GW session (Min. 1k IP-IP sessions)

including Gateway Element Manager (GUI) - (7510 SW RTU - Peering)

Appendix D Revision History



This appendix lists the revisions to this document.

Table 24 Reason for Revision

Location Description

2.7.9 Section reworded.

Several graphics improved.