AudioCodes Service Requirements
Question
How should I configure my AudioCodes device to work with Fuze Services?
Applies To
- Fuze
- AudioCodes
Answer
Fuze provided AudioCodes devices use similar ports as our Voice and Collaboration services. However, the AudioCodes requires several other ports to be opened for initial troubleshooting and setup. Since they are isolated within a customer network and sometimes require more troubleshooting during initial setup, it’s crucial for all of the paths to be opened.
Network (IP Ranges)
Please reference the Fuze Services Guide for the current UC Services - Production Traffic IPs for the Port Directions.
AudioCodes Standard Service and Ports Requirements
|
Service |
Priority |
Source Ports |
Destination Ports/timeouts |
Additional Comments |
|
Provisioning and Administration |
||||
|
HTTP |
N/A |
N/A |
TCP 80 |
HTTP and HTTP-like transactions are using this port to allow egress from customer sites with strict outbound policies. If you have a deep inspection firewall, ensure that this traffic from your clients to the Fuze cloud is not rejected by over aggressive rules as this traffic. Provisioning Server 1: bos-cga-fc1.thinkingphones.com Provisioning Server 2: x.fuze.com |
|
HTTPS |
N/A |
N/A |
TCP 443 |
Again, packet inspection firewalls should be configured to not discard packets to these ports on addresses within our network block. Provisioning Server 1: bos-cga-fc1.thinkingphones.com Provisioning Server 2: x.fuze.com |
|
SSH |
N/A |
N/A |
TCP 22 |
Used on MPLS deployments only |
|
Signalling |
||||
|
SIP |
DSCP 26 (af31) IP Precedence 3 |
UDP 5060 TCP 5060 TCP 5061: TLS |
UDP 5060 (360 sec) TCP 5060 (600 sec) TCP 5061: TLS (600 sec) |
Performance Guidelines: Delay <150ms Jitter <30ms Packet Loss <1% |
|
Media Transmission |
||||
|
Audio RTP |
DSCP 46(ef) IP Precedence 5 |
UDP 6000-20000 |
UDP 6000-20000 (30 sec) |
Performance Guidelines: Delay <150ms; Jitter <30ms; Packet Loss <1% NOTE: Ports may vary if NAT is in use. |
|
Monitoring/Troubleshooting |
||||
|
ICMP |
N/A |
N/A |
ICMP |
Inbound ICMP to EDGE also recommended |
|
SNMP |
N/A |
N/A |
TCP 161,162,1161 |
34.239.225.160 |
|
SYSLOG |
N/A |
N/A |
UDP 5514 |
Syslog Server: 18.210.147.169 The Syslog port does not need to be permanently opened as Syslog is not enabled on the device by default. |
SNMP
Where SNMP cannot be authorized as outbound protocol for AudioCodes management, Fuze will only know if the customer is having a hardware or carrier outage when they inform Fuze rather than Fuze telling the customer.
SYSLOG
If the customer is unable to provide syslog access during periods of troubleshooting, then the customer must provide a form of remote access via a local laptop to run the syslogger application. The laptop must be connected to the same local network as the AudioCodes. The additional time to do this when required will impact the SLA and should be considered for any escalation/P1 time impact as well.
Faxing
When connecting a fax to an AudioCodes device, the recommended baud rate is 9,600 to ensure stable fax transmission.
Faxing over VoIP can present certain challenges which require a slower transmission speed, to ensure the data reaches it's destination with the maximum amount of reliability. Packet loss, jitter, and latency all contribute to the degradation of fax transmission over VoIP. When a fax machine determines that data is lost, it will shut down the transmission, even though the document is still complete from a usability standpoint. By slowing down the transmission speed to 9600, you significantly increase the probability of successful completion of the transmission because the amount of data reaching the destination is very likely to stay above the aforementioned threshold. This reduced baud rate may require additional time when sending and receiving multi-page faxes.
Fuze also recommends using a G.711 audio codec and not a compressed codec (e.g., G.729) ,as well as ensuring that ECM is disabled on the fax machine.