sr-users July 2011

sr-users@lists.kamailio.org

75 participants
120 discussions

Kamailio 1.5: replying a 200 (OPTIONS) with SDP
by Iñaki Baz Castillo 24 Jul '11

24 Jul '11

Hi, I've a stupid SIP PBX (Alcatel) which after registering sends a periodic OPTIONS with no RURI username and with "Accept: application/sdp". My proxy replies 200 in this case, but without SDP body (how could I know which codecs to show???) and unfortunately the Alcatel does not like it and send retransmissions of the requests (sad but true). After a while Alcatel determines that the proxy is down (pathetic but true). So I must do a hack and reply 200 with SDP from Kamailio when the request is an OPTIONS and contains "Accept: application/sdp". I don't want to forward the OPTIONS to PSTN gateways behind Kamailio for different reasons. Which would be the best way to do it? is it possible to add a spoofed body to a response replied stateless from Kamailio? Note: options_reply() in siputils module is not valid as AFAIK it does not show a SDP. Thanks a lot. -- Iñaki Baz Castillo <ibc(a)aliax.net>

2 6

Avoiding to send 603 DECLINED to un-trusted IPs - Is that possible with Kamilio?
by Bruce B 23 Jul '11

23 Jul '11

Hi everyone, Brand new to kamailio and was told that Asterisk is not able to NOT send 603 DECLINED for anonymous SIP Invites. Is it possible to set Kamilio to absorb SIP invites from all over the world and only respond to those requests whose IPs are registered as PEERS and to not respond back AT ALL to those IPs that are not registered peers? Thanks, Bruce

1 0

Siremis & Asterisk
by Roman Dmytriv 22 Jul '11

22 Jul '11

Hello, I have my Kamailio super node up and running on Debian 6.0 machine and have few questions: I'm planning to install Asterisk and Siremis on top of it. Which I should do first if it matters? Do you have any guides documentations on how to do it? I was testing Jitsi and found out that I can only use IP for registrar not FQDN. For proxy I can use FQDN no problem. What could possibly cause that? Regards Roman

2 2

dispatcher - call load distribution algorithm
by Giuseppe Carella 21 Jul '11

21 Jul '11

Hi all, I'm using kamailio like dispatcher, for INVITE requests. The client is the IMS bench as UAC, and the backend node are sip servlet container, in which is running an UAS servlet. Between the client and kamailio there is the OpenIMSCore. I was using the hash over callid like algorithm, and all was going well. Now I'm trying to use the last algorithm, based on the call load of the destination backend, and the ACK message of the same dialog is sent to another instance. I read on the documentation that there is no SIP dialog tracking depending on other modules. This is my configuration: # main request routing block route { if ( !mf_process_maxfwd_header("10") ) { sl_send_reply("483","To Many Hops"); exit; } # select from first dst group by round-robin if(!ds_select_dst("1", "10")) { sl_send_reply("500", "No destination available"); exit; } t_on_failure("RTF_DISPATCH"); if(!t_relay()) { sl_reply_error(); exit; } } # dispatcher failure routing block failure_route[RTF_DISPATCH] { if (t_is_canceled()) { exit; } # select next destination only for local timeout if (t_branch_timeout() & !t_branch_replied()) { if(ds_next_dst()) { t_on_failure("RTF_DISPATCH"); t_relay(); exit; } } } Thanks and best regards, Giuseppe

1 0

Kamailio presence server problem with PostgreSQL
by Roberto Fichera 21 Jul '11

21 Jul '11

Hi all, I've setup for testing purpose an xcap server with Kamailio v3.1.4 backed with a postgresql v8.4.8 all in 64bits versions. On that configuration, I'm getting the errors below and consequently the presence doesn't correctly reports the status. Does anyone has the same problem? Best regards, Roberto Fichera. Jul 19 10:31:52 roberto /usr/sbin/kamailio[2005]: INFO: pua_usrloc [ul_publish.c:211]: should not send ul publish Jul 19 10:31:52 roberto /usr/sbin/kamailio[2015]: ERROR: <script>: ===== xhttp: xcap-caps : <null> Jul 19 10:31:52 roberto /usr/sbin/kamailio[2017]: ERROR: <script>: ===== xhttp: resource-lists : sip:roberto@192.168.2.92 Jul 19 10:31:52 roberto /usr/sbin/kamailio[2017]: ERROR: <script>: ===== xhttp: get sip:roberto@192.168.2.92 => /xcap-root/resource-lists/users/sip:roberto@192.168.2.92/index Jul 19 10:31:52 roberto /usr/sbin/kamailio[2021]: ERROR: <script>: ===== xhttp: pres-rules : sip:roberto@192.168.2.92 Jul 19 10:31:52 roberto /usr/sbin/kamailio[2021]: ERROR: <script>: ===== xhttp: get sip:roberto@192.168.2.92 => /xcap-root/pres-rules/users/sip:roberto@192.168.2.92/presrules Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: ERROR: presence [subscribe.c:711]: Missing or unsupported event header field value Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: ERROR: presence [subscribe.c:714]: #011event= message-summary Jul 19 10:31:52 roberto /usr/sbin/kamailio[2004]: INFO: presence [notify.c:1588]: NOTIFY sip:roberto@192.168.2.92 via sip:roberto@192.168.2.92:5090;transport=udp;registering_acc=192_168_2_92 on behalf of sip:roberto@192.168.2.92 for event presence.winfo Jul 19 10:31:52 roberto /usr/sbin/kamailio[2005]: INFO: presence [notify.c:1588]: NOTIFY sip:roberto@192.168.2.92 via sip:roberto@192.168.2.92:5090;transport=udp;registering_acc=192_168_2_92 on behalf of sip:mattia@192.168.2.92 for event presence *Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: ERROR: db_postgres [km_dbase.c:427]: invalid query, execution aborted Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: ERROR: db_postgres [km_dbase.c:428]: driver error: PGRES_FATAL_ERROR, ERROR: null value in column "sender" violates not-null constraint#012* *Jul 19 10:31:52 roberto /usr/sbin/kamailio[1999]: WARNING: db_postgres [km_dbase.c:473]: unexpected result returned*

5 17

xcap server - http load–balancer: xcap authentication problem
by laura testi 21 Jul '11

21 Jul '11

Hello all, I’m using two Kamailio Presence Servers that are also XCAP Servers for the presence and resources management and the Kamailio Dispatcher in order to balance the SIP requestes coming from SIP Client. Then I’m trying to configure a HTTP load–balancer for the xcap/http traffic. I’m testing both Apache and INginx HTTP proxy but I’m facing with a problem related with the Xcap authentication: when a client sends the first xcap request to the http load-balancer, it forwards the request to one of the configured Xcap Server that replies with the 401 response in order to let the client authenticates. So, the client sends the second request with the Digest authentication to the http load-balancer. But, sometimes, the http load-balancer forwards the authenticate request to the second Xcap Server that is not able to authenticate the request. Then the client receive the “Unauthorized” response… Could you please give us some hints about this problem? Thanks in advance, laura

4 11

dns_srv_lb
by Jon Bonilla 21 Jul '11

21 Jul '11

Hi all I'm running a kamailio 3.1 based proxy which actually relays REGISTER requests to a domain "example.com" I've setup a DNS SRV record for that domain which returns two hosts with same prio and weight. I want kamailio to balance the requests to both servers 50%. Taking a look to ./doc/dns.txt I've setup these configuration options: dns_try_ipv6=no dns_retr_time=1 dns_retr_no=1 dns_use_search_list=no use_dns_cache=on use_dns_failover=on dns_srv_lb=on If I understood right the last setting would have to make kamailio work as I described, balancing the requests between both servers. But my logs say that kamailio is actually using only one of the ip addresses (host2.example.com) to send the REGISTER requests. Here's the output of sercmd dns.view: sercmd> dns.view { name: _sip._udp.example.com type: SRV size (bytes): 232 reference counter: 1 permanent: no expires in (s): 31364 last used (s): 446 negative entry: no rr name: host1.example.com rr port: 5060 rr priority: 0 rr weight: 0 rr expires in (s): 31364 rr name: host2.example.com rr port: 5060 rr priority: 0 rr weight: 0 rr expires in (s): 31364 } { name: host2.example.com type: A size (bytes): 128 reference counter: 1 permanent: no expires in (s): 592964 last used (s): 446 negative entry: no rr ip: 192.168.0.103 rr expires in (s): 592964 } { name: host1.example.com type: A size (bytes): 128 reference counter: 1 permanent: no expires in (s): 592964 last used (s): 11835 negative entry: no rr ip: 192.168.0.102 rr expires in (s): 592964 } Any suggestions? What am I doing wrong? Thanks, Jon

2 2

Call is terminated in callee side after 36s @Kamailio 3.1 @debian sqeeze64
by Coca 21 Jul '11

21 Jul '11

Hi List, I have a Kamailio3.1 server and RTPProxy running in WAN. The calls between UA will automatically terminated in Callee UA side 36s after connected, while no one sends a BYE. While Kamailio and UA are in LAN at all , everything is just working well. Is it my rtpproxy doesn't working correctly or something else is wrong? What can I do to fix it. Any hint?? BTW, Kamailio is installed following official guide http://www.kamailio.org/dokuwiki/doku.php/install:kamailio-3.1.x-from-git The kamailio.cfg wasn't changed at all except for below: ----------------------------------------------------------------------------------------- 1) adding the following lines: #!define WITH_MYSQL #!define WITH_AUTH #!define WITH_USRLOCDB #!define WITH_NAT 2)uncommenting the line below in route[REGISTRAR], setbflag(FLB_NATSIPPING); 3)change rtpproxy port corresponding modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:22222") ----------------------------------------------------------------------------------------- and my rtpproxy1.2.1 was installed by apt-get install rtpproxy, with 1) /etc/default/rtpproxy changed into: # Defaults for rtpproxy # The control socket. #CONTROL_SOCK="unix:/var/run/rtpproxy/rtpproxy.sock" # To listen on an UDP socket, uncomment this line: CONTROL_SOCK=udp:127.0.0.1:22222 LISTEN_ADDR=xx.xx.xx.xx # Additional options that are passed to the daemon. EXTRA_OPTS="-l ${LISTEN_ADDR}" 2) and started by rtpproxy -l xx.xx.xx.xx -s udp:localhost:22222 -u kamailio Your help will be great appreciated. Coca

1 0

Kamailio: 500 Server error occurred (19/SL).
by Max Doronin 21 Jul '11

21 Jul '11

Hello guys, I have strange behavior on my Kamailio-1.5.1-notls instance. I have LCR and TM modules enabled.For a particular destination I have 4 routes to try. When I call to non-existing number, it tries - route 1 (404 Not Found) - route 2 (404 Not Found) - route 3 (503 Service unavailable) And the problem is with the last 503. Kamailio ACKs it, immediately drops these 2 lines into syslog Jul 13 04:14:47 /usr/local/sbin/kamailio[23572]: ERROR:tm:t_forward_nonack: no branch for forwarding Jul 13 04:14:47 /usr/local/sbin/kamailio[23572]: ERROR:tm:w_t_relay: t_forward_nonack failed And sends SIP/2.0 500 Server error occurred (19/SL). To the call originator. 30 microseconds later it sends SIP/2.0 500 Service Unavailable. to the originator again Latter 500 looks like the relayed original "503 Service unavailable". I think so because the Reason header is the same: Reason: SIP;cause=503;text="Service Unavailable";icodetext="NoCircuitAvailable";iintcode=10034;isubsystem=3. Obviously call is terminated. I noticed that that last peer rewrites my Via headers like this: Original: == Via: SIP/2.0/UDP 187.45.214.132;branch=z9hG4bK3dac.fae9b793.2. Via: SIP/2.0/UDP 192.168.2.33:5622;received=49.49.59.23;branch=z9hG4bK-d8754z-a6ba40014f97fb7c-1---d8754z-;rport=23832. == Rewritten == Via: SIP/2.0/UDP 187.45.214.132;received=187.45.214.132;branch=z9hG4bK3dac.fae9b793.2,SIP/2.0/UDP 192.168.2.33:5622;received=49.49.59.23;branch=z9hG4b == I tried to modify via1_matching parameter (1 -> 0) but no changes. My questions are: - What can be the reason of that 500 with 19/SL - Can kamailio properly handle this 1 line Via header? - What can be the reason of that "t_forward_nonack: no branch for forwarding"? Regards, Max

2 4

(no subject)
by Eliezer Croitoru 20 Jul '11

20 Jul '11

1 0

← Newer
1
2
3
4
5
6
7
8
9
...
12
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users July 2011