[SR-Users] Fwd: Stack smash error when using auth_ephemeral with KEMI

2019-05-02 Thread Grant Bagdasarian
Hi Daniel, See pastebin url below for the backtrace. https://pastebin.com/tTUUk4YH Hopefully I did it the right way. Please let me know if you need anything else. FYI, Kamailio is running inside of a docker container. version: kamailio 5.2.1 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, US

Re: [SR-Users] run some extra things before relying message

2019-05-02 Thread Mojtaba
Hi. I have tried the same things like it. I got sdp changed by rtpengine. But i want to run some extra script before relying message. It is strange the script will be run after the call stablished. It means the script will be run at the same time the message is relying. On Thu, 2 May 2019, 16:23 Y

Re: [SR-Users] Problem with topoh

2019-05-02 Thread Phillman25 Kyriacou
Ok thanks for your input Daniel Will test and let you know. Regards Phillip On Thu, May 2, 2019 at 10:54 AM Daniel-Constantin Mierla wrote: > Hello, > > first I wanted to confirm there is still an issue with such case on > maintained versions. Since 4.4, there were many changes to topoh module

Re: [SR-Users] run some extra things before relying message

2019-05-02 Thread YASIN CANER
Hello, "write_sdp_pv" parameter helps to write a pvalue that includes modified sdp. Could you try it? Yasin CANER https://kamailio.org/docs/modules/5.2.x/modules/rtpengine.html#rtpengine.p.write_sdp_pv From: sr-users on behalf of Mojtaba Sent: Thursday, Ma

[SR-Users] run some extra things before relying message

2019-05-02 Thread Mojtaba
Hello, I have encountered with problem in Kamailio. At first glance it looks simple. Considering the Data Lump feature in Kamailio, All changes in SIP body, does not apply quickly. So if we are using RTPEngine or RTPProxy, How we can get body message (Actually IP and port from SDP after rtpengine_m

Re: [SR-Users] Problem with topoh

2019-05-02 Thread Daniel-Constantin Mierla
Hello, first I wanted to confirm there is still an issue with such case on maintained versions. Since 4.4, there were many changes to topoh module. You can test on your computer with Kamailio 5.2 and using sipp to simulate such SIP traffic. If still and issue, it will be fixed and you can backport

Re: [SR-Users] Problem with topoh

2019-05-02 Thread Phillman25 Kyriacou
Hi Daniel-Constantin Thanks for your response. Yes we are using Kamailio v4.4.x in production. In case we cant upgrade to 5.x right now would there an alternative work around for this? Thanks again Phillip On Thu, May 2, 2019 at 10:07 AM Daniel-Constantin Mierla wrote: > Hello, > > are you us

Re: [SR-Users] Problem with topoh

2019-05-02 Thread Daniel-Constantin Mierla
Hello, are you using Kamailio v4.4.x? If yes, can you try with a newer version to be sure we do not hunt an issue that was already fixed? At this moment 5.2.x and 5.1.x are maintained branches. Cheers, Daniel On 01.05.19 13:51, Phillman25 Kyriacou wrote: > Dear List > > I have an issue with topo

Re: [SR-Users] Stack smash error when using auth_ephemeral with KEMI

2019-05-02 Thread Daniel-Constantin Mierla
Hello, can you get a core file for this case? Set `ulimit -c unlimited` before starting Kamailio as root and run again. Once you have the core file, get the backtrace with gdb. Cheers, Daniel On 01.05.19 20:26, Grant Bagdasarian wrote: > Hello, > > I was trying out the auth_ephemeral module in

Re: [SR-Users] Kamailio stop to process incoming SIP traffic via TCP.

2019-05-02 Thread Daniel-Constantin Mierla
Hello, I think one possibility to reproduce the issue would be to create a scenario when same connection is wanted at the same time, when the first process that gets the lock on it needs a bit more time to execute. Not sure how to create the case, maybe something like:   - enable onsend_route for

[SR-Users] Modify DMQ 200OK in on_reply route

2019-05-02 Thread jenus
Hi all, I'm trying to run a kamailio DMQ node inside a docker container. All works fine but i have one issue with DMQ. Since the kamailio process inside the container is behind a nat i have set the advertise address to the external ip, this works fine for the via headers but DMQ keeps sending