...
Tip |
---|
There are many different architectures which might be used for connecting remote sites to a main site. The manual pages for this 3G4G feature specify a VLAN switch with the 3G4G and WAN networks sharing a single port of the UX. The implementation below uses a 3G4G router connected to the remote LAN segment, thus dedicating the WAN connection to a SBC port. This configuration elminates then need for a VLAN-capable switch. |
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
As a prerequisite to installing the RBA feature, check the following items:
...
Configure Send STUN Packets to Enabled in the Media | Media System Configuration.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Tip |
---|
If your HQ-side SBC was running version 2.2, you will need upgrade both the ASM image as well as the SBC firmware. The latest ASM image is available at support.net.com. |
...
Under the Tasks Tab | Application Solution Module | Reinitialize the pull-down selection will supply the possible images currently available on your ASM. Update your ASM images if you are implementing Lync Server 2013 and there is no Lync 2013 image available on your ASM.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Verify that your SBC is licensed for the RBA feature.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Add both SBCs to the DNS server. In the example, SBC2000 is the HQ SBC and SBC1000 is the remote network SBC. The DNS server is configured only with the LAN-side IP addresses of these nodes, 10.1.1.74 and 10.1.2.71, respectively.
...
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
...
Start the Topo Builder
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Enter Login Credentials
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Download the Topology
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Specify a Filename
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Confirm Changes
Panel |
---|
| |||||||
|
Add a new Branch Site. In the example, Taveuni is the new remote branch.
Right-click on Branch Sites and select New Branch Site
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Enter the remote site identity
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Configure the site details
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Add sbc1000.sbc.net as Taveuni's PSTN Gateway.
...
Panel |
---|
...
|
...
|
...
|
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Info |
---|
The RBA function requires media bypass, which, in turn requires TLS/SRTP. Later this document, the remote PSTN gateway will be re-configured from TCP/RTP to TLS/SRTP. Employing the simplier TCP/RTP model will help ease the implementation by providing a phased approach to the implementation. |
...
Finally, Publish the newly configured topology.
...
Panel |
---|
...
|
| |||||||
|
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Click New
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Add a Site Policy
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Click New
Add a Site Policy
Select the remote site you just added to the Lync topology.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Add a new PSTN Usage
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Add a new PSTN Usage
Supply a Name and Add a Route
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Configure a call route pattern
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Add a Trunk
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Choose the newly added remote-network SBC
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Click OKat each of the configuration layers
Commit the changes to the Voice Policy
Click the Commit pulldown and Commit All
Click OK
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Commit the changes to the Voice Policy
Click the Commit pulldown and Commit All
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Click OK
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Verify the Route and Verify the Route and PSTN Usages were added properly in the previous steps.
In the top navigation bar, click Route. Ensure that the route was added.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
In the top navigation bar, click PSTN Usage. Ensure that the PSTN Usage was added.
PSTN Usage. Ensure that the PSTN Usage was added.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
...
Click Dial Plan in the top navigation. Click New_and select _New User Plan.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Enter the information for your site and click OK.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
...
Click Voice Policy in the top navigation. Click New and select User Policy.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Fill in the form as shown using information for your particular installation.
installation.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Click New under Associated PSTN Usages.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Create a PSTN Usage to be used with the User-level policies.
Create a New PSTN Usage record.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Enter your site-specific configuration information.
specific configuration information.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Click Add for Associated Trunk
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
|
|
Select the remote-network SBC gateway
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Click OKfor all the configuration layers.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Click OKfor all the configuration layers.
Commit the additions to your Lync configuration.
Click the Commit pulldown, then select Commit All.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Click OK.
Verify the Routewas added.
Click OK.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Verify the Routewas added.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Verify the PSTN Usagewas added.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Verify the PSTN Usagewas added.
...
Click Users in the left-hand navigation. Enter the name of the user to move to the remote network and click Find.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
In the Edit pulldown, select Show Details.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Set the Dial Plan and Voice Policy of the user to thos of the remote network Userpolicies.
the remote network Userpolicies.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
...
Click Network Configuration in the left-hand navigation. Click Global in the top navigation, click the Edit pulldown, and select Show Details.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Ensure that the CAC and Bypass options are selected. Change the settings and commit, if necessary.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
...
Click Bandwidth Policy in the top navigation and select New.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Enter the bandwidth specification for your remote network link, then click Commit.
click Commit.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Create regions to be used with the RBA feature. There will be a region for the HQ, as well as the remote-network.
Click Region in the top navigation and select New.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Add a record for the remote region and Commit.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Click Newto add the second region.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Add a record for the HQ site and Commit.
for the HQ site and Commit.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Create sites to be used for the RBA function. Again, there will be a HQ site, as well as a remote site.
Click Site in the top navigation and select New.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Enter the information for your remote site. Click Commit.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Click New and enter the information for your HQ site. Click Commit.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
IP addresses are used by the Lync Server to identify the origin of a Lync client. Create subnet records for both the HQ and remote network sites.
Click Subnet in the top navigation and select New.
New.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Enter the IP network information for the remote network.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Click Newand enter the IP network information for the HQ network.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Create a Region Link between the sites.
Click Region Link in the top navigation and select New.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Using the pulldowns, select the HQ Region, the Remote Region and the Bandwidth Policy profile you previously created.
you previously created.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
...
Click Region Route in the top navigation and select New.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Add the Network Regions as shown and add the newly created Region Link.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
...
On the Domain Controller, open the Server Manager
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Add a new computer to Active Directory. You should have already selected a FQDN for the ASM module during the DNS Configuration section.
section.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Input the name of the ASM computer
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Add the computer to the RTCUniversalServerAdminsgroup
Click OK
RTCUniversalServerAdminsgroup
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Click OK
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Click OK
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Click OK
Tip |
---|
Have you added the RBA as a computer in the Domain Controller and made it part of the RTCUniversalServerAdmins group? |
Verify the ASM Board is Available using the Tasks Tab | Operational Statusselection
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Click Setup SBA in the left-hand navigation
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Click the ASM Config Tab and supply the information for your ASM. Click Apply.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Click the Domain tab and supply the domain information for your network. Click OK. It will take a minutes to add the ASM to the domain and reboot.
the ASM to the domain and reboot.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
The Current Activity Panel will show when the domain join and rebooting processes are complete
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Click the Deploy SBA tab and select Prepare SBA. This will install the necessary components for the ASM to process the CAC changes supplied by the remote-network SBC. It will take approximately 30 minutes for the installation to complete.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Info |
---|
The RBA requires only the Prep SBA step. The other SBA deployment steps are not required. |
...
Ensuring the WAN and IPsec traffic use the appropriate routes is crucial to successful RBA failover.
Click the Settings Tab and select Static Routes as shown in the diagram
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
On the remote-network SBC, add a Static IP Route
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Create a default route that points to the WAN interface on the HQ SBC. Set the Metric to 1.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Create another default route that points to the IPSec interface on the HQ SBC. Set the Metric to 2.
Tip |
---|
Default routes are required for the automated routing failover to function. Only use default routes. |
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Verify the newly added static routes
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
On the HQ SBC, add specific subnet routes that point to the remote-network. One route should use the remote-network SBC's WAN connection (metric 1), the other should point to the Internet gateway (metric 2).
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
...
Click SIP Server Tablesin the left-hand navigation
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Add a SIP Server Table
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Enter a description and click Apply.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Click the newly added SIP Server Table
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
|
|
Enter the information for the HQ SBC
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Click Signaling Groupsin the left-hand navigation. Add a Signaling Group for the HQ SBC.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Add the information to the newly added SG.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
On the HQ SBC, add a SIP Server Table that points to the remote-network SBC
SBC
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
On the HQ SBC, add a Signaling Group that points to the remote-network SBC
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
On both SBCs, ensure that the Signaling Groups come Up
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
On the HQ SBC, verify that the Routing Table shows the route to the remote network using the WAN IP address of the remote SBC. In this case, the route to 10.1.2.0 (remote network) uses the remote SBC's 134.56.242.16 as the gateway.
...
.16 as the gateway.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
...
Click IPSec | Tunnel Tablein the left-hand navigation.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Add a Tunnel Table
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
The Remote Subnet Addressmust be programmed with IP information for the HQ network.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
...
Configure an IPsec tunnel on the HQ SBC with information appropriate to your network. On the HQ SBC, the Local Subnet Address is the HQ network, the Remote Subnet Addressis the remote network subnet(s).
subnet(s).
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
In this section you will test the IPsec tunnel to ensure connectivity exists when the WAN link is down.
...
Manually remove the WAN Route from the HQ SBC
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
On the Remote SBC, use the refresh button to verify the Service Status is Link Up.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
The Signaling Groups should come back up after the IPsec tunnel is esablished.
esablished.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
...
Before proceeding, replace the HQ SBC WAN route to the remote SBC.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
...
Modify the Remote SBC IPSec Tunnel Activation to Link Monitor Action and click OK.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
The CAC profiles are transmitted to the Lync Server via the HQ SBC when the WAN transitions link states.
...
Click WAN in the left-hand navigation and select CAC Profiles.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Create a profile for the WAN up situation. Set the bandwidths according to your desired WAN link configuration and capacity. Click Applywhen finished.
.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Now, create a CAC profile for WAN down. Setting the Bandwidth State to Disabledresults in any HQ<>remote-network calls being routed over the PSTN.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
The Link Monitors provide the ability for the remote SBC to know whether the WAN is up and available.'
Click Link Monitor Configuration
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Add a monitor to monitor the public IP interface of the HQ SBC and click Apply.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Add a monitor to monitor the 3G4G router port. Associate this Link Monitor with the IPsec Tunnel you recently created. With this link activated (due to WAN down), the IPsec tunnel will be automatically started.
tunnel will be automatically started.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Verify the following tables on the remote SBC
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
...
Create a fake CAC entry. This entry will be ignored for purposes of bandwidth adjustment.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Create a Link Monitor that monitors the WAN interface of the remote SBC.
remote SBC.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Verify the condition of the routes and IPsec links.
...
With the WAN link up, the HQ SBC routing table and Link Monitor should resemble the following.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
With the WAN link up, the remote SBC's routing table should point to the WAN interface on the HQ SBC.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
The Link Monitor Table should be Readyon the WAN link
WAN link
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
The IPsec tunnel should be Link Down
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Verify the Lync Bandwidth Profile using the Bandwidth Policy Service Monitor, which is installed as a component of the optional Lync Server Resource Kit (available from the Microsoft Lync Server website).
Open Windows Explorer to C:\Program Files\Microsoft Lync Server 2013\ResKit\BandwidthPolicyServiceMonitor and select PDPMonUI.exe.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Expand the server name in the left-hand navigation and select the expanded server.
and select the expanded server.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Click the Topology Infotab
Click thePanel | |||||
---|---|---|---|---|---|
| |||||
|
|
Verify the bandwidth settings are for the WAN up values.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Test a call between a HQ and Remote Lync client. Calls between HQ and Lync clients should connect directly over the WAN without need for a PSTN connection.
...
Downing the WAN Link should result in the following status. With the WAN link down, verify your implementation to the following:
On the HQ SBC, the WAN Link Monitor should show down and the IPsec tunnel up.
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
|
...
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
On the HQ SBC, the WAN Link Monitor should show down and the IPsec tunnel up.
On the Remote SBC, the Link Monitor should show the 3G4G link up, the WAN link down, and the IPsec tunnel up.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Within two or three minutes, the Bandwidth Policy should automatically update to the Bandwidth Policy should automatically update to the WAN down bandwidth values.
...
WAN down bandwidth values.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Test a call between a HQ and Remote Lync client. In the WAN down condition, you should be able to call between HQ and Remote Lync clients. The calls should utilize the PSTN connection between the SBCs.
...
On the Lync Server, start the Topology Builder and Edit Propertiesfor the remote site Trunk.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Change the port and configuration to support TLS as shown.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Publish the topology.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Certificates are required for TLS/SRTP functionality. The following steps will assist you in installing certificates on the remote SBC.
Click the Taskstab.
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
|
|
Click Lync Setupin the left-hand navigation
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Obatin the root certificate from your network administrator and copy it to your PC. From the webui, click Import Trusted CA Certificateas shown.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Set the Mode to File Upload and Browseto find the file containing the root certificate.
the root certificate.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Click OKto import the root certificate.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Click OKto import the root certificate.
Click the Generate CSRto generate a certificate request for the SBC. You will send this certificate request to be signed by the your certificae authority.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Copy and paste the certificate request into a file and send it to your root certificate authority for signing.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
When the signed certificate is returned, click the Sonus SBC Certificatetab and import the certificate.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Set the Mode to File Upload and Browseto find the file containing the SBC certificate.
the SBC certificate.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Verify the SBC and root certificates
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
On the remote SBC, set/create the Lync Server SIP Server as shown.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Set/create a Lync Server Signaling Group as shown.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
The Lync Server Signaling Group should come up
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
Panel | |
---|---|
|
...
|
...
|
...
A wireshark trace which shows an exception due to an unrecognized cmdlet is likely due to the Prep SBA function not being executed. Review the Configuring the RBA section of this document.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
...
Check the routing table on the remote SBC. The remote SBC must use default routes (0.0.0.0/0) rather than network routes.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
...
Panel | |||||
---|---|---|---|---|---|
| |||||
|
...
|
...
|
...
This wireshark trace shows a properly working cmdlet to change the CAC bandwidth policies.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
rev 0.2