During a Dual Version PortaSwitch migration, customers must be able to continue using their services as before, regardless of which system their account is in. For example, if John Doe's account has already been migrated to the target system, he must be able to make and receive calls exactly as before the migration.
PortaSwitch uses the dispatching Session Border Controller (DSBC) to route call requests to and from accounts in either system.
Usage scenarios
The following examples show how PortaSwitch delivers calls to and from John’s account in two cases:
- The account is located in the source system.
- The account has been migrated to the target system.
In both cases, John’s phone registers with the DSBC’s IP address or hostname, which does not change when his account is migrated.
Source system – outgoing calls
John calls his friend Harry.
- John's phone sends an INVITE request to the DSBC.
- The DSBC looks up the account ID in the forwarding registry, which shows that the account belongs to the source system.
- The DSBC routes the INVITE request to the source system PortaSIP.
- PortaSIP sends an authorization request to the source system PortaBilling, which authorizes the call and provides PortaSIP with the routing results.
- The source system PortaSIP is configured to route outgoing calls through the DSBC, so it sends the call there.
- DSBC delivers the call to Harry.
- When the call ends, PortaSIP sends accounting information to PortaBilling, which calculates the charges and produces xDRs.
Source system – incoming calls
John receives a call from Harry.
- The DSBC receives a call from Harry.
- The DSBC looks up the DID number that matches the destination number in the forwarding registry and finds that this number belongs to the source system.
- The DSBC routes the call to the source system PortaSIP.
- PortaSIP sends an authorization request to the source system PortaBilling. PortaBilling authorizes the call, checks that the destination number matches the ID of an account in the source system, and returns the result to PortaSIP.
- PortaSIP finds that the account's phone is registered with the DSBC, so it sends the call to the DSBC.
- The DSBC delivers the call to John's phone and it starts ringing.
- When the call ends, PortaSIP sends accounting information to PortaBilling, which calculates the charges and produces xDRs.
Target system – outgoing calls
John's customer record with his account has been migrated to the target system. John calls his friend Harry.
- John's phone sends an INVITE request to the DSBC.
- The DSBC looks up the account ID in the forwarding registry, which shows that the account belongs to the target system.
- The DSBC routes the INVITE request to the target system PortaSIP.
- PortaSIP sends the authorization request to the target system PortaBilling, which authorizes the call and provides PortaSIP with the routing results.
- The target system PortaSIP is configured to route outgoing calls through the DSBC, so it sends the call there.
- The DSBC delivers a call to Harry.
- When the call ends, PortaSIP sends accounting information to PortaBilling, which calculates the charges and produces xDRs.
Target system – incoming calls
John's customer record with his account has been migrated to the target system. John receives a call from Harry.
- The DSBC receives a call from Harry.
- The DSBC looks up the DID number that matches the destination number in the forwarding registry and finds that this number belongs to the target system.
- The DSBC routes the call to the target system PortaSIP.
- PortaSIP sends an authorization request to the target system PortaBilling. PortaBilling authorizes the call, checks that the destination number matches the local account, and returns the result to PortaSIP.
- PortaSIP finds that the account's phone is registered with the DSBC, so it sends the call to the DSBC.
- The DSBC delivers the call to John's phone and it starts ringing.
- When the call ends, PortaSIP sends accounting information to PortaBilling, which calculates the charges and produces xDRs.
Inter-system calling
When a customer is migrated from the source system to the target system, it must remain reachable both from the external networks and from the source system.
PortaSwitch treats a call between an account in the source system and an account in the target system like an on-net call. It routes the call directly between the two systems, without leaving PortaSwitch's own network. Find the configuration steps here.
John's account is located in the source system. Mary's customer record with her account has already been migrated to the target system. John calls Mary.
- John's phone sends an INVITE request to the DSBC.
- The DSBC looks up the account ID in the forwarding registry, which shows that it belongs to the source system.
- The DSBC routes the INVITE request to the source system PortaSIP.
- PortaSIP sends an authorization request to the source system PortaBilling, which searches the forwarding registry for the destination number. The registry shows that the destination account belongs to the target system, so PortaBilling instructs PortaSIP to route the call there.
- The source system PortaSIP is configured to route outgoing calls through the DSBC, so it sends the call there.
- The DSBC sends the call to the target system PortaSIP.
- The target system PortaSIP sends an authorization request to the target system PortaBilling. PortaBilling authorizes the call, checks that the destination number matches the local account, and returns the result to PortaSIP.
- PortaSIP finds that Mary's phone is registered with the DSBC, so it sends the call to the DSBC.
- The DSBC delivers the call to Mary's phone and it starts ringing.
- When the call ends, PortaSIP in each system sends accounting information to its own PortaBilling, which calculates the charges and produces xDRs for the customer in that system. John is charged for the outgoing call, and Mary is charged for the incoming call.
Fallback call delivery
To determine which system should handle an incoming call, the DSBC checks the caller’s and called numbers against the account and DID records in the forwarding registry. If it finds a match, it sends the call to the system where the account or DID is located.
If the DSBC cannot find a match (for example, the number is dialed in a short, internal format), it uses fallback call delivery. It sends the call to the source system or the target system, whichever is set in the ForwardingRegistry.fallback_env option in the Configuration server web interface.
During a Dual Version migration, the scripts that switch SIP traffic to the DSBC automatically set the option to the source system, so the DSBC sends the calls it cannot match to the source system. If such a call belongs to the target system, PortaBilling in the source system instructs PortaSIP to route it there.
After all entities have been migrated and the service provider confirms that everything is working correctly, the admin clears the option. If the option has no defined value, the DSBC sends the calls it cannot match to the target system.





