< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index  

RE: [reSIProcate] B2BUA and SdpContents::Session::Medium questions


Daniel,

I too have been scouring the web for just such a project and have come
up empty handed.  Would you be interested in sharind what you are put
together for your B2BUA?  We can help each other.

Mike

-----Original Message-----
From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
Daniel Pocock
Sent: Thursday, January 19, 2006 5:34 PM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate] B2BUA and SdpContents::Session::Medium questions



Hi,

I've just started experimenting with resiprocate and DUM.

I thought it would be interesting to start off by writing a B2BUA, as I 
couldn't find a demonstration one anywhere.

The B2BUA links to rtpproxy using a unix socket, so that the media 
stream won't go between the two endpoints.

Anyhow, now that I've got this working I've got some questions:

- is there already a working open source example B2BUA using resiprocate

and/or DUM?

- when I rewrite the RTP media ports, I notice that there is no easy way

to clone the SdpContents::Session::Medium object and retain all the 
existing values while changing the port number (private variable 
mPort).  I must confess to being more of a Java developer than a C++ 
expert, but nonetheless I'd like to find the most efficient way to clone

these Medium objects - can someone please give me an example or point me

in the right direction.  If I just clone the object, there appears to be

no way to do `setPort(value from rtpproxy)'

- has anyone got any tips on rewriting SDP to be compatible with 
rtpproxy?  I presume there are some things that rtpproxy can't handle, 
like TCP, so I intend to remove obvious things like that from the SDP
offer.

Regards,

Daniel