Versions Compared

Old Version 3

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin


CSS Stylesheet

.wiki-content h1 {
border-top: 1px solid rgb(145,150,153);
}
h1, h2, {font-size: 18pt !important;}
h3 {font-size: 16pt !important;}
h4 {font-size: 14pt !important;}
h5 {font-size: 14pt !important;}
 CSS Stylesheet

 Section

 Column
width40%
Table of Contents
 Panel
 Table of Contents
maxLevel4


 
 Column
width5%


 Column
width55%

 Noprint
 Add_workflow_for_appnotes
AUTH1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cbbe0663, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV4UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb220566, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a0c8662400ad016635fa5dd8000e, userName='null'}
REV2UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd6e0a07, userName='null'}


...
The following equipment and software were used for the sample configuration:
 Caption
0Table
1Requirements
...


Equipment
Software Version
Ribbon Networks
Ribbon EdgeMarc 2900A 
Ribbon EdgeMarc 2900aPoE
Ribbon SBC SWe
Ribbon EdgeView		V15.3.0
V15.5.0
V07.02.01R002
V15.2.2
Third-party Equipment
Polycom Phones VVX411
Broadsoft
Analog Phones
Fax Machine
5.6.1.1740
Rel_22.0_1.1123

Sharp UX-P115


Reference Configuration
The following reference configuration shows connectivity between the third-party and the Ribbon EdgeMarc.
 Caption
0Figure
1Reference Configuration
Image Modified
 

Support
For any questions regarding this document, contact your maintenance and support provider. 
...
Third-Party Product Features
  • Network
    • WAN VLAN
    • LAN VLAN
  • DHCP
    • Options
  • NAT
    • Port Forwarding
  • SIP UA / FAX
    • T.38 / G.711
    • Analog Gateway FAX
  • Security
    • Firewall
    • Trusted Hosts
  • Survivability 
    • SIP Server Reachability
  • Test UA
  • Traffic Shaper
    • Class of Service
    • Call Admission Control
  • System
    • Backup / Restore
    • Proxy ARP
    • Syslog - MOS
    • Upgrade Firmware
  • EdgeView
    • Discover
    • Monitor
    • Test UA
    • Change Parameter
    • Remote Backup / Restore
    • Load Template
 

Verify License
There is no special licensing required for this test.
Broadsoft Configuration.
This section includes the following new configurations:

 Tip
titleBroadworks Service Guide
See Appendix A for further information regarding how to configure Broadworks services.

 Tip
titlePolycom VVX Phones Configuration Guide
See Appendix A for further information regarding how to configure Polycom VVX phones.
 Anchor
Domain
Domain
Domain
  1. Log into Broadsoft XSP as the Admin user.
  2. Select System > Resources > Domain and click Add to configure a new Domain in the system.
  3. Fill in the Domain information and click OK to confirm the changes.
     Caption
    0Figure
    1Domain
    Image Modified

 Anchor
Enterprise
Enterprise
Enterprise
  1. Select System > Enterprises and click Add to configure a new Enterprise.
  2. Fill in the Enterprise information and click OK to confirm the changes.
     Caption
    0Figure
    1Enterprise
    Image Modified

 Anchor
Group
Group
Group
  1. Select System > Enterprise > Groups > Profile and click Add to configure a new Group.
     Caption
    0Figure
    1Group
    Image Modified

  2. Fill in the Group profile information and click OK to confirm the changes. In this example we used the Group name Hawaiian Telecom.
     Caption
    0Figure
    1Group Profile
    Image Modified

 Anchor
Assign Numbers
Assign Numbers
Assign Numbers
  1. Select System > Enterprise > Resources > Numbers and click Add to configure the Numbers.
  2. Fill in the Number Add information and click OK to confirm the changes.
     Caption
    0Figure
    1Numbers Add
    Image Modified

  3. Click Apply on the Numbers page.
     Caption
    0Figure
    1Numbers
    Image Modified

 Anchor
Assign Group Numbers
Assign Group Numbers
Assign Group Numbers
Select System > Enterprise > Hawaiian Telecom > Resources > Assign Numbers and click Add to configure the group Numbers.
 Caption
0Figure
1Assign Group Numbers 
Image Modified

 Anchor
Assign Group Services
Assign Group Services
Assign Group Services
Select System > Enterprise > Hawaiian Telecom > Resources > Assign Group Services to assign or unassign services for the group.
 Caption
0Figure
1Assign Group Services
Image Modified

 Anchor
Users
Users
Users
  1. Select System > Enterprise > Hawaiian Telecom > Profile > Users and click Add to configure a new User for the Hawaiian Telecom group.
     Caption
    0Figure
    1Users
    Image Modified

  2. Fill in the User profile information and click on the OK icon to confirm the changes. In this example we used the User name vvx411A.
     Caption
    0Figure
    1User Profile
    Image Modified

 Anchor
User Phone Number
User Phone Number
User Phone Number
  1. Select System > Enterprise > Hawaiian Telecom > Users > vvx411A > Profile > Addresses to view and maintain your phone number and other identities that make and receive calls.
  2. Fill in the Addresses information and click OK to confirm the changes.
     Caption
    0Figure
    1Addresses
    Image Modified

 Anchor
Assign User Services
Assign User Services
Assign User Services
Select System > Enterprise > Hawaiian Telecom > Users > vvx411A > Profile > Assign Services to assign or unassign services for the User.
 Caption
0Figure
1User Services
Image Modified

EdgeMarc 2900A Configuration
...
  1. Select VoIP > SIP > B2BUA to configure the B2BUA settings.
  2. Configure a Trunk Device if needed and click Update.
     Caption
    0Figure
    1Trunk Devices
    Image Modified

  3. Configure an Action if needed and click Update.
     Caption
    0Figure
    1Action
    Image Modified

  4. Configure a Match if needed and click Update.
     Caption
    0Figure
    1Match
    Image Modified

EdgeMarc 2900A PoE IAD Configuration
...
Log into the IAD as the root user and click Network to configure the LAN and WAN interfaces.
 Caption
0Figure
1IAD LAN Interface
 Image Modified

 Caption
0Figure
1IAD WAN Interface
 Image Modified

 Anchor
IAD Static Routes
IAD Static Routes
Static Routes
Select Network > Static Routes to configure the routes if needed.
 Caption
0Figure
1Static Routes
Image Modified

 Anchor
IAD VoIP
IAD VoIP
VoIP
...
  1. Login as the root user and click VoIP to configure the VoIP features.
  2. Enable the B2BUA feature by checking the Route all SIP signalling through B2BUA box.
     Caption
    0Figure
    1VoIP
     Image Modified

 Anchor
IAD SIP Settings
IAD SIP Settings
SIP Settings
  1. Select VoIP > SIP to configure the SIP settings.
  2. Configure the SIP server and the custom domain if needed.
     Caption
    0Figure
    1SIP
     Image Modified

 Anchor
IAD B2BUA
IAD B2BUA
B2BUA
  1. Select VoIP > SIP > B2BUA to configure the B2BUA settings.
  2. Configure a Trunk Device if needed and click Update.
     Caption
    0Figure
    1Trunk Devices
    Image Modified

  3. Configure an Action if needed and click Update.
     Caption
    0Figure
    1Action
    Image Modified

  4. Configure a Match if needed and click Update.
     Caption
    0Figure
    1Match
    Image Modified

 Anchor
SIP UA
SIP UA
SIP UA
  1. Select VoIP > SIP > SIP UA to configure the FSX/Phone port settings.
  2. Configure the Global configuration as needed.
  3. Configure the Ports.
     Caption
    0Figure
    1Global Configuration
    Image Modified

     Caption
    0Figure
    1Port Level Configuration
    Image Modified

     Tip
    titleFXS/Phone Port Settings
    Bind the FXS ports to the LAN interface. Perform this configuration under the Advanced options.

...
This subsection verifies the WAN VLAN header interoperability (for IADs with EOC circuits only).
 Caption
0Table
1WAN LAN

Case #
Description
Action
Expected Results
Observed Results
P/F
2.1.1.1    
SIP
(EOC Only)
Actions:
  1. Connect or provision at least one phone on a switch behind IAD.
  2. Mirror port on a switch for the IAD WAN interface or connect hub to the IAD WAN interface.
  3. Capture signaling for approximately 30 seconds.
Verify:
SIP signaling packets sent from IAD contain a header with VLAN ID = 3.
We do not have an EOC.
N/A
2.1.1.2    
RTP
(EOC Only)
Actions:
  1. Connect or provision at least one phone on a switch behind IAD.
  2. Mirror port on a switch for the IAD WAN interface or connect hub to the IAD WAN interface.
  3. Capture signaling for approximately 5 seconds while placing the call from a phone out to PSTN.
Verify:
RTP packets sent from IAD contain a header with VLAN ID = 3.
...

We do not have an EOC.
N/A
2.1.1.3    
Data
(EOC Only)
Actions:
  1. Connect and startup at least one PC on a switch behind IAD.
  2. Mirror port on a switch for the IAD WAN interface or connect hub to the IAD WAN interface.
  3. Capture signaling for approximately 5-10 seconds while browsing out to the internet from PC.
Verify:
HTTP packets sent thru IAD contain a header with VLAN ID = 3.
...

We do not have an EOC.
N/A


 Anchor
LAN VLAN
LAN VLAN
LAN VLAN
This subsection verifies the LAN VLAN / DHCP interoperability.
 Caption
0Table
1LAN VLAN

Case #
Description
Action
Expected Results
Observed Results
P/F
2.1.1.4    
VLAN 10
Actions:
  1. Connect and startup at least one PC on a switch or behind a phone.
  2. Use a PC to browse out to the internet.
Verify:
  • PC has an IP address between 192.168.1.20 and 192.168.1.200.
  • PC can successfully browse out to internet.
N/A
P
2.1.1.5    
VLAN 20
Actions:
  1. Connect and startup at least one phone on a switch behind IAD.
  2. Establish a call out to PSTN.
Verify:
  • Phone has an IP address between 172.20.20.20 and 172.20.20.200.
  • Phone can register and establish a call to the PSTN.
N/A
P
2.1.1.6    
VLAN 30
Actions:
  1. Connect a PC to the management port on a switch (port 48 on SG500-52P; otherwise G2).
  2. Set a PC IP address to 10.30.30.10 or higher.
  3. Browse from a PC to IAD management IP address (10.30.30.1) and log into the IAD GUI.
Verify:
PC can browse to an IAD management IP address (10.30.30.1) and login to the IAD GUI is successful.
N/A
P


 Anchor
DHCP
DHCP
2.2 DHCP
This section verifies the DHCP interoperability. Some DHCP interoperability is verified in the preceding LAN VLAN section.
...
This subsection verifies the DHCP interoperability.
 Caption
0Table
1Options

Case #
Description
Action
Expected Results
Observed Results
P/F
2.2.1.1    
Option 66
Actions:
  1. Factory default Polycom phone.
  2. Place phone on a switch behind IAD.
Verify:
Phone is provided provisioning server info from the IAD through DHCP option 66.
It was verified using PCAP file.
P
2.2.1.2    
Option 42
Actions:
  1. Factory default Polycom phone.
  2. Place phone a on switch behind IAD.
Verify:
Phone is provided NTP server = btnp.hawaiiantel.net from the IAD through DHCP.
It was verified using PCAP file.
P
2.2.1.3    
Time Offset
Actions:
  1. Factory default Polycom phone.
  2. Place phone on a switch behind IAD.
Verify:
Phone is provided time offset (-10) from the IAD through DHCP.
It was verified using PCAP file.
P


 Anchor
NAT
NAT
2.3 NAT
This section verifies the NAT interoperability.
...
This subsection verifies the interoperability with the NAT – Port Forwarding feature.
 Caption
0Table
1Port Forwarding

Case #
Description
Action
Expected Results
Observed Results
P/F
2.3.1.1   
SIP
Actions:
  1. Log into the IAD GUI and select Configuration Menu > Network > NAT > Port Forwarding.
  2. Add the Port Forwarding Rule to DUT.
  3. Use browser to access.
Verify:
SIP signaling packets sent from the IAD contain header with VLAN ID = 3.
It was testing by mapping the WAN IP address and port 9090 to the Polycom phone behind the IAD, so login to the Polycom GUI was possible using the WAN IP:9090 address.
P


 Anchor
SIP UA / FAX
SIP UA / FAX
2.4 SIP UA / FAX
...
This subsection verifies the T.38 and G.711 interoperability.
 Caption
0Table
1T.38 / G.711

Case #
Description
Action
Expected Results
Observed Results
P/F
2.4.1.1    
G.711 / ECM-On / 14.4 / PSTN-to-VoIP / 1-Page
Configure fax machine as follows:
  1. ECM = On
  2. Speed = 14.4 (Normal)
Actions:
Send 1 page fax from PSTN based fax machine to VoIP based fax machine.
Verify:
1 page received.
N/A
P
2.4.1.2    
G.711 / ECM-Off / 9.6 / PSTN-to-VoIP / 5-Page
Configure fax machine as follows:
  1. ECM = Off
  2. Speed = 9.6
Actions:
Send 5 page fax from PSTN based fax machine to VoIP based fax machine.
Verify:
5 pages received.
N/A
P
2.4.1.3    
G.711 / ECM-On / 14.4 / PSTN-to-VoIP / 10-Page
Configure fax machine as follows:
  1. ECM = On
  2. Speed = 14.4 (Normal)
Actions:
Send 10 page fax from PSTN based fax machine to VoIP based fax machine.
Verify:
10 pages received.
N/A
P
2.4.1.4    
T.38 / ECM-On / 14.4 / VoIP-to-VoIP / 5-Page
Configure fax machine as follows:
  1. ECM = On
  2. Speed = 14.4
Actions:
Send 5 page fax from VoIP based fax machine to VoIP based fax machine.
Verify:
5 pages received.
N/A
P
2.4.1.5    
T.38 / ECM-Off / 9.6 / VoIP-to-VoIP / 5-Page
Configure fax machine as follows:
  1. ECM = Off
  2. Speed = 9.6
Actions:
Send 5 page fax from VoIP based fax machine to VoIP based fax machine.
Verify:
5 pages received.
N/A
P
2.4.1.6    
T.38 / ECM-On / 14.4 / VoIP-to-PSTN / 1-Page
Configure fax machine as follows:
  1. ECM = On
  2. Speed = 14.4
Actions:
Send 1 page fax from VoIP based fax machine to PSTN based fax machine.
Verify:
1 page received.
N/A
P
2.4.1.7    
T.38 / ECM-Off/ 9.6 / PSTN-to-VoIP / 5-Page
Configure fax machine as follows:
  1. ECM = Off
  2. Speed = 9.6
Actions:
Send 5 page fax from PSTN based fax machine to VoIP based fax machine.
Verify:
5 pages received.
N/A
P
2.4.1.8    
T.38 / ECM-On / 14.4 / PSTN-to-VoIP / 10-Pages
Configure fax machine as follows:
  1. ECM = On
  2. Speed = 14.4
Actions:
Send 10 page fax from PSTN based fax machine to VoIP based fax machine.
Verify:
10 pages received.
N/A
P


 Anchor
4570 Analog Gateway Fax
4570 Analog Gateway Fax
4570 Analog Gateway Fax
This subsection verifies the 4570 Analog Gateway fax interoperability.
 Caption
0Table
14570 Analog Gateway Fax

Case #
Description
Action
Expected Results
Observed Results
P/F
2.4.1.9    
ATA to PSTN
Configure fax machine as follows:
  1. ECM = On
  2. Speed = 14.4
Actions:
Send 5 page fax from 4570 ATA based fax machine to PSTN based fax machine.
Verify:
5 pages received.
N/A
P
2.4.1.10   
PSTN to ATA
Configure fax machine as follows:
  1. ECM = On
  2. Speed = 14.4
Actions:
Send 5 page fax from PSTN based fax machine to 4570 ATA based fax machine.
Verify:
5 pages received.
N/A
P
2.4.1.11    
ATA to ALG
Configure fax machine as follows:
  1. ECM = On
  2. Speed = 14.4
Actions:
Send 5 page fax from 4570 ATA based fax machine to ALG based fax machine.
Verify:
5 pages received.
N/A
P
2.4.1.12    
ALG to ATA
Configure fax machine as follows:
  1. ECM = On
  2. Speed = 14.4
Actions:
Send 5 page fax from ALG based fax machine to 4570 ATA based fax machine.
Verify:
5 pages received at VoIP fax machine.
N/A
P
2.4.1.13    
ALG to PSTN
Configure fax machine as follows:
  1. ECM = On
  2. Speed = 14.4
Actions:
Send 5 page fax from ALG based fax machine with 4570 ATA to PSTN based fax machine.
Verify:
5 pages received.
N/A
P
2.4.1.14    
PSTN to ALG
Configure fax machine as follows:
  1. ECM = On
  2. Speed = 14.4
Actions:
Send 5 page fax from PSTN based fax machine to ALG based fax machine with 4570 ATA.
Verify:
5 pages received.
N/A
P
2.4.1.15    
ATA to ATA
Configure fax machine as follows:
  1. ECM = On
  2. Speed = 14.4
Actions:
Send 5 page fax from VoIP based fax machine to PSTN based fax machine.
Verify:
5 pages received.
N/A
P
2.4.1.16    
ALG to ALG
Configure fax machine as follows:
  1. ECM = On
  2. Speed = 14.4
Actions:
Send 5 page fax from VoIP based fax machine to PSTN based fax machine.
Verify:
5 pages received.
N/A
P


 Anchor
Security
Security
2.5 Security
...
This subsection verifies the firewall interoperability.
 Caption
0Table
1Firewall

Case #DescriptionActionExpected ResultsObserved ResultsP/F
2.5.1.1    HTTPActions:
  1. Browse to the WAN IP address of the IAD from the PC not behind IAD.
  2. Browse through all tabs of the IAD GUI.
Verify:
  • IAD GUI can be reached through HTTP.
  • All IAD GUI tabs can be accessed.
N/AP
2.5.1.2
SSH
Actions:
Establish an SSH connection to the WAN IP address of the IAD from the PC not behind IAD.
Verify:
SSH connection can be established via WAN IP address of IAD from PC not behind IAD.
N/AP
2.5.1.3 
SNMPThis is a place holder for a future test. Currently the SNMP is enabled but configured on IAD.N/AN/A


 Anchor
Trusted Hosts
Trusted Hosts
Trusted Hosts
 This subsection verifies the Trusted Hosts interoperability.
 Caption
0Table
1Trusted Hosts

Case #
Description
Action
Expected Results
Observed Results
P/F
2.5.1.4    
HTTP
Actions:
Attempt to browse to the WAN IP address of the IAD from a PC with an IP address not listed in Trusted Hosts.
Verify:
The attempt to browse should time-out (no response from IAD).
The untrusted IP address is 10.10.216.47.
P
2.5.1.5    
SSH
Actions:
Attempt to establish an SSH connection to the WAN IP address of the IAD from a PC not listed in Trusted Hosts.
Verify:
The attempt should time-out (fail) as no response should be received.
The untrusted IP address is 10.10.216.47.
P
2.5.1.6    
SNMP
This is a place holder for a future test.
SNMP enabled but configured on IAD at this time.
N/A
N/A


 Anchor
Survivability
Survivability
2.6 Survivability
...
This subsection verifies the SIP server reachability interoperability.
 Caption
0Table
1SIP Server Reachability

Case #
Description
Action
Expected Results
Observed Results
P/F
2.6.1.1   
KeepAlives
Actions:
  1. Ensure Configuration Menu > Survability page is configured as described in section 2.2.4.4.4 of HPBX LLD.
  2. Place one or more phones on the switch behind IAD.
Verify:
  • IAD sends keepalive messages every 5 seconds.
  • IAD marks the SIP server as down 6 seconds after missed SIP message.
  • IAD marks the SIP server up (after being down) on the 10 successfully received response.
  • IAD interprets error code 403 as success.
N/A
P
2.6.1.2    
Register Rate-Pacing
Actions:
  1. Ensure Configuration Menu > Survability > Register Rate-Pacing parameters are configured as described in section 2.2.4.4.4 of HPBX LLD.
  2. Place phone one or more phones on the switch behind IAD.
Verify:
The 200 OK response sent back to a phone respective to a REGISTER initiated by the phone has Expires = 30 (not 1800), which means the IAD does not perform register rate-pacing and allows the SBC to dictate the registration interval.
N/A
P


 Anchor
Test UA
Test UA
2.7 Test UA
This section is a place holder for a possible future test. Currently, this functionality is verified in the Edgeview section below.
 Caption
0Table
1Test UA

Case #
Description
Action
Expected Results
Observed Results
P/F
N/AN/AN/AN/AN/AN/A

 

 Anchor
Traffic Shaper
Traffic Shaper
2.8 Traffic Shaper
 This section verifies the Traffic Shaper interoperability.
 Caption
0Table
1Traffic Shaper

Case #
Description
Action
Expected Results
Observed Results
P/F
2.8.1.1    
DSL
Actions:
  1. Ensure Traffic Shaping is enabled and configured per section 2.2.4.5.3 of HPBX LLD.
  2. Place a PC on the switch behind IAD with DSL.
  3. From a PC, perform the bandwidth speed test (or establish a large FTP upload and a large FTP download) while performing 2 to 3 simultaneous test calls.
Verify:
  • Test calls completed successfully with 4.0 or higher MOS.
  • Bandwidth test or FTP transfer completed successfully.
We do not have a DSL.
N/A
2.8.1.2    
EoC
Actions:
  1. Ensure Traffic Shaping is enabled and configured per section 2.2.4.5.3 of HPBX LLD.
  2. Place a PC on the switch behind IAD with EOC.
  3. From a PC, perform the bandwidth speed test (or establish a large FTP upload and a large FTP download) while performing 2 to 3 simultaneous test calls.
Verify:
  • Test calls completed successfully with 4.0 or higher MOS.
  • Bandwidth test or FTP transfer completed successfully.
We do not have an EoC.
N/A


 Anchor
Class of Service
Class of Service
Class of Service
This section verifies the Class of Service interoperability.
 Caption
0Table
1Class of Service

Case #
Description
Action
Expected Results
Observed Results
P/F
2.8.1.3    
LAN / WAN Markings
Actions:
  1. Place one or more Phones on the switch connected to IAD.
  2. Place a PC on the switch behind IAD.
  3. Perform the following simultaneously:
    • Establish a test call from the phone behind IAD out to the phone not behind IAD.
    • Execute bandwidth speed test from the PC behind IAD.
    • Execute tcpdump command on the LAN interface of IAD.
    • Execute tcpdump command on the WAN interface of IAD.
Verify:
  • SIP and RTP packets sent to a phone through the LAN interface of IAD are marked with DSCP 46 and include VLAN ID = 20.
  • Data packets sent to a PC through the LAN interface are not marked with DSCP 46 (that is, best effort) and include VLAN ID = 10.
  • SIP / RTP packets sent through the WAN interface of IAD are marked with DSCP 46 and (if IAD has EoC circuit) include VLAN ID = 3.
  • Data packets sent through the WAN interface are not marked with DSCP 46 (that is, best effort) and (if IAD has EoC circuit) include VLAN ID = 3.
 
 N/A
P
2.8.1.4    
  CoS
...
 
...
 
 
 
 
 
 
 



Actions:
  1. Place one or more Phones on the switch connected to IAD.
  2. Place a PC on the switch behind IAD.
  3. Delete CoS settings from IAD as shown.
  4. Perform bandwidth speed test from the PC behind IAD.
  5. Record download speed from the bandwidth speed test results (should match access method).
  6. Restore CoS settings on the IAD per section 2.2.4.5.3 in HPBX LLD.
  7. Establish approximately 75% of the max number of simultaneous calls using G.711 (that is, DSL = 8) from the phone(s) behind IAD out to phones not behind IAD.
  8. Perform a bandwidth speed test from the PC behind IAD.
  9. Record download speed of the bandwidth speed test results.
Verify:
  • Download bandwidth test results taken after removing CoS match access method (that is, approximately 1000k for DSL).
  • Download bandwidth test results taken after re-adding CoS should be limited to 25% of access method (that is, approximately 250k for DSL).
 
 


  
There are only three phones to place simultaneous calls, so the data bandwidth was set as 87%.
P

 

 Anchor
Call Admission Control
Call Admission Control
Call Admission Control
This subsection verifies the CAC interoperability.
 Caption
0Table
1Call Admission Control

Case #
Description
Action
Expected Results
Observed Results
P/F
2.8.1.5   
CAC - PSTN
Configuration:
Ensure Enable Call Admission Control on Traffic Shaper page is checked.
Actions:
  1. SSH to IAD and monitor the /var/log/messages file.
  2. Establish a call from the phone behind IAD to the PSTN phone.
  3. Verify CAC is incremented in messages file.
  4. Release call to the PSTN phone from the IP phone.
  5. Verify CAC is decremented.
  6. Establish call to the phone behind IAD from the PSTN phone.
  7. Verify CAC is incremented in messages file.
  8. Release a call from PSTN phone.
  9. Verify CAC is decremented.
Verify:
  • When a call is established, CAC is incremented in messages file.
  • When a call is released, CAC is decremented in messages file.
...

Active calls were incremented/decremented in the message file.
P
2.8.1.6    
CAC – Single IAD
Configuration: 
Ensure Enable Call Admission Control on Traffic Shaper page is checked.
Actions:
  1. SSH to IAD and monitor the /var/log/messages file.
  2. Establish a call from phone A behind IAD to phone B behind same IAD.
  3. Verify CAC is not incremented in messages file.
  4. Release a call from phone A.
Verify:
When a call is established between phones behind the same IAD, CAC is not incremented or decremented in messages file.
...

Direct Media was enabled on the SBC Core, so no configuration is needed in the EM.
P
2.8.1.7    
CAC – Multiple IADs
Configuration:
Ensure Enable Call Admission Control on Traffic Shaper page is checked.
Actions:
  1. SSH to IAD and monitor the /var/log/messages file.
  2. Establish a call from phone A behind IAD (A) to phone B behind another IAD (B).
  3. Verify CAC is incremented in messages file of IAD (A).
  4. Release call phone A.
  5. Verify CAC is decremented.
  6. Establish a call from phone A behind IAD (A) to phone B behind another IAD (B).
  7. Verify CAC is incremented in messages file.
  8. Release a call from PSTN phone B.
  9. Verify CAC is decremented.
Verify:
  • When a call is established, CAC is incremented in messages file.
  • When a call is released, CAC is decremented in messages file.
A second EM was used to simulate a different IAD.
P
2.8.1.8    
CAC – Local Hold
Configuration:
Ensure Enable Call Admission Control on Traffic Shaper page is checked.
Actions:
  1. SSH to IAD and monitor the /var/log/messages file.
  2. Establish a call from phone A behind IAD to phone B behind different IAD or to PSTN.
  3. From phone A, place call on hold.
  4. Resume call on phone A.
  5. Release call from phone A.
Verify:
  • When a call is established, CAC is incremented.
  • When a call is held, CAC is decremented.
  • When a call resumes, CAC is incremented.
  • When a call is released, CAC is decremented.
 

N/A
P
2.8.1.9   
CAC Exceeded Outbound
Configuration:
  1. Set CAC max on the Traffic Shaper page to max = 2 calls.
  2. Ensure Enable Call Admission Control is checked. 
Actions: 
  1. SSH to IAD and monitor the /var/log/messages file.
  2. Attempt to establish 3 calls from the phones behind IAD out to phones not behind DUT (that is, PSTN phones or phones not behind other IADs).
Verify:
Busy tone is heard when attempting to establish the third call and the messages file reports CAC exceeded message.
CAC is not working as expected, so the case 200115-297792 was opened for this issue.
...

Note: Jira EM-24480 was created for this issue.
F
2.8.1.10    
CAC Exceeded Inbound
Configuration:
  1. Set CAC max on the Traffic Shaper page to max = 2 calls. 
  2. Ensure Enable Call Admission Control is checked.
Actions:
  1. SSH to IAD and monitor the /var/log/messages file.
  2. Attempt to establish 3 calls from phones not behind IAD in to phones behind DUT.
Verify:
Treatment or VM is heard when attempting to establish the third call and the messages file reports CAC exceeded message.
CAC is not working as expected, so the case 200115-297792 was opened for this issue.
 

Note: Jira EM-24480 was created for this issue.
F
2.8.1.11   
CAC Reboot
Configuration:
Ensure Enable Call Admission Control is checked.
Actions:
  1. SSH to IAD and monitor the /var/log/messages file.
  2. Establish call from phone A behind IAD to phone B on PSTN phone or behind another IAD.
  3. Verify CAC is incremented in the /var/log/messages file.
  4. Remove power / Ethernet cable on phone A.
  5. Hang up after 20-30 seconds.
  6. Verify CAC is decremented in the /var/log/messages file.
Verify:
  • When call is established, CAC is incremented.
  • When phone is rebooted, CAC is not incremented or decremented.
  • When phone B is hung up, CAC is decremented.
N/A
P


 Anchor
System
System
2.9 System
...
This subsection verifies the backup interoperability.
 Caption
0Table
1Backup / Restore

Case #
Description
Action
Expected Results
Observed Results
P/F
2.9.1.1    
Backup / Restore
Actions:
  1. Log into IAD.
  2. Select Configuration Menu > System > Backup / Restore page and create a backup.
  3. After creating a backup successfully, change any parameter of choice on the IAD.
  4. Select Configuration Menu > System > Backup / Restore page and restore the backup created in this procedure.
Verify:
  • Backup completes successful.
  • Restore completes successful.
  • Parameter changed in action step 3 changes back to original value after the restore.
N/A
P


 Anchor
Proxy ARP
Proxy ARP
Proxy ARP
This subsection verifies the proxy ARP interoperability.
 Caption
0Table
1Proxy ARP

Case #
Description
Action
Expected Results
Observed Results
P/F
2.9.1.2    
 Proxy ARP
Actions:
  1. Configure the Proxy ARP feature per section 2.2.4.5.5 of HPBX LLD using a PC as the Proxy ARP device.
  2. From a PC not behind IAD, attempt to ping the PC configured as Proxy ARP device.
Verify:
Successfully receive a response from the device configured as Proxy ARP device (that is, PC).
Arping was sent from another EM connected to the WAN interface of the IAD. IAD’s MAC address is used as a source address of the ARP response when pinging the PC behind the IAD.
P


 Anchor
Syslog - MOS
Syslog - MOS
Syslog - MOS
This is a place holder for a possible future test to verify the MOS interoperability.  MOS functionality is currently covered in the EdgeView section.
 Caption
0Table
1Syslog - MOS

Case #
Description
Action
Expected Results
Observed Results
P/F
N/A
N/A
N/A
N/A
N/A
N/A


 
 Anchor
Upgrade Firmware
Upgrade Firmware
Upgrade Firmware
This subsection verifies the upgrade interoperability.
 Caption
0Table
1Upgrade Firmware

Case #
Description
Action
Expected Results
Observed Results
P/F
2.9.1.3    
Downgrade
Actions:
  1. Select Configuration Menu > System > Upgrade Firmware page and downgrade IAD to version 11.6.9.
Verify:
  • Verify downpgrade completes successfully.
  • Verify IAD can successfully pass phone registrations and calls after upgrade.
N/A
P
2.9.1.4    
Upgrade
Actions:
  1. Select Configuration Menu > System > Upgrade Firmware page and upgrade IAD to version 11.6.14.
Verify:
  • Verify upgrade completes successfully.
  • Verify IAD can successfully pass phone registrations and calls after upgrade.
N/A
P


 Anchor
EdgeView
EdgeView
2.10 EdgeView
...
This subsection verifies the EdgeMarc / EdgeView discovery interoperability.
 Caption
0Table
1Discover

Case #
Description
Action
Expected Results
Observed Results
P/F
2.10.1.1    
Discover / Move
Actions:
  1. Ensure Configuration Menu > System > Services Configuration > Enable Remote System Logging is enabled and Remote Syslog Hosts field is populated with EV IP address.
  2. Create new group on EV.
  3. Move EM to new group.
Verify:
  • IAD displays in the Unknown group of EV device list.
  • New group can be created on EV.
  • EM can be moved to new group.
N/A
P


 Anchor
Monitor
Monitor
Monitor
This subsection verifies the EdgeView monitoring interoperability.
 Caption
0Table
1Monitor

Case #
Description
Action
Expected Results
Observed Results
P/F
2.10.1.2  
 Monitor
  Actions:
  1. Log into EV and navigate to IAD in device list.
  2. Test IAD from EV.  
Verify:
  • SSH access is successful.
  • SNMP is successful.
SNMP was configured in the EdgeMarc and SNMP traps are sent to the EdgeView.
P


 Anchor
Test UA
Test UA
Test UA
This subsection verifies Outlook Integration interoperability.
 Caption
0Table
1Test UA

Case #
Description
Action
Expected Results
Observed Results
P/F
2.10.1.3    
MOS
Actions:
  1. Configure the Test UA feature on two IADs (see section 2.2.4.5.1 of HPBX LLD for configuration instructions).
  2. Using EV, perform a test call between two IADs.
Verify:
Test call completed successfully with 3.9 or higher MOS.
The managing Test UA feature is not supported by the EdgeView 15.x and later versions.
N/A


 Anchor
Change Parameter
Change Parameter
Change Parameter

 Caption
0Table
1Change Parameter

Case #
Description
Action
Expected Results
Observed Results
P/F
2.10.1.4    
Change Single Parameter
...

Actions:
  1. Log into EV and locate IAD in device list.
  2. Change a single parameter on IAD.
Verify:
A single parameter was changed successfully.
N/A
P


 Anchor
Remote Backup / Restore
Remote Backup / Restore
Remote Backup / Restore
This subsection verifies the EdgeView Remote Backup and Remote Restore interoperability.
 Caption
0Table
1Remote Backup / Restore

Case #
Description
Action
Expected Results
Observed Results
P/F
2.10.1.5    
Remote Backup / Restore - Immediate
Actions:
  1. Log into EV and locate IAD in device list.
  2. Backup IAD immediately.
  3. Make change to any parmater on IAD configuration and save change to IAD.
  4. Restore IAD configuration.
Verify:
  • Backup completes successfully.
  • IAD config change is saved.
  • Restore completes successfully.
  • Change made to IAD config was removed in restore.
N/A
P
2.10.1.6   
Remote Backup / Restore - Scheduled
Actions:
  1. Log into EV and locate IAD in device list.
  2. Schedule IAD backup.
  3. Make change to any parmater on IAD configuration and save change to IAD.
  4. Restore (and load) backup configuration.
Verify:
  • Backup completes successfully.
  • IAD config change is saved.
  • Restore completes successfully.
  • Change made to IAD config was removed in restore.
N/A
P


 Anchor
Load Template
Load Template
Load Template
This subsection verifies the template loading interoperability.
 Caption
0Table
1Load Template

Case #
Description
Action
Expected Results
Observed Results
P/F
2.10.1.7    
Upload Template
  Actions:
  1. Create template on EV.
  2. Configure IAD only with IP address information.
  3. Upload template to IAD.
Verify:
  • Template can be created on EV.
  • IP address information is configured on IAD.
  • Each page of IAD configuration reflects expected parameters following the template upload.
The managing Template feature is not supported by the EdgeView 15.x.
N/A


Conclusion
These Application Notes describe the configuration steps required for the Ribbon EdgeMarc 2900A and Ribbon SWe to successfully interoperate with Broadsoft. All feature and serviceability test cases were completed and passed with the exceptions and observations noted in Test Results.
Appendix A
 Anchor
Broadworks Service Guide
Broadworks Service Guide
Broadworks Service Guide

 Anchor
Broadworks - Polycom UC Software VVX and Trio Phones Guide
Broadworks - Polycom UC Software VVX and Trio Phones Guide
Broadworks - Polycom UC Software VVX and Trio Phones Guide