sr-users August 2006

sr-users@lists.kamailio.org

184 participants
360 discussions

[Serusers] ser-0.9.6: modules/postgres bugreport & patch

by Alexandre Snarskii

Hi! I'm running ser-0.9.6, on FreeBSD 6.1-stable, database backend is postgresql version 8.1.3. Today I got errors in logfiles, saying: messages.2.bz2:May 29 14:35:03 <XXX> /usr/local/sbin/ser[51448]: ERROR:avpops:dbrow2avp: dbrow contains NULL fields The similar problem reported in: http://lists.iptel.org/pipermail/serusers/2005-May/019681.html with much more detailed description of error, database contents and config samples. Patch is trivial, and looks more like a fix to copy'n'paste error: in mysql/val.c function str2val states: if (!_s) { memset(_v, 0, sizeof(db_val_t)); VAL_TYPE(_v) = _t; VAL_NULL(_v) = 1; return 0; } VAL_NULL(_v) = 0; and the last line mentions that 'well, that's value is not NULL'. In postgresql/db_val.c, line 182, function str2valp, the same statement is the: if (!_s) { DLOG("str2valp", "got a null value"); VAL_TYPE(_v) = _t; VAL_NULL(_v) = 1; return 0; } without explicit notification that this is not-NULL value. More than, nowhere else in this function VAL_NULL(_v) not set to 0. So, if a value _v.val contained anyting but 0 at the function start, resulting value will be threated as NULL despite the fact, that _s is NOT NULL. Patch is obvious, just add VAL_NULL(_v)=0; after cited block (line 188) and everyting will be ok. At least for me it's ok for some hours :)

16 years, 1 month

[Serusers] SER Accounting.

by Robert Zorop

Hi, all. I know this is a little bit out off Topic. I'm trying to install CDRTool for CDR normalization and billing with SER. I get the things allmost working (freeradius + MySQL + SER) But i can't get the CDRs normalized with price. Can anybody please help me or post a CDRTool global.inc working file? . Thanks a lot in advance any help will be highly apreciated!

17 years, 4 months

[Users] bug in radiusclient ng for 64b

by Stuart Clark

Hello, I have a 64bit machine running openser 1.1.0, and wish to log radius accounting details to radius using the acc module and radiusclient-ng. I am facing issues talking to a freeradius server, as described at: https://developer.berlios.de/bugs/?func=detailbug&bug_id=7442&group_id=1208 Basically, the server reports: Error: Received Accounting-Request packet from w.x.y.z with invalid signature! (Shared secret is incorrect.) I have updated to the cvs version of radiusclient-ng, but the problem still exists. It would appear that the md5 routine is not compatible with the md5 routine used by the freeradius software. Just wondering is anyone else has worked their way around this problem. Cheers, Stuart > X-Archived: http://article.gmane.org/gmane.comp.voip.openser.user/4415 > From: Daniel-Constantin Mierla <daniel@...> > Subject: FYI: bug in radiusclient ng for 64b > Newsgroups: gmane.comp.voip.openser.user, gmane.comp.voip.openser.devel > Date: 2006-05-16 01:44:16 GMT (13 weeks, 3 days and 58 minutes ago) > > On 05/16/06 02:48, Maxim Sobolev wrote: >> Hi, >> >> Reportedly there is an problem in radiusclient library with md5 hash >> calculation on 64bit platforms (amd64, sparc64, etc), which results in >> server rejecting requests even with proper secret configured on >> client. I have applied a fix, but don't have access to any 64bit >> hardware, therefore can't verify. >> >> Therefore, if anybody is having problems with radiusclient on 64bit >> arch he is more than welcome to try update to the latest version from >> cvs and let me know if it helps or not. Instructions on checking out >> sources from berlios cvs are here: >> https://developer.berlios.de/cvs/?group_id=1208. >> >> Thanks! >> >> -Maxim >

17 years, 8 months

[Users] OpenSER administrator issue

by Pat wang

Hi, Just managed to install the new openser administrator and everything just works. Thanks to Mike for this nice application. However I can't add user with openserctl anymore. The following error appears: ERROR 1054 (42S22) at line 1: Unknown column 'phplib_id' in 'field list' ERROR: introducing the new user '5702' to the database failed On the other hand, adding new users from administrator GUI does not have this problem. This happened right after installation of aministrator so I think it is related to the administrator mysql table changes. Any suggestions please? Thanks, Patrick

17 years, 8 months

[Users] get_hdr_field: bad to header...

by Lars Sundqvist

Hello, We have a few hundred users registered to a openser we are running and everything works fine, however i get som error messages in the logs I would like to get rid of... //sbin/openser[28867]: ERROR: get_hdr_field: bad to header /sbin/openser[28867]: ERROR: bad header field /sbin/openser[28867]: ERROR: get_hdr_field: bad to header /sbin/openser[28867]: ERROR: bad header field /sbin/openser[28867]: ERROR:parse_from_header: bad from header /sbin/openser[28867]: xl_get_from: ERROR cannot parse FROM header /sbin/openser[28867]: ERROR: get_hdr_field: bad to header /sbin/openser[28867]: ERROR: bad header field /sbin/openser[28867]: xl_get_to: ERROR cannot parse TO header /sbin/openser[28867]: [REGISTER] from [<null>] to [<null>] /sbin/openser[28867]: ERROR: get_hdr_field: bad to header /sbin/openser[28867]: ERROR: bad header field /sbin/openser[28867]: ERROR:maxfwd:is_maxfwd_present : parsing MAX_FORWARD header failed! /sbin/openser[28867]: ERROR:parse_from_header: bad from header /sbin/openser[28867]: insert_RR(): From parsing failed /sbin/openser[28867]: record_route(): Error while inserting Record-Route line /sbin/openser[28867]: ERROR: get_hdr_field: bad to header /sbin/openser[28867]: ERROR: bad header field /sbin/openser[28867]: find_first_route: Error while parsing headers /sbin/openser[28867]: analyzing REGISTER request /sbin/openser[28867]: ERROR: get_hdr_field: bad to header /sbin/openser[28867]: ERROR: bad header field /sbin/openser[28867]: find_credentials(): Error while parsing headers /sbin/openser[28867]: pre_auth(): Error while looking for credentials /sbin/openser[28867]: ERROR: get_hdr_field: bad to header /sbin/openser[28867]: ERROR: bad header field /sbin/openser[28867]: ERROR: get_hdr_field: bad to header /sbin/openser[28867]: ERROR: bad header field /sbin/openser[28867]: ERROR: build_res_buf_from_sip_req: alas, parse_headers failed /sbin/openser[28867]: pre_auth(): Error while sending 400 reply / Anyone has a clue what I can do to debug this to find out where the request are coming from or what can be done to stop the invalid(?) requests from being processed and clutter my logs? Thanks Lars Sundqvist

17 years, 10 months

[Users] failure route doubts

by Jose Silva

Hi, I'm having some doubts on how to use/do some things with dispatcher module and failure route. I'll try to explain my problem. On my main route block I select the destination (using ds_select_dst) to where I want to send the message, and indicate that responses should pass through the failure_route, I also add a header with some things that are needed by the next proxy. On the failure route when I get 408 Time Out I mark the previous destination and select the next destination. until here everything goes fine. After this I want to change the message that I'm going to send to next proxy, for this I need to remove the header that I inserted previously on the main route block and access the destination URI that the ds_next_dst updates. My first doubt is that when I print the destination URI it has the previous destination ( the one used in the main route block) but when it relay's the message it goes to the right destination (the one returned from ds_next_dst), Is there any reason for this ? I'm using $du to access it, is this wrong? My second doubt is, what sip message do I have access to in the failure route (the one I received or the one I sent out)? I ask this because I try to remove the header I inserted in the main route block and it does not remove anything but when I relay the message the header I tried to remove goes on the message. Thanks in advance, José Carlos Silva

18 years

[Serusers] Carrier-grade framework for SER

by Andreas Granig

Hi guys, I'd like to propose another possibility for a highly-available and scalable system design based on SER: The problems I've encountered for scalable systems are: - Distribution of the user location and alias location among the nodes (user location is based on registrations, alias location comes from web interfaces and is used for call forwarding). - Reloading up to date location tables after breakdown and recovery of a node So I'm just thinking loud about the following provisioning system: - Write a client which fulfills the this demands: - Receive one or more locations from SER via a SER module or from a web application and distribute them to other known clients. Take care of retransmissions if a client isn't reachable or reports a temporary failure. - Receive one or more locations from other clients and write them into the SER FIFO. If writing into the FIFO fails, try to write directly into the database (location-table, alias-table etc.). Report a temporary failure if this also fails. Maybe a centralized server should be used which receives the locations from the clients and distributes them to other clients, so that the nodes just know about the server and nothing about other nodes. This would make integration of new nodes easy. On the other hand, it's another single point of failure, so a decentralized solution should be considered. But that would mean that you've to inform every node about the existence of a new node. The protocol used between the nodes should be simple and fast. So I think SOAP drops out here. Maybe XMLRPC or ICE (http://www.zeroc.com/ice.html) could be used. One might think now why not just use replication on SIP layer, but t_replicate only supports one peer and you've no possibility to get locations on a node while it's down. Replication of other location tables like the alias-table is also not possible. I'd be willing to release these parts as GPL for creating an open framework for carrier-grade SER integration, so any feedback, improvements or flames are highly welcome. Cheers, Andy

18 years, 1 month

[Serusers] OT: DIDs from Europe.

by Juan

Hi Gang. The company I work for is interested in buying DIDs from Europe. Of course the connection should be SIP. If any of you is selling them, please contact me off the list. Regards Juan Ferrari VoIP & Telecom Specialist United World Telecom Phone: +1561-276 7156 ext. 302

18 years, 2 months

[Serusers] SIP client with video???

by Joao Pereira

Hello to all can someone recommend me a nice SIP client with video for windows?? I tried X-Lite 3.0 but it's a lousy piece of software..... Does someone knows about a better software? Regards Joao Pereira

18 years, 2 months

Re: [Users] more on accounting

by tele

Glenn Dalgliesh wrote: >This is from previous list > >"i Glenn, > >For this feature to work, you need to be sure that you do record_route() on >the INVITE and that "append_fromtag" RR module param is not disable. > >regards, >bogdan " > > Yes i have read that thread. i always record_route all messages before do things. if (!method=="REGISTER") record_route(); by the sample openser.cfg and for be sure i have also forced: modparam("rr","append_fromtag",1) >-----Original Message----- >From: users-bounces(a)openser.org [mailto:users-bounces@openser.org] On Behalf >Of tele >Sent: Wednesday, June 28, 2006 11:05 AM >To: users(a)openser.org >Subject: [Users] more on accounting > >Hi all, > >I'm using OpenSER v1.0.1 and i have done an accounting compatible with >my billing system. >Now i have problem with detection of flow direction for billing reason. > >i'm talking about openser 1.0.x: > >the problem is when the BYE come from callee. >i know the problem is solved in openser1.1.x with the > >modparam("acc", "detect_direction", 1) > >i have read in modules documentation of 1.0.x that i can use >is_direction() of RR module for detect call flow direction but it says >that this must be called after loose_route() > >so for the accounting i must call setflag before loose_route() but what >can i do if i want detect call flow >before of exec setflag? > >Hmmm i think that i must install OpenSER 1.1.x and test with it > >:tele > > > >_______________________________________________ >Users mailing list >Users(a)openser.org >http://openser.org/cgi-bin/mailman/listinfo/users > > >

18 years, 2 months

Jump to page:

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 August 2006