Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.
I am new to opensips. I have, with help, gotten 1.8 using mysql to accept registrations and make calls to UAs on the local lan connected to the machine running opensips. For some reason I cannot register UAs that are located outside this lan. The devices in question are known UAs with previously working configurations.
I have looked through the opensip cfg and not found anything I recognize that would block this like access lists.
I am sure this is a simple issue but I don't see it.
Thanks in advance.
First check if the actual REGISTER requests from the external UAs really get to opensips machine (at network level) - if so, place xlog() messages into your script to see how those REGISTERs are flowing through your script.
My topology is opensips behind a NAT adsl router with a fixed IP address (I currently have no other options). The external UAs are Grandstream HT-701 also behind NAT adsl routers (different from the opensips) There is a STUN server running on the WAN side of the opensips router that the external UAs use.
The REGISTER packets do indeed reach the opensips server but the source address of these packets is the external ip address of the server end router not the external ip address of the remote end router. Something is really messed up here and I don't think it is the opensips at this point. I tried using another public stun server but same results.
Do you think if I setup a combination router/opensips server that used the external/public ip address that this would work to make things simpler?
I would say that is your only option - if your opensips will not use/advertise the pub IP, it will not be able to talk with the external clients via public net.