I am embarrassed to say that I created my own problem. I had forgotten some of
the details of my firewall configuration. Iptables was set to allow everything
from the LAN, that is to say 192.168.0.0. Ip6tables was not set that way
because the hosts on the LAN had global addresses. To allow SIP
Actually when I was testing I entered the listen parameters on the command
line. I have now added them to the configuration file. The result is the same.
The UA keeps sending the REGISTER request but there is no response from
opensips. A UA on IPV4 can register on port 5062.
The configuration
Hello Robert,
Please post the "listen" lines you have in cfg and the output of
"netstat -ulnp | grep opensips" .
Best regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 05.12.2016 21:37, Robert Dyck wrote:
This is a re-send. I apologize if it
This is a re-send. I apologize if it is a duplicate. I suspect my subscription
was not enabled.
--
I have been doing some testing with opensips 2.2.2 using ipv6. I found that
the server will only respond to a
Hi, Robert!
Are you using only a single listening interface, on port 5062? Or you're
doing more complex scenarios?
You're saying that you are not seeing any debugging logs when a message
is sent to the 5062 port?
Best regards,
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com
On
I have been doing some testing with opensips 2.2.2 using ipv6. I found that
the server will only respond to a request over IPV6 if it is configured to
listen on the default port.
Wireshark sees a request addressed to the server but there is no reply.
Running opensips in the foreground show no
