Hi I have two network interfaces on my system in which one interface is connected to my office WAN/LAN and other is connected to SIP private network connected to PSTN.
Now, I want to access sip server using the internal IP of our office LAN as proxy. *192.168.6.2 (Office LAN IP as proxy) -> 10.50.185.2 (SIP)* So on machine 192.168.6.2, I setup kamailio as SIP proxy server so that our office LAN machine can connect to SIP server directly via SIP proxy. I used config defined in - *https://github.com/kamailio/kamailio/blob/master/misc/examples/mixed/kamailio-minimal-proxy.cfg* <https://github.com/kamailio/kamailio/blob/master/misc/examples/mixed/kamailio-minimal-proxy.cfg> and I changed the local domain alias with SIP IP -* 10.50.185.2*. When I try to connect to SIP via proxy using *linphone* (UDP) I got below errors in* /var/log/syslog* and shows *connection in progress* every time. Nov 23 15:15:49 ubantudesk /usr/sbin/kamailio[25784]: WARNING: {1 20 REGISTER ek82LguQ6z} sanity [sanity.c:585]: check_cl(): content length header missing in request Nov 23 15:15:53 ubantudesk /usr/sbin/kamailio[25785]: WARNING: {1 20 REGISTER ek82LguQ6z} sanity [sanity.c:585]: check_cl(): content length header missing in request Nov 23 15:15:57 ubantudesk /usr/sbin/kamailio[25784]: WARNING: {1 20 REGISTER ek82LguQ6z} sanity [sanity.c:585]: check_cl(): content length header missing in request Nov 23 15:16:01 ubantudesk /usr/sbin/kamailio[25785]: WARNING: {1 20 REGISTER ek82LguQ6z} sanity [sanity.c:585]: check_cl(): content length header missing in request Nov 23 15:16:05 ubantudesk /usr/sbin/kamailio[25784]: WARNING: {1 20 REGISTER ek82LguQ6z} sanity [sanity.c:585]: check_cl(): content length header missing in request Can you help me what I should do? -- *Thanks & Regards,* *Ashwini Kumar | Technology |* www.industrybuying.com | Ghitorni, Delhi - 110030 | India | È*+91-8802137782* | * [email protected] |
_______________________________________________ Kamailio (SER) - Users Mailing List [email protected] https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
