sr-users

sr-users@lists.kamailio.org

18 participants
37468 discussions

[Kamailio-Users] OpenBSD port updated to version 1.5.1
by Don Jackson 27 May '09

27 May '09

Hello, I have updated the OpenBSD port of Kamailio to support the 1.5.1 release. The port is available at: http://kamailio.org/pub/kamailio/1.5.1/packages/openbsd/ The posting to the OpenBSD ports mailing list is here: http://archives.neohapsis.com/archives/openbsd/2009-05/1702.html Thanks again to Henning Westerholt for putting this up on the kamailio site. Best regards, Don

2 1

[Kamailio-Users] Can't get allow_trusted to work
by Saúl Ibarra 26 May '09

26 May '09

Hi all, I'm a little stuck here :-/ I can't get allow_trusted function from the premissions module to word. I'm receiving the following error: May 26 18:36:24 [18825] DBG:core:parse_msg: method: <PUBLISH> May 26 18:36:24 [18825] DBG:core:parse_msg: uri: <sip:saghul@10.69.69.1:5070> May 26 18:36:24 [18825] DBG:core:parse_msg: version: <SIP/2.0> May 26 18:36:24 [18825] DBG:core:parse_headers: flags=2 May 26 18:36:24 [18825] DBG:core:parse_via_param: found param type 232, <branch> = <z9hG4bK1f7d.e63e45e5.0>; state=16 May 26 18:36:24 [18825] DBG:core:parse_via: end of header reached, state=5 May 26 18:36:24 [18825] DBG:core:parse_headers: via found, flags=2 May 26 18:36:24 [18825] DBG:core:parse_headers: this is the first via May 26 18:36:24 [18825] DBG:core:receive_msg: After parse_msg... May 26 18:36:24 [18825] DBG:core:receive_msg: preparing to run routing scripts... May 26 18:36:24 [18825] DBG:core:parse_headers: flags=100 May 26 18:36:24 [18825] DBG:core:parse_via_param: found param type 234, <received> = <10.69.69.2>; state=6 May 26 18:36:24 [18825] DBG:core:parse_via_param: found param type 235, <rport> = <5060>; state=6 May 26 18:36:24 [18825] DBG:core:parse_via_param: found param type 232, <branch> = <z9hG4bKqtsklyyn>; state=16 May 26 18:36:24 [18825] DBG:core:parse_via: end of header reached, state=5 May 26 18:36:24 [18825] DBG:core:parse_headers: via found, flags=100 May 26 18:36:24 [18825] DBG:core:parse_headers: parse_headers: this is the second via May 26 18:36:24 [18825] DBG:maxfwd:is_maxfwd_present: value = 69 May 26 18:36:24 [18825] ERROR:permissions:allow_trusted_2: unknown protocol udp Configuration is realli simple: modparam("permissions", "db_url", "mysql://...") modparam("permissions", "db_mode", 1) modparam("permissions", "trusted_table", "trusted") if (!allow_trusted("$si", "$proto")) { xlog("L_INFO","\n\n--NOT trusted! - $si - $proto"); sl_send_reply("403", "Forbidden"); exit; } The trusted table seems OK: mysql> select * from trusted; +----+------------+-------+--------------+------+ | id | src_ip | proto | from_pattern | tag | +----+------------+-------+--------------+------+ | 1 | 10.69.69.1 | any | NULL | NULL | +----+------------+-------+--------------+------+ What am I doing wrong? Thanks in advance!! Regards, -- Saúl -- "Nunca subestimes el ancho de banda de un camión lleno de disketes." ---------------------------------------------------------------- http://www.saghul.net/

5 9

[Kamailio-Users] Mediaproxy relay error: 'module' object has no attribute 'Interface'
by jh＠tutpro.com 26 May '09

26 May '09

CSB writes: > When attempting to start the MediaProxy relay I get the following: > > May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: Starting MediaProxy > Relay 2.3.4 > > May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: fatal error: failed to > create MediaProxy Relay: 'module' object has no attribute 'Interface' i just tried with 2.3.4 (from debian packages) and it worked without problems. in config.ini try if using ip addresses instead of domain names would help. -- juha

2 2

[Kamailio-Users] Mediaproxy relay error: 'module' object has no attribute 'Interface'
by CSB 26 May '09

26 May '09

When attempting to start the MediaProxy relay I get the following: May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: Starting MediaProxy Relay 2.3.4 May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: fatal error: failed to create MediaProxy Relay: 'module' object has no attribute 'Interface' May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: Traceback (most recent call last): May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: --- <exception caught here> --- May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: File "./media-relay", line 55, in ? May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: from mediaproxy.relay import MediaRelay May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: File "/usr/lib/python2.4/site-packages/mediaproxy/relay.py", line 30, in ? May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: from twisted.names import dns May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: File "/usr/lib/python2.4/site-packages/twisted/names/dns.py", line 116, in ? May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: class IRecord(components.Interface): May 26 16:45:00 ip-10-250-54-212 media-relay[18032]: exceptions.AttributeError: 'module' object has no attribute 'Interface' rpm -q python-twisted-core python-twisted-core-2.5.0-4.el5 rpm -q python-twisted-names python-twisted-names-0.3.0-3.el5 rpm -q python-twisted-web2 python-twisted-web2-8.1.0-1.el5.rf Any assistance appreciated. Cameron

2 1

[Serusers] Nathelper doesn't support multipart MIME even though allowed by RFC 3261?
by Frank Durda IV 26 May '09

26 May '09

I have someone who is trying to send me SIP-T messages through a SER system that acts as a PSTN gateway. The destination PSTN switch can accept either SIP or SIP-T as can the originator of the INVITE. The SIP-T message appears to pass through SER in both directions with the SIP-T data apparently intact. However, there are problems with the SDP payload. The functions in modules/nathelper that locate the SDP payload (mainly in check_content_type() in nhelpr_funcs.c) appear to be coded to never work properly with multi-part MIME in the message headers, nor deal with section boundary markers in the message body. So when the headers contain a: Content-Type: multipart/mixed;boundary=tekBoundary instead of the expected*: Content-Type: application/sdp nathelper gets confused and says things like: May 22 21:25:56 ser1 ser[24905]: ERROR:check_content_type: invalid type for a message May 22 21:25:56 ser1 ser[24905]: ERROR: extract_body: content type mismatching May 22 21:25:56 ser1 ser[24905]: ERROR: force_rtp_proxy: can't extract body from the message * (nhelpr_funcs.c also tests for Content-Types beginning with "icat", "ion" and "appl" in addition to sdp but doesn't know how to deal with any others, including a "multipart/mixed" and the resulting nested message body. Subsequently, calls to the various force_rtp_proxy() and related functions when processing the INVITE, 183 Session Progress or 200 OK replies do not substitute in the new IP address provided by rtpproxy (because it can't find the start of the body or a known body type), and so the party receiving this message will get the uncorrected IP address and audio for the call fails due to an unreachable IP address. This limitation is noted in ser-2.0.0-rc1. Has anybody done any development to make check_content_type() and the related functions in nhelpr_funcs.c capable of dealing with multi-part MIME sections? Ideally, SER should allow the entire message body even with more than one section to pass without comment or complaint. Meanwhile, nathelper should be able to find the sdp section and allow parsing and editing of it as would have been done if the body contained only one section. In reading RFC 3261, it appears that multi-part MIME is allowed and so it appears that nathelper is violating the RFC by not coping with this. Here is the passage on this subject that caught my attention: 7.4.1 Message Body Type (RFC 3261) The Internet media type of the message body MUST be given by the Content-Type header field. If the body has undergone any encoding such as compression, then this MUST be indicated by the Content- Encoding header field; otherwise, Content-Encoding MUST be omitted. If applicable, the character set of the message body is indicated as part of the Content-Type header-field value. The "multipart" MIME type defined in RFC 2046 [11] MAY be used within the body of the message. Implementations that send requests containing multipart message bodies MUST send a session description as a non-multipart message body if the remote implementation requests this through an Accept header field that does not contain multipart. SIP messages MAY contain binary bodies or body parts. When no explicit charset parameter is provided by the sender, media subtypes of the "text" type are defined to have a default charset value of "UTF-8". Thanks in advance to any pointers to newer nathelper code that deals with this RFC-permitted message body format. Here is an example of the INVITE message that caused the problem: INVITE sip:9712345678@230.123.45.67:5060 SIP/2.0 Via: SIP/2.0/UDP 225.67.89.1:5060;branch=z9hG4bKfi0cjdk0qb8sv24f18ki1ddao4 To: <sip:9712345678@230.123.45.67:5060> From: <sip:8005551212@225.67.89.1>;tag=11775339 Call-ID: 1241812549-66096587@SIP CSeq: 1 INVITE Max-Forwards: 69 Contact: <sip:8005551212@225.67.89.1:5060;transport=udp> Supported: 100rel Expires: 330 Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, PRACK, REFER, SUBSCRIBE, NOTIFY, UPDATE, REGISTER P-Asserted-Identity: <sip:8005551212@8.4.99.59> MIME-Version: 1.0 Content-Type: multipart/mixed;boundary=tekBoundary Content-Length: 426 --tekBoundary Content-Type: application/sdp v=0 o=- 321533952 1243026447 IN IP4 225.67.89.1 s=- c=IN IP4 225.67.89.1 t=0 0 a=sendrecv m=audio 49168 RTP/AVP 18 101 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=yes a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 --tekBoundary Content-Type: application/isup; base=ansi92; version=ansi ..x ..x...x..x.Pxx ....x@xp.xx..xx.. --tekBoundary--

1 0

[Kamailio-Users] Error with table version
by Raúl Alexis Betancor Santana 25 May '09

25 May '09

This is and old issue that I still have around here ... -Kamailio 1.5.1 (svn) -PostgreSQL database -Database created with "kamdbctl create", so just clean - in kamailio.cfg: [...] loadmodule "uri_db.so" modparam("uri_db", "db_url", "postgres://openser:XXXXX@localhost:5435/voip3") modparam("uri_db", "db_table", "uri") modparam("uri_db", "user_column", "username") modparam("uri_db", "domain_column", "domain") modparam("uri_db", "uriuser_column", "uri_user") modparam("uri_db", "use_uri_table", 0) modparam("uri_db", "use_domain", 0) [...] May 24 10:22:27 [23631] INFO:core:init_mod: initializing module auth_db May 24 10:22:27 [23631] INFO:core:init_mod: initializing module uri_db May 24 10:22:27 [23631] ERROR:uri_db:mod_init: Invalid table version of the subscriber table May 24 10:22:27 [23631] ERROR:core:init_mod: failed to initialize module uri_db May 24 10:22:27 [23631] ERROR:core:main: error while initializing modules And I don't undestand why ... because subscriber table it's on version 6, that is what uri_db checks ... [uri_db_mod.c] /* Check table version */ ver = uridb_db_ver(&db_url, &db_table); if (ver < 0) { LM_ERR("Error while querying table version\n"); return -1; } else { if (use_uri_table) { if (ver != URI_TABLE_VERSION) { LM_ERR("Invalid table version of the uri table\n"); return -1; } } else { if (ver != SUBSCRIBER_TABLE_VERSION) { LM_ERR("Invalid table version of the subscriber table\n"); return -1; } } } [uri_db_mod.c] and SUBSCRIBER_TABLE_VERSION has value 6 is there something I'm doing wrong?, last time I compile myself this I was forced to comment that block of code on the uri_db sources. -- Raúl Alexis Betancor Santana Dimensión Virtual

3 4

[Kamailio-Users] Auth problems with 1.5.1
by Raúl Alexis Betancor Santana 25 May '09

25 May '09

Hi all, I'm getting a lot of problems to migrate to 1.5.1, the last one is with auth. I'm using postgresql as DB and auth_db with the next params: [...] loadmodule "auth.so" modparam("auth", "nonce_expire", 300) modparam("auth", "realm_prefix", "sip.") modparam("auth", "rpid_suffix", ";party=calling;id-type=subscriber;screen=yes") modparam("auth", "rpid_avp", "$avp(s:rpid)") loadmodule "auth_db.so" modparam("auth_db", "db_url", "postgres://openser:XXXX@localhost:5435/voip3") modparam("auth_db", "user_column", "username") modparam("auth_db", "domain_column", "domain") modparam("auth_db", "password_column", "password") modparam("auth_db", "password_column_2", "ha1b") modparam("auth_db", "calculate_ha1", 0) modparam("auth_db", "use_domain", 1) modparam("auth_db", "load_credentials", "$avp(s:caller_uuid)=uuid") [...] With openser 1.3.2 and this: [...] if(!www_authorize("", "subscriber")) { xlog("L_INFO", "Register authentication failed BI $T_branch_idx - M=$rm RURI=$ru F=$fu T=$tu IP=$si I D=$ci\n"); www_challenge("", "0"); exit; } [...] All is working ok .. but with kamailio 1.5.1 it doesn't run, It allway return 401 Authentication needed ... I don't found anything in the docs about any change on auth modules ... what could be happen ? Best regards -- Raúl Alexis Betancor Santana Dimensión Virtual

2 1

[Kamailio-Users] Error runing svn version
by Raúl Alexis Betancor Santana 24 May '09

24 May '09

I'm geting this error when trying to run kamailio svn trunk version ... May 23 22:27:30 [17510] INFO:core:init_mod: initializing module usrloc May 23 22:27:30 [17510] INFO:usrloc:ul_init_locks: locks array size 512 May 23 22:27:30 [17510] ERROR:core:db_check_api: module db_postges does not export db_use_table function May 23 22:27:30 [17510] ERROR:usrloc:mod_init: failed to bind database module May 23 22:27:30 [17510] ERROR:core:init_mod: failed to initialize module usrloc May 23 22:27:30 [17510] ERROR:core:main: error while initializing modules ... Any clue? -- Raúl Alexis Betancor Santana Dimensión Virtual

2 6

Re: [Kamailio-Users] Error runing svn version
by Daniel-Constantin Mierla 24 May '09

24 May '09

On 05/24/2009 10:50 AM, Raúl Alexis Betancor Santana wrote: > On Sunday 24 May 2009 08:38:42 you wrote: > >> Hello, >> >> On 05/24/2009 12:30 AM, Raúl Alexis Betancor Santana wrote: >> >>> I'm geting this error when trying to run kamailio svn trunk version >>> >>> ... >>> May 23 22:27:30 [17510] INFO:core:init_mod: initializing module usrloc >>> May 23 22:27:30 [17510] INFO:usrloc:ul_init_locks: locks array size 512 >>> May 23 22:27:30 [17510] ERROR:core:db_check_api: module db_postges >>> >> looks like there is a typo in the db_postgres name (you miss r or?!?). >> >> If you want to play with development version, then you should take the >> sources from GIT http://sip-router.org. It is the place where the >> development is done now. >> > > Umm, I want to use kamailio not sip-router by now, maybe I sould get .tar.gz > version of 1.5.1 instead of the svn > I thought you have Kamailio development version from svn trunk. If you have 1.5.x, use the SVN branch 1.5, it is recommended. There are some fixes since 1.5.1. Was the error the typo I the db_postgres module name? Cheers, Daniel -- Daniel-Constantin Mierla http://www.asipto.com/

1 0

[Serusers] Memory allocation
by Jose Silva 22 May '09

22 May '09

Hi, I was trying to understand how SER manages its memory. From what I searched and read on the mailing list and SER documentation it seams to me that SER allocates all the necessary memory at start time and never allocates anymore memory. If the initial memory defined (PKG,SHM) is full no more will be allocated. Is this the correct Interpretation? Kind Regards, José Carlos Silva

1 0

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