SonicWall VoIP Jive Networks QOS Tagging512
Pages:
1
|
LiquidLayer private msg quote post Address this user | |
| Sample dialog / SonicWall, Hosted VoIP from Jive Networks VoIP settings sample: Best Practice configuration document that Jive put together with the best practices for their VoIP system through a Sonicwall. In the VoIP settings of the Sonicwall I enabled consistent NAT, disabled SIP transformations, and increased the UDP timeout per Jive's instructions. They requested a WAN > LAN rule to allow inbound access from their IPs however they made no mention of a NAT policy to an internal VoIP server IP. I let Bobby know that the inbound rule would do no good without a NAT policy so he's going to reach out to Jive and see what they have to say. If these modifications don't help once the device is installed I let Bobby know that I can create some BWM rules for them to guarantee bandwidth to their phones. Also, unless their modem and all their switches/routers are doing QoS tagging, enabling this on the Sonicwall won't do any good because those will be stripped out on the other networking equipment. If they are still having issues after all the other areas of troubleshooting have been addressed then I'll look into configuring that and Bobby will need to ensure that's enabled on all his other equipment as well. |
||
| Post 1 • IP flag post | ||
|
|
LiquidLayer private msg quote post Address this user | |
| I am not aware of any VoIP server on premises, so I think the inbound rule may not be needed unless we hear different from Jive Networks. As far as I am aware there is only just "hosted" handsets . Pleased to hear that you were able to configure the firewall for Jive's Best Practice - I agree the BWM would be the next best option to enable if they continue to see quality issues with VoIP Calls. Good points on the QOS tagging regarding the Modem / switch's / routers - make perfect sense. |
||
| Post 2 • IP flag post | ||
Pages:
1
