<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.3157" name=GENERATOR>
<STYLE>@font-face {
        font-family: Cambria Math;
}
@font-face {
        font-family: Calibri;
}
@font-face {
        font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
        FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman","serif"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; mso-believe-normal-left: yes
}
LI.MsoNormal {
        FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman","serif"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; mso-believe-normal-left: yes
}
DIV.MsoNormal {
        FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman","serif"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; mso-believe-normal-left: yes
}
A:link {
        COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
        COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
        COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
        COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P {
        FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman","serif"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; mso-style-priority: 99
}
SPAN.EmailStyle18 {
        COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal-reply
}
.MsoChpDefault {
        FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.Section1 {
        page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US style="MARGIN: 3pt 3pt 0.75pt" vLink=purple link=blue
bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Most PBX vendors allow you to forward secondary
lines too. ;)</FONT></DIV>
<DIV> </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=SCASPER@mtb.com href="mailto:SCASPER@mtb.com">STEVEN CASPER</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=c3voip@nc.rr.com
href="mailto:c3voip@nc.rr.com">c3voip</A> ; <A
title=cisco-voip@puck.nether.net
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Wednesday, September 05, 2007 10:04
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [cisco-voip] Unused DN
treatment</DIV>
<DIV><BR></DIV> That is what I am trying to avoid doing. Most traditional
PBX vendors have an option to easily route vacant numbers to various
termination points such as an announcement, attendant or a routable
DN.<BR><BR>>>> "c3voip" <<A
href="mailto:c3voip@nc.rr.com">c3voip@nc.rr.com</A>> 9/5/2007 9:21 AM
>>><BR>
<DIV class=Section1>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">You
can use a translation pattern with wildcards and that should take care of
unused numbers in a block.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">-C<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> <A
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</A>
[mailto:cisco-voip-bounces@puck.nether.net] <B>On Behalf Of </B>STEVEN
CASPER<BR><B>Sent:</B> Wednesday, September 05, 2007 9:09 AM<BR><B>To:</B>
cisco-voip@puck.nether.net<BR><B>Subject:</B> [cisco-voip] Unused DN
treatment<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><BR> In Call Manager is
there any way to define a treatment such as an announcement or routing to an
attendant/Unity for unused numbers in DID blocks that terminate to
MGCP gateways? I could do translation patterns but that would be a real pain
to create and maintain. <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"> <o:p></o:p></P></DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt">Steve Casper<BR>Voice
Technologies<BR>M&T Bank<BR>(410) 347-6026 <o:p></o:p></P>
<P>************************************<BR>This email may contain privileged
and/or confidential information that is intended solely for the use of the
addressee. If you are not the intended recipient or entity, you are strictly
prohibited from disclosing, copying, distributing or using any of the
information contained in the transmission. If you received this communication
in error, please contact the sender immediately and destroy the material in
its entirety, whether electronic or hard copy. This communication may contain
nonpublic personal information about consumers subject to the restrictions of
the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act. You may not directly or
indirectly reuse or disclose such information for any purpose other than to
provide the services for which you are receiving the information.<BR>There are
risks associated with the use of electronic transmission. The sender of this
information does not control the method of transmittal or service providers
and assumes no duty or obligation for the security, receipt, or third party
interception of this
transmission.<BR>************************************<o:p></o:p></P></DIV>
<P>************************************<BR>This email may contain privileged
and/or confidential information that is intended solely for the use of the
addressee. If you are not the intended recipient or entity, you are strictly
prohibited from disclosing, copying, distributing or using any of the
information contained in the transmission. If you received this communication
in error, please contact the sender immediately and destroy the material in
its entirety, whether electronic or hard copy. This communication may contain
nonpublic personal information about consumers subject to the restrictions of
the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act. You may not directly or
indirectly reuse or disclose such information for any purpose other than to
provide the services for which you are receiving the information.<BR>There are
risks associated with the use of electronic transmission. The sender of this
information does not control the method of transmittal or service providers
and assumes no duty or obligation for the security, receipt, or third party
interception of this
transmission.<BR>************************************<BR></P>
<P>
<HR>
<P></P>_______________________________________________<BR>cisco-voip mailing
list<BR>cisco-voip@puck.nether.net<BR>https://puck.nether.net/mailman/listinfo/cisco-voip</BLOCKQUOTE></BODY></HTML>