29 Sep
2014
29 Sep
'14
8:03 p.m.
On 09/25/14 10:22, Frank Carmickle wrote:
On Sep 25, 2014, at 10:09 AM, Marino Mileti <marino.mileti(a)alice.it
<mailto:marino.mileti@alice.it>> wrote:
That's also what I'm confused about. The calling client only offers one
endpoint, so without RTP proxy in between, all receiving clients would
be offered the same IP and port, just as they do now with an RTP proxy.
In either case, the offering client would receive multiple early media
streams from different endpoints. I'm not sure what difference the RTP
proxy should make.
cheers
Because I've more than 1 client behind NAT
(1,2,3 mobile phones) and I would like to reach all of them in parallel mode. I can't
use for all of them same ports because all mobile clients have early media (the receive
video media before they answer)
I don't understand. Are you saying that you have clients that when they
receive an invite sent video with 183? How do you want to composite the
video to show to the caller? It is not RFC3261 compliant to change IP
and port from 183 to 200. Of course you can reinvite after the 200.
Most B2BUAs require you to ignore early media and generate something
locally to send to the caller or just send them 180.
Maybe if you explain your use case someone can help you.