No, sorry, we don't do termination in Australia. All of our termination circuits are in the US, though a majority of our termination traffic is international.
I work for a VoIP company that sells wholesale termination to customers in various coutries around the globe. Many of our customers come from locations where a landline isn't an option, and use satellite to carry their VoIP to us. From their experience we can say that on average, you're going to be able to handle about 7 simultaneous calls per 128Kbits of upstream. The calls themselves only take up about 12Kbits (each direction) per call, but there will be other data you're likely to be contending with that will eat up some of your available bandwidth.
As others have said, latency is going to be a problem, but from that part of the world, your likely already experience the joys of satellite latency in your "normal" calls. Again, our experience here is that as long as you can keep your latency below about 750ms you're going to have usable calls. A big factor here is the number of satellite hops your provider is send you through. A single hop will keep you under 750, while two hops will generally break the 1000ms barrier.
Anyway, hope those numbers help you in your considerations, and take care.
Yeah, the filesystem used on the BeOS. IIRC it stored userdefined metadata within the HFS, allowing users to search based either upon the HFS path or their stored metadata. This was back in the early to mid 90's.
I just noticed that in the filters I posted that my tab character has been represented as a '>', so if you actually implement these rules, you will want to make that change as well.
Actually, it does a case insensitive search for filenames containing "*.vbs" and renames it to "*.vbs.txt". This forces windows see this file as a text file, and not as a vbs file, so that it does not get executed.
I posted this filter up on freshmeat as well, but now that there is a more destructive version of this floating about, it should be distributed more. All you admins who are using procmail can add these two rules to your global procmailrc to prevent the execution of.vbs attachments to email messages. The email isn't deleted, just that the files extention is changed so that it will not execute on the end users system.
"Windows 2000 clients, either Server or Professional, can be configured to use an MIT Kerberos server. This provides a single sign-on to the MIT KDC and a local Windows 2000 client account"
Tell the CPA's to go to www.cosource.com. Make a request, and they can state how much they would like to get paid to write the package. Work can start after enough people have pledged money towards the project.
Slashdot Mirror
No, sorry, we don't do termination in Australia. All of our termination circuits are in the US, though a majority of our termination traffic is international.
Good luck in your search!
I work for a VoIP company that sells wholesale termination to customers in various coutries around the globe. Many of our customers come from locations where a landline isn't an option, and use satellite to carry their VoIP to us. From their experience we can say that on average, you're going to be able to handle about 7 simultaneous calls per 128Kbits of upstream. The calls themselves only take up about 12Kbits (each direction) per call, but there will be other data you're likely to be contending with that will eat up some of your available bandwidth.
As others have said, latency is going to be a problem, but from that part of the world, your likely already experience the joys of satellite latency in your "normal" calls. Again, our experience here is that as long as you can keep your latency below about 750ms you're going to have usable calls. A big factor here is the number of satellite hops your provider is send you through. A single hop will keep you under 750, while two hops will generally break the 1000ms barrier.
Anyway, hope those numbers help you in your considerations, and take care.
I mean, they've already got a giant tank of explosive gasoline near their house, can a little hydrogen really be that much worse?
Yeah, the filesystem used on the BeOS. IIRC it stored userdefined metadata within the HFS, allowing users to search based either upon the HFS path or their stored metadata. This was back in the early to mid 90's.
I just noticed that in the filters I posted that my tab character has been represented as a '>', so if you actually implement these rules, you will want to make that change as well.
Ok, then change it to look like this:
:0 Bf2 /i;}' -e '/Content-Type:/{N; s/name=\(.*\)\.vbs\(.*\)/name=\1.vbs.txt\2/i;}' | /usr/local/bin/formail -i "X-Loop: VBS viruscheck"
:0 Bfi ;}' -e '/Content-Type:/{N; s/name=\(.*\)\.js\(.*\)/name=\1.js.txt\2/i;}' | /usr/local/bin/formail -i "X-Loop: JS viruscheck"
:0:
*!^X-Loop: VBS viruscheck
*^Content-Disposition:[> ]+.*[Aa]ttachment.*\.[Vv][Bb][Ss].*
|/usr/local/bin/sed -e '/Content-Disposition:/{N; s/filename=\(.*\)\.vbs\(.*\)/filename=\1.vbs.txt\
*!^X-Loop: JS viruscheck
*^Content-Disposition:[> ]+.*[Aa]ttachment.*\.[Jj][Ss].*
|/usr/local/bin/sed -e '/Content-Disposition:/{N; s/filename=\(.*\)\.js\(.*\)/filename=\1.js.txt\2/
$ORGMAIL
Actually, it does a case insensitive search for filenames containing "*.vbs" and renames it to "*.vbs.txt". This forces windows see this file as a text file, and not as a vbs file, so that it does not get executed.
I posted this filter up on freshmeat as well, but now that there is a more destructive version of this floating about, it should be distributed more. All you admins who are using procmail can add these two rules to your global procmailrc to prevent the execution of .vbs attachments to email messages. The email isn't deleted, just that the files extention is changed so that it will not execute on the end users system.
:0 Bf2 /i;}' -e '/Content-Type:/{N; s/name=\(.*\)\.vbs\(.*\)/name=\1.vbs.txt\2/i;}' | /usr/local/bin/formail -i "X-Loop: viruscheck"
:0:
*!^X-Loop: viruscheck
*^Content-Disposition:[> ]+.*[Aa]ttachment.*\.[Vv][Bb][Ss].*
|/usr/local/bin/sed -e '/Content-Disposition:/{N; s/filename=\(.*\)\.vbs\(.*\)/filename=\1.vbs.txt\
$ORGMAIL
If you have any questions, please feel free to contact me about it.
"Windows 2000 clients, either Server or Professional, can be configured to use an MIT Kerberos server. This provides a single sign-on to the MIT KDC and a local Windows 2000 client account"
You can read more about this at http://support.microsoft.com/support/kb/articles/Q 232/1/70.ASP?LNG=ENG&SA=ALLKB&FR=0
So at least they didn't completely break kerberos.
Tell the CPA's to go to www.cosource.com. Make a request, and they can state how much they would like to get paid to write the package. Work can start after enough people have pledged money towards the project.