Scope / deliverables
- SIP firewall and NAT traversal: SIP deep-packet inspection (DPI), dynamic pinhole open/close, stateful SIP protocol validation, network topology hiding, DoS/DDoS mitigation
- TLS/SRTP encryption: TLS signaling on both core-side (PBX) and access-side (SIP trunk/remote users); SRTP media encryption — transparent relay (pass-through) and termination/mediation modes
- SIP trunk interoperability: configurable SIP service provider parameters; tested/certified compatibility with Turkey and regional SIP trunk operators; B2B-UA (Back-to-Back User Agent) architecture
- Microsoft Teams Direct Routing certified: bridges Teams calls to OpenScape Voice/OS4000; Teams SBA (Survivable Branch Appliance) support in V11
- Remote user and branch support: SIP endpoint registration services, SIP access beyond NAT for remote workers and branch offices; distributed SIP trunking with OpenScape Branch
- Media control: media anchoring (for NAT traversal) or direct media (media-bypass); media transcoding and packet resizing (codec mismatch resolution)
- Capacity: depends on hardware platform (Lenovo SR250 V2 → medium scale; SR630 → high scale); Licensing: Base + Redundancy (for HA cluster) + Session license (per concurrent SIP connection). Session licenses shared between OpenScape SBC and OpenScape Branch
- Management: centralized SOAP/XML management via CMP (Common Management Platform); local HTTPS web GUI. English and German management UI
- Hardware platforms: Lenovo SR250 V2 / SR250 / SR630 V2 / SR530; OpenScape Branch 550/550HA (NC — no cards, SBC-only mode). Virtualization: VMware ESXi, KVM, MS Hyper-V (Windows Server 2022), ProxMox VE
- Licensing: CAPEX (Base + Redundancy + Session) or OPEX SSL (Software Subscription — fixed-rate). Upgrade licenses from V9/V10 to V11 available
- Promark: SIP trunk security analysis, SBC sizing, Teams Direct Routing integration, CMP license management, installation and commissioning
Tags
SBCSession Border ControllerSIP TrunkTLSSRTPNATDoSMicrosoft TeamsDirect RoutingV11OpenScape VoiceOS4000
Vendor‑neutral approach: We select architecture/components based on need; platforms like Unify/Mitel can be positioned as options.