[cisco-voip] Best Practices

[Lelio Fulgenzi]

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.

Thanks goodness they don't charge you per digit sent. ;)

--------------------------------------------------------------------------------
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
"I can eat fifty eggs." "Nobody can eat fifty eggs."
  ----- Original Message ----- 
  From: Ed Leatherman 
  To: GPate at kenttech.com 
  Cc: cisco-voip at puck.nether.net 
  Sent: Monday, September 18, 2006 8:45 AM
  Subject: Re: [cisco-voip] Best Practices


  Hi Gary,

  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. 

  For example, if the called number from LEC is 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 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. 

  Is there a requirement that you can only have significant digits set to 3?

  Hope that helps/makes sense on monday morning.


  On 9/17/06, Gary L. Pate <gpate at kenttech.com> wrote:
    I'm trying to determine a "best practices" when setting up inbound DID's, extensions, etc. Let me explain:



    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. 

    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. 

    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.



    Gary

  -- 
  Ed Leatherman
  Senior Voice Engineer
  West Virginia University
  Telecommunications and Network Operations 


------------------------------------------------------------------------------


  _______________________________________________
  cisco-voip mailing list
  cisco-voip at puck.nether.net
  https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20060918/2c0f80f5/attachment-0001.html