I am after some guidance on how to implement combined PSTN calling with plans and direct routing with specific regard to customer network configuration.
If a customer has a single egress service for their client and server network to connect to the internet i.e. all traffic goes through one firewall device which also protects inbound services and NAT then all is fine. I don't have an issue with that.
However, I have a customer with two egress services. One for client browsing and one for server hosting. Both egress services are available across VLANs and the way in which the service is chosen is based on a static route at the core switch.
So they have a route for 18.104.22.168/14 which is the PSTN IP destination for PSTN Calling and Direct Routing and have configured it to egress out of their hosting firewall service. The problem is that clients also want to use this route as well as its advertised on the core switch. The problem is the hosting side does not have enough bandwidth and the route from all client subnets to this device is not optimal to be used as fit for purpose.
We can switch the core switch route to route to the browsing service which is optimized for client subnets and has the appropriate bandwidth but that then means the SBCs must also take that route. The problem with this is that the browsing firewall we don't support inbound connections, and have a public IP shortage due to network design to support this.
Our challenge is to fit this into the current network design without the customer having to spend more money or make significant changes to business critical systems.
Static routes on the SBC aren't going to work because I need to route through 4 hops to get to the required firewall. I just haven't found a way to solve this problem without bending their network design. Any help appreciated. thanks