Prerequisites and design considerations
- For partners, access to Cisco Business Edition 4000 Partner Portal is managed by Cisco Partner Self Service (PSS) portal. Partner user roles are defined by the Cisco Partner Administrator in the PSS portal. Partner users must have a Cisco.com login and be associated with a Cisco partner. Once the partner user role is defined in the PSS portal, the partner user can access the BE4000 appliance from the URL be4000.cisco.com.
- For customer administrators and end users, the access to Cisco Business Edition 4000 Selfcare Portal is enabled after the successful deployment of the appliance. Registration emails are sent for notification.
- If you are logging in to the BE4000 Management portal for the first time, you must watch an introductory video. The video contains information about how to configure, deploy, and manage a BE4000 site. You can add or edit the BE4000 sites only after watching the complete video.
BE4000 requires certain network specifications for its deployment. Ensure that the customer network meets all the requirements before adding a site in the Cisco Business Edition 4000 Management Portal.
BE4000 Management Tunnel
Cisco Business Edition 4000 requires permanent access to the internet to communicate with the cloud portal, receive NTP time updates, receive software upgrades, and if configured, for carrying SIP traffic.If the internet connection is lost, the BE4000 still handles the calls that do not involve calls over the internet.
The following DMVPN Ports and Protocols are required to be open outbound on the connection used to connect to theCisco Business Edition 4000 Management cloud:
- UDP Port 500
- Internet Security Association and Key Management Protocol (ISAKMP). Used in IKE
- UDP Port 4500
- NAT Traversal (NAT-T). When the BE4000 is behind NAT, NAT-T encapsulates ESP in UDP port 4500 to allow ESP to communicate in and out of the network
- HTTP (port 80) and HTTPS (port 443) access from the BE4000 to the internet
- Outbound access to Domain Naming System (DNS): DNS port 53 must be open
- ICMP (Internet Control Message Protocol) access to SEA (188.8.131.52/27) and DFW (184.108.40.206/27) servers
Note: Each BE4000 appliance needs to be connected behind a NAT device behind a public IP address for management connectivity. Multiple BE4000 appliances cannot be configured behind the same public IP address.
- By default the BE4000 uses a DHCP address for initial deployment. A static address may be configured locally if a DHCP server is not available. Connection can be via console, or Ethernet to the MGMT port.
- When deploying Cisco Unified IP Phones, it is necessary for the phones to automatically discover the BE4000 to download phone configuration files. DHCP Option 66 and/or DHCP Option 150 is required to provide the TFTP address of the BE4000 for connecting the IP phones. If neither DHCP option 66 nor DHCP Option 150 is available, you must manually configure each IP phone’s TFTP configuration with the IP address of the BE4000.
The following IP Networks are not supported:
BE4000 in Voice VLANs
Before the phone has its IP address, the phone determines which VLAN it should be in by the Cisco Discovery Protocol (CDP) negotiation that takes place between the phone and the switch. This negotiation allows the phone to send packets with 802.1Q tags to the switch in a “voice VLAN” so that the voice data and all other data coming from the computer behind the phone are separated from each other at Layer 2. Voice VLANs are not required for the phones to operate, but they provide additional separation from other data on the network.Voice VLANs can be assigned automatically from the switch to the phone, thus allowing for providing Layer 2 and Layer 3 separation between voice data and all other data on a network. A voice VLAN also allows for a different IP addressing scheme because the separate VLAN can have a separate IP scope at the Dynamic Host Configuration Protocol (DHCP) server.
The BE4000 can be deployed on the voice VLAN or on a different IP subnet. In both the ways, the BE4000 needs to have directed routed access to all phones, and be able to access the internet.
Note: The BE4000 proxies the media. Phones only need signaling and media connectivity to the BE4000. They do not need signaling nor media connectivity to other phones.
Supported SIP VoIP Trunk Connectivity
Please refer to the ‘SIP Trunk Connectivity‘ article for more details.
Direct Inward Dial (DID) Numbers—Up to 98 numbers are supported for SIP trunks and 98 numbers for ISDN trunks (PRI and BRI).
SIP Trunk—Options Ping—Options Ping configuration added with the custom SIP template does not work as expected. If the SIP provider requires you to use Options Ping feature, contact the service provider on boarding team by sending an email to firstname.lastname@example.org.
Configuration Wizard—When a non-deployed configuration is edited, the first page of the configuration wizard is skipped. You cannot edit the Customer Name, and Location fields. In such a case, create a new configuration through the Business Edition 4000 partner portal.
- You can configure only one port for the following multiport BRI and PRI NIM cards:
- You cannot configure a combination of BRI (NIM-2BRI-NT/TE, NIM-4BRI-NT/TE) and PRI (NIM-1MFT-T1/E1, NIM-2MFT-T1/E1, NIM-4MFT-T1/E1) cards on the BE4000 appliance post site deployment (under Manage Site > Line Cards (NIM) > Add NIM Card). If your network requires both BRI and PRI cards, we recommend you to configure the line cards during the initial site deployment (in the Setup Assistant).
Cisco IP Phone 8800 Series
- Cisco Unified IP Conference Phone 8831 does not support Paging.
- Cisco IP Phone 8800 Series currently supports only session line mode (SLM) with the BE4000. As a result only the 5 buttons on the left of the phone display can be used as feature buttons and programmed as desired. The 5 buttons on the right of the phone display can only be used as line buttons to perform tasks such as resuming a held call.
Voicemail Support on FXS—The FXS ports on NIM cards do not support voicemail. If you are using an analog phone on FXS port and require voicemail support, we recommend that a Hunt Group is configured such that when the analog phone does not answer, the call is re-directed to an IP phone that has voicemail.
Centrex Lines—Centrex lines are not supported. Only Plain Old Telephone Service (POTS) lines are supported through FXS cards.
ATA 190 Analog Telephone Adapters—
- Cisco ATA 190 Analog Telephone Adapter can be added only post site deployment. You cannot add during initial site deployment.
- Cisco ATA 190 Analog Telephone Adapter can be added only under Manage Site > Phones. You cannot add Cisco ATA 190 Analog Telephone Adapter under Manage Site > Extensions and Manage Site > User Management.
- A fax call does not fall back to voice only call after the fax is sent.
- The following features are not supported:
- Single Number Reach (SNR)
- Speed dial
Call Detail Records and Emergency Alerting—These features are currently in development and are not intended for production use.
BE4000 is available for deployment in the countries listed below. Dial plan and localization support for end user portal is also available for the following countries:
Cisco Business Edition 4000 supports the following IP Phone Models containing Cisco enterprise software:
- Cisco IP Phone 7800 Series
- Cisco IP Phone 7811
- Cisco IP Phone 7821
- Cisco IP Conference Phone 7832
- Cisco IP Phone 7841
- Cisco IP Phone 7861
- Cisco IP Phone 8800 Series
- Cisco IP Phone 8811
- Cisco Wireless IP Phone 8821
- Cisco Unified IP Conference Phone 8831
- Cisco IP Conference Phone 8832
- Cisco IP Phone 8841
- Cisco IP Phone 8845
- Cisco IP Phone 8851 (Supports up to 2 Key Expansion Modules)
- Cisco IP Phone 8861 (Supports up to 3 Key Expansion Modules)
- Cisco IP Phone 8865 (Supports up to 3 Key Expansion Modules)
- Cisco IP Phone 8800 Key Expansion Module (KEM)
- Cisco ATA 190 Analog Telephone Adapter
—To ensure reliability and performance, your wireless LAN should meet the requirements that are outlined in the Cisco Wireless IP Phone 8821 and 8821-EX Wireless LAN Deployment Guide.
- Cisco IP Phone 8851/8861 Key Expansion Module (CP-8800-A-KEM=) and Cisco IP Phone 8865 Key Expansion Module (CP-8800-V-KEM=) are not supported.
- Cisco IP Phones containing Third-Party Call Control (3PCC) software are not supported.
Supported Line Cards
Cisco Business Edition 4000 supports a maximum of two line cards. The following are the supported line cards:
- NIM-1MFT-T1/E1 (requires PVDM4-32)
- NIM-2MFT-T1/E1 (requires PVDM4-64)
- NIM-4MFT-T1/E1 (requires PVDM4-128)
Supported Codecs in BE4000
BE4000 supports the following codecs:
- G711 (both a-law and mu-law)
Cisco Business Edition 4000 portals support the following browsers:
- Microsoft Internet Explorer (IE) version 11.0 and later
- Google Chrome version 58.0 and later
- Mozilla Firefox version 53.0.2 and later
- Safari version 9.1 and later
Supported Telephony Port Tones and Phone Tones
|Country||Telephony Port Tones||Phone Tones|
|Republic of Korea||Yes||Yes|
|Republic of Montenegro||No||Yes|
|United Arab Emirates||Yes||No|
|United States of America||Yes||Yes|
|Language||Phone Display||Voicemail and System Prompt Language||
(End User access only)
|Chinese (Hong Kong)||Yes||Yes||Yes|
|Spanish (Latin America)||Yes||Yes||Yes|
Supported SIP Service Provider Configuration Templates
BE4000 simplifies the SIP trunk configuration tasks by providing configuration templates specific to SIP service providers. SIP configuration templates are available for the following SIP service providers:
- Bell Canada
- Bell MTS
- Level 3
- Malaysia Telecom
- Novum Networks