![]() ![]() ![]() Configure Bandwidth Management and Quality of Service on the SonicWall.O If multiple routes are used for VoIP Traffic, ensure that all routes are setup with appropriate probes to denote when the relevant route is up or down. On the default load balancing group ensure that Source and Destination IP Address Binding is selected. O If multiple WANs are in use along with WAN load balancing, navigate to Network| System | Failover & LB. Ensure that all VoIP Traffic flows over a single WAN Interface.NOTE: It is also possible to Bypass SSO for an entire Zone, this is appropriate for deployments with a dedicated VoIP subnet. This will populate the entry in the SSO Bypass field. O Select Full Bypass (Don't Trigger SSO) and Save. TIP: It may be necessary to utilize an address or service object group in many deployments. Click Add Bypass and include address object or service object for exclusion from SSO. O On the pop-up window navigate to Enforcement. O Navigate to Device| Users | Settings and click Configure SSO. Exempt the PBX and all IP Phones from Single Sign-On.O Navigate to Policy| Security Services | Content Filter and exclude the necessary IP address ranges from Content Filtering. Exempt the PBX and all IP Phones from Content Filtering.For information on how to do so please see: How to Test and Change the MTU Size of WAN Interfaces. Perform an MTU Test on all WAN Interfaces that VoIP Traffic flows over.Because of this it is often necessary to optimize latency related settings on the SonicWall and other in-line network devices. NOTE: Both SIP and H.323 have poor tolerance for latent connections. In order to enable or disable SIP transformations navigate to Network | VoIP, click Settings and examine the Enable SIP Transformations setting.The below resolution is for customers using SonicOS 7.X firmware. This release includes significant user interface changes and many new features that are different from the SonicOS 6.5 and earlier firmware. TIP: If the PBX is located outside the SonicWall, usually on the public Internet, then SIP transformation should be enabled in most deployments. TIP: If the Public Branch Exchange (PBX) that the SIP Server communicates with is located behind the SonicWall then SIP transformations should be disabled in most deployments. This article will detail the common issues as well as how to resolve them on the SonicWall. While commonly playing the role of a Forwarder for VoIP traffic, there are possible issues that can arise from putting a firewall in line for SIP or H.323 Sessions. ![]() Copy URL The link has been copied to clipboard. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |