2004 June

June 2004

Redfone, based in Miami, USA, announces a commercial PBX based on Asterisk. I\’ve never seen this company acting with contributions to the Asterisk Open Source community. Would be another feather in their hat if they participated and gave back…

\”Our new ECS runs on the highly reliable Linux operating system and is based on the Asterisk PBX software application. Both are from the open-source environment. Asterisk is a proven IP-PBX product operating in hundreds of organizations worldwide, from small \’mom-and-pop\’ installations to organizations with several thousand users,\” notes Mr. Lynn. \”Use of Asterisk and hardware components that comply with open standards ensures a cost- effective solution and a wider choice of telephone and computer equipment for customers,\” he said.

VoiceXML and Asterisk integration announced by Ivores Systems, inc:

Invores Systems, Inc. announces integration of its SIP VoIP VoiceXML gateway platform, EXpress2.0%u2122, with Asterisk, an open source PBX. %u201CEXpress2.0%u2122 integration with Asterisk marks an exciting next gen phase of software solutions for businesses to offer highly cost effective interactive Voice Over IP based self-service,%u201D comments Tom Multer, President of Invores.

SNOM is interviewed in Eweek.com and mentions Asterisk as a reference platform:

Snom, based in Berlin, with offices in Coppell, Texas, was early out of the gate with IP phones years ago, back when H.323 was still the reigning VOIP (voice over IP) protocol. Today, snom pledges particularly strict adherence to the latest Internet Engineering Task Force (IETF)-ratified SIP (Session Initiation Protocol) specifications. The company is so standards-compliant, in fact, that its phones will work with the Asterisk open-source Linux SIP server.

Oliver Kaven reviews Asterisk for PC Magazine\’s online edition:

Using Asterisk was very satisfactory, and the overall call quality was excellent. What imperfections we experienced in the VoIP calls could be attributed to poor network conditions rather than Asterisk. The system\’s performance impressed us, especially considering that we had installed it on a 500-MHz Pentium III system with 256MB of RAM.

\"AsteriskThank you very much for all feedback on Asterisk Sunday News!
This is the last issue for June. This week I\’ll go on vacation
and will be back with more news in early July.

My kids are getting summer leave this week and we\’ll be
visiting the south of England for a while. Another part of
Europe that still use their own currency.

If you think there\’s an European standard, you\’re
wrong. England have different phoneplugs, powerplugs and drives
on the wr…, sorry, the other side of the road. So there\’s not
only a difference between Europe and the US in ISDN standards,
like PRI/E1 and PRI/T1, but also when it comes down to simple
things like power plugs. But that\’s another cup of tea. Time to
focus on Asterisk.

This week\’s topics:

  • Asterisk – gone fishing again
  • Asterisk release plans: What happened with stable?
  • The Astricon FAQ
  • Chan_sip2 news: The Yngve release
  • Recent additions to Asterisk CVS Head


Oliver Kaven has published an article about Asterisk in PC Magazine, the online edition:

If you are interested in Voice over IP, are not intimidated by open-source software, and don\’t want to part with tens of thousands of dollars up front, take a close look at Asterisk (www.asterisk.org). Developed largely by Mark Spencer, this Linux-based, open-source PBX replacement is an excellent appli-cation and can even be considered for use as your permanent VoIP gateway solution.

\"AsteriskThis week, I\’ve been really busy with the launch of a new Swedish Voip provider,
www.bbtele.se, so I haven\’t been able to follow the Asterisk community and haven\’t
been very responsive either. My apologies if you\’ve tried to contact me and I did
not reply quickly or at all.

So to cover up (can\’t report on what is happening I dedicate this
issue of Asterisk Sunday News to the Asterisk SIP channel. Inside you\’ll find
more information on why SIP and NAT doesn\’t really work as clockwork, as well
as some other notes.

This week\’s topics:

  • A new mailing list: Asterisk-BSD
  • AST_DATA: Now on the bug tracker
  • Theme: SIP and NAT – what is the problem, really?
  • One way audio? Why?
  • The phone can call Asterisk, but I get no incoming calls?
  • What can STUN do for me?
  • Asterisk on the INSIDE of a NAT device
  • Outbound SIP proxy – what is that?
  • What\’s the difference between SIP and IAX2?
  • Patch-of-the-week: SIP realm authentication
  • (more…)

    Spring is back in the Stockholm area. After a few day\’s worth winter re-runs,
    the sun is back and night-time temperature is at least 5 degrees celsius. Time to
    move out all my annual flowers and prepare the garden for summer.

    Sweden is famous for our annual five week holidays – by law. From june to late
    august, it\’s almost impossible to make any business decision, since there\’s always
    people away. Some offices close for a couple of weeks during july.

    With people away and offices being closed, it\’s important to have a PBX that can
    handle the calls and make sure the message is delivered. Asterisk is of course
    my preferred choice, and this week, I\’ll give you some insight into how you can
    make Asterisk handle the calls while you\’re away. Stay tuned!

    This week\’s topics:

    • What\’s a stable release, anyway?
    • The Wiki: A mission critical information source
    • A new data architecture: AST_DATA
    • Asterisk: Gone fishing
    • Asterisk award-of-the-week: The inventors of NAT


    Thomas Porter has written an article about H.323 security on securityfocus.com:

    \”An IBM executive was once quoted as saying, \”Our goal is to make the computer as easy to use as the telephone\”. Our goal, now, is the reverse: to make using an IP telephone at least as easy and secure as using a computer on the Internet.

    Voice over IP (VoIP) can be a complex subject. Network security professionals may find the terminology foreign, and VoIP vulnerabilities are often misunderstood. This paper provides an overview of the H.323 protocol suite, its known vulnerabilities, and then suggests twenty rules for securing an H.323-based network. \”