<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=utf-8">
<META content="MSHTML 6.00.2900.2963" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>I would have to agree. We request 7 digits from the carrier
now, but will likely need to change this to 10 as we have recently had a new
area code introduced. As you know, any change on the carrier side is big $$, so
by sending you all the digits, you can do just about anything you
want.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>Thanks goodness they don't charge you per digit sent.
;)</FONT></DIV>
<DIV> </DIV>
<DIV>--------------------------------------------------------------------------------<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>"I can eat fifty eggs." "Nobody can eat fifty eggs."</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=ealeatherman@gmail.com href="mailto:ealeatherman@gmail.com">Ed
Leatherman</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=GPate@kenttech.com
href="mailto:GPate@kenttech.com">GPate@kenttech.com</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B> <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> Monday, September 18, 2006 8:45
AM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [cisco-voip] Best
Practices</DIV>
<DIV><BR></DIV>Hi Gary,<BR><BR>I think its a good idea to get 10 digits from
the LEC, then you alway have more numbers to work with. At that point you
could take more than 3 digits as significant and process them through a
translation pattern to get them to the extension you want. <BR><BR>For
example, if the called number from LEC is <FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">XXX-593-3183, take 4 digits as
significant and have a 3XXX translation pattern intercept the calls from your
gateway and pass them to the correct partition/phone. You could have a 4XXX
pattern catch calls to </SPAN></FONT><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">593-4183 etc. If you still run
into problems you could take more sig digits and make the pattern more
specific to the telephon exchange or something. <BR><BR>Is there a requirement
that you can only have significant digits set to 3?<BR><BR>Hope that
helps/makes sense on monday morning.<BR></SPAN></FONT><BR>
<DIV><SPAN class=gmail_quote>On 9/17/06, <B class=gmail_sendername>Gary L.
Pate</B> <<A href="mailto:gpate@kenttech.com">gpate@kenttech.com</A>>
wrote:</SPAN>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV>
<DIV lang=EN-US vlink="purple" link="blue">
<DIV>
<P><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">I'm trying to determine a "best
practices" when setting up inbound DID's, extensions, etc. Let me
explain:</SPAN></FONT></P>
<P><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">In most situations I've been
involved in, I've used the last 4 digits of a DID as someone's extension. I
make sure the LEC sends 10 digit's, and I do a significant digits of 4 on
the gateway. This has always worked well, and is easy to configure. However,
in a recent install, this customer was using 3 digit extensions, so I again
had the LEC send 10 digits, and I made the gateway significant digits of 3.
Again, this worked, but the problem was that I started running into to many
situations where I had duplicate 3 digits. For example, a DID might be
593-3183, so the phone extension was 183. But I also had a existing fax line
number that was 444-4183. As you can see, the last 3 digits are the same. I
could not make a translation pattern of 444183 because the gateway was only
sending 3 digits. I ended up having the LEC forward the 4444183 to one of
the DID ranges, and then gave the fax the number from that range, but that
is not what I want to do in the future. </SPAN></FONT></P>
<P><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">I guess what I want to know is
what is the "best practice" going forward? Is it a good idea to have the LEC
send 10 digits, and if so, what should I set on the gateway for significant
digit's, and how should I handle my internal phones that are using the last
four digits of the DID as their extension? I've read a document on using
translation patterns to prefix digits, etc, but I'm not sure if that is the
directions I should go. </SPAN></FONT></P>
<P><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Can someone offer advice on
this, and perhaps provide an example of how to do this with both a 4 digit
example, and a 3 digit example? I really want to have more control over the
lines, and not have to worry much about duplicate numbers or having the LEC
getting involved.</SPAN></FONT></P>
<P><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P><FONT face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Gary</SPAN></FONT><FONT
face=Arial size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT></P></DIV></DIV></DIV></BLOCKQUOTE></DIV>--
<BR>Ed Leatherman<BR>Senior Voice Engineer<BR>West Virginia
University<BR>Telecommunications and Network Operations
<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>