580 likes | 802 Views
Introduction to RTG and HVP. sinam.woo@samsung.com Date: 2011.12.16 Revision 1.2. Contents. V4.60 Characteristics RTG HVP Security Appendix NAT Configuration. V4.60 Characteristics. Increase Concurrent Calls RTG Decrease MGI Usage at Paging Service HVP Security Support TLS/ sRTP.
E N D
Introduction to RTG and HVP sinam.woo@samsung.com Date: 2011.12.16 Revision 1.2
Contents • V4.60 Characteristics • RTG • HVP • Security • Appendix • NAT Configuration
V4.60 Characteristics • Increase Concurrent Calls • RTG • Decrease MGI Usage at Paging Service • HVP • Security Support • TLS/sRTP
V4.60 Characteristics (cont.) Concurrent Calls View Concurrent Calls at the hold/ringback state Concurrent Calls At the conversation RTG MPS MPS MGI MGI MGI MGI Before v4.60 v4.60 Before v4.60 v4.60 Assumption: OAS installation or OS7100/7030/7070 system
V4.60 Characteristics (cont.) • Assumption: • All Paging Members are IP phone. • All members are located in same network. • Number of paging member including pager is 20. 20 Number of MGI channels 2 Before v4.60 v4.60
RTG Description • RTG (Real-time Tone Generation) • Support Ringback/Hold Tone Streaming Service • Support RFC 2833 detection service • Used at Mobex. • RTG is served at • OAS Card and Embedded RTG in MP20s/MP10a/OS7030/OS7070 Note) RTG in OAS can be enabled at MP40/MP20/MP20s
No-MGI Operation (incoming call at v4.53) Assumption : Call from SIP Trunk to IP Phone IP Phone OfficeServ SIP/SPNET Trunk Hook On Incoming Ringing Ringing Ringback Tone Stream MGI Hook Off Answer Conversation Voice Stream MPS
No-MGI Operation(incoming call at v4.60) Assumption : Call from SIP Trunk to IP Phone IP Phone OfficeServ SIP/SPNET Trunk MGI is replaced by RTG Hook On Incoming Setup Ringing Ringback Tone Stream RTG Hook Off Answer Conversation Voice Stream MPS
No-MGI Operation (outgoing call at v4.53 and v4.60) Assumption : Call from IP Phone to SIP Trunk IP Phone OfficeServ SIP/SPNET Trunk Hook Off Outgoing Setup Ringing Ringback Tone Stream MPS Answer Conversation Voice Stream MPS
Relation between MPS and RTG Nmax : Number of calls available NMPS: Number of MPS calls used NRTG: Number of RTG channels used Available RTG Channel Available MPS Calls MPS Calls used RTG Channel used
RFC2833 Detection Service MOBEX Executive User 1. conversation MPS 2. hold 3. Transfer tone stream RTG RTG 4. Send RFC833 packet IP Phone 4. Detect RFC833 packet 3. Hold tone stream
How to configure RTG Start DM 2.1.5 MPS Service ? No Yes Set Local RTG port DM 2.2.15 System is NAT ? Set Public RTG port Set NAT machine Yes No DM 5.7.1 Check Cadence End
RTG Configuration RTG Service is available when MPS service is enabled The following figures are captured at OS7400
RTG Configuration (cont.) • RTG Local port is source UDP port about transmitting RTP Stream. • RTG Public port is public UDP port mapped in NAT-machine about RTG Local Port. • e.g) 192.168.41.12/45000 is mapped into 30.0.0.9/45128. • RTG Frame Count means packet interval between RTP packets. Default value is 20ms and Maximum value is 60ms.
RTG Configuration (cont.) • Its information is used for analog devices and RTG. • Cadence value can be changed Column with orange color is read-only.
RTG Status View DM 6.2.10 shows RTG channel information, which includes remote IP/port , codec, tone type.
Trouble Shooting Start DM 6.2.10 No Sound? Info. Is correct ? Check RTG Status Yes No Yes Sound Abnormal ? Adjust RTG Frame Count (20 ~ 60ms) DM 2.2.5 Yes No Capture packet Analyze packet Check packet loss and delay End
Introduction : Unicast Host A Host B 165.213.80.100 Payload Payload Dest: 10.254.176.100 Src : 165.213.80.100 IP Header 10.254.176.100 Packet
Introduction : Multicast (Local-Scope) Host B Receiver 165.213.80.200 L2 Switch Host C Receiver Host A Sender 165.213.80.201 165.213.80.100 Payload Payload Payload Payload Dest: 239.0.0.1 Src : 165.213.80.100 Dest: 239.0.0.1 Src : 165.213.80.100 Dest: 239.0.0.1 Src : 165.213.80.100 Dest: 239.0.0.1 Src : 165.213.80.100 Host D Receiver 165.213.80.202 Multicast Address
Introduction : Multicast (global scope) Note : Router must support multicasting for multicast among networks and host supports IGMP. Mcast Router Router 2. Determine Multicast Route By PIM or DVMRP Host B Host A Sender Mcast Router 10.254.176.100 165.213.80.100 Payload Payload Payload Payload Dest: 239.0.0.1 Src : 165.213.80.100 Dest: 239.0.0.1 Src : 165.213.80.100 Dest: 239.0.0.1 Src : 165.213.80.100 Dest: 239.0.0.1 Src : 165.213.80.100 1.IGMP Join (239.0.0.1) IGMP Join (239.0.0.1) Host D Receiver Host C Receiver 10.254.1.101 10.254.1.100
HVP Description • Hybrid Voice Paging • Voice paging to IP interface is served by the combination of unicast and multicast. Sender Receiver Sender Receiver A D D B E E A C F F Multicast Unicast
HVP Case Study Number of MGI Channels : 1 DGP Phone IP Phone IP Phone MGI IP Phone IP Phone IPT Multicast-Supported IP phone Multicast Stream IPT Unicast Stream Multicast-Unsupported IP phone
HVP Case Study (cont.) Number of MGI Channels : 2 DGP Phone IPT IPT MGI #2 MGI #1 IPT IPT IPT Multicast-Supported IP phone Multicast Stream IPT Unicast Stream Multicast-Unsupported IP phone
HVP Case Study(cont.) Number of MGI Channels : 2 DGP Phone Multicast Router IPT IPT MGI #1 MGI #2 IPT IPT IPT Multicast-Supported IP phone Multicast Stream IPT Unicast Stream Multicast-Unsupported IP phone
HVP Case Study(cont.) Number of MGI Channels : 1 IPT DGP Phone Multicast Router IPT IPT MGI #1 IPT IPT IPT IPT Multicast-Supported IP phone Multicast Stream IPT Unicast Stream Multicast-Unsupported IP phone
How to configure HVP Start IP phones support multicast? All member is co-located with system ? There are Members in multicast network ? DM 2.8.0 Yes No Yes Set Feature Code Yes No No Set Multicast Page to be Auto/Enable DM 2.7.1 Set Page member DM 4.1.3 Set Multicast Page to be Auto/Disable There are IP phones ? Yes Check router configuration No Set IP network End DM 5.2.25 Set Multicast Page to be Auto/Enable DM 2.7.1
HVP Configuration(cont.) Multicast Address : 224.0.0.1 ~ 239.255.255.254 Add Page Member
HVP Configuration(cont.) The field indicates paging option Auto: System automatically determine whether multicast can be used or not. (If ITP is co-located with system’s network or is located into multicast network in DM 5.2.25, multicast is served. ) Enable: Multicast is manually served Disable: Unicast is manually served
HVP Configuration(cont.) The field indicates the network address which multicast is available and ITPs are located. It is not related with multicast address.
Trouble Shooting Start DM 2.7.1 ITP type and version support multicast ? Check Multicast Address and Paging setting ? Yes Yes DM 4.1.3 No Error Check Router and Switch? Yes Change S/W and Device Error Change configuration Change configuration End Change Disabled
Example: Multicast Configuration at GWIMT Select ‘Multicast Tab’ Note: Refer to Data Datasheet for detailed information
Multicast Configuration at GWIMT(cont.) Select ‘Multicast Protocol’
Multicast Configuration at GWIMT(cont.) Set Options about Multicast Protocol
Multicast Configuration at GWIMT(cont.) Set Ethernet Interface for multicasting
Multicast Configuration at GWIMT(cont.) See the information of Multicast Member
Multicast Configuration at GWIMT(cont.) See Multicast Information
Multicast Configuration at GWIMT(cont.) See Multicast Route Information
Security Description • Security • OS7200 and 7400 only support • Control-Layer • TLS ( Transport Layer Security) • RFC 5246 • SIP only support. • Bearer-Layer • sRTP (Secure Real-time Protocol) • RFC 3711
Generic Security Operation Flow 1. Make TLS Session Host A Host B 2. Negotiate VoIP session including Media Session 3. Send/Receive Secure RTP
How to configure Security Start Yes Set sRTP algorithm in DM 2.1.5 No TLS use ? sRTP use ? Yes No SIP station? No SPNET use sRTP? Yes Set sRTP Enable In DM 3.3.1 Yes No Set TLS option In DM 5.2.12 MGI use sRTP ? Yes Set sRTP Enable In DM 5.2.16 Set TLS option In DM 5.2.17 No ITP use sRTP ? Yes No End Set sRTP Enable in DM 2.7.1
Security Configuration AES_CM_128_HMAC_SHA1_80 Encryption Algorithm Key Size : 128 bits Authentication algorithm Tag Size: 80 bits The field indicates whether sRTP will be used or not and sRTP algorithms.
Security Configuration (cont.) The field indicates whether ITP use sRTP or not
Security Configuration (cont.) The field indicates whether SPNET use sRTP or not
Security Configuration (cont.) The field indicates whether MGI use sRTP or not
Security Configuration (cont.) The fields indicate whether SIP station uses TLS or not. Refer to “Feature Guide” for option description.
Security Configuration (cont.) The fields indicate whether SIP peering uses TLS or not. User Information must be set.