[asterisk-biz] Verizon v Vonage

[Brian Fertig]

http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&p=1&u=%2Fn
etahtml%2FPTO%2Fsearch-bool.html&r=0&f=S&l=50&TERM1=Verizon&FIELD1=&co1=AND&
TERM2=&FIELD2=&d=PTXT

This is where I read up on some of what I thought could be the patents 
they
were talking about in the article.

--
........::::::::::.........
Brian Fertig
Sr. Data & Telecom Engineer
Molten, Inc.
Delaware Office

|-----Original Message-----
|From: asterisk-biz-bounces at lists.digium.com [mailto:asterisk-biz-
|bounces at lists.digium.com] On Behalf Of Trevor G. Hammonds
|Sent: Wednesday, February 21, 2007 11:48 AM
|To: 'Commercial and Business-Oriented Asterisk Discussion'
|Subject: RE: [asterisk-biz] Verizon v Vonage
|
|Brian,
|Do you have the referenced patent numbers?  The USA Today article did
|not
|mention the, and a VYER cursory search did not reveal any more
|information.
|
|
|		Sincerely,
|		Trevor Hammonds
|
|> -----Original Message-----
|> From: asterisk-biz-bounces at lists.digium.com [mailto:asterisk-biz-
|> bounces at lists.digium.com] On Behalf Of Brian Fertig
|> Sent: Wednesday, February 21, 2007 6:27 AM
|> To: email at mattruby.com; 'Commercial and Business-Oriented Asterisk
|> Discussion'
|> Subject: RE: [asterisk-biz] Verizon v Vonage
|>
|> I read up on Verizon's claims against Vonage and found their patents
|> are
|> in
|> no way shape or form precise enough to hold any weight.  They are so
|> broad
|> that
|> Asterisk could never work around the patens of Verizon but just remove
|> them
|> instead.
|>
|> --
|> ........::::::::::.........
|> Brian Fertig
|> Sr. Data & Telecom Engineer
|> Molten, Inc.
|> Delaware Office
|>
|>
|> |-----Original Message-----
|> |From: asterisk-biz-bounces at lists.digium.com [mailto:asterisk-biz-
|> |bounces at lists.digium.com] On Behalf Of Matthew Rubenstein
|> |Sent: Wednesday, February 21, 2007 9:08 AM
|> |To: Asterisk-Biz
|> |Subject: [asterisk-biz] Verizon v Vonage
|> |
|> |	Verizon is suing Vonage for violating 48 patent claims, to shut
|> |Vonage
|> |down:
|> |http://www.usatoday.com/printedition/money/20070220/vonage.art.htm .
|> If
|> |Verizon is granted a monopoly on operating under those patents, what
|> |other VoIP services will have to shut down? Is Asterisk either
|immune,
|> |or able to change quickly enough to operate outside these patents?
|> |--
|> |
|> |(C) Matthew Rubenstein
|> |
|
|_______________________________________________
|--Bandwidth and Colocation provided by Easynews.com --
|
|asterisk-biz mailing list
|To UNSUBSCRIBE or update options visit:
|   http://lists.digium.com/mailman/listinfo/asterisk-biz





"The information in this electronic mail ("e-mail") message may contain 
information that is confidential and/or privileged, or may otherwise be 
protected by work product or other legal rules. It is solely for the use 
of the individual(s) or the entity(ies) originally intended. Access to 
this electronic mail message by anyone else is unauthorized. If you are 
not the intended recipient, be advised that any unauthorized review, 
disclosure, copying, distribution or use of this information, or any 
action taken or omitted to be taken in reliance on it, is prohibited and 
may be unlawful. Please notify the sender immediately if you have received 
this electronic message by mistake, and destroy all copies of the original 
message."


"The sender believes that this e-mail and any attachments were free of any 
virus, worm, Trojan horse, malicious code and/or other contaminants when 
sent. E-mail transmissions cannot be guaranteed to be secure or 
error-free, so this message and its attachments could have been infected, 
corrupted or made incomplete during transmission. By reading the message 
and opening any attachments, the recipient accepts full responsibility for 
any viruses or other defects that may arise, and for taking remedial 
action relating to such viruses and other defects. Neither Molten Inc nor 
any of its affiliated entities is liable for any loss or damage arising in 
any way from, or for errors or omissions in the contents of, this message 
or its attachments."