Hello Everyone, Is possible run kamailio without database ? I got ldap working and extension is registered, but can't place calls between two extensions. Getting 404 all the time.
Slava.
In additional I am getting this error, but I checked and srv records for sip and sips resolved ok.
9(6003) DEBUG: <core> [dns_cache.c:830]: dns_cache_add(): dns_cache_add: adding networklab.loc(14) 1 (flags=1) at 720 9(6003) ERROR: <core> [resolve.c:1733]: sip_hostport2su(): ERROR: sip_hostport2su: could not resolve hostname: "networklab.loc" 9(6003) ERROR: tm [ut.h:337]: uri2dst2(): failed to resolve "networklab.loc" 9(6003) ERROR: tm [t_fwd.c:1773]: t_forward_nonack(): ERROR: t_forward_nonack: failure to add branches 9(6003) DEBUG: tm [t_funcs.c:357]: t_relay_to(): ERROR:tm:t_relay_to: t_forward_nonack returned error 9(6003) DEBUG: tm [t_funcs.c:374]: t_relay_to(): -478 error reply generation delayed 9(6003) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=567 a=24 n=sl_reply_error 9(6003) DEBUG: <core> [msg_translator.c:204]: check_via_address(): check_via_address(192.168.100.1, 192.168.100.1, 0) 9(6003) ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: Unresolvable destination (478/SL)
----- Original Message -----
From: "Slava Bendersky" volga629@networklab.ca To: sr-users@lists.sip-router.org Sent: Sunday, March 23, 2014 10:49:07 PM Subject: [SR-Users] kamailio db
Hello Everyone, Is possible run kamailio without database ? I got ldap working and extension is registered, but can't place calls between two extensions. Getting 404 all the time.
Slava.
_______________________________________________ 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
On 03/24/2014 12:33 AM, Slava Bendersky wrote:
How are you checking the SRV records, exactly? Can you paste the invocation and output of the 'host' command, or whatever you're using?
Hello Alex,
Here output from dig.
Yes, for current setup I want setup as border gateway with couple redirection and failover to DR site. Currently I got ldap authentication working. trying test call between remote extension (which failing). And next step will forward to voicemail which partially done. PSTN forward is part of config I will need adjust couple expression to match dial string. That current plan.
[volga629@localhost ~]$ dig srv _sips._tcp.networklab.loc
; <<>> DiG 9.9.4-P2-RedHat-9.9.4-11.P2.fc20 <<>> srv _sips._tcp.networklab.loc ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64602 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 4
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;_sips._tcp.networklab.loc. IN SRV
;; ANSWER SECTION: _sips._tcp.networklab.loc. 3600 IN SRV 0 0 5061 dsm01.networklab.loc.
;; AUTHORITY SECTION: networklab.loc. 86400 IN NS ns1.networklab.loc. networklab.loc. 86400 IN NS ns2.networklab.loc.
;; ADDITIONAL SECTION: dsm01.networklab.loc. 86400 IN A 192.168.100.145 ns1.networklab.loc. 86400 IN A 192.168.10.69 ns2.networklab.loc. 86400 IN A 192.168.10.99
;; Query time: 2 msec ;; SERVER: 192.168.10.99#53(192.168.10.99) ;; WHEN: Mon Mar 24 13:31:27 EDT 2014 ;; MSG SIZE rcvd: 178
[volga629@localhost ~]$ dig srv _sip._udp.networklab.loc
; <<>> DiG 9.9.4-P2-RedHat-9.9.4-11.P2.fc20 <<>> srv _sip._udp.networklab.loc ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15496 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 4
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;_sip._udp.networklab.loc. IN SRV
;; ANSWER SECTION: _sip._udp.networklab.loc. 3600 IN SRV 0 0 5060 dsm01.networklab.loc.
;; AUTHORITY SECTION: networklab.loc. 86400 IN NS ns2.networklab.loc. networklab.loc. 86400 IN NS ns1.networklab.loc.
;; ADDITIONAL SECTION: dsm01.networklab.loc. 86400 IN A 192.168.100.145 ns1.networklab.loc. 86400 IN A 192.168.10.69 ns2.networklab.loc. 86400 IN A 192.168.10.99
;; Query time: 2 msec ;; SERVER: 192.168.10.99#53(192.168.10.99) ;; WHEN: Mon Mar 24 13:32:30 EDT 2014 ;; MSG SIZE rcvd: 177
----- Original Message -----
From: "Alex Balashov" abalashov@evaristesys.com To: sr-users@lists.sip-router.org Sent: Monday, March 24, 2014 12:43:58 AM Subject: Re: [SR-Users] kamailio db
On 03/24/2014 12:33 AM, Slava Bendersky wrote:
How are you checking the SRV records, exactly? Can you paste the invocation and output of the 'host' command, or whatever you're using?
Hello Alex,
I was looking on location as far I understand this part need to be checked on ldap level.
$avp(oexten) = $rU; if (!lookup("location")) { $var(rc) = $rc;
I have defined in ldap as separate item sipDomain I can do ldap_search on it, but not sure about lookup, avp I can set to $avp(domain).
Slava.
----- Original Message -----
From: "Slava Bendersky" volga629@networklab.ca To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Monday, March 24, 2014 1:39:42 PM Subject: Re: [SR-Users] kamailio db
Hello Alex,
Here output from dig.
Yes, for current setup I want setup as border gateway with couple redirection and failover to DR site. Currently I got ldap authentication working. trying test call between remote extension (which failing). And next step will forward to voicemail which partially done. PSTN forward is part of config I will need adjust couple expression to match dial string. That current plan.
[volga629@localhost ~]$ dig srv _sips._tcp.networklab.loc
; <<>> DiG 9.9.4-P2-RedHat-9.9.4-11.P2.fc20 <<>> srv _sips._tcp.networklab.loc ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64602 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 4
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;_sips._tcp.networklab.loc. IN SRV
;; ANSWER SECTION: _sips._tcp.networklab.loc. 3600 IN SRV 0 0 5061 dsm01.networklab.loc.
;; AUTHORITY SECTION: networklab.loc. 86400 IN NS ns1.networklab.loc. networklab.loc. 86400 IN NS ns2.networklab.loc.
;; ADDITIONAL SECTION: dsm01.networklab.loc. 86400 IN A 192.168.100.145 ns1.networklab.loc. 86400 IN A 192.168.10.69 ns2.networklab.loc. 86400 IN A 192.168.10.99
;; Query time: 2 msec ;; SERVER: 192.168.10.99#53(192.168.10.99) ;; WHEN: Mon Mar 24 13:31:27 EDT 2014 ;; MSG SIZE rcvd: 178
[volga629@localhost ~]$ dig srv _sip._udp.networklab.loc
; <<>> DiG 9.9.4-P2-RedHat-9.9.4-11.P2.fc20 <<>> srv _sip._udp.networklab.loc ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15496 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 4
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;_sip._udp.networklab.loc. IN SRV
;; ANSWER SECTION: _sip._udp.networklab.loc. 3600 IN SRV 0 0 5060 dsm01.networklab.loc.
;; AUTHORITY SECTION: networklab.loc. 86400 IN NS ns2.networklab.loc. networklab.loc. 86400 IN NS ns1.networklab.loc.
;; ADDITIONAL SECTION: dsm01.networklab.loc. 86400 IN A 192.168.100.145 ns1.networklab.loc. 86400 IN A 192.168.10.69 ns2.networklab.loc. 86400 IN A 192.168.10.99
;; Query time: 2 msec ;; SERVER: 192.168.10.99#53(192.168.10.99) ;; WHEN: Mon Mar 24 13:32:30 EDT 2014 ;; MSG SIZE rcvd: 177
----- Original Message -----
From: "Alex Balashov" abalashov@evaristesys.com To: sr-users@lists.sip-router.org Sent: Monday, March 24, 2014 12:43:58 AM Subject: Re: [SR-Users] kamailio db
On 03/24/2014 12:33 AM, Slava Bendersky wrote:
How are you checking the SRV records, exactly? Can you paste the invocation and output of the 'host' command, or whatever you're using?
Hello Alex. After some looking around, I added in request route,
Added
# Saving domain + attr in DB save("location");
# user location service route(LOCATION); }
but the problem that call looping. If I dial any extension call back to dialed extension. I see on tcpdump like.
21:12:39.461230 IP (tos 0x10, ttl 64, id 46056, offset 0, flags [none], proto UDP (17), length 1002) 192.168.100.145.5060 > 192.168.100.1.61736: [udp sum ok] SIP, length: 974 INVITE sip:1200@192.168.100.1:61736;transport=UDP SIP/2.0 Record-Route: sip:192.168.100.145;lr=on Via: SIP/2.0/UDP 192.168.100.145;branch=z9hG4bK2c97.11f246b692210236849f9ef31836226b.1 Via: SIP/2.0/UDP 192.168.100.1:57876;branch=z9hG4bK-d8754z-8160e51d28da9ef7-1---d8754z- Max-Forwards: 16 Contact: sip:1200@192.168.100.1:57876;transport=UDP To: sip:120@networklab.loc;transport=UDP From: "Slava Bendersky"sip:1200@networklab.loc;transport=UDP;tag=da605d51 Call-ID: NGFmMzg1NzFjYTQ1Y2FlZmI2ODE2OWEzNTRkNGMzOTI. CSeq: 1 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Content-Type: application/sdp Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri User-Agent: Z 3.2.21368 r21103 Allow-Events: presence, kpml Content-Length: 155
v=0 o=Z 0 0 IN IP4 127.0.0.1 --> ? s=Z c=IN IP4 127.0.0.1 t=0 0 m=audio 8000 RTP/AVP 0 101 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv
----- Original Message -----
From: "Slava Bendersky" volga629@networklab.ca To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Tuesday, March 25, 2014 11:43:57 AM Subject: Re: [SR-Users] kamailio db
Hello Alex,
I was looking on location as far I understand this part need to be checked on ldap level.
$avp(oexten) = $rU; if (!lookup("location")) { $var(rc) = $rc;
I have defined in ldap as separate item sipDomain I can do ldap_search on it, but not sure about lookup, avp I can set to $avp(domain).
Slava.
----- Original Message -----
From: "Slava Bendersky" volga629@networklab.ca To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Monday, March 24, 2014 1:39:42 PM Subject: Re: [SR-Users] kamailio db
Hello Alex,
Here output from dig.
Yes, for current setup I want setup as border gateway with couple redirection and failover to DR site. Currently I got ldap authentication working. trying test call between remote extension (which failing). And next step will forward to voicemail which partially done. PSTN forward is part of config I will need adjust couple expression to match dial string. That current plan.
[volga629@localhost ~]$ dig srv _sips._tcp.networklab.loc
; <<>> DiG 9.9.4-P2-RedHat-9.9.4-11.P2.fc20 <<>> srv _sips._tcp.networklab.loc ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64602 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 4
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;_sips._tcp.networklab.loc. IN SRV
;; ANSWER SECTION: _sips._tcp.networklab.loc. 3600 IN SRV 0 0 5061 dsm01.networklab.loc.
;; AUTHORITY SECTION: networklab.loc. 86400 IN NS ns1.networklab.loc. networklab.loc. 86400 IN NS ns2.networklab.loc.
;; ADDITIONAL SECTION: dsm01.networklab.loc. 86400 IN A 192.168.100.145 ns1.networklab.loc. 86400 IN A 192.168.10.69 ns2.networklab.loc. 86400 IN A 192.168.10.99
;; Query time: 2 msec ;; SERVER: 192.168.10.99#53(192.168.10.99) ;; WHEN: Mon Mar 24 13:31:27 EDT 2014 ;; MSG SIZE rcvd: 178
[volga629@localhost ~]$ dig srv _sip._udp.networklab.loc
; <<>> DiG 9.9.4-P2-RedHat-9.9.4-11.P2.fc20 <<>> srv _sip._udp.networklab.loc ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15496 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 4
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;_sip._udp.networklab.loc. IN SRV
;; ANSWER SECTION: _sip._udp.networklab.loc. 3600 IN SRV 0 0 5060 dsm01.networklab.loc.
;; AUTHORITY SECTION: networklab.loc. 86400 IN NS ns2.networklab.loc. networklab.loc. 86400 IN NS ns1.networklab.loc.
;; ADDITIONAL SECTION: dsm01.networklab.loc. 86400 IN A 192.168.100.145 ns1.networklab.loc. 86400 IN A 192.168.10.69 ns2.networklab.loc. 86400 IN A 192.168.10.99
;; Query time: 2 msec ;; SERVER: 192.168.10.99#53(192.168.10.99) ;; WHEN: Mon Mar 24 13:32:30 EDT 2014 ;; MSG SIZE rcvd: 177
----- Original Message -----
From: "Alex Balashov" abalashov@evaristesys.com To: sr-users@lists.sip-router.org Sent: Monday, March 24, 2014 12:43:58 AM Subject: Re: [SR-Users] kamailio db
On 03/24/2014 12:33 AM, Slava Bendersky wrote:
How are you checking the SRV records, exactly? Can you paste the invocation and output of the 'host' command, or whatever you're using?
That sounds like the registration lookup is resolving to a binding which has as its domain the domain of the proxy itself.
Try printing the value of $ru and $du (via xlog) immediately after the lookup(). It will probably shed some light.
On 25 March 2014 22:14:58 GMT-04:00, Slava Bendersky volga629@networklab.ca wrote:
-- Sent from my mobile, and thus lacking in the refinement one might expect from a fully fledged keyboard.
Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 United States Tel: +1-678-954-0671 Web: http://www.evaristesys.com/, http://www.alexbalashov.com
Hello Alex, Thank you for help, I added xlog, but I don't any records in log.
When I restart kamailio I see
CRITICAL: usrloc [udomain.c:447]: preload_udomain(): empty username record in table location...skipping
Slava.
----- Original Message -----
From: "Alex Balashov" abalashov@evaristesys.com To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Tuesday, March 25, 2014 10:44:33 PM Subject: Re: [SR-Users] kamailio db
That sounds like the registration lookup is resolving to a binding which has as its domain the domain of the proxy itself.
Try printing the value of $ru and $du (via xlog) immediately after the lookup(). It will probably shed some light.
On 25 March 2014 22:14:58 GMT-04:00, Slava Bendersky volga629@networklab.ca wrote:
Hello Alex. After some looking around, I added in request route,
Added
# Saving domain + attr in DB save("location");
# user location service route(LOCATION); }
but the problem that call looping. If I dial any extension call back to dialed extension. I see on tcpdump like.
21:12:39.461230 IP (tos 0x10, ttl 64, id 46056, offset 0, flags [none], proto UDP (17), length 1002) 192.168.100.145.5060 > 192.168.100.1.61736: [udp sum ok] SIP, length: 974 INVITE sip:1200@192.168.100.1:61736;transport=UDP SIP/2.0 Record-Route: sip:192.168.100.145;lr=on Via: SIP/2.0/UDP 192.168.100.145;branch=z9hG4bK2c97.11f246b692210236849f9ef31836226b.1 Via: SIP/2.0/UDP 192.168.100.1:57876;branch=z9hG4bK-d8754z-8160e51d28da9ef7-1---d8754z- Max-Forwards: 16 Contact: sip:1200@192.168.100.1:57876;transport=UDP To: sip:120@networklab.loc;transport=UDP From: "Slava Bendersky"sip:1200@networklab.loc;transport=UDP;tag=da605d51 Call-ID: NGFmMzg1NzFjYTQ1Y2FlZmI2ODE2OWEzNTRkNGMzOTI. CSeq: 1 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Content-Type: application/sdp Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri User-Agent: Z 3.2.21368 r21103 Allow-Events: presence, kpml Content-Length: 155
v=0 o=Z 0 0 IN IP4 127.0.0.1 --> ? s=Z c=IN IP4 127.0.0.1 t=0 0 m=audio 8000 RTP/AVP 0 101 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv
----- Original Message -----
From: "Slava Bendersky" volga629@networklab.ca To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Tuesday, March 25, 2014 11:43:57 AM Subject: Re: [SR-Users] kamailio db
Hello Alex,
I was looking on location as far I understand this part need to be checked on ldap level.
$avp(oexten) = $rU; if (!lookup("location")) { $var(rc) = $rc;
I have defined in ldap as separate item sipDomain I can do ldap_search on it, but not sure about lookup, avp I can set to $avp(domain).
Slava.
----- Original Message -----
From: "Slava Bendersky" volga629@networklab.ca To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Monday, March 24, 2014 1:39:42 PM Subject: Re: [SR-Users] kamailio db
Hello Alex,
Here output from dig.
Yes, for current setup I want setup as border gateway with couple redirection and failover to DR site. Currently I got ldap authentication working. trying test call between remote extension (which failing). And next step will forward to voicemail which partially done. PSTN forward is part of config I will need adjust couple expression to match dial string. That current plan.
[volga629@localhost ~]$ dig srv _sips._tcp.networklab.loc
; <<>> DiG 9.9.4-P2-RedHat-9.9.4-11.P2.fc20 <<>> srv _sips._tcp.networklab.loc ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64602 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 4
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;_sips._tcp.networklab.loc. IN SRV
;; ANSWER SECTION: _sips._tcp.networklab.loc. 3600 IN SRV 0 0 5061 dsm01.networklab.loc.
;; AUTHORITY SECTION: networklab.loc. 86400 IN NS ns1.networklab.loc. networklab.loc. 86400 IN NS ns2.networklab.loc.
;; ADDITIONAL SECTION: dsm01.networklab.loc. 86400 IN A 192.168.100.145 ns1.networklab.loc. 86400 IN A 192.168.10.69 ns2.networklab.loc. 86400 IN A 192.168.10.99
;; Query time: 2 msec ;; SERVER: 192.168.10.99#53(192.168.10.99) ;; WHEN: Mon Mar 24 13:31:27 EDT 2014 ;; MSG SIZE rcvd: 178
[volga629@localhost ~]$ dig srv _sip._udp.networklab.loc
; <<>> DiG 9.9.4-P2-RedHat-9.9.4-11.P2.fc20 <<>> srv _sip._udp.networklab.loc ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15496 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 4
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;_sip._udp.networklab.loc. IN SRV
;; ANSWER SECTION: _sip._udp.networklab.loc. 3600 IN SRV 0 0 5060 dsm01.networklab.loc.
;; AUTHORITY SECTION: networklab.loc. 86400 IN NS ns2.networklab.loc. networklab.loc. 86400 IN NS ns1.networklab.loc.
;; ADDITIONAL SECTION: dsm01.networklab.loc. 86400 IN A 192.168.100.145 ns1.networklab.loc. 86400 IN A 192.168.10.69 ns2.networklab.loc. 86400 IN A 192.168.10.99
;; Query time: 2 msec ;; SERVER: 192.168.10.99#53(192.168.10.99) ;; WHEN: Mon Mar 24 13:32:30 EDT 2014 ;; MSG SIZE rcvd: 177
----- Original Message -----
From: "Alex Balashov" abalashov@evaristesys.com To: sr-users@lists.sip-router.org Sent: Monday, March 24, 2014 12:43:58 AM Subject: Re: [SR-Users] kamailio db
On 03/24/2014 12:33 AM, Slava Bendersky wrote:
How are you checking the SRV records, exactly? Can you paste the invocation and output of the 'host' command, or whatever you're using?
Try get your client to reregister.
But, that message suggests that there's something wrong with the binding. Can you paste the output of SELECT * FROM location WHERE username = 'the username in question';
On 25 March 2014 23:21:37 GMT-04:00, Slava Bendersky volga629@networklab.ca wrote:
-- Sent from my mobile, and thus lacking in the refinement one might expect from a fully fledged keyboard.
Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 United States Tel: +1-678-954-0671 Web: http://www.evaristesys.com/, http://www.alexbalashov.com
Hello Alex, I checked DB and filed username empty. I wonder if save need write all those values in db there only argument send or not send reply.
mysql> SELECT * FROM location WHERE username = '1200'; Empty set (0.00 sec)
Slava.
----- Original Message -----
From: "Alex Balashov" abalashov@evaristesys.com To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Tuesday, March 25, 2014 11:23:38 PM Subject: Re: [SR-Users] kamailio db
Try get your client to reregister.
But, that message suggests that there's something wrong with the binding. Can you paste the output of SELECT * FROM location WHERE username = 'the username in question';
On 25 March 2014 23:21:37 GMT-04:00, Slava Bendersky volga629@networklab.ca wrote:
Hello Alex, Thank you for help, I added xlog, but I don't any records in log.
When I restart kamailio I see
CRITICAL: usrloc [udomain.c:447]: preload_udomain(): empty username record in table location...skipping
Slava.
----- Original Message -----
From: "Alex Balashov" abalashov@evaristesys.com To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Tuesday, March 25, 2014 10:44:33 PM Subject: Re: [SR-Users] kamailio db
That sounds like the registration lookup is resolving to a binding which has as its domain the domain of the proxy itself.
Try printing the value of $ru and $du (via xlog) immediately after the lookup(). It will probably shed some light.
On 25 March 2014 22:14:58 GMT-04:00, Slava Bendersky volga629@networklab.ca wrote: <blockquote>
Hello Alex. After some looking around, I added in request route,
Added
# Saving domain + attr in DB save("location");
# user location service route(LOCATION); }
but the problem that call looping. If I dial any extension call back to dialed extension. I see on tcpdump like.
21:12:39.461230 IP (tos 0x10, ttl 64, id 46056, offset 0, flags [none], proto UDP (17), length 1002) 192.168.100.145.5060 > 192.168.100.1.61736: [udp sum ok] SIP, length: 974 INVITE sip:1200@192.168.100.1:61736;transport=UDP SIP/2.0 Record-Route: sip:192.168.100.145;lr=on Via: SIP/2.0/UDP 192.168.100.145;branch=z9hG4bK2c97.11f246b692210236849f9ef31836226b.1 Via: SIP/2.0/UDP 192.168.100.1:57876;branch=z9hG4bK-d8754z-8160e51d28da9ef7-1---d8754z- Max-Forwards: 16 Contact: sip:1200@192.168.100.1:57876;transport=UDP To: sip:120@networklab.loc;transport=UDP From: "Slava Bendersky"sip:1200@networklab.loc;transport=UDP;tag=da605d51 Call-ID: NGFmMzg1NzFjYTQ1Y2FlZmI2ODE2OWEzNTRkNGMzOTI. CSeq: 1 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Content-Type: application/sdp Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri User-Agent: Z 3.2.21368 r21103 Allow-Events: presence, kpml Content-Length: 155
v=0 o=Z 0 0 IN IP4 127.0.0.1 --> ? s=Z c=IN IP4 127.0.0.1 t=0 0 m=audio 8000 RTP/AVP 0 101 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv
----- Original Message -----
From: "Slava Bendersky" volga629@networklab.ca To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Tuesday, March 25, 2014 11:43:57 AM Subject: Re: [SR-Users] kamailio db
Hello Alex,
I was looking on location as far I understand this part need to be checked on ldap level.
$avp(oexten) = $rU; if (!lookup("location")) { $var(rc) = $rc;
I have defined in ldap as separate item sipDomain I can do ldap_search on it, but not sure about lookup, avp I can set to $avp(domain).
Slava.
----- Original Message -----
From: "Slava Bendersky" volga629@networklab.ca To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Monday, March 24, 2014 1:39:42 PM Subject: Re: [SR-Users] kamailio db
Hello Alex,
Here output from dig.
Yes, for current setup I want setup as border gateway with couple redirection and failover to DR site. Currently I got ldap authentication working. trying test call between remote extension (which failing). And next step will forward to voicemail which partially done. PSTN forward is part of config I will need adjust couple expression to match dial string. That current plan.
[volga629@localhost ~]$ dig srv _sips._tcp.networklab.loc
; <<>> DiG 9.9.4-P2-RedHat-9.9.4-11.P2.fc20 <<>> srv _sips._tcp.networklab.loc ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64602 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 4
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;_sips._tcp.networklab.loc. IN SRV
;; ANSWER SECTION: _sips._tcp.networklab.loc. 3600 IN SRV 0 0 5061 dsm01.networklab.loc.
;; AUTHORITY SECTION: networklab.loc. 86400 IN NS ns1.networklab.loc. networklab.loc. 86400 IN NS ns2.networklab.loc.
;; ADDITIONAL SECTION: dsm01.networklab.loc. 86400 IN A 192.168.100.145 ns1.networklab.loc. 86400 IN A 192.168.10.69 ns2.networklab.loc. 86400 IN A 192.168.10.99
;; Query time: 2 msec ;; SERVER: 192.168.10.99#53(192.168.10.99) ;; WHEN: Mon Mar 24 13:31:27 EDT 2014 ;; MSG SIZE rcvd: 178
[volga629@localhost ~]$ dig srv _sip._udp.networklab.loc
; <<>> DiG 9.9.4-P2-RedHat-9.9.4-11.P2.fc20 <<>> srv _sip._udp.networklab.loc ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15496 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 4
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;_sip._udp.networklab.loc. IN SRV
;; ANSWER SECTION: _sip._udp.networklab.loc. 3600 IN SRV 0 0 5060 dsm01.networklab.loc.
;; AUTHORITY SECTION: networklab.loc. 86400 IN NS ns2.networklab.loc. networklab.loc. 86400 IN NS ns1.networklab.loc.
;; ADDITIONAL SECTION: dsm01.networklab.loc. 86400 IN A 192.168.100.145 ns1.networklab.loc. 86400 IN A 192.168.10.69 ns2.networklab.loc. 86400 IN A 192.168.10.99
;; Query time: 2 msec ;; SERVER: 192.168.10.99#53(192.168.10.99) ;; WHEN: Mon Mar 24 13:32:30 EDT 2014 ;; MSG SIZE rcvd: 177
----- Original Message -----
From: "Alex Balashov" abalashov@evaristesys.com To: sr-users@lists.sip-router.org Sent: Monday, March 24, 2014 12:43:58 AM Subject: Re: [SR-Users] kamailio db
On 03/24/2014 12:33 AM, Slava Bendersky wrote:
How are you checking the SRV records, exactly? Can you paste the invocation and output of the 'host' command, or whatever you're using?
Hello Alex,
The log showing $ru value $du, empty.
$avp(oexten) = $rU; if (!lookup("location")) { xlog("L_INFO", "This $rU and this $du");
Mar 26 03:12:16 dsm01 /usr/sbin/kamailio[9706]: INFO: <script>: This 124 and this <null> Mar 26 03:12:57 dsm01 /usr/sbin/kamailio[9709]: INFO: <script>: This 120 and this <null>
When I specify proxy settings on sip client "zoiper", rtp start working and at least I can dial voicemail on asterisk behind.
Slava.
----- Original Message -----
From: "Alex Balashov" abalashov@evaristesys.com To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Tuesday, March 25, 2014 10:44:33 PM Subject: Re: [SR-Users] kamailio db
That sounds like the registration lookup is resolving to a binding which has as its domain the domain of the proxy itself.
Try printing the value of $ru and $du (via xlog) immediately after the lookup(). It will probably shed some light.
On 25 March 2014 22:14:58 GMT-04:00, Slava Bendersky volga629@networklab.ca wrote:
Hello Alex. After some looking around, I added in request route,
Added
# Saving domain + attr in DB save("location");
# user location service route(LOCATION); }
but the problem that call looping. If I dial any extension call back to dialed extension. I see on tcpdump like.
21:12:39.461230 IP (tos 0x10, ttl 64, id 46056, offset 0, flags [none], proto UDP (17), length 1002) 192.168.100.145.5060 > 192.168.100.1.61736: [udp sum ok] SIP, length: 974 INVITE sip:1200@192.168.100.1:61736;transport=UDP SIP/2.0 Record-Route: sip:192.168.100.145;lr=on Via: SIP/2.0/UDP 192.168.100.145;branch=z9hG4bK2c97.11f246b692210236849f9ef31836226b.1 Via: SIP/2.0/UDP 192.168.100.1:57876;branch=z9hG4bK-d8754z-8160e51d28da9ef7-1---d8754z- Max-Forwards: 16 Contact: sip:1200@192.168.100.1:57876;transport=UDP To: sip:120@networklab.loc;transport=UDP From: "Slava Bendersky"sip:1200@networklab.loc;transport=UDP;tag=da605d51 Call-ID: NGFmMzg1NzFjYTQ1Y2FlZmI2ODE2OWEzNTRkNGMzOTI. CSeq: 1 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Content-Type: application/sdp Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri User-Agent: Z 3.2.21368 r21103 Allow-Events: presence, kpml Content-Length: 155
v=0 o=Z 0 0 IN IP4 127.0.0.1 --> ? s=Z c=IN IP4 127.0.0.1 t=0 0 m=audio 8000 RTP/AVP 0 101 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv
----- Original Message -----
From: "Slava Bendersky" volga629@networklab.ca To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Tuesday, March 25, 2014 11:43:57 AM Subject: Re: [SR-Users] kamailio db
Hello Alex,
I was looking on location as far I understand this part need to be checked on ldap level.
$avp(oexten) = $rU; if (!lookup("location")) { $var(rc) = $rc;
I have defined in ldap as separate item sipDomain I can do ldap_search on it, but not sure about lookup, avp I can set to $avp(domain).
Slava.
----- Original Message -----
From: "Slava Bendersky" volga629@networklab.ca To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Monday, March 24, 2014 1:39:42 PM Subject: Re: [SR-Users] kamailio db
Hello Alex,
Here output from dig.
Yes, for current setup I want setup as border gateway with couple redirection and failover to DR site. Currently I got ldap authentication working. trying test call between remote extension (which failing). And next step will forward to voicemail which partially done. PSTN forward is part of config I will need adjust couple expression to match dial string. That current plan.
[volga629@localhost ~]$ dig srv _sips._tcp.networklab.loc
; <<>> DiG 9.9.4-P2-RedHat-9.9.4-11.P2.fc20 <<>> srv _sips._tcp.networklab.loc ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64602 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 4
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;_sips._tcp.networklab.loc. IN SRV
;; ANSWER SECTION: _sips._tcp.networklab.loc. 3600 IN SRV 0 0 5061 dsm01.networklab.loc.
;; AUTHORITY SECTION: networklab.loc. 86400 IN NS ns1.networklab.loc. networklab.loc. 86400 IN NS ns2.networklab.loc.
;; ADDITIONAL SECTION: dsm01.networklab.loc. 86400 IN A 192.168.100.145 ns1.networklab.loc. 86400 IN A 192.168.10.69 ns2.networklab.loc. 86400 IN A 192.168.10.99
;; Query time: 2 msec ;; SERVER: 192.168.10.99#53(192.168.10.99) ;; WHEN: Mon Mar 24 13:31:27 EDT 2014 ;; MSG SIZE rcvd: 178
[volga629@localhost ~]$ dig srv _sip._udp.networklab.loc
; <<>> DiG 9.9.4-P2-RedHat-9.9.4-11.P2.fc20 <<>> srv _sip._udp.networklab.loc ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15496 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 4
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;_sip._udp.networklab.loc. IN SRV
;; ANSWER SECTION: _sip._udp.networklab.loc. 3600 IN SRV 0 0 5060 dsm01.networklab.loc.
;; AUTHORITY SECTION: networklab.loc. 86400 IN NS ns2.networklab.loc. networklab.loc. 86400 IN NS ns1.networklab.loc.
;; ADDITIONAL SECTION: dsm01.networklab.loc. 86400 IN A 192.168.100.145 ns1.networklab.loc. 86400 IN A 192.168.10.69 ns2.networklab.loc. 86400 IN A 192.168.10.99
;; Query time: 2 msec ;; SERVER: 192.168.10.99#53(192.168.10.99) ;; WHEN: Mon Mar 24 13:32:30 EDT 2014 ;; MSG SIZE rcvd: 177
----- Original Message -----
From: "Alex Balashov" abalashov@evaristesys.com To: sr-users@lists.sip-router.org Sent: Monday, March 24, 2014 12:43:58 AM Subject: Re: [SR-Users] kamailio db
On 03/24/2014 12:33 AM, Slava Bendersky wrote:
How are you checking the SRV records, exactly? Can you paste the invocation and output of the 'host' command, or whatever you're using?
Yeah, but you're checking inside the if(!lookup(...)) block.
! is, in Kamailio, as in most programming language languages, a negation operator. It means "if the lookup failed" in this case, i.e. if lookup() returned a zero or negative value. And if you're seeing the xlog messages where you have placed them, it means the lookups are failing.
It also means the RURI is not being altered by a successful lookup, which means it still has the RURI domain of the proxy (print $ru, not $rU, to see what I mean), which explains the request looping.
On 26 March 2014 03:30:22 GMT-04:00, Slava Bendersky volga629@networklab.ca wrote:
-- Sent from my Nexus 10, with all the figments of autocorrect that might imply.
Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 United States Tel: +1-678-954-0670 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
Hello Alex, That make sense, because all 3 digit extension which in log belong to voicemail server. They not local set it located on asterisk box. Also I see 484. In this case do I need test if it local set or not ?
U 2014/03/26 11:08:27.749579 192.168.100.145:5060 -> 192.168.100.145:5062 SIP/2.0 484 Address Incomplete. Via: SIP/2.0/UDP 192.168.100.145:5062;branch=z9hG4bK0d3ed7d2. From: "asterisk" sip:voicemail@192.168.100.145:5062;tag=as014ee23b. To: sip:192.168.100.145;tag=b27e1a1d33761e85846fc98f5f3a7e58.67c9. Call-ID: 6b1158a1275a1b68568b03057e2a29bb@192.168.100.145:5062. CSeq: 102 OPTIONS. Server: kamailio (4.1.2 (x86_64/linux)). Content-Length: 0.
Look like LOCATION.
----- Original Message -----
From: "Alex Balashov" abalashov@evaristesys.com To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Wednesday, March 26, 2014 3:34:38 AM Subject: Re: [SR-Users] kamailio db
Yeah, but you're checking inside the if(!lookup(...)) block.
! is, in Kamailio, as in most programming language languages, a negation operator. It means "if the lookup failed" in this case, i.e. if lookup() returned a zero or negative value. And if you're seeing the xlog messages where you have placed them, it means the lookups are failing.
It also means the RURI is not being altered by a successful lookup, which means it still has the RURI domain of the proxy (print $ru, not $rU, to see what I mean), which explains the request looping.
On 26 March 2014 03:30:22 GMT-04:00, Slava Bendersky volga629@networklab.ca wrote:
Hello Alex,
The log showing $ru value $du, empty.
$avp(oexten) = $rU; if (!lookup("location")) { xlog("L_INFO", "This $rU and this $du");
Mar 26 03:12:16 dsm01 /usr/sbin/kamailio[9706]: INFO: <script>: This 124 and this <null> Mar 26 03:12:57 dsm01 /usr/sbin/kamailio[9709]: INFO: <script>: This 120 and this <null>
When I specify proxy settings on sip client "zoiper", rtp start working and at least I can dial voicemail on asterisk behind.
Slava.
----- Original Message -----
From: "Alex Balashov" abalashov@evaristesys.com To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Tuesday, March 25, 2014 10:44:33 PM Subject: Re: [SR-Users] kamailio db
That sounds like the registration lookup is resolving to a binding which has as its domain the domain of the proxy itself.
Try printing the value of $ru and $du (via xlog) immediately after the lookup(). It will probably shed some light.
On 25 March 2014 22:14:58 GMT-04:00, Slava Bendersky volga629@networklab.ca wrote: <blockquote>
Hello Alex. After some looking around, I added in request route,
Added
# Saving domain + attr in DB save("location");
# user location service route(LOCATION); }
but the problem that call looping. If I dial any extension call back to dialed extension. I see on tcpdump like.
21:12:39.461230 IP (tos 0x10, ttl 64, id 46056, offset 0, flags [none], proto UDP (17), length 1002) 192.168.100.145.5060 > 192.168.100.1.61736: [udp sum ok] SIP, length: 974 INVITE sip:1200@192.168.100.1:61736;transport=UDP SIP/2.0 Record-Route: sip:192.168.100.145;lr=on Via: SIP/2.0/UDP 192.168.100.145;branch=z9hG4bK2c97.11f246b692210236849f9ef31836226b.1 Via: SIP/2.0/UDP 192.168.100.1:57876;branch=z9hG4bK-d8754z-8160e51d28da9ef7-1---d8754z- Max-Forwards: 16 Contact: sip:1200@192.168.100.1:57876;transport=UDP To: sip:120@networklab.loc;transport=UDP From: "Slava Bendersky"sip:1200@networklab.loc;transport=UDP;tag=da605d51 Call-ID: NGFmMzg1NzFjYTQ1Y2FlZmI2ODE2OWEzNTRkNGMzOTI. CSeq: 1 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Content-Type: application/sdp Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri User-Agent: Z 3.2.21368 r21103 Allow-Events: presence, kpml Content-Length: 155
v=0 o=Z 0 0 IN IP4 127.0.0.1 --> ? s=Z c=IN IP4 127.0.0.1 t=0 0 m=audio 8000 RTP/AVP 0 101 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv
----- Original Message -----
From: "Slava Bendersky" volga629@networklab.ca To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Tuesday, March 25, 2014 11:43:57 AM Subject: Re: [SR-Users] kamailio db
Hello Alex,
I was looking on location as far I understand this part need to be checked on ldap level.
$avp(oexten) = $rU; if (!lookup("location")) { $var(rc) = $rc;
I have defined in ldap as separate item sipDomain I can do ldap_search on it, but not sure about lookup, avp I can set to $avp(domain).
Slava.
----- Original Message -----
From: "Slava Bendersky" volga629@networklab.ca To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Monday, March 24, 2014 1:39:42 PM Subject: Re: [SR-Users] kamailio db
Hello Alex,
Here output from dig.
Yes, for current setup I want setup as border gateway with couple redirection and failover to DR site. Currently I got ldap authentication working. trying test call between remote extension (which failing). And next step will forward to voicemail which partially done. PSTN forward is part of config I will need adjust couple expression to match dial string. That current plan.
[volga629@localhost ~]$ dig srv _sips._tcp.networklab.loc
; <<>> DiG 9.9.4-P2-RedHat-9.9.4-11.P2.fc20 <<>> srv _sips._tcp.networklab.loc ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64602 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 4
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;_sips._tcp.networklab.loc. IN SRV
;; ANSWER SECTION: _sips._tcp.networklab.loc. 3600 IN SRV 0 0 5061 dsm01.networklab.loc.
;; AUTHORITY SECTION: networklab.loc. 86400 IN NS ns1.networklab.loc. networklab.loc. 86400 IN NS ns2.networklab.loc.
;; ADDITIONAL SECTION: dsm01.networklab.loc. 86400 IN A 192.168.100.145 ns1.networklab.loc. 86400 IN A 192.168.10.69 ns2.networklab.loc. 86400 IN A 192.168.10.99
;; Query time: 2 msec ;; SERVER: 192.168.10.99#53(192.168.10.99) ;; WHEN: Mon Mar 24 13:31:27 EDT 2014 ;; MSG SIZE rcvd: 178
[volga629@localhost ~]$ dig srv _sip._udp.networklab.loc
; <<>> DiG 9.9.4-P2-RedHat-9.9.4-11.P2.fc20 <<>> srv _sip._udp.networklab.loc ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15496 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 4
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;_sip._udp.networklab.loc. IN SRV
;; ANSWER SECTION: _sip._udp.networklab.loc. 3600 IN SRV 0 0 5060 dsm01.networklab.loc.
;; AUTHORITY SECTION: networklab.loc. 86400 IN NS ns2.networklab.loc. networklab.loc. 86400 IN NS ns1.networklab.loc.
;; ADDITIONAL SECTION: dsm01.networklab.loc. 86400 IN A 192.168.100.145 ns1.networklab.loc. 86400 IN A 192.168.10.69 ns2.networklab.loc. 86400 IN A 192.168.10.99
;; Query time: 2 msec ;; SERVER: 192.168.10.99#53(192.168.10.99) ;; WHEN: Mon Mar 24 13:32:30 EDT 2014 ;; MSG SIZE rcvd: 177
----- Original Message -----
From: "Alex Balashov" abalashov@evaristesys.com To: sr-users@lists.sip-router.org Sent: Monday, March 24, 2014 12:43:58 AM Subject: Re: [SR-Users] kamailio db
On 03/24/2014 12:33 AM, Slava Bendersky wrote:
How are you checking the SRV records, exactly? Can you paste the invocation and output of the 'host' command, or whatever you're using?
On 03/26/2014 11:13 AM, Slava Bendersky wrote:
No. That's just an OPTIONS ping. The most common use of these is as a keepalive/ping, which means it doesn't matter what the response is.
Hello Alex, Yes, all question that when I am checking location table I see only records for asterisk box, no information about registered extension. Do you think is will good idea put save location after authentication in request route section ? Which another part is domain is empty and username empty.
mysql> SELECT * FROM location; +----+----------------------+----------+--------+------------------------------------+----------+------+---------------------+-------+-------------------------------------------------------+------+---------------------+-------+--------+---------------------+--------------------------+---------+----------+--------+ | id | ruid | username | domain | contact | received | path | expires | q | callid | cseq | last_modified | flags | cflags | user_agent | socket | methods | instance | reg_id | +----+----------------------+----------+--------+------------------------------------+----------+------+---------------------+-------+-------------------------------------------------------+------+---------------------+-------+--------+---------------------+--------------------------+---------+----------+--------+ | 1 | uloc-5332078c-164a-1 | | NULL | sip:voicemail@192.168.100.145:5062 | NULL | NULL | 2014-03-25 19:54:50 | -1.00 | 0798bb1d370e1a93317efee741a2151f@192.168.100.145:5062 | 102 | 2014-03-25 18:54:50 | 0 | 0 | Asterisk PBX 12
Slava.
----- Original Message -----
From: "Slava Bendersky" volga629@networklab.ca To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Wednesday, March 26, 2014 11:13:05 AM Subject: Re: [SR-Users] kamailio db
Hello Alex, That make sense, because all 3 digit extension which in log belong to voicemail server. They not local set it located on asterisk box. Also I see 484. In this case do I need test if it local set or not ?
U 2014/03/26 11:08:27.749579 192.168.100.145:5060 -> 192.168.100.145:5062 SIP/2.0 484 Address Incomplete. Via: SIP/2.0/UDP 192.168.100.145:5062;branch=z9hG4bK0d3ed7d2. From: "asterisk" sip:voicemail@192.168.100.145:5062;tag=as014ee23b. To: sip:192.168.100.145;tag=b27e1a1d33761e85846fc98f5f3a7e58.67c9. Call-ID: 6b1158a1275a1b68568b03057e2a29bb@192.168.100.145:5062. CSeq: 102 OPTIONS. Server: kamailio (4.1.2 (x86_64/linux)). Content-Length: 0.
Look like LOCATION.
----- Original Message -----
From: "Alex Balashov" abalashov@evaristesys.com To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Wednesday, March 26, 2014 3:34:38 AM Subject: Re: [SR-Users] kamailio db
Yeah, but you're checking inside the if(!lookup(...)) block.
! is, in Kamailio, as in most programming language languages, a negation operator. It means "if the lookup failed" in this case, i.e. if lookup() returned a zero or negative value. And if you're seeing the xlog messages where you have placed them, it means the lookups are failing.
It also means the RURI is not being altered by a successful lookup, which means it still has the RURI domain of the proxy (print $ru, not $rU, to see what I mean), which explains the request looping.
On 26 March 2014 03:30:22 GMT-04:00, Slava Bendersky volga629@networklab.ca wrote:
Hello Alex,
The log showing $ru value $du, empty.
$avp(oexten) = $rU; if (!lookup("location")) { xlog("L_INFO", "This $rU and this $du");
Mar 26 03:12:16 dsm01 /usr/sbin/kamailio[9706]: INFO: <script>: This 124 and this <null> Mar 26 03:12:57 dsm01 /usr/sbin/kamailio[9709]: INFO: <script>: This 120 and this <null>
When I specify proxy settings on sip client "zoiper", rtp start working and at least I can dial voicemail on asterisk behind.
Slava.
----- Original Message -----
From: "Alex Balashov" abalashov@evaristesys.com To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Tuesday, March 25, 2014 10:44:33 PM Subject: Re: [SR-Users] kamailio db
That sounds like the registration lookup is resolving to a binding which has as its domain the domain of the proxy itself.
Try printing the value of $ru and $du (via xlog) immediately after the lookup(). It will probably shed some light.
On 25 March 2014 22:14:58 GMT-04:00, Slava Bendersky volga629@networklab.ca wrote: <blockquote>
Hello Alex. After some looking around, I added in request route,
Added
# Saving domain + attr in DB save("location");
# user location service route(LOCATION); }
but the problem that call looping. If I dial any extension call back to dialed extension. I see on tcpdump like.
21:12:39.461230 IP (tos 0x10, ttl 64, id 46056, offset 0, flags [none], proto UDP (17), length 1002) 192.168.100.145.5060 > 192.168.100.1.61736: [udp sum ok] SIP, length: 974 INVITE sip:1200@192.168.100.1:61736;transport=UDP SIP/2.0 Record-Route: sip:192.168.100.145;lr=on Via: SIP/2.0/UDP 192.168.100.145;branch=z9hG4bK2c97.11f246b692210236849f9ef31836226b.1 Via: SIP/2.0/UDP 192.168.100.1:57876;branch=z9hG4bK-d8754z-8160e51d28da9ef7-1---d8754z- Max-Forwards: 16 Contact: sip:1200@192.168.100.1:57876;transport=UDP To: sip:120@networklab.loc;transport=UDP From: "Slava Bendersky"sip:1200@networklab.loc;transport=UDP;tag=da605d51 Call-ID: NGFmMzg1NzFjYTQ1Y2FlZmI2ODE2OWEzNTRkNGMzOTI. CSeq: 1 INVITE Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE Content-Type: application/sdp Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri User-Agent: Z 3.2.21368 r21103 Allow-Events: presence, kpml Content-Length: 155
v=0 o=Z 0 0 IN IP4 127.0.0.1 --> ? s=Z c=IN IP4 127.0.0.1 t=0 0 m=audio 8000 RTP/AVP 0 101 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv
----- Original Message -----
From: "Slava Bendersky" volga629@networklab.ca To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Tuesday, March 25, 2014 11:43:57 AM Subject: Re: [SR-Users] kamailio db
Hello Alex,
I was looking on location as far I understand this part need to be checked on ldap level.
$avp(oexten) = $rU; if (!lookup("location")) { $var(rc) = $rc;
I have defined in ldap as separate item sipDomain I can do ldap_search on it, but not sure about lookup, avp I can set to $avp(domain).
Slava.
----- Original Message -----
From: "Slava Bendersky" volga629@networklab.ca To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Monday, March 24, 2014 1:39:42 PM Subject: Re: [SR-Users] kamailio db
Hello Alex,
Here output from dig.
Yes, for current setup I want setup as border gateway with couple redirection and failover to DR site. Currently I got ldap authentication working. trying test call between remote extension (which failing). And next step will forward to voicemail which partially done. PSTN forward is part of config I will need adjust couple expression to match dial string. That current plan.
[volga629@localhost ~]$ dig srv _sips._tcp.networklab.loc
; <<>> DiG 9.9.4-P2-RedHat-9.9.4-11.P2.fc20 <<>> srv _sips._tcp.networklab.loc ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64602 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 4
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;_sips._tcp.networklab.loc. IN SRV
;; ANSWER SECTION: _sips._tcp.networklab.loc. 3600 IN SRV 0 0 5061 dsm01.networklab.loc.
;; AUTHORITY SECTION: networklab.loc. 86400 IN NS ns1.networklab.loc. networklab.loc. 86400 IN NS ns2.networklab.loc.
;; ADDITIONAL SECTION: dsm01.networklab.loc. 86400 IN A 192.168.100.145 ns1.networklab.loc. 86400 IN A 192.168.10.69 ns2.networklab.loc. 86400 IN A 192.168.10.99
;; Query time: 2 msec ;; SERVER: 192.168.10.99#53(192.168.10.99) ;; WHEN: Mon Mar 24 13:31:27 EDT 2014 ;; MSG SIZE rcvd: 178
[volga629@localhost ~]$ dig srv _sip._udp.networklab.loc
; <<>> DiG 9.9.4-P2-RedHat-9.9.4-11.P2.fc20 <<>> srv _sip._udp.networklab.loc ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15496 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 4
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;_sip._udp.networklab.loc. IN SRV
;; ANSWER SECTION: _sip._udp.networklab.loc. 3600 IN SRV 0 0 5060 dsm01.networklab.loc.
;; AUTHORITY SECTION: networklab.loc. 86400 IN NS ns2.networklab.loc. networklab.loc. 86400 IN NS ns1.networklab.loc.
;; ADDITIONAL SECTION: dsm01.networklab.loc. 86400 IN A 192.168.100.145 ns1.networklab.loc. 86400 IN A 192.168.10.69 ns2.networklab.loc. 86400 IN A 192.168.10.99
;; Query time: 2 msec ;; SERVER: 192.168.10.99#53(192.168.10.99) ;; WHEN: Mon Mar 24 13:32:30 EDT 2014 ;; MSG SIZE rcvd: 177
----- Original Message -----
From: "Alex Balashov" abalashov@evaristesys.com To: sr-users@lists.sip-router.org Sent: Monday, March 24, 2014 12:43:58 AM Subject: Re: [SR-Users] kamailio db
On 03/24/2014 12:33 AM, Slava Bendersky wrote:
How are you checking the SRV records, exactly? Can you paste the invocation and output of the 'host' command, or whatever you're using?
On 03/26/2014 11:30 AM, Slava Bendersky wrote:
Yes, if you want a location binding to go into the 'location' table, that is accomplished with save(). And that is something that should happen after you've authenticated the request. :-)
Hello Alex, I added this section, right now I see mysql get updates. But still some issue that is no rtp stream established. When I place call between extensions I get dial tone and rings on answer it dead.
#!ifdef WITH_LDAP route(LDAP); #!endif
#!ifdef WITH_LDAP if (!save("location")) { sl_reply_error(); xlog("L_INFO", "This $rU"); } #!endif
Slava.
----- Original Message -----
From: "Alex Balashov" abalashov@evaristesys.com To: sr-users@lists.sip-router.org Sent: Wednesday, March 26, 2014 11:31:45 AM Subject: Re: [SR-Users] kamailio db
On 03/26/2014 11:30 AM, Slava Bendersky wrote:
Yes, if you want a location binding to go into the 'location' table, that is accomplished with save(). And that is something that should happen after you've authenticated the request. :-)
On 03/26/2014 11:53 AM, Slava Bendersky wrote:
Well, that's progress!
Kamailio is not involved in RTP, however[1].
Could it be that there is a network or transport-layer reachability issue between your endpoints? Or a firewall getting in the way, perhaps?
-- Alex
[1] It can control third-party, outboard RTP relays such as 'rtpproxy', though. But those are separate processes and pieces of software.
Hello Alex, Yes, should have reinvites. I am getting randomly 404. Is this normal behaviour to specify outbound proxy on client on local network ( sounds bad ). Other wise is no rtp.
U 2014/03/26 11:59:36.207773 10.237.236.207:5060 -> 192.168.100.145:5062 INVITE sip:1200@192.168.100.145:5062 SIP/2.0. Record-Route: sip:10.237.236.207;lr=on. Via: SIP/2.0/UDP 10.237.236.207;branch=z9hG4bK5a7e.03cc1cb9d02595ff6c7096253b4e6034.2. Via: SIP/2.0/UDP 10.237.236.212:63802;branch=z9hG4bK-d8754z-27d8d75f55eb3466-1---d8754z-;rport=63802. Max-Forwards: 16. Contact: sip:1200@10.237.236.212:63802;transport=UDP. To: sip:1200@networklab.loc;transport=UDP. From: sip:1200@networklab.loc;transport=UDP;tag=e145b359. Call-ID: ZTRiNGMzOWYxOTAyMjkyMGFjNjI0NjQzZGZmZDE4N2E.. CSeq: 1 INVITE. Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE. Content-Type: application/sdp. Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri. User-Agent: Z 3.2.21357 r21367. Allow-Events: presence, kpml. Content-Length: 165. . v=0. o=Z 0 0 IN IP4 10.237.236.212. s=Z. c=IN IP4 10.237.236.212. t=0 0. m=audio 8000 RTP/AVP 0 101. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. a=sendrecv.
U 2014/03/26 11:59:36.211476 10.237.236.207:5062 -> 10.237.236.207:5060 SIP/2.0 404 Not Found. Via: SIP/2.0/UDP 10.237.236.207;branch=z9hG4bK5a7e.03cc1cb9d02595ff6c7096253b4e6034.2;received=10.237.236.207. Via: SIP/2.0/UDP 10.237.236.212:63802;branch=z9hG4bK-d8754z-27d8d75f55eb3466-1---d8754z-;rport=63802. From: sip:1200@networklab.loc;transport=UDP;tag=e145b359. To: sip:1200@networklab.loc;transport=UDP;tag=as75383b1b. Call-ID: ZTRiNGMzOWYxOTAyMjkyMGFjNjI0NjQzZGZmZDE4N2E.. CSeq: 1 INVITE. Server: Asterisk PBX 12.0.0. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH. Supported: replaces, timer. Content-Length: 0. .
----- Original Message -----
From: "Alex Balashov" abalashov@evaristesys.com To: sr-users@lists.sip-router.org Sent: Wednesday, March 26, 2014 11:55:18 AM Subject: Re: [SR-Users] kamailio db
On 03/26/2014 11:53 AM, Slava Bendersky wrote:
Well, that's progress!
Kamailio is not involved in RTP, however[1].
Could it be that there is a network or transport-layer reachability issue between your endpoints? Or a firewall getting in the way, perhaps?
-- Alex
[1] It can control third-party, outboard RTP relays such as 'rtpproxy', though. But those are separate processes and pieces of software.
Hello Alex,
Yes, rtpproxy should handle nat cases, but i think on directly connected network should be able handle without any nat.
Slava.
----- Original Message -----
From: "Alex Balashov" abalashov@evaristesys.com To: sr-users@lists.sip-router.org Sent: Wednesday, March 26, 2014 11:55:18 AM Subject: Re: [SR-Users] kamailio db
On 03/26/2014 11:53 AM, Slava Bendersky wrote:
Well, that's progress!
Kamailio is not involved in RTP, however[1].
Could it be that there is a network or transport-layer reachability issue between your endpoints? Or a firewall getting in the way, perhaps?
-- Alex
[1] It can control third-party, outboard RTP relays such as 'rtpproxy', though. But those are separate processes and pieces of software.
Hello Alex, Restart both clients and tried call and call is looping to same extension.
Slava.
----- Original Message -----
From: "Slava Bendersky" volga629@networklab.ca To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Wednesday, March 26, 2014 12:16:29 PM Subject: Re: [SR-Users] kamailio db
Hello Alex,
Yes, rtpproxy should handle nat cases, but i think on directly connected network should be able handle without any nat.
Slava.
----- Original Message -----
From: "Alex Balashov" abalashov@evaristesys.com To: sr-users@lists.sip-router.org Sent: Wednesday, March 26, 2014 11:55:18 AM Subject: Re: [SR-Users] kamailio db
On 03/26/2014 11:53 AM, Slava Bendersky wrote:
Well, that's progress!
Kamailio is not involved in RTP, however[1].
Could it be that there is a network or transport-layer reachability issue between your endpoints? Or a firewall getting in the way, perhaps?
-- Alex
[1] It can control third-party, outboard RTP relays such as 'rtpproxy', though. But those are separate processes and pieces of software.
Hello Alex, Trying determine where is loop and on debug I can see like
6(2434) DEBUG: sanity [mod_sanity.c:255]: w_sanity_check(): sanity checks result: 1 6(2434) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=503 a=5 n=route 6(2434) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=847 a=2 n=return 6(2434) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=514 a=16 n=if 6(2434) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=506 a=25 n=is_method 6(2434) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=523 a=16 n=if 6(2434) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=514 a=24 n=loose_route 6(2434) DEBUG: rr [loose.c:113]: find_first_route(): No Route headers found 6(2434) DEBUG: rr [loose.c:929]: loose_route(): There is no Route HF 6(2434) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=523 a=5 n=route 6(2434) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=679 a=16 n=if 6(2434) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=644 a=24 n=has_totag 6(2434) DEBUG: siputils [checks.c:103]: has_totag(): no totag
Slava.
----- Original Message -----
From: "Slava Bendersky" volga629@networklab.ca To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Wednesday, March 26, 2014 12:29:36 PM Subject: Re: [SR-Users] kamailio db
Hello Alex, Restart both clients and tried call and call is looping to same extension.
Slava.
----- Original Message -----
From: "Slava Bendersky" volga629@networklab.ca To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Wednesday, March 26, 2014 12:16:29 PM Subject: Re: [SR-Users] kamailio db
Hello Alex,
Yes, rtpproxy should handle nat cases, but i think on directly connected network should be able handle without any nat.
Slava.
----- Original Message -----
From: "Alex Balashov" abalashov@evaristesys.com To: sr-users@lists.sip-router.org Sent: Wednesday, March 26, 2014 11:55:18 AM Subject: Re: [SR-Users] kamailio db
On 03/26/2014 11:53 AM, Slava Bendersky wrote:
Well, that's progress!
Kamailio is not involved in RTP, however[1].
Could it be that there is a network or transport-layer reachability issue between your endpoints? Or a firewall getting in the way, perhaps?
-- Alex
[1] It can control third-party, outboard RTP relays such as 'rtpproxy', though. But those are separate processes and pieces of software.
Hello Alex, I cleaned location table and create domain in db and getting error like
Mar 26 15:10:01 dsm01 /usr/sbin/kamailio[1810]: ERROR: tm [t_fwd.c:815]: add_uac(): ERROR: add_uac: maximum number of branches exceeded Mar 26 15:10:01 dsm01 /usr/sbin/kamailio[1810]: ERROR: tm [t_fwd.c:1773]: t_forward_nonack(): ERROR: t_forward_nonack: failure to add branches Mar 26 15:10:01 dsm01 /usr/sbin/kamailio[1810]: ERROR: tm [tm.c:1502]: _w_t_relay_to(): ERROR: w_t_relay_to: t_relay_to failed Mar 26 15:10:01 dsm01 /usr/sbin/kamailio[1810]: ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: Forking capacity exceeded (12/SL) Mar 26 15:10:34 dsm01 /usr/sbin/kamailio[1810]: ERROR: tm [t_fwd.c:815]: add_uac(): ERROR: add_uac: maximum number of branches exceeded Mar 26 15:10:34 dsm01 /usr/sbin/kamailio[1810]: ERROR: tm [t_fwd.c:1773]: t_forward_nonack(): ERROR: t_forward_nonack: failure to add branches Mar 26 15:10:34 dsm01 /usr/sbin/kamailio[1810]: ERROR: tm [tm.c:1502]: _w_t_relay_to(): ERROR: w_t_relay_to: t_relay_to failed Mar 26 15:10:34 dsm01 /usr/sbin/kamailio[1810]: ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: Forking capacity exceeded (12/SL) Mar 26 15:14:10 dsm01 /usr/sbin/kamailio[1810]: ERROR: tm [t_fwd.c:815]: add_uac(): ERROR: add_uac: maximum number of branches exceeded Mar 26 15:14:10 dsm01 /usr/sbin/kamailio[1810]: ERROR: tm [t_fwd.c:1773]: t_forward_nonack(): ERROR: t_forward_nonack: failure to add branches Mar 26 15:14:10 dsm01 /usr/sbin/kamailio[1810]: ERROR: tm [tm.c:1502]: _w_t_relay_to(): ERROR: w_t_relay_to: t_relay_to failed Mar 26 15:14:10 dsm01 /usr/sbin/kamailio[1810]: ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: Forking capacity exceeded (12/SL)
Slava.
----- Original Message -----
From: "Slava Bendersky" volga629@networklab.ca To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Wednesday, March 26, 2014 1:21:24 PM Subject: Re: [SR-Users] kamailio db
Hello Alex, Trying determine where is loop and on debug I can see like
6(2434) DEBUG: sanity [mod_sanity.c:255]: w_sanity_check(): sanity checks result: 1 6(2434) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=503 a=5 n=route 6(2434) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=847 a=2 n=return 6(2434) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=514 a=16 n=if 6(2434) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=506 a=25 n=is_method 6(2434) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=523 a=16 n=if 6(2434) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=514 a=24 n=loose_route 6(2434) DEBUG: rr [loose.c:113]: find_first_route(): No Route headers found 6(2434) DEBUG: rr [loose.c:929]: loose_route(): There is no Route HF 6(2434) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=523 a=5 n=route 6(2434) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=679 a=16 n=if 6(2434) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=644 a=24 n=has_totag 6(2434) DEBUG: siputils [checks.c:103]: has_totag(): no totag
Slava.
----- Original Message -----
From: "Slava Bendersky" volga629@networklab.ca To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Wednesday, March 26, 2014 12:29:36 PM Subject: Re: [SR-Users] kamailio db
Hello Alex, Restart both clients and tried call and call is looping to same extension.
Slava.
----- Original Message -----
From: "Slava Bendersky" volga629@networklab.ca To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Wednesday, March 26, 2014 12:16:29 PM Subject: Re: [SR-Users] kamailio db
Hello Alex,
Yes, rtpproxy should handle nat cases, but i think on directly connected network should be able handle without any nat.
Slava.
----- Original Message -----
From: "Alex Balashov" abalashov@evaristesys.com To: sr-users@lists.sip-router.org Sent: Wednesday, March 26, 2014 11:55:18 AM Subject: Re: [SR-Users] kamailio db
On 03/26/2014 11:53 AM, Slava Bendersky wrote:
Well, that's progress!
Kamailio is not involved in RTP, however[1].
Could it be that there is a network or transport-layer reachability issue between your endpoints? Or a firewall getting in the way, perhaps?
-- Alex
[1] It can control third-party, outboard RTP relays such as 'rtpproxy', though. But those are separate processes and pieces of software.
Slava,
It's pretty hard to tell what you've got going on without seeing your config, in full.
Thanks,
-- Alex
On 03/26/2014 03:18 PM, Slava Bendersky wrote:
Hello Alex, Here config in pastebin
Slava.
----- Original Message -----
From: "Alex Balashov" abalashov@evaristesys.com To: sr-users@lists.sip-router.org Sent: Wednesday, March 26, 2014 3:19:15 PM Subject: Re: [SR-Users] kamailio db
Slava,
It's pretty hard to tell what you've got going on without seeing your config, in full.
Thanks,
-- Alex
On 03/26/2014 03:18 PM, Slava Bendersky wrote:
On 03/26/2014 03:23 PM, Slava Bendersky wrote:
I'll take a look and get back to you as soon as I can. Right now, I need to catch a flight to Kamailio World. :)
Hello Alex, Thank you. I will continue try figure out my self. Kamailio open world, that nice.
Slava.
----- Original Message -----
From: "Alex Balashov" abalashov@evaristesys.com To: sr-users@lists.sip-router.org Sent: Wednesday, March 26, 2014 3:24:38 PM Subject: Re: [SR-Users] kamailio db
On 03/26/2014 03:23 PM, Slava Bendersky wrote:
I'll take a look and get back to you as soon as I can. Right now, I need to catch a flight to Kamailio World. :)
I didn't says clear. While you in busy I will try figure out my self.
Thank you for all help.
Slava. ----- Original Message -----
From: "Slava Bendersky" volga629@networklab.ca To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Wednesday, March 26, 2014 3:31:33 PM Subject: Re: [SR-Users] kamailio db
Hello Alex, Thank you. I will continue try figure out my self. Kamailio open world, that nice.
Slava.
----- Original Message -----
From: "Alex Balashov" abalashov@evaristesys.com To: sr-users@lists.sip-router.org Sent: Wednesday, March 26, 2014 3:24:38 PM Subject: Re: [SR-Users] kamailio db
On 03/26/2014 03:23 PM, Slava Bendersky wrote:
I'll take a look and get back to you as soon as I can. Right now, I need to catch a flight to Kamailio World. :)
Hello Alex,
After some testing I see on SDP call stack after first INVITE,
U 2014/03/27 12:29:05.441651 10.237.236.150:56892 -> 10.237.236.207:5060 REGISTER sip:networklab.loc;transport=UDP SIP/2.0. Via: SIP/2.0/UDP 10.237.236.150:56892;branch=z9hG4bK-d8754z-956aca8a2d207a79-1---d8754z-. Max-Forwards: 70. Contact: sip:1240@10.237.236.150:56892;rinstance=919639f35836b7ff;transport=UDP. To: "John Couch"sip:1240@networklab.loc;transport=UDP. From: "John Couch"sip:1240@networklab.loc;transport=UDP;tag=6e1ac002. Call-ID: MjQ5OTY5OTAxNGM3NDdiOGJlZTg2YjI5NmQ5MWRjM2M.. CSeq: 2 REGISTER. Expires: 3600. Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE. Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri. User-Agent: Z 3.2.21357 r21367. Allow-Events: presence, kpml. Content-Length: 0. .
U 2014/03/27 12:29:05.442162 10.237.236.207:5060 -> 10.237.236.150:56892 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 10.237.236.150:56892;branch=z9hG4bK-d8754z-956aca8a2d207a79-1---d8754z-. To: "John Couch"sip:1240@networklab.loc;transport=UDP;tag=b27e1a1d33761e85846fc98f5f3a7e58.ee33. From: "John Couch"sip:1240@networklab.loc;transport=UDP;tag=6e1ac002. Call-ID: MjQ5OTY5OTAxNGM3NDdiOGJlZTg2YjI5NmQ5MWRjM2M.. CSeq: 2 REGISTER. WWW-Authenticate: Digest realm="networklab.loc", nonce="UzRS/VM0UdG+dpdwGxM0b6wbUgs/AheL", qop="auth". Server: kamailio (4.1.2 (x86_64/linux)). Content-Length: 0. .
U 2014/03/27 12:29:05.451491 10.237.236.150:56892 -> 10.237.236.207:5060 REGISTER sip:networklab.loc;transport=UDP SIP/2.0. Via: SIP/2.0/UDP 10.237.236.150:56892;branch=z9hG4bK-d8754z-57f468fe84211962-1---d8754z-. Max-Forwards: 70. Contact: sip:1240@10.237.236.150:56892;rinstance=919639f35836b7ff;transport=UDP. To: "John Couch"sip:1240@networklab.loc;transport=UDP. From: "John Couch"sip:1240@networklab.loc;transport=UDP;tag=6e1ac002. Call-ID: MjQ5OTY5OTAxNGM3NDdiOGJlZTg2YjI5NmQ5MWRjM2M.. CSeq: 3 REGISTER. Expires: 3600. Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE. Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri. User-Agent: Z 3.2.21357 r21367. Authorization: Digest username="1240",realm="networklab.loc",nonce="UzRS/VM0UdG+dpdwGxM0b6wbUgs/AheL",uri="sip:networklab.loc;transport=UDP",response="492ead1598de81a10ee8a1f2e15cf6f2",cnonce="6b9530780e8e8df2836b6920a3a35144",nc=00000001,qop=auth,algorithm=MD5. Allow-Events: presence, kpml. Content-Length: 0. .
U 2014/03/27 12:29:05.453303 10.237.236.207:5060 -> 10.237.236.150:56892 SIP/2.0 200 OK. Via: SIP/2.0/UDP 10.237.236.150:56892;branch=z9hG4bK-d8754z-57f468fe84211962-1---d8754z-. To: "John Couch"sip:1240@networklab.loc;transport=UDP;tag=b27e1a1d33761e85846fc98f5f3a7e58.8292. From: "John Couch"sip:1240@networklab.loc;transport=UDP;tag=6e1ac002. Call-ID: MjQ5OTY5OTAxNGM3NDdiOGJlZTg2YjI5NmQ5MWRjM2M.. CSeq: 3 REGISTER. Server: kamailio (4.1.2 (x86_64/linux)). Content-Length: 0. .
U 2014/03/27 12:29:24.359951 10.237.236.212:57816 -> 10.237.236.207:5060 . . ..............
U 2014/03/27 12:29:32.661825 10.237.236.150:56892 -> 10.237.236.207:5060 INVITE sip:1200@networklab.loc;transport=UDP SIP/2.0. Via: SIP/2.0/UDP 10.237.236.150:56892;branch=z9hG4bK-d8754z-dd99050e9fca2163-1---d8754z-. Max-Forwards: 70. Contact: sip:1240@10.237.236.150:56892;transport=UDP. To: sip:1200@networklab.loc;transport=UDP. From: "John Couch"sip:1240@networklab.loc;transport=UDP;tag=270d1828. Call-ID: ZGNhMDdmOGQ1MWFhZTA2NGYwMTE1YThlM2UwNTQxYzI.. CSeq: 1 INVITE. Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE. Content-Type: application/sdp. Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri. User-Agent: Z 3.2.21357 r21367. Allow-Events: presence, kpml. Content-Length: 165. . v=0. o=Z 0 0 IN IP4 10.237.236.150. s=Z. c=IN IP4 10.237.236.150. t=0 0. m=audio 8000 RTP/AVP 0 101. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. a=sendrecv.
U 2014/03/27 12:29:32.662331 10.237.236.207:5060 -> 10.237.236.150:56892 SIP/2.0 407 Proxy Authentication Required. Via: SIP/2.0/UDP 10.237.236.150:56892;branch=z9hG4bK-d8754z-dd99050e9fca2163-1---d8754z-. To: sip:1200@networklab.loc;transport=UDP;tag=b27e1a1d33761e85846fc98f5f3a7e58.73fa. From: "John Couch"sip:1240@networklab.loc;transport=UDP;tag=270d1828. Call-ID: ZGNhMDdmOGQ1MWFhZTA2NGYwMTE1YThlM2UwNTQxYzI.. CSeq: 1 INVITE. Proxy-Authenticate: Digest realm="networklab.loc", nonce="UzRTGFM0Uezw+Q1ZC/KUq4LDqr7BFZZ/", qop="auth". Server: kamailio (4.1.2 (x86_64/linux)). Content-Length: 0. .
U 2014/03/27 12:29:32.672262 10.237.236.150:56892 -> 10.237.236.207:5060 ACK sip:1200@networklab.loc;transport=UDP SIP/2.0. Via: SIP/2.0/UDP 10.237.236.150:56892;branch=z9hG4bK-d8754z-dd99050e9fca2163-1---d8754z-. Max-Forwards: 70. To: sip:1200@networklab.loc;transport=UDP;tag=b27e1a1d33761e85846fc98f5f3a7e58.73fa. From: "John Couch"sip:1240@networklab.loc;transport=UDP;tag=270d1828. Call-ID: ZGNhMDdmOGQ1MWFhZTA2NGYwMTE1YThlM2UwNTQxYzI.. CSeq: 1 ACK. Content-Length: 0. .
U 2014/03/27 12:29:32.680559 10.237.236.150:56892 -> 10.237.236.207:5060 INVITE sip:1200@networklab.loc;transport=UDP SIP/2.0. Via: SIP/2.0/UDP 10.237.236.150:56892;branch=z9hG4bK-d8754z-4ac013f010b101fe-1---d8754z-. Max-Forwards: 70. Contact: sip:1240@10.237.236.150:56892;transport=UDP. To: sip:1200@networklab.loc;transport=UDP. From: "John Couch"sip:1240@networklab.loc;transport=UDP;tag=270d1828. Call-ID: ZGNhMDdmOGQ1MWFhZTA2NGYwMTE1YThlM2UwNTQxYzI.. CSeq: 2 INVITE. Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE. Content-Type: application/sdp. Proxy-Authorization: Digest username="1240",realm="networklab.loc",nonce="UzRTGFM0Uezw+Q1ZC/KUq4LDqr7BFZZ/",uri="sip:1200@networklab.loc;transport=UDP",response="0373158cea6615a4bca50401ace5af75",cnonce="4dfbe915fff3e822e9bc5ac7c3b526f8",nc=00000001,qop=auth,algorithm=MD5. Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri. User-Agent: Z 3.2.21357 r21367. Allow-Events: presence, kpml. Content-Length: 165. . v=0. o=Z 0 0 IN IP4 10.237.236.150. s=Z. c=IN IP4 10.237.236.150. t=0 0. m=audio 8000 RTP/AVP 0 101. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. a=sendrecv.
U 2014/03/27 12:29:32.682376 10.237.236.207:5060 -> 10.237.236.150:56892 SIP/2.0 200 OK. Via: SIP/2.0/UDP 10.237.236.150:56892;branch=z9hG4bK-d8754z-4ac013f010b101fe-1---d8754z-. To: sip:1200@networklab.loc;transport=UDP;tag=b27e1a1d33761e85846fc98f5f3a7e58.eb89. From: "John Couch"sip:1240@networklab.loc;transport=UDP;tag=270d1828. Call-ID: ZGNhMDdmOGQ1MWFhZTA2NGYwMTE1YThlM2UwNTQxYzI.. CSeq: 2 INVITE. Server: kamailio (4.1.2 (x86_64/linux)). Content-Length: 0. .
U 2014/03/27 12:29:35.462838 10.237.236.150:56892 -> 10.237.236.207:5060 .
----- Original Message -----
From: "Alex Balashov" abalashov@evaristesys.com To: sr-users@lists.sip-router.org Sent: Wednesday, March 26, 2014 3:24:38 PM Subject: Re: [SR-Users] kamailio db
On 03/26/2014 03:23 PM, Slava Bendersky wrote:
I'll take a look and get back to you as soon as I can. Right now, I need to catch a flight to Kamailio World. :)
Hello,
the invite is replied with 200ok by kamailio, that should not happen. You have some wrong logic inside kamailio.cfg.
You can load debugger module and set cfgtrace parameter of it to 1, then watch the logs to see which actions from kamailio.cfg are executed for the invite.
Cheers, Daniel
On 27/03/14 17:34, Slava Bendersky wrote:
Daniel,
I found your writeup at http://kb.asipto.com/kamailio:skype-like-service-in-less-than-one-hour and tried to follow it. Jitsi would not connect even though it is running in the same box as Kamailio set up exactly as the linked page suggested. No firewalls exist between them.
It connects fine over TCP and works, it also connects fine over UDP but cannot send/receive text messages and voice does not work. But over TLS it never connects, and never times out - it just sits there connecting.
I tried changing the port ## for TLS from 5060 to 5061 etc and even creating an SRV record on the local DNS server for this LAN, but nothing worked.
Can you suggest any troubleshooting steps?
Thank you! ve
Hello Daniel, After looking on debug I have question, about this debug
9(2046) DEBUG: <core> [parser/parse_addr_spec.c:893]: parse_addr_spec(): end of header reached, state=29 9(2046) DEBUG: <core> [parser/msg_parser.c:190]: get_hdr_field(): DEBUG: get_hdr_field: <To> [82]; uri=[sip:120@networklab.loc;transport=UDP] 9(2046) DEBUG: <core> [parser/msg_parser.c:192]: get_hdr_field(): DEBUG: to body [sip:120@networklab.loc;transport=UDP] 9(2046) DEBUG: sl [sl_funcs.c:431]: sl_filter_ACK(): SL local ACK found -> dropping it! --- ? I wonder what it s mean. 9(2046) DEBUG: <core> [usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) 9(2046) DEBUG: <core> [usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) 9(2046) DEBUG: <core> [usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) 9(2046) DEBUG: <core> [usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) 9(2046) DEBUG: <core> [usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) 9(2046) DEBUG: <core> [usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) 9(2046) DEBUG: <core> [xavp.c:448]: xavp_destroy_list(): destroying xavp list (nil) 9(2046) DEBUG: <core> [receive.c:296]: receive_msg(): receive_msg: cleaning up
Slava.
----- Original Message -----
From: info@vintageelectronics.ca To: miconda@gmail.com, "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Friday, March 28, 2014 8:29:53 PM Subject: Re: [SR-Users] kamailio db
Daniel,
Following up.
Thanks ve
On 03/27/2014 04:44 PM, info@vintageelectronics.ca wrote:
_______________________________________________ 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
Hello Daniel, Doing more look up on config, but can't figure out where problem with call flow. I tried use debug to track down where conversation is breaks, but I see only INVITE and let it. Still come OK after first INVITE.
This warning which show up logs.
Mar 30 19:31:12 dsm01 /usr/sbin/kamailio[10264]: WARNING: sanity [sanity.c:833]: check_parse_uris(): sanity_check(): check_parse_uris(): failed to parse From uri
U 2014/03/30 19:53:58.585467 10.230.242.100:32305 -> 192.168.10.120:5060 INVITE sip:120@networklab.loc;transport=UDP SIP/2.0. Via: SIP/2.0/UDP 99.224.107.222:32305;branch=z9hG4bK-d8754z-4c0bcbe0934f0686-1---d8754z-;rport. Max-Forwards: 70. Contact: sip:1240@99.224.107.222:32305;transport=UDP. To: sip:120@networklab.loc;transport=UDP. From: "John Couch"sip:1240@networklab.loc;transport=UDP;tag=4c660a39. Call-ID: YTE0M2U0NTY3ZjExYjJlMzkyNzE4NTMwOTdmYzkxNTk.. CSeq: 2 INVITE. Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE. Content-Type: application/sdp. Proxy-Authorization: Digest username="1240",realm="networklab.loc",nonce="UzivwlM4rpbCgH2p+34mDCD9rfukpxSD",uri="sip:120@networklab.loc;transport=UDP",response="5bc9a9a06ecd7247a653602c5e9b141b",cnonce="a39c83dccf8c4702f5613fa809669dfe",nc=00000001,qop=auth,algorithm=MD5. Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri. User-Agent: Z 3.2.21357 r21103. Allow-Events: presence, kpml. Content-Length: 165. . v=0. o=Z 0 0 IN IP4 99.224.107.222. s=Z. c=IN IP4 99.224.107.222. t=0 0. m=audio 8000 RTP/AVP 0 101. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. a=sendrecv.
U 2014/03/30 19:53:58.586898 192.168.10.120:5060 -> 10.230.242.100:32305 SIP/2.0 200 OK. Via: SIP/2.0/UDP 99.224.107.222:32305;branch=z9hG4bK-d8754z-4c0bcbe0934f0686-1---d8754z-;rport=32305;received=10.230.242.100. To: sip:120@networklab.loc;transport=UDP;tag=b27e1a1d33761e85846fc98f5f3a7e58.aad9. From: "John Couch"sip:1240@networklab.loc;transport=UDP;tag=4c660a39. Call-ID: YTE0M2U0NTY3ZjExYjJlMzkyNzE4NTMwOTdmYzkxNTk.. CSeq: 2 INVITE. Server: kamailio (4.1.2 (x86_64/linux)). Content-Length: 0.
Slava.
----- Original Message -----
From: info@vintageelectronics.ca To: miconda@gmail.com, "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Sunday, March 30, 2014 2:32:55 PM Subject: Re: [SR-Users] kamailio db
Daniel:
Following up.
Thank you!
On 03/28/2014 08:29 PM, info@vintageelectronics.ca wrote:
_______________________________________________ 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
Hello Daniel, Here debug of first invite, but I can't see. what actually not right.
7(4161) INFO: <script>: This is 1200 and 1200 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=757 a=16 n=if 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=739 a=25 n=lookup 7(4161) DEBUG: registrar [lookup.c:181]: lookup(): contact for [1200@networklab.loc] found by address 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=762 a=16 n=if 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=757 a=25 n=is_method 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=759 a=39 n=setflag 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=762 a=5 n=route 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=605 a=16 n=if 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=601 a=25 n=is_method 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=602 a=25 n=t_on_branch 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=603 a=25 n=t_on_reply 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=609 a=16 n=if 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=605 a=25 n=is_method 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=606 a=25 n=t_on_failure 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=612 a=16 n=if 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=609 a=24 n=t_relay 7(4161) DEBUG: tm [t_lookup.c:1373]: t_newtran(): DEBUG: t_newtran: msg id=13 , global msg id=13 , T on entrance=(nil) 7(4161) DEBUG: tm [t_lookup.c:527]: t_lookup_request(): t_lookup_request: start searching: hash=53747, isACK=0 7(4161) DEBUG: tm [t_lookup.c:485]: matching_3261(): DEBUG: RFC3261 transaction matching failed 7(4161) DEBUG: tm [t_lookup.c:709]: t_lookup_request(): DEBUG: t_lookup_request: no transaction found 7(4161) DEBUG: tm [t_hooks.c:374]: run_reqin_callbacks_internal(): DBG: trans=0x7fc3ea9cf688, callback type 1, id 0 entered 7(4161) DEBUG: <core> [md5utils.c:67]: MD5StringArray(): DEBUG: MD5 calculated: aec714b86f229713d513ffed6ac538f3 7(4161) DEBUG: tm [t_funcs.c:347]: t_relay_to(): SER: new INVITE 7(4161) DEBUG: <core> [msg_translator.c:204]: check_via_address(): check_via_address(192.168.10.116, 192.168.10.116, 0) 7(4161) DEBUG: <core> [mem/shm_mem.c:111]: _shm_resize(): WARNING:vqm_resize: resize(0) called 7(4161) DEBUG: tm [t_reply.c:728]: _reply_light(): DEBUG: reply sent out. buf=0x7fc3f639f7d8: SIP/2.0 100 trying -..., shmem=0x7fc3ea9cb100: SIP/2.0 100 trying - 7(4161) DEBUG: tm [t_reply.c:738]: _reply_light(): DEBUG: _reply_light: finished 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=1003 a=25 n=xdbg 7(4161) DEBUG: <script>: new branch [0] to sip:1240@192.168.10.116:48961;transport=UDP;alias=192.168.10.116~48961~1 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=1004 a=5 n=route 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=861 a=16 n=if 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=854 a=24 n=is_request 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=860 a=16 n=if 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=855 a=24 n=has_totag 7(4161) DEBUG: siputils [checks.c:103]: has_totag(): no totag 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=866 a=16 n=if 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=861 a=41 n=isflagset 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=866 a=24 n=rtpproxy_manage 7(4161) DEBUG: <core> [parser/sdp/sdp_helpr_funcs.c:565]: extract_mediaip(): located IP address [127.0.0.1] in `o=' field 7(4161) DEBUG: <core> [parser/sdp/sdp_helpr_funcs.c:565]: extract_mediaip(): located IP address [127.0.0.1] in `c=' field 7(4161) DEBUG: rtpproxy [rtpproxy_funcs.c:148]: check_content_type(): type <application/sdp> found valid 7(4161) DEBUG: rtpproxy [rtpproxy.c:2696]: force_rtp_proxy(): proxy reply: 43056 192.168.10.120
7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=873 a=16 n=if 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=868 a=24 n=is_request 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=872 a=16 n=if 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=869 a=24 n=has_totag 7(4161) DEBUG: siputils [checks.c:103]: has_totag(): no totag 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=870 a=25 n=add_rr_param 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=881 a=16 n=if 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=873 a=24 n=is_reply 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=881 a=2 n=return 7(4161) DEBUG: <core> [msg_translator.c:456]: clen_builder(): clen_builder: content-length: 184 (184) 7(4161) DEBUG: <core> [msg_translator.c:204]: check_via_address(): check_via_address(192.168.10.116, 192.168.10.116, 0) 7(4161) DEBUG: tm [t_funcs.c:394]: t_relay_to(): SER: new transaction fwd'ed 7(4161) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=612 a=2 n=exit 7(4161) DEBUG: <core> [usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) 7(4161) DEBUG: <core> [usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) 7(4161) DEBUG: <core> [usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) 7(4161) DEBUG: <core> [usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) 7(4161) DEBUG: <core> [usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) 7(4161) DEBUG: <core> [usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) 7(4161) DEBUG: <core> [xavp.c:448]: xavp_destroy_list(): destroying xavp list (nil) 7(4161) DEBUG: <core> [receive.c:296]: receive_msg(): receive_msg: cleaning up 7(4161) DEBUG: <core> [parser/sdp/sdp.c:793]: free_sdp(): _sdp = 0x7fc3f639b728 7(4161) DEBUG: <core> [parser/sdp/sdp.c:795]: free_sdp(): sdp = 0x7fc3f639ecd0 7(4161) DEBUG: <core> [parser/sdp/sdp.c:797]: free_sdp(): session = 0x7fc3f639c3d0 6(4160) DEBUG: <core> [parser/msg_parser.c:633]: parse_msg(): SIP Reply (status): 6(4160) DEBUG: <core> [parser/msg_parser.c:635]: parse_msg(): version: <SIP/2.0> 6(4160) DEBUG: <core> [parser/msg_parser.c:637]: parse_msg(): status: <100> 6(4160) DEBUG: <core> [parser/msg_parser.c:639]: parse_msg(): reason: <Trying> 6(4160) DEBUG: <core> [parser/parse_via.c:1284]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK3f1d.aec714b86f229713d513ffed6ac538f3.0>; state=16 6(4160) DEBUG: <core> [parser/parse_via.c:2672]: parse_via(): end of header reached, state=5 6(4160) DEBUG: <core> [parser/msg_parser.c:513]: parse_headers(): parse_headers: Via found, flags=2 6(4160) DEBUG: <core> [parser/msg_parser.c:515]: parse_headers(): parse_headers: this is the first via 6(4160) DEBUG: <core> [receive.c:152]: receive_msg(): After parse_msg... 6(4160) DEBUG: tm [t_lookup.c:1072]: t_check_msg(): DEBUG: t_check_msg: msg id=13 global id=11 T start=(nil) 6(4160) DEBUG: <core> [parser/parse_via.c:1284]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK-d8754z-88fe2d7ab6e1e390-1---d8754z->; state=6 6(4160) DEBUG: <core> [parser/parse_via.c:1284]: parse_via_param(): Found param type 235, <rport> = <48961>; state=16 6(4160) DEBUG: <core> [parser/parse_via.c:2672]: parse_via(): end of header reached, state=5 6(4160) DEBUG: <core> [parser/msg_parser.c:513]: parse_headers(): parse_headers: Via found, flags=62 6(4160) DEBUG: <core> [parser/msg_parser.c:526]: parse_headers(): parse_headers: this is the second via 6(4160) DEBUG: <core> [parser/parse_addr_spec.c:893]: parse_addr_spec(): end of header reached, state=10 6(4160) DEBUG: <core> [parser/msg_parser.c:190]: get_hdr_field(): DEBUG: get_hdr_field: <To> [41]; uri=[sip:1200@networklab.loc;transport=UDP] 6(4160) DEBUG: <core> [parser/msg_parser.c:192]: get_hdr_field(): DEBUG: to body [sip:1200@networklab.loc;transport=UDP ] 6(4160) DEBUG: <core> [parser/msg_parser.c:170]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <2> <INVITE> 6(4160) DEBUG: tm [t_lookup.c:949]: t_reply_matching(): DEBUG: t_reply_matching: hash 53747 label 0 branch 0 6(4160) DEBUG: tm [t_lookup.c:1004]: t_reply_matching(): DEBUG: t_reply_matching: reply matched (T=0x7fc3ea9cf688)! 6(4160) DEBUG: tm [t_hooks.c:288]: run_trans_callbacks_internal(): DBG: trans=0x7fc3ea9cf688, callback type 2, id 0 entered 6(4160) DEBUG: acc [acc_logic.c:557]: tmcb_func(): acc callback called for t(0x7fc3ea9cf688) event type 2, reply code 100 6(4160) DEBUG: tm [t_lookup.c:1141]: t_check_msg(): DEBUG: t_check_msg: msg id=13 global id=13 T end=0x7fc3ea9cf688 6(4160) DEBUG: tm [t_reply.c:2206]: reply_received(): DEBUG: reply_received: org. status uas=100, uac[0]=0 local=0 is_invite=1) 6(4160) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=1009 a=25 n=xdbg 6(4160) DEBUG: <script>: incoming reply 6(4160) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=1012 a=16 n=if 6(4160) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=1011 a=5 n=route 6(4160) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=861 a=16 n=if 6(4160) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=854 a=24 n=is_request 6(4160) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=866 a=16 n=if 6(4160) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=861 a=41 n=isflagset 6(4160) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=866 a=24 n=rtpproxy_manage 6(4160) DEBUG: <core> [parser/msg_parser.c:204]: get_hdr_field(): DEBUG: get_hdr_body : content_length=0 6(4160) DEBUG: <core> [parser/msg_parser.c:106]: get_hdr_field(): found end of header 6(4160) DEBUG: <core> [parser/sdp/sdp.c:712]: parse_sdp(): message body has length zero 6(4160) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=873 a=16 n=if 6(4160) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=868 a=24 n=is_request 6(4160) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=881 a=16 n=if 6(4160) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=873 a=24 n=is_reply 6(4160) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=879 a=16 n=if 6(4160) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=874 a=25 n=isbflagset 6(4160) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=881 a=2 n=return 6(4160) DEBUG: tm [t_reply.c:1304]: t_should_relay_response(): ->>>>>>>>> T_code=100, new_code=100 6(4160) DEBUG: tm [t_reply.c:1822]: relay_reply(): DEBUG: relay_reply: branch=0, save=0, relay=-1 icode=0 6(4160) DEBUG: <core> [usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) 6(4160) DEBUG: <core> [usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) 6(4160) DEBUG: <core> [usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) 6(4160) DEBUG: <core> [usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) 6(4160) DEBUG: <core> [usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) 6(4160) DEBUG: <core> [usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) 6(4160) DEBUG: <core> [xavp.c:448]: xavp_destroy_list(): destroying xavp list (nil) 6(4160) DEBUG: <core> [receive.c:296]: receive_msg(): receive_msg: cleaning up 8(4162) DEBUG: <core> [parser/msg_parser.c:633]: parse_msg(): SIP Reply (status): 8(4162) DEBUG: <core> [parser/msg_parser.c:635]: parse_msg(): version: <SIP/2.0> 8(4162) DEBUG: <core> [parser/msg_parser.c:637]: parse_msg(): status: <180> 8(4162) DEBUG: <core> [parser/msg_parser.c:639]: parse_msg(): reason: <Ringing> 8(4162) DEBUG: <core> [parser/parse_via.c:1284]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK3f1d.aec714b86f229713d513ffed6ac538f3.0>; state=16 8(4162) DEBUG: <core> [parser/parse_via.c:2672]: parse_via(): end of header reached, state=5 8(4162) DEBUG: <core> [parser/msg_parser.c:513]: parse_headers(): parse_headers: Via found, flags=2 8(4162) DEBUG: <core> [parser/msg_parser.c:515]: parse_headers(): parse_headers: this is the first via 8(4162) DEBUG: <core> [receive.c:152]: receive_msg(): After parse_msg... 8(4162) DEBUG: tm [t_lookup.c:1072]: t_check_msg(): DEBUG: t_check_msg: msg id=15 global id=14 T start=(nil) 8(4162) DEBUG: <core> [parser/parse_via.c:1284]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK-d8754z-88fe2d7ab6e1e390-1---d8754z->; state=6 8(4162) DEBUG: <core> [parser/parse_via.c:1284]: parse_via_param(): Found param type 235, <rport> = <48961>; state=16 8(4162) DEBUG: <core> [parser/parse_via.c:2672]: parse_via(): end of header reached, state=5 8(4162) DEBUG: <core> [parser/msg_parser.c:513]: parse_headers(): parse_headers: Via found, flags=62 8(4162) DEBUG: <core> [parser/msg_parser.c:526]: parse_headers(): parse_headers: this is the second via 8(4162) DEBUG: <core> [parser/parse_addr_spec.c:176]: parse_to_param(): DEBUG: add_param: tag=c23f2e5e 8(4162) DEBUG: <core> [parser/parse_addr_spec.c:893]: parse_addr_spec(): end of header reached, state=29 8(4162) DEBUG: <core> [parser/msg_parser.c:190]: get_hdr_field(): DEBUG: get_hdr_field: <To> [54]; uri=[sip:1200@networklab.loc;transport=UDP] 8(4162) DEBUG: <core> [parser/msg_parser.c:192]: get_hdr_field(): DEBUG: to body [sip:1200@networklab.loc;transport=UDP] 8(4162) DEBUG: <core> [parser/msg_parser.c:170]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <2> <INVITE> 8(4162) DEBUG: tm [t_lookup.c:949]: t_reply_matching(): DEBUG: t_reply_matching: hash 53747 label 0 branch 0 8(4162) DEBUG: tm [t_lookup.c:1004]: t_reply_matching(): DEBUG: t_reply_matching: reply matched (T=0x7fc3ea9cf688)! 8(4162) DEBUG: tm [t_hooks.c:288]: run_trans_callbacks_internal(): DBG: trans=0x7fc3ea9cf688, callback type 2, id 0 entered 8(4162) DEBUG: acc [acc_logic.c:557]: tmcb_func(): acc callback called for t(0x7fc3ea9cf688) event type 2, reply code 180 8(4162) DEBUG: tm [t_lookup.c:1141]: t_check_msg(): DEBUG: t_check_msg: msg id=15 global id=15 T end=0x7fc3ea9cf688 8(4162) DEBUG: tm [t_reply.c:2206]: reply_received(): DEBUG: reply_received: org. status uas=100, uac[0]=100 local=0 is_invite=1) 8(4162) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=1009 a=25 n=xdbg 8(4162) DEBUG: <script>: incoming reply 8(4162) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=1012 a=16 n=if 8(4162) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=1011 a=5 n=route 8(4162) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=861 a=16 n=if 8(4162) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=854 a=24 n=is_request 8(4162) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=866 a=16 n=if 8(4162) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=861 a=41 n=isflagset 8(4162) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=866 a=24 n=rtpproxy_manage 8(4162) DEBUG: <core> [parser/msg_parser.c:204]: get_hdr_field(): DEBUG: get_hdr_body : content_length=0 8(4162) DEBUG: <core> [parser/msg_parser.c:106]: get_hdr_field(): found end of header 8(4162) DEBUG: <core> [parser/sdp/sdp.c:712]: parse_sdp(): message body has length zero 8(4162) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=873 a=16 n=if 8(4162) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=868 a=24 n=is_request 8(4162) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=881 a=16 n=if 8(4162) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=873 a=24 n=is_reply 8(4162) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=879 a=16 n=if 8(4162) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=874 a=25 n=isbflagset 8(4162) ERROR: *** cfgtrace: c=[/etc/kamailio/kamailio-ldap.cfg] l=881 a=2 n=return 8(4162) DEBUG: tm [t_reply.c:1304]: t_should_relay_response(): ->>>>>>>>> T_code=100, new_code=180 8(4162) DEBUG: tm [t_reply.c:1822]: relay_reply(): DEBUG: relay_reply: branch=0, save=0, relay=0 icode=0 8(4162) DEBUG: <core> [msg_translator.c:2007]: generate_res_buf_from_sip_res(): old size: 596, new size: 509 8(4162) DEBUG: <core> [msg_translator.c:2025]: generate_res_buf_from_sip_res(): copied size: orig:108, new: 21, rest: 488 msg=
Slava.
----- Original Message -----
From: "Slava Bendersky" volga629@networklab.ca To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Cc: miconda@gmail.com Sent: Sunday, March 30, 2014 8:01:43 PM Subject: Re: [SR-Users] kamailio db
Hello Daniel, Doing more look up on config, but can't figure out where problem with call flow. I tried use debug to track down where conversation is breaks, but I see only INVITE and let it. Still come OK after first INVITE.
This warning which show up logs.
Mar 30 19:31:12 dsm01 /usr/sbin/kamailio[10264]: WARNING: sanity [sanity.c:833]: check_parse_uris(): sanity_check(): check_parse_uris(): failed to parse From uri
U 2014/03/30 19:53:58.585467 10.230.242.100:32305 -> 192.168.10.120:5060 INVITE sip:120@networklab.loc;transport=UDP SIP/2.0. Via: SIP/2.0/UDP 99.224.107.222:32305;branch=z9hG4bK-d8754z-4c0bcbe0934f0686-1---d8754z-;rport. Max-Forwards: 70. Contact: sip:1240@99.224.107.222:32305;transport=UDP. To: sip:120@networklab.loc;transport=UDP. From: "John Couch"sip:1240@networklab.loc;transport=UDP;tag=4c660a39. Call-ID: YTE0M2U0NTY3ZjExYjJlMzkyNzE4NTMwOTdmYzkxNTk.. CSeq: 2 INVITE. Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE. Content-Type: application/sdp. Proxy-Authorization: Digest username="1240",realm="networklab.loc",nonce="UzivwlM4rpbCgH2p+34mDCD9rfukpxSD",uri="sip:120@networklab.loc;transport=UDP",response="5bc9a9a06ecd7247a653602c5e9b141b",cnonce="a39c83dccf8c4702f5613fa809669dfe",nc=00000001,qop=auth,algorithm=MD5. Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri. User-Agent: Z 3.2.21357 r21103. Allow-Events: presence, kpml. Content-Length: 165. . v=0. o=Z 0 0 IN IP4 99.224.107.222. s=Z. c=IN IP4 99.224.107.222. t=0 0. m=audio 8000 RTP/AVP 0 101. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. a=sendrecv.
U 2014/03/30 19:53:58.586898 192.168.10.120:5060 -> 10.230.242.100:32305 SIP/2.0 200 OK. Via: SIP/2.0/UDP 99.224.107.222:32305;branch=z9hG4bK-d8754z-4c0bcbe0934f0686-1---d8754z-;rport=32305;received=10.230.242.100. To: sip:120@networklab.loc;transport=UDP;tag=b27e1a1d33761e85846fc98f5f3a7e58.aad9. From: "John Couch"sip:1240@networklab.loc;transport=UDP;tag=4c660a39. Call-ID: YTE0M2U0NTY3ZjExYjJlMzkyNzE4NTMwOTdmYzkxNTk.. CSeq: 2 INVITE. Server: kamailio (4.1.2 (x86_64/linux)). Content-Length: 0.
Slava.
----- Original Message -----
From: info@vintageelectronics.ca To: miconda@gmail.com, "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Sunday, March 30, 2014 2:32:55 PM Subject: Re: [SR-Users] kamailio db
Daniel:
Following up.
Thank you!
On 03/28/2014 08:29 PM, info@vintageelectronics.ca wrote:
_______________________________________________ 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
The server is installed on a Linux machine on my LAN and there are two users with Jitsi for a client. One user is in the same box as kamailio (IP 10.10.10.3), another is on a Windows machine (IP 10.10.10.20).
Both users can connect and come online using TCP or UDP protocol. I can see them in the output from kamctl online, but Jitsi is still showing them as offline. When they try to send text messages to one another, they get below error:
The above message could not be delivered A network problem occurred. Please check your network configuration and try again. Error was: 478 Unresolvable destination (478/SL)
What is the root cause and what should be done to enable them to communicate?
Thank you!
When initially configuring kamailio, I used DBTEXT for database and uncommented default path in subject, but the directory is still empty after creating 2 users. I see the users coming online with kamctl online. Where and how is kamailio storing the user database and how can I access it and verify what information is there?
Thank you!
Hello Daniel, I fixed config and right now it fully functional local calls. VM server still need see why asterisk not send correct direction rtp.
Here config.
http://sebsauvage.net/paste/?ffca000a32579ed0#JhOA+vZnTWFH05V2Ey7lL6u5Ntp95j...
Slava.
----- Original Message -----
From: info@vintageelectronics.ca To: miconda@gmail.com, "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Sunday, March 30, 2014 2:32:55 PM Subject: Re: [SR-Users] kamailio db
Daniel:
Following up.
Thank you!
On 03/28/2014 08:29 PM, info@vintageelectronics.ca wrote:
_______________________________________________ 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
Hello Daniel, I was looking where is problem, and I see call is looping meaning coming back to caller. I putted couple xlog to see where is breaks.
$avp(oexten) = $rU; xlog("L_INFO", "This is $avp(oexten)"); if (!lookup("location")) { xlog("L_INFO", "This $rU and this $du");
this is log
Mar 28 18:16:46 dsm01 /usr/sbin/kamailio[1754]: INFO: <script>: This is 1240.
In main routing logic I tried use on save location 0x04 to store last registrar for external users. Also tried use MULTIDOMAIN.
Here config file http://fpaste.org/89673/60456311/
And here debug, I see 486 busy
http://fpaste.org/89676/46038139/
In mysql I see record in location table.
| 146 | uloc-5335f27e-6da-2 | 1240 | networklab.loc | sip:1200@192.168.100.1:57967;transport=UDP | NULL | NULL | 2014-03-28 19:16:46 | -1.00 | YmRiZmE0MzQ5YTU0NjkwNTFiMmM0NDFmOGQzNTljZDg. | 2 | 2014-03-28 18:16:46 | 0 | 0 | Z 3.2.21368 r21103 | udp:192.168.100.145:5060 | 5087 | NULL | 0 |
Slava.
----- Original Message -----
From: "Daniel-Constantin Mierla" miconda@gmail.com To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Thursday, March 27, 2014 2:47:38 PM Subject: Re: [SR-Users] kamailio db
Hello,
the invite is replied with 200ok by kamailio, that should not happen. You have some wrong logic inside kamailio.cfg.
You can load debugger module and set cfgtrace parameter of it to 1, then watch the logs to see which actions from kamailio.cfg are executed for the invite.
Cheers, Daniel
On 27/03/14 17:34, Slava Bendersky wrote:
Hello Alex,
After some testing I see on SDP call stack after first INVITE, .
U 2014/03/27 12:29:32.680559 10.237.236.150:56892 -> 10.237.236.207:5060 INVITE sip:1200@networklab.loc;transport=UDP SIP/2.0. Via: SIP/2.0/UDP 10.237.236.150:56892;branch=z9hG4bK-d8754z-4ac013f010b101fe-1---d8754z-. Max-Forwards: 70. Contact: sip:1240@10.237.236.150:56892;transport=UDP . To: sip:1200@networklab.loc;transport=UDP . From: "John Couch" sip:1240@networklab.loc;transport=UDP ;tag=270d1828. Call-ID: ZGNhMDdmOGQ1MWFhZTA2NGYwMTE1YThlM2UwNTQxYzI.. CSeq: 2 INVITE. Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE. Content-Type: application/sdp. Proxy-Authorization: Digest username="1240",realm="networklab.loc",nonce="UzRTGFM0Uezw+Q1ZC/KUq4LDqr7BFZZ/",uri= "sip:1200@networklab.loc;transport=UDP" ,response="0373158cea6615a4bca50401ace5af75",cnonce="4dfbe915fff3e822e9bc5ac7c3b526f8",nc=00000001,qop=auth,algorithm=MD5. Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri. User-Agent: Z 3.2.21357 r21367. Allow-Events: presence, kpml. Content-Length: 165. . v=0. o=Z 0 0 IN IP4 10.237.236.150. s=Z. c=IN IP4 10.237.236.150. t=0 0. m=audio 8000 RTP/AVP 0 101. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. a=sendrecv.
U 2014/03/27 12:29:32.682376 10.237.236.207:5060 -> 10.237.236.150:56892 SIP/2.0 200 OK. Via: SIP/2.0/UDP 10.237.236.150:56892;branch=z9hG4bK-d8754z-4ac013f010b101fe-1---d8754z-. To: sip:1200@networklab.loc;transport=UDP ;tag=b27e1a1d33761e85846fc98f5f3a7e58.eb89. From: "John Couch" sip:1240@networklab.loc;transport=UDP ;tag=270d1828. Call-ID: ZGNhMDdmOGQ1MWFhZTA2NGYwMTE1YThlM2UwNTQxYzI.. CSeq: 2 INVITE. Server: kamailio (4.1.2 (x86_64/linux)). Content-Length: 0. .
U 2014/03/27 12:29:35.462838 10.237.236.150:56892 -> 10.237.236.207:5060 .
----- Original Message -----
From: "Alex Balashov" abalashov@evaristesys.com To: sr-users@lists.sip-router.org Sent: Wednesday, March 26, 2014 3:24:38 PM Subject: Re: [SR-Users] kamailio db
On 03/26/2014 03:23 PM, Slava Bendersky wrote:
I'll take a look and get back to you as soon as I can. Right now, I need to catch a flight to Kamailio World. :)
Hello,
there is no loop there -- the log is incomplete, not showing what happened with the INVITE request, only with its replies -- but anyhow, the replies 180 and 486 are coming from callee, the user-agen: z ...
So all seems ok with routing of the invite, just the callee is busy, not answering the call.
Cheers, Daniel
On 28/03/14 23:36, Slava Bendersky wrote:
Hello Daniel,
Please see screen shot, https://www.dropbox.com/s/zot54rs9d13dthy/loop1.png
Slava.
----- Original Message -----
From: "Daniel-Constantin Mierla" miconda@gmail.com To: "Slava Bendersky" volga629@networklab.ca, "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Friday, March 28, 2014 6:54:20 PM Subject: Re: [SR-Users] kamailio db
Hello,
there is no loop there -- the log is incomplete, not showing what happened with the INVITE request, only with its replies -- but anyhow, the replies 180 and 486 are coming from callee, the user-agen: z ...
So all seems ok with routing of the invite, just the callee is busy, not answering the call.
Cheers, Daniel
On 28/03/14 23:36, Slava Bendersky wrote:
Hello Daniel, I was looking where is problem, and I see call is looping meaning coming back to caller. I putted couple xlog to see where is breaks.
$avp(oexten) = $rU; xlog("L_INFO", "This is $avp(oexten)"); if (!lookup("location")) { xlog("L_INFO", "This $rU and this $du");
this is log
Mar 28 18:16:46 dsm01 /usr/sbin/kamailio[1754]: INFO: <script>: This is 1240.
In main routing logic I tried use on save location 0x04 to store last registrar for external users. Also tried use MULTIDOMAIN.
Here config file http://fpaste.org/89673/60456311/
And here debug, I see 486 busy
http://fpaste.org/89676/46038139/
In mysql I see record in location table.
| 146 | uloc-5335f27e-6da-2 | 1240 | networklab.loc | sip:1200@192.168.100.1:57967;transport=UDP | NULL | NULL | 2014-03-28 19:16:46 | -1.00 | YmRiZmE0MzQ5YTU0NjkwNTFiMmM0NDFmOGQzNTljZDg. | 2 | 2014-03-28 18:16:46 | 0 | 0 | Z 3.2.21368 r21103 | udp:192.168.100.145:5060 | 5087 | NULL | 0 |
Slava.
----- Original Message -----
From: "Daniel-Constantin Mierla" miconda@gmail.com To: "Kamailio (SER) - Users Mailing List" sr-users@lists.sip-router.org Sent: Thursday, March 27, 2014 2:47:38 PM Subject: Re: [SR-Users] kamailio db
Hello,
the invite is replied with 200ok by kamailio, that should not happen. You have some wrong logic inside kamailio.cfg.
You can load debugger module and set cfgtrace parameter of it to 1, then watch the logs to see which actions from kamailio.cfg are executed for the invite.
Cheers, Daniel
On 27/03/14 17:34, Slava Bendersky wrote:
<blockquote>
Hello Alex,
After some testing I see on SDP call stack after first INVITE, .
U 2014/03/27 12:29:32.680559 10.237.236.150:56892 -> 10.237.236.207:5060 INVITE sip:1200@networklab.loc;transport=UDP SIP/2.0. Via: SIP/2.0/UDP 10.237.236.150:56892;branch=z9hG4bK-d8754z-4ac013f010b101fe-1---d8754z-. Max-Forwards: 70. Contact: sip:1240@10.237.236.150:56892;transport=UDP . To: sip:1200@networklab.loc;transport=UDP . From: "John Couch" sip:1240@networklab.loc;transport=UDP ;tag=270d1828. Call-ID: ZGNhMDdmOGQ1MWFhZTA2NGYwMTE1YThlM2UwNTQxYzI.. CSeq: 2 INVITE. Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE. Content-Type: application/sdp. Proxy-Authorization: Digest username="1240",realm="networklab.loc",nonce="UzRTGFM0Uezw+Q1ZC/KUq4LDqr7BFZZ/",uri= "sip:1200@networklab.loc;transport=UDP" ,response="0373158cea6615a4bca50401ace5af75",cnonce="4dfbe915fff3e822e9bc5ac7c3b526f8",nc=00000001,qop=auth,algorithm=MD5. Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri. User-Agent: Z 3.2.21357 r21367. Allow-Events: presence, kpml. Content-Length: 165. . v=0. o=Z 0 0 IN IP4 10.237.236.150. s=Z. c=IN IP4 10.237.236.150. t=0 0. m=audio 8000 RTP/AVP 0 101. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. a=sendrecv.
U 2014/03/27 12:29:32.682376 10.237.236.207:5060 -> 10.237.236.150:56892 SIP/2.0 200 OK. Via: SIP/2.0/UDP 10.237.236.150:56892;branch=z9hG4bK-d8754z-4ac013f010b101fe-1---d8754z-. To: sip:1200@networklab.loc;transport=UDP ;tag=b27e1a1d33761e85846fc98f5f3a7e58.eb89. From: "John Couch" sip:1240@networklab.loc;transport=UDP ;tag=270d1828. Call-ID: ZGNhMDdmOGQ1MWFhZTA2NGYwMTE1YThlM2UwNTQxYzI.. CSeq: 2 INVITE. Server: kamailio (4.1.2 (x86_64/linux)). Content-Length: 0. .
U 2014/03/27 12:29:35.462838 10.237.236.150:56892 -> 10.237.236.207:5060 .
----- Original Message -----
From: "Alex Balashov" abalashov@evaristesys.com To: sr-users@lists.sip-router.org Sent: Wednesday, March 26, 2014 3:24:38 PM Subject: Re: [SR-Users] kamailio db
On 03/26/2014 03:23 PM, Slava Bendersky wrote:
I'll take a look and get back to you as soon as I can. Right now, I need to catch a flight to Kamailio World. :)
On 03/23/2014 10:49 PM, Slava Bendersky wrote:
Is possible run kamailio without database ?
Well, sure. But its applications are considerably more limited, since, without a database, it's pretty tough to make any "dynamic" decisions.
I got ldap working and extension is registered, but can't place calls between two extensions. Getting 404 all the time.
Could that be a domain issue? (Domain is a component of location resolution.)
That said, you can certainly run Kamailio in a registrar role without database backing, using solely the in-memory 'usrloc'.
-- Alex
-
Alex Balashov -
Daniel-Constantin Mierla -
info＠vintageelectronics.ca -
Slava Bendersky