codesanitize

The evolution of digital enterprise—pushed by distant work, cloud adoption, and the necessity for safe connectivity—has made safe, seamless entry extra important and extra complicated than ever. Safe Entry Service Edge (SASE) is redefining how organizations shield customers and knowledge throughout distributed environments. Service suppliers play an important position in accelerating SASE adoption by delivering scalable, built-in, and easy-to-manage options that align with at the moment’s fashionable department architectures.

We’re excited to announce a serious milestone in our partnership with KDDI, one in every of Japan’s largest telecom and ICT service suppliers. Not too long ago, KDDI introduced its launch of Japan’s first totally managed, single-vendor SASE resolution, powered by Cisco. This announcement highlights the increasing affect of our collaboration and demonstrates our shared dedication to advancing safe, cloud-delivered networking for enterprises. On this weblog, we’ll discover how partnerships just like the one between Cisco and KDDI are accelerating SASE adoption throughout world enterprises.

How Service Suppliers Speed up the SASE Journey

Service suppliers convey world attain, deep networking experience, and sturdy managed companies, making them splendid companions for organizations navigating SASE adoption. By leveraging options from main distributors, service suppliers may help companies streamline the transition to SASE, scale back operational complexity, and safe their branches, customers, and cloud functions—all by a single, unified platform.

Redefining the Department with Cisco SASE

Cisco is a acknowledged chief in single-vendor SASE, combining industry-leading networking and safety capabilities right into a cohesive cloud-delivered service. Cisco SASE empowers organizations to attach branches, safe distant employees, and shield cloud functions—all with centralized visibility and administration. The end result: branches which might be agile, safe, and future-ready.

Key Advantages of Cisco’s Single-Vendor SASE Strategy

• Unified Administration: One platform for networking and safety, decreasing complexity and operational overhead.
• Constant Safety: Finish-to-end visibility and safety, regardless of the place customers or functions reside.
• Scalability: Simply broaden to new branches or distant customers with out infrastructure complications.
• Optimized Efficiency: Built-in SD-WAN delivers dependable, high-performance connectivity.
• Sooner Innovation: Speedy deployment of latest options and safety updates throughout the enterprise.

Actual-World Case Research

1. KDDI: Delivering Built-in SASE for Japanese Enterprises

KDDI, a serious Japanese service supplier, in partnership with Cisco, is now delivering Japan’s first totally managed, single-vendor SASE resolution. KDDI makes use of Cisco’s SASE resolution to offer companies with seamless, safe connectivity throughout department places of work, distant customers, and cloud functions. KDDI’s single-vendor strategy with Cisco allows fast deployment, centralized coverage administration, and high-performance networking, making certain sturdy safety whereas decreasing operational complexity for purchasers navigating digital transformation.

Be taught extra: KDDI Launches Cisco SASE Answer (Japanese)

2. TKC: Securing a Advanced, World Operation with Cisco SASE

TKC Company, a number one Japanese firm supporting over 10,000 tax professionals and entities makes use of Cisco’s Safe Entry to implement a single-vendor SASE resolution, changing its legacy VPN system for two,800+ customers. Going through tight timelines and excessive confidentiality wants, TKC adopted Cisco’s cloud-first, zero-trust strategy. The answer mixed steady person authentication and identity-driven, safe software entry through Cisco Safe Entry with Cisco SD-WAN’s cloud-managed, zero-trust community structure, centralized coverage enforcement, and built-in security measures. A unified shopper and console simplified operations for safety lowered reliance on a number of instruments. This contemporary, cloud-managed structure lowered complexity and delivered cost-efficient, scalable connectivity.

Hiroyo Ichikawa, Director of IT Funding Planning for TKC Company, stated, “Gone are the times of complicated processes like equipment procurement, website planning, and complicated deployments. Having the ability to launch shortly made the advantages of cloud deployment – like utilizing a cloud-based VPNaaS vs. an on-premises VPN – very tangible for us.”

Be taught extra: From Legacy VPN to Cloud-First Safety: How TKC has Strengthened Safety and Decreased Complexity (Case Research)

3. Monetary Companies: Enabling Safe Hybrid Work

A number one monetary agency turned to its service supplier and Cisco SASE to help a distant workforce and keep regulatory compliance. The one-vendor resolution supplied safe distant entry, knowledge loss prevention, and real-time menace detection, all whereas making certain a constant person expertise throughout places of work and residential networks.

Conclusion

As organizations redefine their department architectures to fulfill the calls for of a digital-first world, Service Suppliers worldwide are leveraging Cisco networking and safety options and driving SASE adoption. With single-vendor SASE, companies achieve the simplicity, safety, and scalability they should innovate and thrive—at the moment and into the longer term.

Discover Cisco SASE to study extra.

We’d love to listen to what you suppose! Ask a query and keep linked with Cisco Safety on social media.

Cisco Safety Social Media

LinkedIn
Fb
Instagram

Share:

I’m organising an SRS origin-edge cluster utilizing Docker. I need to publish a single RTMP stream to the origin and play it again on the proxy utilizing HTTP-FLV, HLS, and WebRTC. My motivation is that once I stream a number of cameras with WebRTC via my AWS server, the second digicam experiences latency. From my understanding, SRS works on a single thread which may create points. Thus, I made a decision to make use of multi-containers system (Please let me know if there are higher methods to do!). For now, I’m simply attempting two containers:

1. origin that receives the stream
2. proxy that pulls the stream from origin and stream on an html web page

I used to be capable of:

• Setup a single-container setup works completely for all protocols (FLV, HLS, and WebRTC).
• Create a multi-container setup, HTTP-FLV and HLS playback works accurately, which proves the stream is being pulled from the origin to the proxy.

My drawback:

WebRTC playback is the one factor that fails. The browser makes a profitable connection to the proxy (logs present connection established), however no video ever seems. The proxy log exhibits it connects to the origin to tug the stream, however the connection then instances out or fails with a video parsing error (avc demux annexb : not annexb).

My docker-compose.yml:

model: '3.8'
networks:
  srs-net:
    driver: bridge
companies:
  srs-origin:
    picture: ossrs/srs:6
    container_name: srs-origin
    networks: [srs-net]
    ports: ["1936:1935"]
    expose:
      - "1935"
    volumes: ["./origin.conf:/usr/local/srs/conf/srs.conf:ro"]
    command: ["./objs/srs", "-c", "conf/srs.conf"]
    restart: unless-stopped      
  srs-proxy:
    picture: ossrs/srs:6
    container_name: srs-proxy
    networks: ["srs-net"]
    ports:
      - "1935:1935"
      - "1985:1985"
      - "8000:8000/udp"
      - "8080:8080"
    depends_on:
      - srs-origin
    volumes: 
      - "./proxy.conf:/usr/native/srs/conf/srs.conf:ro"
      - "./html:/usr/native/srs/html"
    command: ["./objs/srs", "-c", "conf/srs.conf"]
    restart: unless-stopped

origin.conf:

hear 1935;
daemon off;
srs_log_tank console;
srs_log_level hint;

vhost __defaultVhost__ {
}

proxy.conf:

hear              1935;
max_connections     1000;
daemon              off;
srs_log_tank        console;
srs_log_level       hint;

http_server {
    enabled         on;
    hear          8080;
    dir             ./html;
    crossdomain     on;
}

http_api {
    enabled         on;
    hear          1985;
    crossdomain     on;
}

rtc_server {
    enabled         on;
    hear          8000;
    candidate      xxx.xxx.xxx.xxx; # IP tackle
}

vhost __defaultVhost__ {
    enabled         on;

    # Allow cluster mode to tug from the origin server
    cluster {
        mode            distant;
        origin          srs-origin:1935;
    }

    # Low latency settings
    play {
        gop_cache       off;
        queue_length    1;
        mw_latency      50;
    }

    # WebRTC configuration (Not working)
    rtc {
        enabled         on;
        rtmp_to_rtc     on;
        rtc_to_rtmp     off;
        
        # Essential for SRS v6
        bframe          discard;
        keep_bframe     off;
    }

    # HTTP-FLV (working)
    http_remux {
        enabled     on;
        mount       /[app]/[stream].flv;
    }
    
    # HLS (working)
    hls {
        enabled         on;
        hls_path        ./html;
        hls_fragment    3;
        hls_window      9;
    }
}

The ffmpeg pipe I exploit in my python code from my host machine to push video frames to my AWS server:

IP_ADDRESS      = ip_address
        RTMP_SERVER_URL = f"rtmp://{IP_ADDRESS}:1936/reside/Camera_0"
        BITRATE_KBPS    = bitrate # Goal bitrate for the output stream (2 Mbps)
        # Threading and queue for body processing
        ffmpeg_cmd = [
            'ffmpeg',
            '-y',
            '-f', 'rawvideo',
            '-vcodec', 'rawvideo',
            '-pix_fmt', 'bgr24',
            '-s', f'{self.frame_width}x{self.frame_height}',
            '-r', str(self.camera_fps),
            '-i', '-',

            # Add audio source (silent audio if no mic)
            '-f', 'lavfi',
            '-i', 'anullsrc=channel_layout=stereo:sample_rate=44100',

            # Video encoding
            '-c:v', 'libx264',
            '-preset', 'ultrafast',
            '-tune', 'zerolatency',
            '-pix_fmt', 'yuv420p',
            # Keyframe interval: 1 second. Consider 0.5s if still high, but increases bitrate.
            '-g', str(2*self.camera_fps), 
            # Force no B-frames (zerolatency should handle this, but explicit is sometimes better)
            '-bf', '0', 
            '-profile:v', 'baseline',   # Necessary for apple devices 

            # Specific libx264 options for latency (often implied by zerolatency, but can be explicit)
            # Add options to explicitly disable features not in Baseline profile,
            # ensuring maximum compatibility and avoiding implicit enabling by preset.
            '-x264-params', 'cabac=0:ref=1:nal-hrd=cbr:force-cfr=1:no-mbtree=1:slice-max-size=1500', 
            # Force keyframes only if input allows (might not be practical for camera input)
            '-keyint_min', str(self.camera_fps), # Ensure minimum distance is also 1 second
            
            # Rate control and buffering for low latency
            '-b:v', f'{BITRATE_KBPS}k',         # Your target bitrate (e.g., 1000k)
            '-maxrate', f'{BITRATE_KBPS * 1.2}k', # Slightly higher maxrate than bitrate
            '-bufsize', f'{BITRATE_KBPS * 1.5}k', # Buffer size related to maxrate
            
            '-f', 'flv',
            RTMP_SERVER_URL
        ]

self.ffmpeg_process = subprocess.Popen(ffmpeg_cmd, stdin=subprocess.PIPE, stdout=subprocess.DEVNULL, stderr=subprocess.PIPE, bufsize=10**5)