29 Sep
2014
29 Sep
'14
8:30 p.m.
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 same..so for rtpengine there's no
difference...for this reason I can see early media only on one of the
receivers
I still don't understand what difference an RTP proxy is supposed to
make for the invite. Your offering client only opens one endpoint and
sends that out. Without RTP proxy, all receiving clients see the same
endpoint and they will all send their early media to that same endpoint.
With RTP proxy, the same thing happens. What's the difference?
cheers
29 Sep
29 Sep
8:51 p.m.
New subject: R: Re: R: Re: RTPPROXY & BRANCH
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 to send audio/video RTP to C on port c1,c2
With rtpproxy:
- A offers port a1,a2 (audio video) in INVITE to Kamailio....
- Kamailio contact rtpproxy because B&C are natted clients
- rtpproxy check callid and offer offers port k1,k2....
- Kamailio sends INVITE to B offering k1,k2
- Kamailio sends INVITE to C offering k1,k2
- B offers port b1,b2 (183)
- C offers port c1,c2 (182)
- Kamailio sends 183 to A (for B leg) offering p1,p2
- Kamailio sends 183 to A (for B leg) offering p3,p4
- A starts to stream on p1,p2,p3,p4 but only one receiver can see the video
(B or C depends who will be the first:))
I don't know if it depends on that B & C receives same ports; i don't know
if rtpproxy is able to "duplicate" stream received from A to all
"receiver"
-----Messaggio originale-----
Da: sr-users-bounces(a)lists.sip-router.org
[mailto:sr-users-bounces@lists.sip-router.org] Per conto di Richard Fuchs
Inviato: lunedì 29 settembre 2014 20:31
A: sr-users(a)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 are the same...This happens because
for all these clients the callid is still the same..so for rtpengine
there's no difference...for this reason I can see early media only on
one of the receivers
I still don't understand what difference an RTP proxy is supposed to make
for the invite. Your offering client only opens one endpoint and sends that
out. Without RTP proxy, all receiving clients see the same endpoint and they
will all send their early media to that same endpoint.
With RTP proxy, the same thing happens. What's the difference?
cheers
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
---
Questa e-mail è priva di virus e malware perché è attiva la protezione avast! Antivirus.
http://www.avast.com
3500
days inactive
3500
days old
1 comments
2 participants
participants (2)
-
Marino Mileti -
Richard Fuchs