1 / 20

OfficeServ Data Server

Enterprise IP Solutions. OfficeServ Data Server. VoIP Service. Mar, 2006 OfficeServ Lab. Samsung Electronics Co., Ltd. Voice & Data Convergence [1]. Requirement of data networking equipment for VoIP service. NAPT, Firewall, IDS/IPS Traversal VPN QoS Etc ?.

josiah
Télécharger la présentation

OfficeServ Data Server

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Enterprise IP Solutions OfficeServ Data Server VoIP Service Mar, 2006 OfficeServ Lab. Samsung Electronics Co., Ltd.

  2. Voice & Data Convergence [1] • Requirement of data networking equipment for VoIP service. • NAPT, Firewall, IDS/IPS Traversal • VPN • QoS • Etc ?

  3. Voice & Data Convergence [2] • What are advantages of convergence ? • Easy Configuration and Maintenance. • Efficient and correct stateful operation for VoIP sesstions. • Potential Advantages. Imagine !!!

  4. Convergence in OfficeServ7400 • Specialized Feature named “VoIP Service” • Focused on … • NAPT auto-conf. • Firewall auto-conf, strong and efficient VoIP packet inspection (like SPI) • QoS auto-conf.

  5. MGI64 MP40 P1 P1 P2 P2 P3 P3 P4 P4 P5 P5 P6 P6 P13 P13 LNK LNK ACT ACT LNK LNK ACT ACT RST RST P7 P7 P8 P8 P9 P9 P10 P10 P11 P11 P12 P12 P14 P14 GLIMP GLIMP P1 P2 P3 P4 P5 LNK ACT SIO P6 P7 P8 P9 P10 GSIM V35 P1 P2 RUN V35 HSSI P1 P2 P3 RST SIO P3 HSSI GWIM V/S Scenario #1. Private Network with F/W ADSL * Frame Relay as Primary WAN connection * xDSL as Back-up WAN connection * One or a few fixed public IP addresses(/32) assigned to the Site. * VLAN1 for 10.0.0.1/24, VLAN2 for 10.0.1.1/24 * Firewall enabled IP Pone ISP2 INTERNET ISPA ISP B OfficeServ7400 ADSL CSU/DSU GWIM VLAN1 GSIM VLAN2 GPLIM MGI64 IP Pone GPLIM IP Pone IP Pone IP Pone IP Pone

  6. MGI64 MP40 P1 P1 P2 P2 P3 P3 P4 P4 P5 P5 P6 P6 P13 P13 LNK LNK ACT ACT LNK LNK ACT ACT RST RST P7 P7 P8 P8 P9 P9 P10 P10 P11 P11 P12 P12 P14 P14 GLIMP GLIMP P1 P2 P3 P4 P5 LNK ACT SIO P6 P7 P8 P9 P10 GSIM V35 P1 P2 RUN V35 HSSI P1 P2 P3 RST SIO P3 HSSI GWIM V/S Scenario #2. Public Network with F/W ADSL • * More than one C class Public IP groups (/24) assigned. • * VLAN1 for 165.213.89.1/24, VLAN2 for 165.213.90.1/24 • * Firewall enabled IP Pone ISP2 INTERNET Metro OfficeServ7400 GWIM VLAN1 GSIM VLAN2 GPLIM MGI64 IP Pone GPLIM IP Pone IP Pone IP Pone IP Pone

  7. MP40 P1 P1 P2 P2 P3 P3 P4 P4 P5 P5 P6 P6 P13 P13 LNK LNK ACT ACT LNK LNK ACT ACT RST RST P7 P7 P8 P8 P9 P9 P10 P10 P11 P11 P12 P12 P14 P14 GLIMP GLIMP V/S Scenario #3. Public and Private Networks with F/W ADSL * More than one C class Public IP groups (/24) assigned. * One private network (192.168.0.1/24) is also employed. * VLAN1 for 165.213.89.1/24, VLAN2 for 192.168.0.1/24 * Firewall enabled IP Pone ISP2 INTERNET Metro OfficeServ7400 V35 P1 P2 RUN V35 HSSI GWIM P1 P2 P3 RST SIO P3 HSSI GWIM VLAN1 [public] GSIM P1 P2 P3 P4 P5 LNK ACT VLAN2 [private] P6 P7 P8 P9 P10 SIO GSIM GPLIM MGI64 IP Pone GPLIM IP Pone IP Pone IP Pone IP Pone

  8. MGI64 MP40 MP40 P1 P1 P1 P1 P2 P2 P2 P2 P3 P3 P3 P3 P4 P4 P4 P4 P5 P5 P5 P5 P6 P6 P6 P6 P13 P13 P13 P13 LNK LNK LNK LNK ACT ACT ACT ACT LNK LNK LNK LNK ACT ACT ACT ACT RST RST RST RST P7 P7 P7 P7 P8 P8 P8 P8 P9 P9 P9 P9 P10 P10 P10 P10 P11 P11 P11 P11 P12 P12 P12 P12 P14 P14 P14 P14 GLIMP GLIMP GLIMP GLIMP P1 P2 P3 P4 P5 LNK ACT SIO P6 P7 P8 P9 P10 GSIM V35 P1 P2 RUN V35 HSSI P1 P2 P3 RST SIO P3 HSSI GWIM V/S Scenario #4. VoIP between OS7400 and OS7400 VoIP Signal (SIP, H323, SPNET] VoIP Media INTERNET ISPA Site B CSU/DSU Metro Site A GWIM VLAN1 V35 P1 P2 GSIM RUN V35 HSSI GWIM P1 P2 P3 RST SIO P3 HSSI GWIM VLAN2 VLAN1 [public] GSIM P1 P2 P3 P4 P5 LNK ACT VLAN2 [private] GPLIM P6 P7 P8 P9 P10 SIO GSIM GPLIM MGI64 GPLIM IP Pone IP Pone IP Pone IP Pone IP Pone IP Pone

  9. VoIP Service Functions • GWIM • Auto-configuration of NAPT for MCP and MGIs. • Dynamic Control of static NAPT and Firewall under development. • GSIM • Auto-QoS supported. • auto-configuration of classification for VoIP traffics • auto-configuration of DSCP Marking for VoIP traffics. • auto-configuration of IEEE 802.1p marking, CoS Mapping for VoIP traffics. • GLIMP • TBD

  10. VoIP Service Internal [1] • IPC • Message exchange via DPRAM • 1 to 1 communication between MCP and other card (IPC among data cards not supported) • Message Types • Request/Reply/Notification. Fig.1 DPRAM map

  11. VoIP Service Internal [2] • V/S IPC Flow MCP Data Module Bootup or V/S Restart 1.Card_status Noti. 2.C/S_status Noti. 3.MCP_Info Req. 4.MCP_Info Rep. 5.Time_Info Req. Only if “Time synch. with C/S” option is on 6.Time_Info Rep. 7.MGI_Info Req. 8.MGI_List_Info Rep. 8-1.MGI_List(#1) Req/Rep Get current DB for MGIs,ITPs,WIPs 8-2.MGI_List(#2) Req/Rep … 8-7.MGI_List(#7) Req/Rep. DB Learning finished 9. DB_Info Noti.

  12. VoIP Service Internal [3] • V/S IPC Flow [Cont.] MCP Data Module 10. Service_Info Req. Current Service Info including NAPT/FW… 11. Service_Info Rep. 12. NAPT_Info Req. If NAT=ON in Serivce_info, IP_Type=Private&Public * Only for GWIM * NAPT Auto-conf. 13-1. MGI_NAPT_Info Rep. 13-2. MGI_NAPT_Info Rep. 13-n. MGI_NAPT_Info Rep. 14. MCP_NAPT_Info Rep. 15. MGI_Info Noti. New MGI/ITP/WIP Info added 16. MGI_Status_info Noti. Existing MGI/ITP/WIP disconnected 17. MGI_Call_Info Noti. Call_Setup(MGI channel) * Static NAPT, F/W opened * Under Implemetation * Only for GWIM 18. MGI_Call_info Noti. Call_Finish (MGI Channel) * Static NAPT, F/W closed After MCP/LCP reset 19. Reset Noti. Restart V/S IPC

  13. VoIP Service Web Management [1] LAN Interface for VoIP Modules WAN Interface for VoIP traffics WAN Interface for data traffics * In case of Multiple WAN Interface, if any interface is set WAN Interface that can be selected for VoIP Service.

  14. VoIP Service Web Management [2] * The [VoIP DB] menu allows displaying the current information on the OfficeServ 7400 System (ex: MCP, MGI, IP Phone, WIP Phone)

  15. VoIP Service Web Management [3] VoIP for dynamic NAPT mapping of media port VoIP Signalling H323 SIP PC-MMC VoIP Media * Configured NAPT list for NAT traversal of inbound VoIP signal, media traffics. * Public IP/Port ranges are automatically notified to MCP and MGIs through IPC. Check the MMC 320, 321.

  16. VoIP Auto-QoS (GSIM) [1] Signal Media VoIP Signal For ITPs, WIPs Media By DSCP MGI MCP For MCP, MGIs MGI MCP * voip_common/system/terminal_classmaps are automatically created by V/S. * In case of V/S DB update, voip_system_classmaps are automatically updated.

  17. VoIP Auto-QoS (GSIM) [2] * Following actions are configured as confirm actions for voip_xxx_classmaps : - insert DSCP 40 - insert 802.1p priority 7 => at least, one VLAN is needed to transmit tagged packets to connected switches. (egress_tagged option)

  18. VoIP Auto-QoS (GSIM) [3] * voip_policymap is applied to all ports by default. * Also, user can replace the voip_policymap with a user-defined policymap.

  19. VoIP Auto-QoS (GSIM) [4] * Not affected by V/S. By default. * By V/S, priority of VoIP traffic is set to 7 and is enqueued to the highest queue (7).

  20. VoIP Auto-QoS (GSIM) [5] * Not affected by V/S. By default.

More Related