Smiertx Site

Here the Architecture : Description : Assume for NBC Channel, we want to channel redundant, it means that, more than one feeds from HMP. For HMP 1: run HMP, we get sdp like this, for example: nbc.sdp send sdp file to Helix Server on ../Content/rtpencodersdp/ directory. rename nbc.sdp to nbc.sdp.1 at Helix Server side. Just follow this for HMP 2 and so on. After this we get list on ../Content/rtpencodersdp/ directory like this : # ls -la --------------- nbc.sdp.1 nbc.sdp.2 --------------- Go to Helix Server Admin Web Interface: Just add the mount point, on example to /redundant/ Result : - redundant access through rtsp ://ip_helix/redundant/nbc.sdp - we can also access rtsp://ip_helix/rtpencoder/nbc.sdp.1, rtsp://ip_helix/rtpencoder/nbc.sdp.2, and so on. - at least one of nbc.sdp.n running, we still can access rtsp ://ip_helix/redundant/nbc.sdp Great thanks to Mas Abi, he has a great of Streaming Solution.

I used Cisco 3750, here I add to my conf : > enable # configure terminal # ip multicast-routing distributed # interface Vlan1 # ip pim version 2 # ip pim dense-mode # ip cgmp # end It means that Vlan1 enable Multicast Transport.

Here the architecture : Network Element Information 1. Helix Mobile Producer - feeds sdp with multicast mode to each of Helix Server - can be connect to each of Helix Server - on VLAN A - default gateway on Switch Layer 3 2. Helix Server - Each of Helix Server can connect to each of HMP's - Communicating with SIP Proxy using IP Virtual created on BIG-IP ( 10.10.10.254 ) - Default Gateway on BIG-IP - For communicating with HMP's, just add gateway for IP HMP's to Switch Layer 3 directly. 3. BIG-IP - Allocating IP Virtual for Helix Server's redundant mode. - Default Gateway on Switch Layer 3 - Define load balancing procedure for Helix Server 1 & 2. Active - Active using Round Robin. - NAT 10.10.10.1 to 10.10.10.254, it means that for outgoing connection initiated by 10.10.10.254, this action done by Helix Server 1. - if we aren't using NAT, we can use SNAT (10.10.10.254 to 10.10.10.1 & 10.10.10.2 ) but it useless only when comunicating with SIP Proxy that using

I think this case confused me on last week, but now it solved. Thanks God ... Here the architecture : On Load Balancing Process, I use BIG-IP here. Just adding NAT for 10.10.10.1 to 10.10.10.254. It means HMP on Internet will feed on Helix Server 1 only ... Configuring on HMP on Internet : Just fill Server Address option with IP Public of Load balancer here sdp file on HMP on Internet : v=0 o=- 3722427326 36815170 IN IP4 yy.yy.yy.yy s=HelixSession c=IN IP4 xx.xx.xx.xx t=0 0 m=video 5050 RTP/AVP 96 b=AS:37 a=rtpmap:96 MP4V-ES/90000 a=fmtp:96 profile-level-id=8; config=000001B008000001B50EA020202F000001000000012000C788BA9850584121463F a=cliprect:0,0,144,176 a=mpeg4-esid:201 a=x-envivio-verid:00035A30 m=audio 5052 RTP/AVP 97 b=AS:12 a=rtpmap:97 AMR/8000 a=fmtp:97 octet-align=1 a=mpeg4-esid:101 a=x-envivio-verid:00035A30 Then upload these sdp to Helix Server 1 on rtpencodersdp folder, on my example : /opt/Helix/Content/rtpencodersdp/ After this, we must edit this sdp to approriate IP Addr