Live Endpoint Proxy

To validate standard PJSIP client credentials instantly, application controllers query live database tables directly. Asterisk 2 maps relational Entity Framework collections to the external ps_endpoints storage structures to resolve SIP identity scopes.

Relational Entity Mapping Matrix

The flowchart below maps out the precise field structures mirrored across C# models and underlying telecommunications databases:

graph TD
    %% Proxy Schema
    subgraph CSharpModel["C# Application Class"]
        PsEndpointEntity["PsEndpoint Entity Proxy<br/>(PK: Id String)"]
    end

    %% Underlying Fields
    subgraph RawTable["wb_ast DB Schema"]
        F_Auth["auth Column<br/>(SIP Authentication Object Hash)"]
        F_Aors["aors Column<br/>(Address of Record Mappings)"]
        F_Context["context Column<br/>(Routing Ingress Scope: 'default')"]
        F_Disallow["disallow Column<br/>(Purged Audio Codecs: 'all')"]
        F_Allow["allow Column<br/>(Approved Audio Codecs: 'ulaw,alaw')"]
    end

    %% Verification Target
    subgraph LogicTarget["Application Validation Action"]
        CheckAuth["Verify Client SIP Access"]
    end

    %% Mappings
    PsEndpointEntity ==>|"Maps Schema Column"| F_Auth
    PsEndpointEntity ==>|"Maps Schema Column"| F_Aors
    PsEndpointEntity ==>|"Maps Schema Column"| F_Context
    PsEndpointEntity ==>|"Maps Schema Column"| F_Disallow
    PsEndpointEntity ==>|"Maps Schema Column"| F_Allow
    
    F_Auth -->|"Evaluates Hash"| CheckAuth
    F_Context -->|"Routes Stream"| CheckAuth

    %% Tailored Style System
    classDef modelToken fill:#0f172a,stroke:#38bdf8,stroke-width:2px,color:#fff,rx:6px,ry:6px;
    classDef tableToken fill:#1e293b,stroke:#a855f7,stroke-width:2px,color:#fff,rx:6px,ry:6px;
    classDef actToken fill:#312e81,stroke:#ec4899,stroke-width:2px,color:#fff,rx:6px,ry:6px;

    class CSharpModel,PsEndpointEntity modelToken;
    class RawTable,F_Auth,F_Aors,F_Context,F_Disallow,F_Allow tableToken;
    class LogicTarget,CheckAuth actToken;

Detailed Entity Schema Properties

1. PsEndpoint Model Structure

• Id (string): Primary authorization string key mapping directly to specific SIP extension identities (e.g., 9001).
• Transport (string): Socket layer definition string (e.g., transport-udp or transport-tcp).
• Aors (string): Address of record targets specifying physical binding registrations.
• Auth (string): Relational link mapping to dedicated authorization profiles storing active user MD5 hashes.
• Context (string): Ingress logic profile string routing calls directly into authorized dialplan blocks.
• Disallow & Allow: Codec string negotiation arrays determining streaming options for high-fidelity audio interfaces.