Cisco Business Edition 4000

1000px-Cisco_logo.svg
How Can We Help?

SIP Trunk Connectivity

The BE4000 also allows calling via IP trunks to service providers using SIP.

Note: SIP Trunk supports up to 100 sessions

A variety of options are provided that allow services to be delivered via dedicated service connections, or over the top of a customer’s internet access. To simplify configuration, a number of preconfigured templates for certain service providers are also offered through the management portal.

SIP Service Provider

As part of the End of Life strategy onboarding new SIP Trunk providers is no longer possible (new templates are no longer getting created).
The majority of SIP trunk providers can be configured using one of the existing provider templates or using the ‘Custom’ option.

If none of these options is working for your SIP provider, you can request that your BE4000 be released from the BE4000 portal which will allow for local unrestricted configuration using the CLI. For this option please carefully read the “End of Life Communications” section and then visit the “Appliance Release Request” section.

If you require minor modifications to an existing SIP trunk that cannot be resolved through the portal and deleting the existing trunk and adding a new one has not been successful, please raise a support case with TAC and the case will be assessed for support eligibility.


Supported SIP Trunk Connectivity

The BE4000 offers two primary options for connecting to a SIP VoIP trunking service:

  1. Using the main interface (GE 0/0/0) of the BE4000 for the SIP trunk, media and cloud management connection

  2. Using the BE4000 secondary interface (GE 0/0/1) connected to a dedicated internet connection for your VoIP service

Using the BE4000 Main Interface for SIP Trunk Connectivity

In this scenario, the BE4000 is connected as a privately addressed host in your local area network, so it is assumed that all traffic sent to the internet is subject to Network Address Translation (NAT). As such, the following is required to reliably exchange VoIP traffic:

  1. Secure a static public internet address from your ISP. The BE4000 uses this address to ensure that signaling is properly formatted as it is sent.

  2. It may also be necessary to forward inbound traffic to the BE4000, especially if your SIP provider does not require registration. Depending on the capabilities of your WAN router, this may be accomplished in a number of ways:

    1. Add port forwarding rules for SIP signaling and media traffic.

    2. Use static NAT rules.

    3. Configure the BE4000 IP address as a DMZ host.

Using the BE4000 Secondary Interface for SIP Trunk and External Media

The secondary interface may be configured with an IP address either manually or dynamically through DHCP. If a manual address is configured and traffic is passed through NAT, then an external IP address may be configured in the portal to fix up signaling traffic. This option is not currently offered where an address is assigned dynamically. In this case, it is assumed that the assigned address is either publically routable, or if NAT is used, then the VoIP provider offers transparent hosted NAT traversal.

When using the secondary interface, the BE4000 must be assigned an address in a different subnet to that used for the primary interface.

To ensure that traffic is correctly routed and accepted, all IP addresses used by your provider must be included in the portal trusted address list for the trunk.

Previous Single-Site Deployment
Next Transfer an inbound caller to an external PSTN number via AA
Table of Contents
Close Menu