[VOIPSEC] Juniper as an SBC

[J. Oquendo]

> 
> Stay far far away, go look at Covergence and Acme.
> 
> ><>
> Nathan Stratton                                CTO, BlinkMind, Inc.
> nathan at robotics.net                         nathan at blinkmind.com
> http://www.robotics.net                        http://www.blinkmind.com

Can you offer some clarity other than one sentence. Why would
or should I stay far far away. Can you give me any detailed
cons/pros about your experience. This definitely was not the
kind of answer I had hoped for. For example, I currently am
using Netrakes(Audiocodes) and I can tell you some of the
pros and cons:

Cons:
Takes forever implementing changes. Once you push a policy,
you'll be stuck for no less than 10 minutes (I've timed it)
waiting for the policy to take place. If you erred, you have
to wait it out.

EMS - once stuck on stupid (as I like to say) - if it gets
in any way hiccuped, you have to literally reboot that side
of the SBC. It's based on Java and happens frequently.

Name changes/reconfigurations - horrible - rebuild your
trunk from scratch.

There are plenty more cons but it would become a book.

Pros:
Extremely fast failover
CLI! For those who don't like being limited to GUI. On
the con side however, changes need to be made via GUI.
Does EXACTLY what we need it to do... (too long to explain)

Anyone can say "No!!!" But please offer some form of con
for stating no otherwise I tend to go back to the days
when zealotry over things like operating systems was a
high concern. "No!!! You use BSD! Dude! Solaris so rocks
your Linux slash QNX slash BeOS devel!"


=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
J. Oquendo
SGFA, SGFE, C|EH, CNDA, CHFI, OSCP

"Enough research will tend to support your
conclusions." - Arthur Bloch

"A conclusion is the place where you got
tired of thinking" - Arthur Bloch

227C 5D35 7DCB 0893 95AA  4771 1DCE 1FD1 5CCD 6B5E
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x5CCD6B5E