[VOIPSEC] Really RTP is end-to-end?

Simon Horne s.horne at packetizer.com
Tue Jul 18 20:11:26 CDT 2006


 From a SRTP standpoint having DTMF digits carried inband (RFC 2833) is 
less than ideal as each hop would need to decrypt and re-encrypt the media 
at each hop just to detect the presence of DTMF digits. Is there a way to 
carry DTMF digits out of band like other protocols can do? I mean you can 
encrypt media right through the asterisk box in H.323

Simon


At 08:24 PM 18/07/2006, you wrote:
>This is the default asterisk behaviour, it keeps itself in the RTP data
>path to listen for inband DTMF for feature codes (eg. for recording,
>transferring, ...). This also allows it to transcode between different
>codecs.
>
>Regards,
>
>Wence Van der Meersch
>Information Security Consultant
>Ascure NV
>
>e-mail  wence.vandermeersch at ascure.com
>Web     http://www.ascure.com/
>
>
> > -----Original Message-----
> > From: Voipsec-bounces at voipsa.org
> > [mailto:Voipsec-bounces at voipsa.org] On Behalf Of rgigli at libero.it
> > Sent: maandag 17 juli 2006 9:32
> > To: voipsec
> > Subject: [VOIPSEC] Really RTP is end-to-end?
> >
> > Hi,
> > I have two x-lite softphone, A and B, and an asterisk server,
> > C, when A call B initiates a SIP session whit C. My problem
> > is in RTP session because A and B don't communicate in
> > end-to-end manner but through C. I think there is a problem
> > in my x-lite configuration, is it right?
> >
> >
> > ______________________________________________________________
> > __________________
> > Con Full Casa proteggi abitazione e famiglia da 50 cent al
> > giorno, e 6 mesi in piu' li offre RAS.
> > http://click.libero.it/ras
> >
> >
> >
> > _______________________________________________
> > Voipsec mailing list
> > Voipsec at voipsa.org
> > http://voipsa.org/mailman/listinfo/voipsec_voipsa.org
> >
>---- eMail Disclaimer ----
>This message may be confidential. It is also solely for the use of the 
>individual or group to whom it is addressed. If you have received it
>by mistake, please let us know by e-mail reply. Ascure is not liable for 
>any direct or indirect damage arising from errors, inaccuracies or
>any loss in the message, from unauthorized use, disclosure, copying or 
>alteration of it.
>For the complete version or other languages of this disclaimer see 
>http://www.ascure.com/disclaimer.html
>
>_______________________________________________
>Voipsec mailing list
>Voipsec at voipsa.org
>http://voipsa.org/mailman/listinfo/voipsec_voipsa.org






More information about the Voipsec mailing list