sr-users

sr-users@lists.kamailio.org

9 participants
37568 discussions

[Kamailio-Users] "Permanent" AVP
by Antonio Reale 26 Jan '10

26 Jan '10

Hi all, I'd like to simulate in kamailio 1.4.4, the loading of a global setting (like a parameter that is loaded only at startup), using AVPs. So, I want to load some AVP only at proxy startup. Probably it is not possible because, if I'm not wrong, AVPs are transaction persistent. The problem is that I don't need to load those AVPs for every transaction. There is a why to implement such configuration? Thanks. Best regards. -- Antonio

3 5

[Kamailio-Users] 477 Send failed
by vragukumar＠signalogic.com 25 Jan '10

25 Jan '10

Hello, I have setup Kamailio and rtpproxy on a server, that acts as a SIP Proxy. An asterisk server sits behind this proxy server. I have noticed that on some occasions when the softphone(x-lite) tries to register with the asterisk through the proxy,it receives a 477 send failed. If i restart Kamailio, the problem seems to disappear. I have attached a logfile showing Kamailio's error output. What could be the reason for such behavior ? Thanks and Regards, Vikram.

3 2

[Serusers] how to compile the docs?
by Chump Chumpster 25 Jan '10

25 Jan '10

Hi, I'm sure this is a simple question and hopefully a simple answer. I've downloaded and am experimenting with SER 2.0.x. I can't find any instructions on how to compile the docs included with the source, into a usable format. They're pretty difficult to use as XML without a stylesheet :-) I appreciate any advice to get me going in the right direction....

1 0

[Kamailio-Users] Fwd: TLS Multiple records not read
by Jijo Jose 25 Jan '10

25 Jan '10

Thanks for the response. The SIP server is reading only the first record(first sip message), the _tls_read() function's log shows the length of first sip message which is matching with length of first record in wireshark.. This means SSL_read returns only the first record. I did the test using TCP which is working fine as it is reading two sip messages on a single read. Please find the log and attached print screen of wireshark traces. Jan 22 20:41:37 REGS-1a0240 openser[936]: io_wait_loop_sigio_rt: siginfo: signal=35 (35), si_code=1, si_band=0x41, si_fd=37 Jan 22 20:41:37 REGS-1a0240 openser[936]: TCPCONN: handle_io: fd map 0x1011d73c (37): {37, 2, 0x30294da0} Jan 22 20:41:37 REGS-1a0240 openser[936]: tls_update_fd: New fd is 37 Jan 22 20:41:37 REGS-1a0240 openser[936]: _tls_read: 559 bytes read Jan 22 20:41:37 REGS-1a0240 openser[936]: read= 559 bytes, parsed=559, state=4, error=1 Jan 22 20:41:37 REGS-1a0240 openser[936]: tcp_read_req: last char=0x0A, parsed msg= BYE sip:551138175007@21.21.81.11:6061;transport=tls SIP/2.0^M To: SIP5007_TLS_SIMPLEX <sip:551138175007@41.41.0.230<sip%3A551138175007(a)41.41.0.230>>;tag=91c2c894c0^M From: <sip:551138175008@41.41.0.230:5061;transport=tls>;tag=snl_G84KdX4MLT^M Call-ID: 0ad3e453326a4160^M CSeq: 1 BYE^M Route: <sip:21.21.27.10:5061;transport=tls;ftag=91c2c894c0;lr=on>^M Via: SIP/2.0/TLS 41.41.0.230:5061;branch=z9hG4bK_brancha_41.41.0.230_KonTU5DMPx^M Accept-Language: en;q=0.0^M Allow: REGISTER, INVITE, ACK, BYE, CANCEL, NOTIFY, REFER^M Date: Fri, 22 Jan 2010 20:41:36 GMT ^M Max-Forwards: 69^M Content-Length: 0^M ^M Jan 22 20:41:37 REGS-1a0240 openser[936]: tcp_read_req: end of header part Jan 22 20:41:37 REGS-1a0240 openser[936]: - received from: port 5061 Jan 22 20:41:37 REGS-1a0240 openser[936]: - received from: ip 41.41.0.230 Jan 22 20:41:37 REGS-1a0240 openser[936]: tcp_read_req: headers: BYE sip:551138175007@21.21.81.11:6061;transport=tls SIP/2.0^M To: SIP5007_TLS_SIMPLEX <sip:551138175007@41.41.0.230<sip%3A551138175007(a)41.41.0.230>>;tag=91c2c894c0^M From: <sip:551138175008@41.41.0.230:5061;transport=tls>;tag=snl_G84KdX4MLT^M Call-ID: 0ad3e453326a4160^M CSeq: 1 BYE^M Route: <sip:21.21.27.10:5061;transport=tls;ftag=91c2c894c0;lr=on>^M Via: SIP/2.0/TLS 41.41.0.230:5061;branch=z9hG4bK_brancha_41.41.0.230_KonTU5DMPx^M Accept-Language: en;q=0.0^M Allow: REGISTER, INVITE, ACK, BYE, CANCEL, NOTIFY, REFER^M Date: Fri, 22 Jan 2010 20:41:36 GMT ^M Max-Forwards: 69^M Content-Length: 0^M ^M . Jan 22 20:41:37 REGS-1a0240 openser[936]: tcp_read_req: content-length= 0 Jan 22 20:41:37 REGS-1a0240 openser[936]: tcp_read_req: body: Jan 22 20:41:37 REGS-1a0240 openser[936]: calling receive_msg(0x30294e14, 559, ) Jan 22 20:41:37 REGS-1a0240 openser[936]: SIP Request: Jan 22 20:41:37 REGS-1a0240 openser[936]: method: <BYE> Jan 22 20:41:37 REGS-1a0240 openser[936]: uri: <sip:551138175007@21.21.81.11:6061;transport=tls> Jan 22 20:41:37 REGS-1a0240 openser[936]: version: <SIP/2.0> Thanks Jijo On Sun, Jan 24, 2010 at 5:53 AM, Klaus Darilion < klaus.mailinglists(a)pernau.at> wrote: > I would verify if the received fragment really contains 2 complete SIP > messages (e.g. 2xCRLF at the end of the SIP headers and if Content-Length > header is correct). > > For debugging, TLS is PITA. > > Maybe the SIP server shows the same behavior when using TCP. Otherwise you > can try to configure the NULL:CIPHER on both servers - then you see the > plaintext SIP message in the TLS packets. > > regards > klaus > > Jijo Jose wrote: > >> Hi All, >> We have a SIP server which enabled NAGLE algorithm and proxy as openser >> ver 1.1 >> SIP Server send a TLS multiple records( 2 SIP messages) in a packet to >> openser. Openser is reading only the first record( first SIP message). The >> second TLS record(sip message) is read only when the next message recieved >> by openser from the SIP Server. >> I would like to know anybody observed this issue. I have compared the >> codebase of kamailio 1.4 and openser 1.1 but didin't find any diffrence for >> TLS. >> I have looked at the API _tls_read() in openser which is same as that of >> kamilio. >> Don't we need to use SSL_pending() after SSL_read() to verify any buffer >> is left in the SSL layer ? >> Do you think is it due to the poll method error? The poll method we use >> is POLL_SIGIO_RT >> Please let me know your comments. >> Thanks in advance. >> Jijo >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Kamailio (OpenSER) - Users mailing list >> Users(a)lists.kamailio.org >> http://lists.kamailio.org/cgi-bin/mailman/listinfo/users >> http://lists.openser-project.org/cgi-bin/mailman/listinfo/users >> > >

2 4

[Kamailio-Users] load drouting
by Denis Putyato 25 Jan '10

25 Jan '10

Hello everybody! Such error happens when I try start kamailio Jan 25 10:52:57 ubuntutest kamailio: ERROR: <core> [sr_module.c:390]: ERROR: load_module: could not open module </usr/local/lib/kamailio/modules_k/drouting.so>: /usr/local/lib/kamailio/modules_k/drouting.so: undefined symbol: db_bind_mod Jan 25 10:52:57 ubuntutest kamailio: : <core> [cfg.y:3326]: parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 42, column 12-24: failed to load module ls /usr/local/lib/kamailio/modules_k/ acc.so db_text.so group.so nathelper.so pv.so sl.so uac_redirect.so alias_db.so dialog.so htable.so nat_traversal.so qos.so sms.so uac.so auth_db.so dispatcher.so imc.so path.so ratelimit.so speeddial.so uri_db.so auth_diameter.so diversion.so kex.so pdt.so registrar.so sqlops.so userblacklist.so auth.so domainpolicy.so maxfwd.so permissions.so rr.so sst.so usrloc.so benchmark.so domain.so mi_datagram.so pike.so rtimer.so statistics.so xlog.so call_control.so drouting.so mi_fifo.so presence_mwi.so siptrace.so textops.so cfgutils.so exec.so msilo.so pua_mi.so siputils.so tmx.so In config file: loadpath "/usr/local/lib/kamailio/modules:/usr/local/lib/kamailio/modules_k" loadmodule "db_mysql.so" loadmodule "mi_fifo.so" loadmodule "sl.so" loadmodule "tm.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "textops.so" loadmodule "siputils.so" loadmodule "xlog.so" loadmodule "acc.so" loadmodule "avpops.so" loadmodule "siptrace.so" loadmodule "dialplan.so" loadmodule "lcr.so" loadmodule "sqlops.so" loadmodule "carrierroute.so" loadmodule "drouting.so" Kamailio ver 3.0 was installed from GIT. Thank you for any help

2 4

[Kamailio-Users] Outgoing registrations
by Andrey Utkin 25 Jan '10

25 Jan '10

How do you make outgoing registrations to sip providers' accounts? I haven't found Kamailio functionality like this, so looks this requires some b2bua usage? Is there some other way?

3 6

[Kamailio-Users] Option ac_extra_hdrs to tm in K 3.0.x
by Alex Balashov 25 Jan '10

25 Jan '10

What exactly is the appropriate syntax for the value of the ac_extra_hdrs option in K3's 'tm'? As described here, it is not very clear: http://www.kamailio.org/docs/modules/3.0.x/modules/tm.html#ac_extra_hdrs modparam("tm", "ac_extra_hdrs", "myfavoriteheaders-") What does this mean? Where do I put the header name, and what is the delimeter? Is it a semicolon or colon-separated list? What if, for example, I want to pass X-Alex-Status and X-Alex-Cause in CANCELs and negative ACKs from the original INVITE? Do I use ... modparam("tm", "ac_extra_hdrs", "X-Alex_Status;X-Alex-Cause") If so, what is the significance of the '-' in the above example? Thanks! -- Alex Balashov - Principal Evariste Systems LLC Tel : +1 678-954-0670 Direct : +1 678-954-0671 Web : http://www.evaristesys.com/

2 3

[Kamailio-Users] ACC on Failure route
by alex pappas 25 Jan '10

25 Jan '10

Dear Friends, In case of a call failure I'm trying from failure route to send the call through other gateways with Dispatcher module. I would like to have ACC for all failures that a call can possibly pass. If the call fails in the 3 first gateways I want them also in my mysql ACC table. I tried that with AVPs in the syslog and it works fine BUT is there any way that I can simply setflag(1) for accounting and I can have ACC for every try? I tryied to add in failure route : setflag(1); # do accounting ... setflag(3); # ... even if the transaction fails but I'm getting ACC only the last try. Thanks Alex

3 11

[Kamailio-Users] TLS Multiple records not read
by Jijo Jose 24 Jan '10

24 Jan '10

Hi All, We have a SIP server which enabled NAGLE algorithm and proxy as openser ver 1.1 SIP Server send a TLS multiple records( 2 SIP messages) in a packet to openser. Openser is reading only the first record( first SIP message). The second TLS record(sip message) is read only when the next message recieved by openser from the SIP Server. I would like to know anybody observed this issue. I have compared the codebase of kamailio 1.4 and openser 1.1 but didin't find any diffrence for TLS. I have looked at the API _tls_read() in openser which is same as that of kamilio. Don't we need to use SSL_pending() after SSL_read() to verify any buffer is left in the SSL layer ? Do you think is it due to the poll method error? The poll method we use is POLL_SIGIO_RT Please let me know your comments. Thanks in advance. Jijo

2 1

[Kamailio-Users] state field on dialog table
by Panagiotis Skoulikaritis 23 Jan '10

23 Jan '10

Hello I have a question about the state field on the dialog table. I guess it is more sip protocol oriented than kamailio deployment, I assume that the values (1-5) that are logged are the state of the dialog correct ? and if the above are correct the dialog states are the following ? 1. waiting for UAC deciscion 2. Initiate dialog 3. Establish dialog 4. Stop Media 5. Destroy dialog I apologize for my sip ignorance Trying to build up my knowledge. :) I' m asking this because I' m trying to export statistics about the calls that are handled from the kamailio and the state of the call for specific users,IP's, destinations. Thanks Panagiotis

4 5

Jump to page:

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