[SR-Users] Using Kamailio to convert TCP to TLS

Hello, I would like to use Kamailio as a TCP <=> TLS convertor ? Do you think it's possible ? I have developed a software (which simulate a SIP phone) which can use UDP or TCP (not TLS). I need a SIP proxy to convert TCP to TLS. For example: UA => TCP OPTION (5060) => Kamailio => TLS OPTION (506

[SR-Users] Open source HLR (Home Location Register).

I know this is the mailing list for Kamailio, but hopefully someone can help me out as it is "kinda" related to VoIP etc. Does anyone know any open source / free HLR implementation? ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing l

Re: [SR-Users] pua_xmpp questions

Hi Laura, thanks, I will apply the patches soon. Cheers, Daniel On 8/10/11 12:32 PM, laura testi wrote: Hi Daniel, please find the attached diff files and the files patched. Best Regards, Laura On Tue, Aug 9, 2011 at 4:34 PM, Daniel-Constantin Mierla wrote: Hi Laura, thanks for the patch

Re: [SR-Users] Using Kamailio to convert TCP to TLS

Hello, On 8/9/11 1:43 PM, aur.hoffm...@free.fr wrote: Hello, I would like to use Kamailio as a TCP<=> TLS convertor ? Do you think it's possible ? I have developed a software (which simulate a SIP phone) which can use UDP or TCP (not TLS). I need a SIP proxy to convert TCP to TLS. For exampl

Re: [SR-Users] $hu is not documented

Hello, On 8/7/11 8:50 AM, Juha Heinanen wrote: xcap_server examples refer to pseudo variable $hu, which is not documented on pseudo variables wiki page: http://sip-router.org/wiki/cookbooks/pseudo-variables/devel indeed, seems I missed that -- I will try to fix the docs soon if none is doing i

Re: [SR-Users] Open source HLR (Home Location Register).

I'm assuming you are looking IMS specific - in which case the HLR is called an HSS. I only know of one open source one - FhoSS which is part of the openimscore - www.openimscore.org HTH Cheers Jason 2011/8/9 Henrik Aagaard Sørensen > I know this is the mailing list for Kamailio, but hopefully

[SR-Users] time for acc records

Hello, it seems that is some parts of the world it is required to have call duration with two decimals precision. By default acc module does the timestamp in seconds. Thinking of adding an option to save the milliseconds, I see two option: - a new column to store the milliseconds part as inte

Re: [SR-Users] new functionality: CDR-based accounting

Hi Timo, related to another email I just sent to this mailing list, just to double check for your enhancement, time related values (start, stop, duration) in full CDRs are also second-based like in the classic acc records? Thanks, Daniel On 8/4/11 8:08 AM, Timo Reimann wrote: Hi all, as

Re: [SR-Users] new functionality: CDR-based accounting

Hi Timo, I would be interested in the 1.5 backported module. Is that available for the masses? Thanks! -graham On 8/4/11 1:08 AM, "Timo Reimann" wrote: > > > Hi all, > > as announced quite a while ago, I finally checked in code that allows to > produce CDRs (Call Data Records) dire

Re: [SR-Users] new functionality: CDR-based accounting

Hello Daniel, our solution is milisecond-based (signature: .). But we can add a switch to support both solutions. Suggestion #modparam("acc","cdr_time","milliseconds"). Bye Sven Am 10.08.2011 14:24, schrieb Daniel-Constantin Mierla: Hi Timo, related to another email I just sent to this m

Re: [SR-Users] $hu is not documented

Daniel-Constantin Mierla writes: > indeed, seems I missed that -- I will try to fix the docs soon if none > is doing it meanwhile (it is in 3.1 as well). The PV is exported by > xhttp module and gives the http url, which is practically the original > URI of the request. i added $hu to devel ps

Re: [SR-Users] time for acc records

Hey, On 10.08.2011 14:21, Daniel-Constantin Mierla wrote: > it seems that is some parts of the world it is required to have call > duration with two decimals precision. By default acc module does the > timestamp in seconds. > > Thinking of adding an option to save the milliseconds, I see two opt

[SR-Users] lookup for specified user

Hi folks, I discussed this issue in previous email ( [SR-Users Modifying $rU after lookup() ) but the question is a bit different now. I would like to change uri like lookup() function does it, but for the specific user. Problem is I want to have one registration (X) for several numbers. When thi

[SR-Users] lookup for specified user

Efelin Novak writes: > I would like to change uri like lookup() function does it, but for the > specific user. Problem is I want to have one registration (X) for > several numbers. When this number is called I have to perform lookup() > for this one common registration (X) and send this call there

Re: [SR-Users] Using Kamailio to convert TCP to TLS

yes it's possible, I've a running configuration with Kamailio and OXE R10 like this, but why OPTIONS end-to-end? Kamailio could reply the OPTIONS or want you use SIP NOE feature of OXE? regards, Andreas Am 09.08.2011 13:43, schrieb aur.hoffm...@free.fr: Hello, I would like to use Kamailio as