Prerequisites
You need anynode version 4.12.5 or higher to successfully use this feature. The node configuration must be identical on every anynode instance if you want to set up a request router. To successfully set up and configure the system, ensure that you have appropriate network access, correct network routing, and administration rights. Additionally, an accessible and pre-configured VoIP environment is required to permit necessary configurations. Finally, make sure you have a fully functional anynode production or trial license.
The node configuration must be identical on every anynode instance if you want to set up a request router.
The remote party, in our example the provider, must ensure that it accepts SIP messages from all involved anynode systems. The provider should send all incoming calls only to the anynode system where the Request Router is configured. The Request Router will then handle the distribution of calls to the other anynode systems.
Since anynode with the Request Router handles the initial SIP INVITES to the anynode systems, incoming requests from the VoIP provider are first processed by the anynode with the Request Router and then potentially forwarded to secondary or other anynode systems.
To ensure that other anynode systems accept SIP invites from the Request Router anynode, the IP address of the anynode with the Request Router must be added to the provider node's whitelist for all other anynode systems.
For encrypted connections, the Request Router's certificate must be included in the Trusted Peer Certificates of the receiving node.
In scenarios involving Microsoft Teams Direct Routing, note the following:
The Request Router may receive calls from Teams and distribute them to the various anynode systems. Since connections will not only be established from Microsoft to the Teams node, but also from the Request Router, each Teams node must trust the Request Router's certificate. If Subject Alternative Names (SANs) are used, the SAN of the Request Router must be included as well.