The AudioCodes MP1xx devices will need to be manual configured to work with ACO. Please find here some guidelines for the configuration of these devices. The devices will work via UDP, TCP or TLS.
For TLS to work, please make sure you loaded the required certificates to the AudioCodes device. More information regarding secure SIP transport can be found here.
To configure the registration you will first need to get the SIP registration data from ACO service web. Each port will be configured as an "existing phone". The registration data can be copied from ACO service web to a text editor. The below is an example on how to configure the device for TLS (the configuration for UDP/TCP is similar to TLS, there are some ports that change and no media security needs to be configured).
SIP domain sip.ringcentral.co.uk:5060 ---> AudioCodes SIP Group Name / Gateway Name
SIP domain sip.ringcentral.co.uk --> AudioCodes SIP Group Name / Gateway Name
Remote SIP port 5060
Local SIP port 5060
Outbound proxy sip30.ringcentral.com:5096 ---> AudioCodes Proxy Address (5090 for TCP/UDP)
Outbound proxy port 5096 (5090 for TCP/UDP)
Username xxxxxxxxxxx <phone number> --> AudioCodes Hunt Group Endpoint Number
Password yyyyyyyyy <password> --> AudioCodes Authentication Password
Authorisation ID zzzzzzzzz <Authenthication> --> AudioCodes Authentication User Name
The above parameters are subject to change and should always be verified. It could be possible that the domain name changes. Please verify always the correct data from ACO service web.
For secure voice configure Media Security as below.
Media Security --> Enable
Authentication On Transmitted RTP Packets --> Active
Encryption On Transmitted RTP Packets --> Active
Encryption On Transmitted RTCP Packets --> Active