I'm dealing with an idea to exchange data in a socket connection style or a sort of ftp transfer with IAX2 as the transport medium. An IAX client on e.g. a notebook could establish a connection to any remote machine (also client) via any Asterisk Server where both clients are registered. Due to the unique properties of IAX2 one could connect quite easily to any "hidden" remote computer without server functionality and exchange data. To my opinion it should be quite simple to bypass audio->RTP packet conversion in order to allow digital data transmission.
On Fri, Jun 26, 2009 at 6:48 PM, Maris <maris.rob at vdi.de> wrote:> I'm dealing with an idea to exchange data in a socket connection style > or a sort of ftp transfer with IAX2 as the transport medium. > > An IAX client on e.g. a notebook could establish a connection to any > remote machine (also client) via any Asterisk Server where both > clients are registered. Due to the unique properties of IAX2 one > could connect quite easily to any "hidden" remote computer without > server functionality and exchange data. > > To my opinion it should be quite simple to bypass audio->RTP packet > conversion in order to allow digital data transmission.Just a question since I am not quite sure I understand your suggestion. How do you plan to reliably transmit a file through UDP which does not guarantee delivery?, not to mention that IAX2 does not use RTP. Are you suggesting to change the protocol to support such transfers? -- Moises Silva Software Developer Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R 9T3 Canada t. 1 905 474 1990 x 128 | e. moy at sangoma.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20090626/debae4b0/attachment.htm
> guarantee delivery?, not to mention that IAX2 does not use RTP. Areyou> suggesting to change the protocol to support such transfers?When it makes sense, yes - see below, otherwise the idea can get into the waste paper backet. ...> But why does he want to do it ? Share secret / illegal files LOL ? >Transfer files and/or logging data to/from computers anywhere in the intranet of organizations - over the internet. Due to restrictions this computer may not have server functionality. For the purpose, an IAX client can be installed on the remote computer. Of course, such client-client communication can be solved using an intermediate server which two clients that exchange data connects to. The specific features of IAX (NAT transparency) could help, provided that simple TCP channels initiated by the clients can posess problems in establishing connections under certain weird network constellations - it goes beyond my knowledge to judge that. ...> to the other side and decode it there Asterisk (or just about anyVoIP> software) will opt for timely delivery rather than a reliabledelivery. Encoding digital data into audio in order to transfer it as digital audio data packets makes no sense for me. Packet problems can be overcome with other methods, as pointed out by other contributors. Rob Maris Hardware developer
On 27 Jun 2009, at 11:27, Maris wrote:>> guarantee delivery?, not to mention that IAX2 does not use RTP. Are > you >> suggesting to change the protocol to support such transfers? > > When it makes sense, yes - see below, otherwise the idea can get into > the waste paper backet. > > ... > >> But why does he want to do it ? Share secret / illegal files LOL ? >> > > Transfer files and/or logging data to/from computers anywhere in the > intranet of organizations - over the internet. Due to restrictions > this computer may not have server functionality. For the purpose, an > IAX client can be installed on the remote computer. Of course, such > client-client communication can be solved using an intermediate > server which two clients that exchange data connects to. The specific > features of IAX (NAT transparency) could help, provided that simple > TCP channels initiated by the clients can posess problems in > establishing connections under certain weird network constellations - > it goes beyond my knowledge to judge that. > > ... > >> to the other side and decode it there Asterisk (or just about any > VoIP >> software) will opt for timely delivery rather than a reliable > delivery. > > Encoding digital data into audio in order to transfer it as digital > audio data packets makes no sense for me. Packet problems can be > overcome with other methods, as pointed out by other contributors. > > Rob Maris > Hardware developerYou should read the protocol spec. http://www.rfc-editor.org/authors/rfc5456.txt It already supports a couple of 'data' transports, including the one that was used to upgrade the IAXy firmware. I don't think you would have to change much (if anything) in the protocol to make it work. Tim. Tim Panton - Web/VoIP consultant and implementor www.westhawk.co.uk -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2419 bytes Desc: not available Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20090628/ab7fae62/attachment.bin