Hello
I have created a SRV record for sip.domain.tld pointing to our kamailio server, the domain by itself resolves to our DNS IP. Regarding the sockets:
root@kamailio1:~# netstat -lnp | grep kamailio tcp 0 0 192.168.14.25:5060 0.0.0.0:* LISTEN 4752/kamailio unix 2 [ ACC ] STREAM LISTENING 17100 4745/kamailio /tmp/kamailio_ctl
Thanks
2012/10/11 Daniel-Constantin Mierla miconda@gmail.com
Hello,
I recommend using 3.3.x if you start a new deployment.
Is the domain resolvable by DNS? What are the sockets kamailio is listening on?
Cheers, Daniel
On 10/10/12 5:21 PM, Christophe ROY wrote:
Hello
I'm quite new to SIP and TOIP so I may not understand the concepts correctly. I'm supposed to make work SIP clients (for now, linphone on android and windows) with a Kamailio 3.2 server and ldap authentication.
Ldap authentication seems to be working fine, as the login/pass is validated against the Active Directory before registering the SIP client. However, Linphone seems to register the SIP client as sip:user@true_ip_address instead of sip:user@domain.
If I try to make a call to sip:anotheruser@domain it doesn't work, and I can find in /var/log/syslog the following lines:
Oct 10 17:19:21 kamailio1 /usr/sbin/kamailio[1790]: ERROR: tm [ut.h:333]: no corresponding socket for af 2 Oct 10 17:19:21 kamailio1 /usr/sbin/kamailio[1790]: ERROR: tm [t_fwd.c:424]: ERROR: can't fwd to af 2, proto 1 (no corresponding listening socket) Oct 10 17:19:21 kamailio1 /usr/sbin/kamailio[1790]: ERROR: tm [t_fwd.c:1534]: ERROR: t_forward_nonack: failure to add branches Oct 10 17:19:21 kamailio1 /usr/sbin/kamailio[1790]: ERROR: sl [sl_funcs.c:282]: ERROR: sl_reply_error used: I'm terribly sorry, server error occurred (7/SL)
However, if I try to make a direct call to sip:anotheruser@his_true_IP, it works
How can I make the registered users to be reachable with user@domain with Kamailio? And by the way, is there a way to get a list of registered users?
Thank you for the help
Christophe
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing listsr-users@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 - http://asipto.com/u/katu
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
12 okt 2012 kl. 09:57 skrev Christophe ROY christophe.roy.thales@gmail.com:
I have created a SRV record for sip.domain.tld pointing to our kamailio server, the domain by itself resolves to our DNS IP.
If you check the SRV record standards - especially RFC 3263 - you see that you need
_sip._udp.domain.tld _sip._tcp.domain.tld
as a bare minimum. "sip.domain.tld" is not a SRV record name.
/O
Hi Christophe ,
Did you add 'alias' row into your kamailio.cfg file? For example: alias=myvoipcompany.com
2012/10/13 Olle E. Johansson oej@edvina.net
12 okt 2012 kl. 09:57 skrev Christophe ROY < christophe.roy.thales@gmail.com>:
I have created a SRV record for sip.domain.tld pointing to our kamailio server, the domain by itself resolves to our DNS IP.
If you check the SRV record standards - especially RFC 3263 - you see that you need
_sip._udp.domain.tld _sip._tcp.domain.tld
as a bare minimum. "sip.domain.tld" is not a SRV record name.
/O
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hi
That's the way I did it, I wrote it "quickly" here. As I did it only for TCP (I force TCP in my voip client and kamailio was set to listen only on tcp before), I've added the record for udp and told kamailio to listen on udp too:
Restarting Kamailio: loading modules under /usr/lib/kamailio/modules_k/:/usr/lib/kamailio/modules/ Listening on udp: 192.168.14.25 [192.168.14.25]:5060 tcp: 192.168.14.25 [192.168.14.25]:5060 Aliases: *: my-domain.tld:*
kamailio started.
2012/10/13 Olle E. Johansson oej@edvina.net
12 okt 2012 kl. 09:57 skrev Christophe ROY < christophe.roy.thales@gmail.com>:
I have created a SRV record for sip.domain.tld pointing to our kamailio server, the domain by itself resolves to our DNS IP.
If you check the SRV record standards - especially RFC 3263 - you see that you need
_sip._udp.domain.tld _sip._tcp.domain.tld
as a bare minimum. "sip.domain.tld" is not a SRV record name.
/O
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
If anyone has already succeeded having kamailio to work with ldap authentication and sip clients being able to connect to others using sip:user@domain, would you mind sharing your kamailio.cfg? Thanks in advance!
2012/10/15 Christophe ROY christophe.roy.thales@gmail.com
Hi
That's the way I did it, I wrote it "quickly" here. As I did it only for TCP (I force TCP in my voip client and kamailio was set to listen only on tcp before), I've added the record for udp and told kamailio to listen on udp too:
Restarting Kamailio: loading modules under /usr/lib/kamailio/modules_k/:/usr/lib/kamailio/modules/ Listening on udp: 192.168.14.25 [192.168.14.25]:5060 tcp: 192.168.14.25 [192.168.14.25]:5060 Aliases: *: my-domain.tld:*
kamailio started.
2012/10/13 Olle E. Johansson oej@edvina.net
12 okt 2012 kl. 09:57 skrev Christophe ROY < christophe.roy.thales@gmail.com>:
I have created a SRV record for sip.domain.tld pointing to our kamailio server, the domain by itself resolves to our DNS IP.
If you check the SRV record standards - especially RFC 3263 - you see that you need
_sip._udp.domain.tld _sip._tcp.domain.tld
as a bare minimum. "sip.domain.tld" is not a SRV record name.
/O
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users