# Socket Transport Declarations

To support diverse telecommunication client environments, **Asterisk 2** configures dedicated PJSIP transport blocks. The application defines isolated listening structures for clear network layer communications.

---

## Multi-Transport Network Interface Architecture

The flowchart below outlines how incoming socket calls route across dedicated protocol listener handlers:

```mermaid
graph LR
    %% Edge Network
    subgraph IngressTransport["Socket Interface Array"]
        TransUdp["transport-udp Container<br/>(Binds 0.0.0.0:5060)"]
        TransTcp["transport-tcp Container<br/>(Binds 0.0.0.0:5060)"]
        TransTls["transport-tls Container<br/>(Binds 0.0.0.0:5061)"]
    end

    %% Core Proxy
    subgraph AsteriskCore["Ingress Media Router"]
        StasisApp["res_stasis Integration Engine"]
    end

    %% Flows
    TransUdp ==>|"Unreliable Packet Handshake"| StasisApp
    TransTcp ==>|"Reliable Byte Connection"| StasisApp
    TransTls ==>|"Encrypted TLS Handshake"| StasisApp

    %% Premium CSS Tokens
    classDef transToken fill:#0f172a,stroke:#38bdf8,stroke-width:2px,color:#fff,rx:6px,ry:6px;
    classDef coreToken fill:#312e81,stroke:#ec4899,stroke-width:2px,color:#fff,rx:6px,ry:6px;

    class IngressTransport,TransUdp,TransTcp,TransTls transToken;
    class AsteriskCore,StasisApp coreToken;
```

---

## Configuration Parameter Directives

### 1. Dedicated UDP Sockets (`transport-udp`)
Optimized for standard LAN hardware connections and local carrier links:
- **`protocol`**: `udp`
- **`bind`**: `0.0.0.0:5060`
- **`tos`**: `cs3` (High-priority voice signaling marking)

### 2. Persistent TCP & TLS Bindings
Enforces reliable delivery across public networks:
- **`protocol`**: `tcp` / `tls`
- **`cert_file`** & **`priv_key_file`**: References storing validated organizational public/private certificates.