Does the Dual Version architecture provide any sort of redundancy?
Your current release system (source) and the newer release system (target) are linked together but operate independently of each other. So, when either system is down or unavailable, those services do not fail over to the other system. To ensure uninterrupted service provisioning for both systems in Dual Version PortaSwitch, you need to make them both redundant. In general, the redundancy of a system can be achieved in two ways:
- You can deploy billing, SIP, and web clusters
- Or you can disperse your system across multiple sites
The latter solution provides high-availability and geo-redundancy options, and that is what we recommend. Keep in mind that for Dual Version, both of your systems should adhere to the requirements for high availability and geo-redundancy.
Do I need to deploy dispatching SBC if I already have a PortaSIP cluster?
Yes. The dispatching session border controller (SBC) will link the current (source) and the new (target) systems in Dual Version mode, and it is required to deliver calls across systems. The dispatching SBC knows in what system the customer record is located and delivers the call there. The dispatching SBC is deployed on the target system. You can configure it on an on-premise server or on a virtual server.
Does the PortaOne dispatching SBC participate in media streaming?
No, it does not. The dispatching session border controller (SBC) only participates in the signaling path of the call by distributing incoming call initiation requests across the systems for processing. When a call is established, the endpoints directly exchange a media stream, or it can take place via the RTP proxies of their respective PortaSIP clusters.
