It looks like I'm having a NAT issue, when the client is trying to register
to the opensip server, my opensips server doesn't realize that
184.108.40.206 is itself, it only know that 172.31.23.32 (the private IP) is
its IP address. So when my request send to 220.127.116.11 (my opensips
server public IP), it doesn't realize that is itself, so my server forward
the request to 18.104.22.168, which is itself, again and again.
@billsimon Apache and I are now on speaking terms. @wardmundy's articles have piqued my interest, but I'm stuck a bit moving forward. If you don't mind more newbie questions, I'll ask away. If they are too dumb or you want to point me to a (valuable) online resource, that would be fine. It seems most OpenSips docs just tell you what configurations fields are, they don't explain how to use them!
So -- my goal is to use OpenSips are a Session Border Controller. All my PBX instances are cloud hosted. I want endpoints for multiple domains to register via OpenSips. I understand how to do that, and it is working.
What I want to understand is how routing works.
So, let's say I want to route all 10-digit NA calls to a particular provider, which uses IP Auth. This provider has a steering prefix. I'm not sure where to put the Steering prefix in.
Any enlightenment is appreciated, and any tips of brilliance will be accepted gracefully.