Yep, logs helps. Actually, was mix of errors in PBX and Kamailio config.
So yea, rtpproxy is working as expected, can’t say same for my config files :)
Regards, Igor
On 22 дек. 2016 г., 19:24 +0200, Alex Balashov ,
wrote:
> That just sounds like the rtpproxy is not being engaged, i.e. that the
Oh, I see. Yes, that could be.
-- Alex
> On Dec 22, 2016, at 12:49 PM, Daniel Tryba wrote:
>
>> On Thu, Dec 22, 2016 at 12:23:52PM -0500, Alex Balashov wrote:
>> That just sounds like the rtpproxy is not being engaged, i.e. that the
>> rtpproxy_manage() call is failing. When that happens, the
On Thu, Dec 22, 2016 at 12:23:52PM -0500, Alex Balashov wrote:
> That just sounds like the rtpproxy is not being engaged, i.e. that the
> rtpproxy_manage() call is failing. When that happens, the SDP from .2
> will be passed through unaltered.
>
> The Kamailio log should give you some idea of why
That just sounds like the rtpproxy is not being engaged, i.e. that the
rtpproxy_manage() call is failing. When that happens, the SDP from .2 will be
passed through unaltered.
The Kamailio log should give you some idea of why the rtpproxy invocation has
failed.
RTPProxy is certainly not limited
Sorry, I got media address 111.222.3.2 in SDP, but not 111.222.3.3
Regards, Igor
On 22 дек. 2016 г., 19:19 +0200, Igor Olhovskiy ,
wrote:
> Hi!
> Issue I can’t figure out. Or all working ok and that’s just me who not
> understands.
>
> I have situation
> softPhone (111.222.3.2) -> Kamailio w.
Hi!
Issue I can’t figure out. Or all working ok and that’s just me who not
understands.
I have situation
softPhone (111.222.3.2) -> Kamailio w. rtpproxy (111.222.3.3) -> PBX
(111.222.3.4)
All addresses are on same public network.
rtpproxy is running with -l 111.222.3.3 -A 111.222.3.3
I want all
Hi list,
We have two eth, one with a private ip and the other with a public ip. We
have MHOMED configured. The call comes from private network and then is
routed to a public network via rtjson routing. The call is routed but the
thing is that the record route is being set with the private one (It
Hi list,
We have two eth, one with a private ip and the other with a public ip. We
have MHOMED configured. The call comes from private network and then is
routed to a public network via rtjson routing. The is routed but the thing
is that the record route is being set with the private one (It's th
Daniel,
It works like a charm!
Thanks again!
Diego.
2016-12-22 10:17 GMT-03:00 Diego Nadares :
> Thanks Daniel, I will try it today!
>
> Cheers,
>
> Diego
>
> 2016-12-22 5:17 GMT-03:00 Daniel-Constantin Mierla :
>
>> Hello,
>>
>> indeed, enforcing the socket was missing. Can you try with lates
Thanks Daniel, I will try it today!
Cheers,
Diego
2016-12-22 5:17 GMT-03:00 Daniel-Constantin Mierla :
> Hello,
>
> indeed, enforcing the socket was missing. Can you try with latest git from
> master or 4.4 branches? I pushed a patch for it.
>
> Cheers,
> Daniel
>
> On 21/12/2016 15:50, Diego N
Hello,
how much shared memory did you configure for kamailio (the value of -m
parameter)? There are safety checks to ensure that there are available
256 to 512KB of shm/kamailio process in order to have safe ssl
operations. If you don't allocate enough and you have a high value for
children global
Hi,
shared memory not freed once TLS connection close means shm available
memory decreasing for new connection that leads to the following error
*tls: ssl bug #1491 workaround: not enough memory for safe operation*
*TestCase:*
1. start kamailio
2. use sample program to establish tls connection a
Hello,
indeed, enforcing the socket was missing. Can you try with latest git
from master or 4.4 branches? I pushed a patch for it.
Cheers,
Daniel
On 21/12/2016 15:50, Diego Nadares wrote:
> Hi Guys,
>
> Anybody knows if each 'socket' specified in routes struct should be
> use to send the messag
13 matches
Mail list logo