[77982] in North American Network Operators' Group
RE: Vonage complains about VoIP-blocking
daemon@ATHENA.MIT.EDU (Michael Hallgren)
Tue Feb 15 17:44:35 2005
From: "Michael Hallgren" <m.hallgren@free.fr>
To: "'Jay Hennigan'" <jay@west.net>,
"'Hannigan, Martin'" <hannigan@verisign.com>
Cc: "'Eric Gauthier'" <eric@roxanne.org>, <nanog@merit.edu>
Date: Tue, 15 Feb 2005 23:43:54 +0100
In-Reply-To: <Pine.LNX.4.58.0502151403370.17853@ohtf.fo.jrfg.arg>
Errors-To: owner-nanog-outgoing@merit.edu
> >
> >
> > Was that a device trying to phone home and get it's configs?
> > Cisco, Nortel, etc. phone home and get configs via tftp.
> >
> > Vonage doesn't need to phone home for config. The device is
> programmed
> > (router) and it registers with the call manager.
> > If you analyze the transactions it's about 89% SIP and 11% SDP.
>
> Vonage devices initiate an outbound TFTP connection back to
> Vonage to snarf their configs on initial connection and also
> (presumably) on reboot.
>
> Many, many VoIP devices do this, including Cisco phones in
> all major flavors. If an ISP is blocking TFTP originated by
> its customers at the border, this will cause numerous
> problems with many VoIP devices as well as numerous other
> things where a customer needs to initiate a TFTP session over
> the Internet.
>
> Filtering customer-initiated TFTP will cause problems with
> many legitimate applications and devices.
Consequently, should "unlikely or most likely not :)" be filtered
by (I|N)SP, IMHO. Who's (still) using TFTP for fragile tasks...?
Cheers,
mh
>
> --
> Jay Hennigan - CCIE #7880 - Network Administration - jay@west.net
> WestNet: Connecting you to the planet. 805 884-6323 WB6RDV
> NetLojix Communications, Inc. - http://www.netlojix.com/
>
>
