B2B module will not handle any media. Only Mediaproxy. So when it comes to
mediaproxy you will have this
Caller <-> Mediaproxy <-> Callee
On Sep 13, 2011 7:37pm, Wilmar Campos <[email protected]> wrote:
Can you explain the media flow scenario?
My current scenario is:
Call:
client->proxy->final client.
Media:
Client->mediaP->Final client.
I want to clarify that I am taken this scenario cause I am getting RTCP
statistics from the mediaP and to the final client, so I do not want to
have a B2B in the middle handleling media cause it will break the RTPC
that I am taken from my mediaP to the Final Client host.
Thanks,
WIll
On Tue, Sep 13, 2011 at 7:06 PM, Duane Larson [email protected]>
wrote:
It should be client > proxy > b2b > end point. The proxy should do all
your route logic and then pass it on to b2b. The b2b can be on the same
box as the proxy, but I went ahead and separated them.
On Sep 13, 2011 5:31 PM, [email protected]> wrote:> Hi, thanks for
your response, is there any specific call flow I have to follow?
>
> Client- b2- proxy-end client?
>
> Or it can be
>
> Client b2b end client??
>
> Please point me to the right direction..
>
> Thanks,
>
> Wilmar
>
> Sent via BlackBerry from T-Mobile
>
> -----Original Message-----
> From: [email protected]
> Sender: [email protected]
> Date: Tue, 13 Sep 2011 22:07:38
> To: OpenSIPS users mailling [email protected]>
> Reply-To: OpenSIPS users mailling list [email protected]>
> Subject: Re: [OpenSIPS-Users] OpenSips B2B and MediaProxy
>
> _______________________________________________
> Users mailing list
> [email protected]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
> _______________________________________________
> Users mailing list
> [email protected]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
--
Wilmar Campos
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
