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
