Unfortunately rtpengine doesn't work in this way. At the end of the calls this
is the output log:
Final packet stats:
Tag 'Fw3D7R0', created 0:41 ago, in dialogue with 'TTPyT~Hdw'
Media #1, port 30224192.168.10.20:7078 , 540 p, 92880 b, 0 e
Media #1, port 30225192.168.10.20:7079
Hi Richard,
this is more or less the same problem that I am experiencing. To understand
it better, just assume one branch needs to do SRTP, and the other simple
RTP.
To make this happen, you will have to enable rtpengine differently for the
same call, and this is where the crash/error happens.
On 09/25/14 10:41, Marino Mileti wrote:
No no. The video will be sent by the caller user to all the callees.
I'l try to explain better. My scenario is:
- A make a call to a group... B C are group member...so Kamailio is
able to call them in parallel using alias..
- B C receive the
On Sep 29, 2014, at 1:14 PM, Richard Fuchs rfu...@sipwise.com wrote:
This may work with rtpengine, as it will open new ports for answers come
from different endpoints. But the final two-way association for the
actual call may still end up broken, as it has no way of knowing which
client
On 09/29/14 13:19, Frank Carmickle wrote:
On Sep 29, 2014, at 1:14 PM, Richard Fuchs rfu...@sipwise.com wrote:
This may work with rtpengine, as it will open new ports for answers come
from different endpoints. But the final two-way association for the
actual call may still end up broken, as
On Sep 29, 2014, at 1:24 PM, Richard Fuchs rfu...@sipwise.com wrote:
On 09/29/14 13:19, Frank Carmickle wrote:
On Sep 29, 2014, at 1:14 PM, Richard Fuchs rfu...@sipwise.com wrote:
This may work with rtpengine, as it will open new ports for answers come
from different endpoints. But the
On 09/29/14 13:29, Frank Carmickle wrote:
On Sep 29, 2014, at 1:24 PM, Richard Fuchs rfu...@sipwise.com wrote:
On 09/29/14 13:19, Frank Carmickle wrote:
On Sep 29, 2014, at 1:14 PM, Richard Fuchs rfu...@sipwise.com wrote:
This may work with rtpengine, as it will open new ports for
@lists.sip-router.org
Oggetto: Re: [SR-Users] R: Re: R: Re: RTPPROXY BRANCH
On 09/29/14 14:23, Marino Mileti wrote:
The problem isn't on 183s but on the multiple INVITE that Kamailio
sends to clients behind rtpengine. Rtpengine open new ports for answer
but on INVITE the rtpengine ports
On 09/29/14 14:23, Marino Mileti wrote:
The problem isn't on 183s but on the multiple INVITE that Kamailio sends to
clients behind rtpengine. Rtpengine open new ports for answer but on INVITE
the rtpengine ports are the same...This happens because for all these
clients the callid is still the
On 09/29/14 14:51, Marino Mileti wrote:
Without rtpproxy:
- A offers port a1,a2 (audio video) in INVITE to B,C (in case of no natted
client so no needs of rtpproxy)
- B offers port b1,b2 (183)
- C offers port c1,c2 (182).
- A starts to send audio/video RTP to B on port b1,b2
- A starts
On Sep 25, 2014, at 10:41 AM, Marino Mileti marino.mil...@alice.it wrote:
No no. The video will be sent by the caller user to all the callees.
I'l try to explain better. My scenario is:
- A make a call to a group... B C are group member...so Kamailio is able to
call them in
11 matches
Mail list logo
