Re: RTP Multicast TTL

But a good idea :).  If a current base class constructor is changed, 
maybe we should bump the version (to 1.4.0), since linkage will be 
broken.  But it seems a large version jump for such a small change :). 
We could also just redo the library versioning in configure.ac 
(LT_VERSION) to 1:0, and this too will mark for binary images that this 
is an incompatible revision with programs compiled against prior releases.

Federico Montesino Pouzols wrote:
> Ooops, I'm afraid this didn't get to the list...
> 
> On Sat, Jan 21, 2006 at 05:24:12PM +0100, Federico Montesino Pouzols wrote:
>> Hi, 
>>
>> I think this is one of the points where the current API may be too
>> restrictive. I think setMcastTTL should be made protected an also that
>> an additional 'default TTL' optional parameter should be added to the
>> multicast constructor of the TRTPSessionBase template. That way, the
>> public interface would provide a means to select the TTL at
>> construction time and the protected interface would allow for custom
>> changes of the TTL.
>>
>> I would introduce this change together with some others shortly, or
>> are ther any other suggestions?
>>
>> On Tue, Jan 17, 2006 at 11:41:37AM +0100, Arjan Knepper wrote:
>>> Tom Anwyll wrote:
>>>
>>>> Hello RTP Gurus,
>>>>
>>>> Pardon my ignorance and inexperience.
>>>>
>>>> It is my understanding of multicast that the time to
>>>> live (TTL) option determines the number of times a
>>>> multicast packet will be routed beyond the network the
>>>> packets originate from.
>>>>
>>>>
>>> yes, basically.
>>>
>>>> However, I can not determine the method to set the TTL
>>>> for multicast RTP session transmitters in ccRTP.
>>>>
>>>>
>>> in rtp.h: class TRTPSessionBase
>>>
>>>    inline Socket::Error
>>>    setMcastTTL(uint8 ttl)
>>>    {
>>>        Socket::Error error = dso->setMulticast(true);
>>>        if ( error ) return error;
>>>        error = dso->setTimeToLive(ttl);
>>>        if ( error ) return error;
>>>        error = cso->setMulticast(true);
>>>        if ( error ) return error;
>>>        return cso->setTimeToLive(ttl);
>>>    }
>>>
>>> This member is private though. (Why ??) But the 'dso' and 'cso' are
>>> protected so in your derived class you should be able to access them.
>>>
>>>
>>>> If possible, could someone explain to me how to set
>>>> TTL in ccRTP for multicast RTP session transmitters? 
>>>>
>>>> If it is not possible to set TTL in ccRTP, doesn't
>>>> this limit ccRTP for use only in local networks? How
>>>> would multicast RTP transmitted packets get routed to
>>>> multiple networks?
>>>>
>>>> Thanks (in advance) for the explanation,
>>>> Tom
>>>>
>>>>
>>>>
>>>>
>>>> __________________________________________________
>>>> Do You Yahoo!?
>>>> Tired of spam?  Yahoo! Mail has the best spam protection around 
>>>> http://mail.yahoo.com 
>>>>
>>>>
>>>> _______________________________________________
>>>> Ccrtp-devel mailing list
>>>> [email protected]
>>>> http://lists.gnu.org/mailman/listinfo/ccrtp-devel
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Ccrtp-devel mailing list
>>> [email protected]
>>> http://lists.gnu.org/mailman/listinfo/ccrtp-devel
> 
> 
> _______________________________________________
> Ccrtp-devel mailing list
> [email protected]
> http://lists.gnu.org/mailman/listinfo/ccrtp-devel

_______________________________________________
Ccrtp-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/ccrtp-devel

begin:vcard
fn:David Sugar
n:Sugar;David
org:GNU Telephony
email;internet:[email protected]
tel;work:+1 201 215 2609
x-mozilla-html:FALSE
url:http://www.gnutelephony.org
version:2.1
end:vcard