In this section:

Deployment Scenarios


Note

Native Call Forking does not support GW-GW scenarios.

Scenario 1 - Same AOR for Different Devices:

Redundant Call Servers

  • An incoming call to a specific number (for example, +1-80-41774568) is forked towards PBX1 and PBX2.

  • Both the devices should belong to different call servers/PBXs so the SBC can fork the call.

  • In the scenario below, the SBC forks the call to routes R11 and R21. If the call is not completed through R11, the SBC cracks back the call through route R12 to complete the process. All the call legs contain the egress INVITE R-URI as the calling number (+1-80-41774568). Therefore, the call can be rescheduled to any route to reach the destination.
    Figure 1: Redundant Call Servers - Same AOR


Non-Redundant Call Servers

  • An incoming call to a specific number (for example, +1-80-41774568) is forked towards PBX1 and PBX2.
  • Both the devices should belong to different call servers/PBXs so the SBC can fork the call.

  • In the below scenario, the SBC forks the call to routes R1 and R2. Here, all the call legs contain the egress INVITE R-URI as the calling number (for example, +1-80-41774568). Therefore, the call is directed to both routes simultaneously.
    Figure 2: Non-Redundant Call Servers - Same AOR


Scenario 2 - Different AORs for Different Devices:

Redundant Call Server

  • An incoming call to a specific number (for example, +1-80-41774568) is forked to both the AORs (for instance, AOR1:+1-80-41774568 and AOR2: sip:example@sonusnet.com) simultaneously via PBX1 and PBX2.
  • Both the AORs belong to different call servers. The redundant call servers handle these two devices.

  • In the below scenario, the SBC forks the call to routes R11 and R21. If the call is not completed through route R11, the SBC cracks back the call through route R12 to complete the process. The routes R11 and R12 contain the egress INVITE R-URI as +1-80-41774568, and the routes R21 and R22 contain the egress INVITE R-URI as sip:example@sonusnet.com.
    Figure 3: Redundant Call Servers - Different AORs

Non-Redundant Call Server

  • An incoming call to a specific number (for example, +1-80-41774568) is forked to both the AORs (for instance, AOR1:+1-80-41774568 and AOR2: sip:example@sonusnet.com) simultaneously via PBX1 and PBX2.
  • Both the AORs belong to different call servers. The redundant call servers handle these two devices.

  • In the below scenario, the SBC forks the call to routes R1 and R2. Route R1 contains the egress INVITE R-URI as +1-80-41774568, and route R2 contains the egress INVITE R-URI as sip:example@sonusnet.com.
    Figure 4: Non-Redundant Call Servers - Different AORs