Hello,
what do you mean by "register fails"?
Is the REGISTER request getting to kamailio? Is there a reply for it?
A ngrep output taken on kamailio server for such registration would help
to figure out where is the issue.
Cheers,
Daniel
On 13/01/14 18:08, meres wrote:
I have kamailio 4.1.0 running on a server on a real ip and behind a
firewall.
NAT detection is enabled on kamailio because many remote clients are
behind NAT, so NAT is working fine along with rtpproxy.
Everything else (incoming, outgoing) is working fine except the following:
Users who are connected to our openvpn server (bridged mode) which is
on the same subnet with kamailio, fail to register.
I suspect that kamailio detects NAT on these clients as all of them
are behind NAT, but they also have obtained a real ip from our openvpn
server on their tap interface and as a result, REGISTER fails.
One solution, but not the best is to exclude kamailio from our openvpn
routes but I would not prefer this because I wil not be able to manage
the server remotely
My config:
http://pastebin.com/JSxzgmKH
Any suggestions?
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -
http://www.asipto.com
http://twitter.com/#!/miconda -
http://www.linkedin.com/in/miconda