<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.3268" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>I would suspect that at some point in time,
especially in the event of a hardware failure, the licencing team will have to
issue you a new licence based on the new MAC address. While I don't condone it,
I don't see why you couldn't install the software, do what you have to do, then
call the TAC to say you are upgrading hardware and require a new licence key.
Essentially that's what you are doing anyways.</FONT></DIV>
<DIV> </DIV>
<DIV>Lelio<BR>--------------------------------------------------------------------------------<BR>Lelio
Fulgenzi, B.A.<BR>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario
N1G 2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<BR>Java-Clavis-Domus Theorem: The ability to keep your hands on the home keys
is inversely<BR>related to the amount of caffeine ingested in the last 30
minutes. <BR></DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=aman.chugh@gmail.com href="mailto:aman.chugh@gmail.com">Aman
Chugh</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=cisco-voip@puck.nether.net
href="mailto:cisco-voip@puck.nether.net">Cisco Voip List</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Friday, March 07, 2008 11:11
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [cisco-voip] callmanager
license migration from 4.x to 6.x</DIV>
<DIV><BR></DIV>
<DIV>Thanks all for helping out with this one, I had to work with the
Cisco Account team to get a new license.</DIV>
<DIV> </DIV>
<DIV>Regards,</DIV>
<DIV> </DIV>
<DIV>Aman<BR><BR> </DIV>
<DIV><SPAN class=gmail_quote>On 3/7/08, <B class=gmail_sendername>Jonathan
Charles</B> <<A href="mailto:jonvoip@gmail.com">jonvoip@gmail.com</A>>
wrote:</SPAN>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Delete
all references to it on the publisher, make it look like a<BR>single node,
then add the new Subscriber and create a new CallManager<BR>group with the
new Subscriber.<BR><BR><BR><BR>Jonathan<BR><BR>On Thu, Mar 6, 2008 at 2:41
PM, Justin Steinberg <<A
href="mailto:jsteinberg@gmail.com">jsteinberg@gmail.com</A>>
wrote:<BR>> you have me doubting myself now...<BR>><BR>> Speaking
of the DMA upgrade, I am in the middle of one right now in which I<BR>>
changed hostnames during the 4.x to 6.x upgrade.<BR>><BR>> For some
reason, the new 6.1.1a publisher is still trying to replicate to<BR>> the
old subscriber hostname, even though i deleted it. This has
broken the<BR>> replication to the new subscriber as
well.<BR>><BR>> I have a TAC case open and the first two TAC engineers
have told me that it<BR>> isn't supported to change hostname from 4.x to
6.x......ahhhh<BR>><BR>> Does anyone know what I need to do to get rid
of the old subscriber name? i<BR>> think TAC needs to root in
and edit the sqlhosts maybe?<BR>><BR>><BR>><BR>><BR>><BR>>
On Thu, Mar 6, 2008 at 5:06 PM, Ryan Ratliff <<A
href="mailto:rratliff@cisco.com">rratliff@cisco.com</A>> wrote:<BR>>
><BR>> > I don't think the mac is included in the xml
output. I know for a fact<BR>> the mac address is a separate
field in the web page from the XML output.<BR>> ><BR>> ><BR>>
> Regarding the time wasted I imagine for most people getting DMA
done<BR>> correctly is the longest part. The install itself
will generally be a small<BR>> part of the entire time for the
upgrade.<BR>> ><BR>> ><BR>> > While on this note please,
please if you are considering a 4.x to 5/6.x<BR>> upgrade do not wait to
the last minute to do your DMA and assume everything<BR>> will be
fine. If your system has been in production (or even in a lab)
for<BR>> any amount of time you will most likely have some errors that
need to be<BR>> taken care of and sorting these out can take
time. Running DMA for the<BR>> first time Friday night before
your Saturday upgrade is just asking for<BR>> trouble.<BR>>
><BR>> ><BR>> ><BR>> ><BR>> > -Ryan<BR>>
><BR>> ><BR>> ><BR>> ><BR>> ><BR>> > On Mar
6, 2008, at 4:56 PM, Justin Steinberg wrote:<BR>> > not
exactly.<BR>> ><BR>> > If you install CM6 on your LAB 7835, the
associated DMA license files will<BR>> generate with that lab 7835 MAC
address<BR>> ><BR>> ><BR>> > On Thu, Mar 6, 2008 at 4:45
PM, Linsemier, Matthew<BR>> <<A
href="mailto:MLinsemier@apcapital.com">MLinsemier@apcapital.com</A>>
wrote:<BR>> ><BR>> > > This would great, except for the fact
that you still have to perform the<BR>> > > entire upgrade to get
this result. Again, there are a lot of us out<BR>> > >
there that want to perform a more controlled migration to 6.x than
just<BR>> > > upgrading the entire box in one fell swoop.<BR>>
> ><BR>> > > In our case we have an extra 7835 server in the
lab so if I can't get<BR>> > > licensing through using the SO I can
pop a drive out of our production<BR>> > > Publisher and perform
the upgrade, get the new license without effecting<BR>> > >
actually upgrading our production environment. However, everyone
can't<BR>> > > necessarily do this.<BR>> > ><BR>> >
> There still needs to be an easier way. Would just running a
utility on<BR>> > > a 4.x server that generates a 6.x license (for
Cisco) without upgrading<BR>> > > really make a huge
difference? I understand that they are trying to<BR>> >
> prevent people from "cheating the proverbial licensing system",
but<BR>> > > there are so many workarounds already that it really
doesn't matter in<BR>> > > the grand scheme of things in my humble
opinion.<BR>> > ><BR>> > > Matt<BR>> > ><BR>>
> ><BR>> > ><BR>> > ><BR>> > >
-----Original Message-----<BR>> > > From: Jonathan Charles
[mailto:<A href="mailto:jonvoip@gmail.com">jonvoip@gmail.com</A>]<BR>>
> > Sent: Thursday, March 06, 2008 4:32 PM<BR>> > > To:
Linsemier, Matthew<BR>> > > Cc: Frazee, Timothy; Cisco Voip
List<BR>> > > Subject: Re: [cisco-voip] callmanager license
migration from 4.x to 6.x<BR>> > ><BR>> > > Then, here's
what you do to make life easy<BR>> > ><BR>> > > Use the
DMA tool and upgrade CCM to 6<BR>> > ><BR>> > > Then, get
the license.<BR>> > ><BR>> > > Then blow the CCM6 box away
and build it from scratch<BR>> > ><BR>> > > use the
license you just got.<BR>> > ><BR>> > ><BR>> >
><BR>> > > Jonathan<BR>> > ><BR>> > > On Thu,
Mar 6, 2008 at 3:23 PM, Linsemier, Matthew<BR>> > > <<A
href="mailto:MLinsemier@apcapital.com">MLinsemier@apcapital.com</A>>
wrote:<BR>> > > > We will be doing something similar as the
original poster here within<BR>> > > > the next
month. We are installing a brand new cluster specifically<BR>>
> > > because we don't want to upgrade. At
Networkers Live in 2006, the<BR>> > > Cisco<BR>> > >
> personnel in the CallManager 5.x/6.x licensing breakout
session<BR>> > > stated<BR>> > > > that you
can get licenses generated by providing them with the<BR>> > >
original<BR>> > > > Cisco Sales Order number.<BR>>
> > ><BR>> > > > On a side note, someone
does need to take this back to Cisco to make<BR>> > >
> this process easier. In our case we have almost 5
years of moves,<BR>> > > adds,<BR>> > >
> changes, office closures, multiple upgrades of the database
(from<BR>> > > > versions 3.x to 4.x), old
configurations lingering around, etc. I<BR>> > >
don't<BR>> > > > want this stuff imported into a
fresh clean UCM 6.0 cluster. We want<BR>> > > a<BR>> > >
> virgin start which is why we are planning to install from
scratch. I<BR>> > > > imagine we are not
alone.<BR>> > > ><BR>> > > > Matt<BR>>
> > ><BR>> > > ><BR>> > >
> -----Original Message-----<BR>> > >
> From: <A
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</A><BR>>
> > > [mailto:<A
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</A>]
On Behalf Of Jonathan<BR>> > > > Charles<BR>> >
> ><BR>> > > ><BR>> > > > Sent: Thursday,
March 06, 2008 1:34 PM<BR>> > > > To: Frazee,
Timothy<BR>> > > > Cc: Cisco Voip List<BR>> >
> > Subject: Re: [cisco-voip] callmanager license migration
from 4.x to<BR>> > > 6.x<BR>> > > ><BR>> > >
> No.<BR>> > > ><BR>> > >
> There are only two methods of getting data from CCM 4 to CCM
6<BR>> > > ><BR>> > > > METHOD 1: DMA and
then a clean rebuild of CCM6 referencing the DMA<BR>> > >
file.<BR>> > > ><BR>> > > > METHOD 2:
BAT, export the info from CCM 4, reimport into CCM6<BR>> > >
><BR>> > > ><BR>> > > ><BR>> > >
> Jonathan<BR>> > > ><BR>> > >
> On Thu, Mar 6, 2008 at 12:05 PM, Frazee, Timothy<BR>>
> > > <<A
href="mailto:Timothy_Frazee@adp.com">Timothy_Frazee@adp.com</A>>
wrote:<BR>> > > > > Can you do the upgrade on the
4.x box to 6.x, to get all of your<BR>> > >
> > licenses upgraded and such, then do a
backup/restore from the<BR>> > > > upgraded<BR>>
> > > > 4to6 box to a newly installed 6
server?<BR>> > > > ><BR>> > >
> > A lot of work I know.<BR>> > >
> ><BR>> > > > ><BR>> >
> > > -----Original Message-----<BR>> >
> > > From: <A
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</A><BR>>
> > > > [mailto:<A
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</A>]
On Behalf Of Jonathan<BR>> > >
> > Charles<BR>> > >
> ><BR>> > > > ><BR>> >
> > > Sent: Thursday, March 06, 2008 11:08 AM<BR>>
> > > > To: Aman Chugh<BR>> > >
> > Cc: Cisco Voip List<BR>> > >
> > Subject: Re: [cisco-voip] callmanager
license migration from 4.x<BR>> > > to<BR>> > >
> 6.x<BR>> > > > ><BR>> > >
> > Do the windows upgrade.<BR>> > >
> ><BR>> > >
> > Seriously, you only have two other
options...<BR>> > > > ><BR>> > >
> > Option 1: Buy licenses for
everything.<BR>> > > > ><BR>> > >
> > Options 2: Convince Cisco to give you
one.<BR>> > > > ><BR>> > >
> ><BR>> > > > ><BR>> >
> > > Jonathan<BR>> > >
> ><BR>> > > > > On
Thu, Mar 6, 2008 at 9:23 AM, Aman Chugh <<A
href="mailto:aman.chugh@gmail.com">aman.chugh@gmail.com</A>><BR>> >
> > wrote:<BR>> > >
> > > Thanks all for replying. I am not doing
a backup and restore ,<BR>> > > I<BR>> > >
> have<BR>> > >
> > two<BR>> > >
> > > different clusters one 4.x cluster and
one 6.x cluster , We are<BR>> > > not<BR>> > >
> > using<BR>> > >
> > > the backup of 4.x on 6.x, I build a new
6.x system and did a new<BR>> > >
> > install on<BR>> > >
> > > it, Now we are taking down the 4.x
system and want to migrate<BR>> > > all<BR>> > >
> > phones on<BR>> > >
> > > it to 6.x. How do I get this file as I
am not doing a windows<BR>> > > > upgrade<BR>>
> > > > for<BR>> > >
> > > 6.x. I extracted the tar file which DMA
generates , i could not<BR>> > > > find<BR>> >
> > > any<BR>> > >
> > > license xml fle.Hope I am
clear.<BR>> > > > > ><BR>> >
> > > > Regards,<BR>> > >
> > ><BR>> > >
> > > Aman<BR>> > >
> > ><BR>> > >
> > ><BR>> > >
> > ><BR>> > >
> > ><BR>> > >
> > > On 3/6/08, James Buchanan <<A
href="mailto:jbuchanan@ctiusa.com">jbuchanan@ctiusa.com</A>>
wrote:<BR>> > > > > > >
Hello,<BR>> > > > > > ><BR>>
> > > > > > FYI...it fails because
the first one or two lines of the XML<BR>> > > are<BR>> >
> > > > > actually not XML. Omit those
lines in the copy, and all should<BR>> > > be<BR>> > >
> > well.<BR>> > >
> > > ><BR>> > >
> > > > Thanks,<BR>> > >
> > > ><BR>> > >
> > > > James<BR>> > >
> > > ><BR>> > >
> > > > -----Original Message-----<BR>>
> > > > > > From: <A
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</A><BR>>
> > > > > > [mailto:<A
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</A>]
On Behalf Of<BR>> > > Jonathan<BR>> > >
> > > > Charles<BR>> > >
> > > > Sent: Thursday, March 06, 2008
8:07 AM<BR>> > > > > > > To:
Justin Steinberg<BR>> > > > > > >
Cc: Cisco Voip List<BR>> > > > > >
> Subject: Re: [cisco-voip] callmanager license migration from<BR>>
> > 4.x<BR>> > > > to<BR>> > >
> > 6.x<BR>> > >
> > > ><BR>> > >
> > > > Just a quick note...<BR>> >
> > > > ><BR>> > >
> > > > The last four times I have done
this, it has failed and said,<BR>> > >
> > 'invalid<BR>> > >
> > > > XML file'... I then sent it to <A
href="mailto:licensing@cisco.com">licensing@cisco.com</A> and got a<BR>>
> > > license<BR>> > >
> > > > in a few hours... no biggie... but
expect it to fail...<BR>> > > > > >
><BR>> > > > > > ><BR>>
> > > > > ><BR>> > >
> > > ><BR>> > >
> > > > JOnathan<BR>> > >
> > > ><BR>> > >
> > > > On Thu, Mar 6, 2008 at 6:51 AM,
Justin Steinberg<BR>> > > > > <<A
href="mailto:jsteinberg@gmail.com">jsteinberg@gmail.com</A>><BR>> >
> > > > > wrote:<BR>> > >
> > > > > on the new cm6 system, login
to ccmadmin goto<BR>> > >
> > system>licensing>license<BR>> >
> > > > > file<BR>> > >
> > > > > upload. You can
download the xml file there and then you<BR>> > > will<BR>> >
> > > need to<BR>> > >
> > > > > upload that file to cisco's
website and they will then email<BR>> > > > you
a<BR>> > > > > > >
permanent<BR>> > > > > > > >
xml license file.<BR>> > > > > >
> ><BR>> > > > > > > >
The above process will give you:<BR>> > >
> > > > > 1) DLU's for your
system<BR>> > > > > > > > 2)
CM node licenses<BR>> > > > > > >
><BR>> > > > > > > >
However, you will need to use the PUT to order a CM4to6<BR>> > >
upgrade<BR>> > > > > and<BR>> >
> > > > > they<BR>> > >
> > > > > will ship you a PAK that you
can use to license the CM6<BR>> > > feature<BR>> > >
> > > > license.<BR>> > >
> > > > > Without this feature license
the CM service will not start.<BR>> > >
> > > > ><BR>> > >
> > > > > Justin<BR>> > >
> > > > ><BR>> > >
> > > > ><BR>> > >
> > > > ><BR>> > >
> > > > > On Thu, Mar 6, 2008 at 5:36
AM, Aman Chugh<BR>> > > > <<A
href="mailto:aman.chugh@gmail.com">aman.chugh@gmail.com</A>><BR>> >
> > > > > wrote:<BR>> > >
> > > > ><BR>> > >
> > > > > ><BR>> > >
> > > > > ><BR>> > >
> > > > > ><BR>> > >
> > > > > ><BR>> > >
> > > > > > I need some help with
this, I am migrating licenses from<BR>> > > ccm<BR>> > >
> 4.x<BR>> > >
> > to<BR>> > >
> > > > 6.x, I<BR>> > >
> > > > > have ran DMA and I am looking
for the intermediary license<BR>> > > file<BR>> > >
> > which<BR>> > >
> > > > all<BR>> > >
> > > > > the documents talk about, I
am not doing a complete restore<BR>> > > of<BR>> > >
> 4.x<BR>> > >
> > on<BR>> > >
> > > > 6 .x ,<BR>> > >
> > > > > I just need licenses to be
migrated from the old system to<BR>> > > the<BR>> > >
> new<BR>> > > > > >
> one. I<BR>> > > > > > > >
have looked at tar file which DMA creates but can't find<BR>> > >
that<BR>> > > > xml<BR>> > >
> > file<BR>> > >
> > > > > needed for new license
generation.<BR>> > > > > > > >
><BR>> > > > > > > > >
TIA<BR>> > > > > > > >
><BR>> > > > > > > > >
Aman<BR>> > > > > > > >
><BR>> > > > > > > >
><BR>> > > > > > > > >
_______________________________________________<BR>> > >
> > > > > > cisco-voip mailing
list<BR>> > > > > > > > >
<A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>>
> > > > > > > > <A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>>
> > > > > > > ><BR>> >
> > > > > > ><BR>> > >
> > > > ><BR>> > >
> > > > ><BR>> > >
> > > > >
_______________________________________________<BR>> > >
> > > > > cisco-voip mailing
list<BR>> > > > > > >
> <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>>
> > > > > > > <A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>>
> > > > > > ><BR>> > >
> > > > ><BR>> > >
> > > >
_______________________________________________<BR>> > >
> > > > cisco-voip mailing list<BR>>
> > > > > > <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>>
> > > > > > <A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>>
> > > > > >
_______________________________________________<BR>> > >
> > > > cisco-voip mailing list<BR>>
> > > > > > <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>>
> > > > > > <A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>>
> > > > > ><BR>> > >
> > ><BR>> > >
> > ><BR>> > >
> > >
_______________________________________________<BR>> > >
> > > cisco-voip mailing
list<BR>> > > > > > <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>>
> > > > > <A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>>
> > > > ><BR>> > >
> > ><BR>> > >
> > _______________________________________________<BR>>
> > > > cisco-voip mailing list<BR>>
> > > > <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>>
> > > > <A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>>
> > > ><BR>> > >
> ><BR>> > > > > This
message and any attachments are intended only for the use of<BR>> >
> the<BR>> > > > addressee and may contain
information that is privileged and<BR>> > >
> confidential. If the reader of the message is not the
intended<BR>> > > recipient<BR>> > > > or an
authorized representative of the intended recipient, you are<BR>> >
> > hereby notified that any dissemination of this
communication is<BR>> > > strictly<BR>> > >
> prohibited. If you have received this communication in
error, please<BR>> > > > notify us immediately by
e-mail and delete the message and any<BR>> > >
> attachments from your system.<BR>> > >
> ><BR>> > >
> _______________________________________________<BR>> >
> > cisco-voip mailing list<BR>> > >
> <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>>
> > > <A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>>
> > > CONFIDENTIALITY STATEMENT<BR>> > >
> This communication and any attachments are CONFIDENTIAL and
may<BR>> > > > be protected by one or more legal
privileges. It is intended<BR>> > > > solely for the
use of the addressee identified above. If you<BR>> > >
> are not the intended recipient, any use, disclosure,
copying<BR>> > > > or distribution of this
communication is UNAUTHORIZED. Neither<BR>> > >
> this information block, the typed name of the sender,
nor<BR>> > > > anything else in this message is
intended to constitute an<BR>> > > > electronic
signature unless a specific statement to the<BR>> > >
> contrary is included in this message. If you have received
this<BR>> > > > communication in error, please
immediately contact me and delete<BR>> > > > this
communication from your computer. Thank you.<BR>> > > ><BR>>
> > CONFIDENTIALITY STATEMENT<BR>> > > This communication and
any attachments are CONFIDENTIAL and may<BR>> > > be protected by
one or more legal privileges. It is intended<BR>> > > solely for
the use of the addressee identified above. If you<BR>> > > are not
the intended recipient, any use, disclosure, copying<BR>> > > or
distribution of this communication is UNAUTHORIZED. Neither<BR>> >
> this information block, the typed name of the sender, nor<BR>> >
> anything else in this message is intended to constitute an<BR>> >
> electronic signature unless a specific statement to the<BR>> >
> contrary is included in this message. If you have received this<BR>>
> > communication in error, please immediately contact me and
delete<BR>> > > this communication from your computer. Thank
you.<BR>> > >
_______________________________________________<BR>> > > cisco-voip
mailing list<BR>> > > <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>>
> > <A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>>
> ><BR>> ><BR>> ><BR>> >
_______________________________________________<BR>> > cisco-voip
mailing list<BR>> > <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>>
> <A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>>
><BR>><BR>><BR>>
_______________________________________________<BR>> cisco-voip
mailing list<BR>> <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>> <A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>><BR>><BR>_______________________________________________<BR>cisco-voip
mailing list<BR><A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR></BLOCKQUOTE></DIV><BR>
<P>
<HR>
<P></P>_______________________________________________<BR>cisco-voip mailing
list<BR>cisco-voip@puck.nether.net<BR>https://puck.nether.net/mailman/listinfo/cisco-voip<BR></BLOCKQUOTE></BODY></HTML>