DO NOT SHARE THESE DOCS WITH CUSTOMERS!

This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.

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 both PBX1 and PBX2.

  • Both the devices should belong to different call server/PBX for the SBC to fork the call.

  • In the below scenario, the SBC forks the call to the routes R11 and R21. If the call does not complete through R11, the SBC crack back the call through route R12 to complete the process. Here, all the call legs contain the egress INVITE R-URI as the calling number (+1-80-41774568). Therefore, the call can crank back to any route to reach the destination.

    Redundant Call Servers - Same AOR

Non-Redundant Call Servers

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

  • In the below scenario, the SBC forks the call to the 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 the routes simultaneously.

    Non-Reduntant 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 example AOR1:+1-80-41774568 and AOR2: sip:bob@sonusnet.com) simultaneously via PBX1 and PBX2.
  • Both the AORs belong to different call servers. These two devices are handled by the redundant call servers.

  • In the below scenario, the SBC forks the call to routes R11 and R21. If the call does not complete through route R11, The SBC crack 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 contains the egress INVITE R-URI as sip:bob@sonusnet.com.

    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 example AOR1:+1-80-41774568 and AOR2: sip:bob@sonusnet.com) simultaneously via PBX1 and PBX2.
  • Both the AORs belong to different call servers. These two devices are handled by the redundant call servers.

  • In the below scenario, the SBC forks the call to routes R1 and R2. The routes R1 contains the egress INVITE R-URI as +1-80-41774568 and the routes R2 contains the egress INVITE R-URI as sip:bob@sonusnet.com.

    Non-Redundant Call Servers - Different AORs


  • No labels