<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2800.1515" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV dir=ltr align=left><SPAN class=937200423-23032006><FONT face=Arial
color=#0000ff size=2>Also keep in mind, this has changed significantly in
5.x. DN's are essentially separate now from the phones (unless something
changed since early on).</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=937200423-23032006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=937200423-23032006><FONT face=Arial
color=#0000ff size=2>When I first saw CM 5, you had to create the DN's under the
route menu, then assign them to a phone. If you deleted the phone, the DN
still appeared in the DN list, and had to be deleted separately, but at least it
was visible all the time.</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <B>On Behalf Of </B>Lelio
Fulgenzi<BR><B>Sent:</B> Thursday, March 23, 2006 3:05 PM<BR><B>To:</B> Kevin
Thorngren<BR><B>Cc:</B> cisco-voip@puck.nether.net; Voll, Scott; Matt Slaga
(US)<BR><B>Subject:</B> Re: [cisco-voip] unassigned DNs in
4.x<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><FONT size=2>No offense to anyone on the list (or to my account team) but
putting a FR forward seems to be a fruitless endeavour. No feed back
whatsoever on the status of them or even if they are even entered in the
system. Very dissappointing in that respect.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>I look towards CIPTUG for feaure requests. It seems a little
more 'structured' over there.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>I also think it seems silly to have to ask for a feature
request for something that is obviously a fix. In this case, not so much, but
forwarding secondary lines in particular. Especially when that has been filed
as a bug for four years. :(</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>
<DIV><FONT size=2>serenity now
<DIV><FONT size=2>serenity now
<DIV><FONT size=2>serenity
now</FONT></DIV></FONT></DIV></FONT></DIV></FONT>--------------------------------------------------------------------------------<BR>Lelio
Fulgenzi, B.A.<BR>Network Analyst (CCS) * University of Guelph * Guelph,
Ontario N1G 2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<BR>Sanity First : Number of days with fewer than<BR>50 messages in my inbox
at the end of the day:
14</DIV>
<BLOCKQUOTE dir=ltr
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=kthorngr@cisco.com href="mailto:kthorngr@cisco.com">Kevin
Thorngren</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=lelio@uoguelph.ca
href="mailto:lelio@uoguelph.ca">Lelio Fulgenzi</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=Matt.Slaga@us.didata.com
href="mailto:Matt.Slaga@us.didata.com">Matt Slaga (US)</A> ; <A
title=scall@metreos.com href="mailto:scall@metreos.com">Seth Call</A> ; <A
title=cisco-voip@puck.nether.net
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A> ; <A
title=Scott.Voll@wesd.org href="mailto:Scott.Voll@wesd.org">Voll, Scott</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Thursday, March 23, 2006 3:59
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [cisco-voip] unassigned
DNs in 4.x</DIV>
<DIV><BR></DIV>I agree that Unassigned DN's can be a pain. I have run into
issues where I forgot I had added and deleted a DN to only get an error when
adding it again. A service parameter or other mechanism to control this
would be a good idea. I am sure this is said quite often but if there is
something you would like changed work with your Cisco account team to create
a feature request for this change. There is no guarantee that the feature
will be added but if multiple customers add their business case to the
feature request then it may help to increase the chances of implementing the
feature. Being a Cisco employee, there is not much pull I have with
development :-)<BR><BR>Kevin<BR><BR>On Mar 23, 2006, at 3:28 PM, Lelio
Fulgenzi wrote:<BR><BR>
<BLOCKQUOTE><?smaller>I think there should be service parameters for stuff
like this.
;)<?/smaller><BR> <BR>--------------------------------------------------------------------------------<BR>Lelio
Fulgenzi, B.A.<BR>Network Analyst (CCS) * University of Guelph * Guelph,
Ontario N1G 2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<BR>Sanity
First : Number of days with fewer than<BR>50 messages in my inbox at the
end of the day: 14<BR>
<BLOCKQUOTE><?fontfamily><?param Arial><?x-tad-bigger>----- Original
Message -----<?/x-tad-bigger><?/fontfamily><BR><B><?fontfamily><?param Arial><?x-tad-bigger>From:<?/x-tad-bigger><?/fontfamily></B><?fontfamily><?param Arial><?x-tad-bigger>
<?/x-tad-bigger><?color><?param 0000,0000,EEEE><?x-tad-bigger>Kevin
Thorngren<?/x-tad-bigger><?/color><?x-tad-bigger> <?/x-tad-bigger><?/fontfamily><BR><B><?fontfamily><?param Arial><?x-tad-bigger>To:<?/x-tad-bigger><?/fontfamily></B><?fontfamily><?param Arial><?x-tad-bigger>
<?/x-tad-bigger><?color><?param 0000,0000,EEEE><?x-tad-bigger>Voll,
Scott<?/x-tad-bigger><?/color><?x-tad-bigger> <?/x-tad-bigger><?/fontfamily><BR><B><?fontfamily><?param Arial><?x-tad-bigger>Cc:<?/x-tad-bigger><?/fontfamily></B><?fontfamily><?param Arial><?x-tad-bigger>
<?/x-tad-bigger><?color><?param 0000,0000,EEEE><?x-tad-bigger>Matt Slaga
(US)<?/x-tad-bigger><?/color><?x-tad-bigger> ; <?/x-tad-bigger><?color><?param 0000,0000,EEEE><?x-tad-bigger>Seth Call<?/x-tad-bigger><?/color><?x-tad-bigger> ; <?/x-tad-bigger><?color><?param 0000,0000,EEEE><?x-tad-bigger>cisco-voip@puck.nether.net<?/x-tad-bigger><?/color><?x-tad-bigger>
; <?/x-tad-bigger><?color><?param 0000,0000,EEEE><?x-tad-bigger>Lelio
Fulgenzi<?/x-tad-bigger><?/color><?x-tad-bigger> <?/x-tad-bigger><?/fontfamily><BR><B><?fontfamily><?param Arial><?x-tad-bigger>Sent:<?/x-tad-bigger><?/fontfamily></B><?fontfamily><?param Arial><?x-tad-bigger>
Thursday, March 23, 2006 2:55 PM<?/x-tad-bigger><?/fontfamily><BR><B><?fontfamily><?param Arial><?x-tad-bigger>Subject:<?/x-tad-bigger><?/fontfamily></B><?fontfamily><?param Arial><?x-tad-bigger>
Re: [cisco-voip] unassigned DNs in
4.x<?/x-tad-bigger><?/fontfamily><BR><BR>No, I wouldn't like to chime in
;-)<BR><BR>Actually this URL explains why this feature was added:<BR><?color><?param 0000,0000,EEEE>http://www.ciscotaccc.com/voice/showcase?case=K91031031<?/color><BR><BR>"Unassigned
DNs allow customers to continue forwarding to voice mail or another
destination for DNs that are no longer assigned to devices. This happens
often when employees are reassigned or terminated."<BR><BR>We had
requirements from some customers for this type of
feature.<BR><BR>HTH,<BR>Kevin<BR>On Mar 23, 2006, at 1:10 PM, Voll,
Scott wrote:<BR><BR>
<BLOCKQUOTE><BR>Wes, Ryan, or Kevin like to chime
in?<BR> <BR>Scott<BR> <BR>PS. I’m with you
all<BR> <BR><BR><B>From:</B>
<?color><?param 0000,0000,EEEE>cisco-voip-bounces@puck.nether.net<?/color>
[mailto:cisco-voip-bounces@puck.nether.net] <B>On Behalf Of </B>Lelio
Fulgenzi<BR><B>Sent:</B> Thursday, March 23, 2006 8:21
AM<BR><B>To:</B> Matt Slaga (US); Seth Call;
cisco-voip@puck.nether.net<BR><B>Subject:</B> Re: [cisco-voip]
unassigned DNs in 4.x<BR> <BR>You have to remember that some
people are doing in-house management, so more work equals less $$.
:(<BR> <BR>--------------------------------------------------------------------------------<BR>Lelio
Fulgenzi, B.A.<BR>Network Analyst (CCS) * University of Guelph *
Guelph, Ontario N1G 2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<BR>Sanity
First : Number of days with fewer than<BR>50 messages in my inbox at
the end of the day:
14<BR>
<BLOCKQUOTE>----- Original Message -----<BR><B>From:</B> Matt Slaga
(US)<BR><B>To:</B> Seth Call ; Lelio Fulgenzi ;
cisco-voip@puck.nether.net<BR><B>Sent:</B> Thursday, March 23, 2006
10:31 AM<BR><B>Subject:</B> RE: [cisco-voip] unassigned DNs in
4.x<BR> <BR>Well, it does create more work for people like
us.... That equals $$....<BR> <BR><BR><BR><B>From:</B>
cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <B>On Behalf Of </B>Seth
Call<BR><B>Sent:</B> Thursday, March 23, 2006 9:25 AM<BR><B>To:</B>
Lelio Fulgenzi; cisco-voip@puck.nether.net<BR><B>Subject:</B> Re:
[cisco-voip] unassigned DNs in 4.x<BR>There has to be a good reason
for it, but I sure wish I knew what it was… maybe line creation is
expensive? And so if you are mucking around with lines and
partitions a lot…<BR> <BR>I don’t like it either,
though<BR> <BR><BR><B>From:</B>
cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <B>On Behalf Of
</B>Lelio Fulgenzi<BR><B>Sent:</B> Thursday, March 23, 2006 8:20
AM<BR><B>To:</B> cisco-voip@puck.nether.net<BR><B>Subject:</B>
[cisco-voip] unassigned DNs in 4.x<BR> <BR>ok, who else doesn't
like how DNs hang around after you delete them? i can understand an
actual deletion, but if i create a DN in partition A and move it to
partition B, voila, an unassigned DN in partition A now
exists.<BR> <BR>ugh.<BR> <BR>--------------------------------------------------------------------------------<BR>Lelio
Fulgenzi, B.A.<BR>Network Analyst (CCS) * University of Guelph *
Guelph, Ontario N1G 2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<BR>Sanity
First : Number of days with fewer than<BR>50 messages in my inbox at
the end of the day:
14<BR><BR> <BR><BR><BR><B>Disclaimer:</B><BR><BR><B>This e-mail
communication and any attachments may contain</B><BR><B>confidential
and privileged information and is for use by
the</B><BR><B>designated addressee(s) named above only. If you are
not the</B><BR><B>intended addressee, you are hereby notified that
you have received</B><BR><B>this communication in error and that any
use or reproduction of</B><BR><B>this email or its contents is
strictly prohibited and may be</B><BR><B>unlawful. If you have
received this communication in error, please</B><BR><B>notify us
immediately by replying to this message and deleting
it</B><BR><B>from your computer. Thank
you.</B><BR></BLOCKQUOTE>_______________________________________________<BR>cisco-voip
mailing
list<BR>cisco-voip@puck.nether.net<BR>https://puck.nether.net/mailman/listinfo/cisco-voip<BR></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>