Re: [SR-Users] Memory leak when reloading htable using db_cluster

2017-05-01 Thread Kristian F . Høgh
Hi The leak is only when reloading an empty htable. I created a pull request (https://github.com/kamailio/kamailio/pull/1110) Regards, Kristian. On Friday, April 28, 2017 1:56:51 PM CEST Kristian F. Høgh wrote: > Hi, > > I did some more testing. > > reloading address and domain is fixed in mas

[SR-Users] TCP port re-using when doing HTTP transfer

2017-05-01 Thread Ramachandran, Agalya (Contractor)
Hi Giacomo, I am using http_async_client module to do http transfer. Currently am testing the HTTP service with a mock server. If I send the HTTP response immediately for the POST request, then the TCP connections are reused from kamailio. In the mock server if I send the response with a delay o

Re: [SR-Users] Oracle and package function

2017-05-01 Thread Ovidiu Sas
It seems that db_unixodbc always expects a result. The errors that you are seeing are harmless in your case. There were some similar issues with the native db_oracle driver but those are fixed now. However, the db_oracle has a restricted set of commands that are allowed in raw mode: select, insert

[SR-Users] Kamailio IMS - Handling 2 SIP transports in an IMS client

2017-05-01 Thread Haggerty, Paul (phaggert)
Hi, Our client registers with the IMS core using UDP but uses TCP when the packet size is over 1300 bytes. When the client sends the TCP reques, the PCSCF replies with 403 Forbidden "you need to reg with the SCSCF" We've traced this back to the code in the PCSCF and it looks like it is c

Re: [SR-Users] handle_uri_alias persists through failure_route

2017-05-01 Thread Daniel Tryba
On Mon, May 01, 2017 at 02:26:55PM +0200, Daniel-Constantin Mierla wrote: > failure route is preserving the attributing of the branch that received > the failure reply. > > You have to use resetdsturi() in this case -- see the readme of kex module. Is resetdsturi in any different from $du=$null ?

[SR-Users] Retrieving the custom header parameter value from contact header

2017-05-01 Thread Juha Heinanen
vi...@advaitamtech.com writes: > Tried using @hf_value.contact.p.tgrp . But it is giving me complete > contact header. > I want only "tgrp" paramter value "tg_0615_prsw1". Anyone , any > sugeestions? Try {uri.param,name} transformation. -- Juha ___ K

[SR-Users] Retrieving the custom header parameter value from contact header

2017-05-01 Thread vi...@advaitamtech.com
Hi, Am trying to extract a custom parameter from the contact header. Below it the example of contact header, Eg: Contact: I want to extract the parameter value of "tgrp" Tried using @hf_value.contact.p.tgrp . But it is giving me complete contact header. I want only "tgrp" paramter value "

Re: [SR-Users] handle_uri_alias persists through failure_route

2017-05-01 Thread David Wilson
Thanks Daniel, I found that very method 20min ago from examining the source of handle_ruri_alias. It works… your advice is spot on as usual. Thanks for your help, Dave Wilson > On 1 May 2017, at 8:26 pm, Daniel-Constantin Mierla wrote: > > Hello, > > failure route is preserving the attrib

Re: [SR-Users] handle_uri_alias persists through failure_route

2017-05-01 Thread Daniel-Constantin Mierla
Hello, failure route is preserving the attributing of the branch that received the failure reply. You have to use resetdsturi() in this case -- see the readme of kex module. Cheers, Daniel On 01.05.17 12:58, David Wilson wrote: > Hello All, > > We use registrar servers (call them A,B) for TLS

[SR-Users] handle_uri_alias persists through failure_route

2017-05-01 Thread David Wilson
Hello All, We use registrar servers (call them A,B) for TLS connections from clients and a central routing proxy (P) that authenticates and manages all call routing. On INVITE, P uses lookup(“location”) and handle_uri_alias() to route the INVITE to A or B depending on the AOR from REGISTER. In