[Devel] TOS setting for SIP signalling

Hello all, The TOS value for SIP signalling is hard coded to IPTOS_LOWDELAY. It would be nice to have it configurable. I can implement this one and submitted if there is a real interest in the community for this configuration. -ovi ___ Devel mailin

Re: [Devel] opeser database scritps and strucuture - aesthetic changes

Daniel, I agree with this proposal. In addition to the review of the columns that need to be kept, I have three additional suggestions: 1. The names of the columns should be made consistent. For example: column name associated with the last_updated time of a record. 2. Additional columns sh

[Devel] A tutorial on the OSP peering module is now available

Dear Users and Developers, A tutorial on the OSP peering module is now available at http://openser.org/docs/osp/Multi-Lateral_Peering_with_OpenSER_1_0_0.pdf. The module enables secure, multi-lateral peering with SIP devices that support OSP (i.e. OpenSER 1.1.x, OpenSER 1.0.x, (Open)SER 0.9.x, A

Re: [Devel] opeser database scritps and strucuture - aesthetic changes

On Thu, 17 Nov 2005, Daniel-Constantin Mierla wrote: Hi Daniel, at a moment it was in discussion whether to change the database scripts to create only the tables needed by openser and the rest using a special parameter, something like: - opensermysql.sh create openserdb (same as "opensermysq

[Devel] CVS commitlog: sip-server/modules/rr loose.c

User: bogdan_iancu Date: 2005/11/17 08:39:49 PST OpenSER CVS - Commit Details Modified files: modules/rr loose.c Commit Log: - fixed double routing handeling for after_strict case - proper send socket set in after_strict case - proper call of rr callbacks in after_stric

[Devel] opeser database scritps and strucuture - aesthetic changes

Hello, at a moment it was in discussion whether to change the database scripts to create only the tables needed by openser and the rest using a special parameter, something like: - opensermysql.sh create openserdb (same as "opensermysql.sh create") - creates only the tables needed by openser

[Devel] Re: [Users] RE: [Serusers] Re: [Serdev] Inaccurate Radius Accounting

On 17-11-2005 10:21, Lenir wrote: > In this case the radius proxy wont work, because you never can anticipate > who hangs up the call, thus radius wont know who hung up the call...Besides > all other voice applications/hardware (SIP and H323) that use radius do not > behave like that, the Called-St

[Devel] Re: [Users] RE: [Serusers] Re: [Serdev] Inaccurate Radius Accounting

Yes, this can happen if the callee sends BYE. In this case the URIs in >From and To header fields are swapped. The only SIP RADIUS related document (which has expired a long time ago) says that Calling-Station-Id is the URI from From header field of any SIP request. Thus -- according this I-D it i

[Devel] openser architecture!

Hi all Where can i have the openser architecture? Regards! ___ Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel

[Devel] RE: [Users] RE: [Serusers] Re: [Serdev] Inaccurate Radius Accounting

In this case the radius proxy wont work, because you never can anticipate who hangs up the call, thus radius wont know who hung up the call...Besides all other voice applications/hardware (SIP and H323) that use radius do not behave like that, the Called-Station-ID ALWAYS remains the same, as with

Re: [Devel] openser scalability

Hi Bruce, indeed I have as working item a dynamic re-allocation for memory at usrloc startup. This will be available soon and it will fix your problem automatically. regards, bogdan Daniel-Constantin Mierla wrote: You can increase the shm memory using -m parameter (see 'openser -h'). For

Re: [Devel] openser scalability

You can increase the shm memory using -m parameter (see 'openser -h'). For the private memory you have to edit "config.h" and change the value of: #define PKG_MEM_POOL_SIZE 1024*1024 The recompile and reinstall. The problem is that at start up, the user location records are first loaded in pri

[Devel] REGISTER & contact maching

Hi, I would like to bring into attention an issue that was large debated previously, but postponed for after the released : contact matching in USRLOC. There are several problems with the current mechanism, problems well underlined by Dan in his original email: http://openser.org/piperma

[Devel] openser scalability

We are trying to scale to 50K users and beyond, but are running into lots of issues with the SIP server. The biggest issue is the database and database abstraction layer, which seems to want to allocate lots of memory. This problem is exacerbated by the fact that memory is not allocated dyn

[Devel] Re: [Users] RE: [Serusers] Re: [Serdev] Inaccurate Radius Accounting

Hi! I think we should leave (open)ser radius as it is. If you need adopt the accounting packets to fit your billing application, I would add a radius proxy, which translates the acounting requests according to your needs and forward it to the billing application. regards klaus Lenir wrote: