[cisco-voip] making the move from 7D to 10D dialing

[Lelio Fulgenzi]

Our local exchange is going to mandatory 10D dialing in the next year or so, but I wanted to make sure we were ready to go way ahead of that, especially since I was redoing our dialplan anyways. Here's how we did it.

9.@ w/filter that says local-area-code does not exist (this allows immediate routing of all 9.7digit calls.

9.@ w/filter that says local area code = 519

if you simply create a filter that says local area code does exist, then i'm pretty sure you will introduce interdigit delay when someone tries to dial 7 digits.

 
  ----- Original Message ----- 
  From: Chad Whitten 
  To: cisco-voip at puck.nether.net 
  Sent: Monday, December 20, 2004 2:37 PM
  Subject: Re: [cisco-voip] making the move from 7D to 10D dialing


  my 7D route pattern is 9.@ and im not doing any prefix'ing or discard'ing of 
  digits. I have more specific route patterns setup for local exchanges served 
  by other gateways, (9.544XXXX for instance) but the 9.@ is the "default 
  route" for any outgoing calls that dont match one of the more specific rules.

  On Monday 20 December 2004 13:16, you wrote:
  > In your 7D Route Pattern you probably have 9.[2-9]XXXXXX.  You can work
  > with the Called Party Transformation like this.  9.[2-9]XXXXXX "Called
  > Party Transformation" Discard digits PreDot, "Prefix Digits (Outgoing
  > Calls)" 9abc (where abc=local area code)
  >
  > When a user dials a 95551212 the route pattern will present 9abc5551212
  > to the Voice Gateway.
  >
  >
  > -----Original Message-----
  > From: Chad Whitten [mailto:cwhitten at nexband.com]
  > Sent: Monday, December 20, 2004 12:19 PM
  > To: cisco-voip at puck.nether.net
  > Subject: [cisco-voip] making the move from 7D to 10D dialing
  >
  > our local RBOC will be forcing the use of 10D dialing for all local
  > calls starting in March 05.  Right now they are allowing permissive
  > dialing of 10D (you can dial 7 digits or 10 digits).  When I try to dial
  > 10 digits for a local number from our callmanager, i get a fast busy
  > after the 7th digit.
  >
  > i have a pri from the local rboc, terminated in a cisco vg200 using h323
  > to my callmanager.  my route pattern on the callmanager uses a
  > route-filter called 7D dialing that has the "Local-Area-Code" set to
  > "Does-Not-Exist"
  >
  > my dial-peer on the vg200 is
  > dial-peer voice 1 pots
  >  destination-pattern 9T
  >  progress_ind alert enable 8
  >  direct-inward-dial
  >  port 1/0:23
  >
  > Im guessing I just need to create a new route-filter where the
  > "Local-Area-Code" does "Exist"
  >
  > Does anyone have any tips on making this transition as smooth as
  > possible?
  >
  > --
  > Chad Whitten
  > Network Administrator
  > neXband Communications
  > cwhitten at nexband.com
  > 601-944-4801 Phone
  > 601-944-4803 Fax
  >
  > _______________________________________________
  > cisco-voip mailing list
  > cisco-voip at puck.nether.net
  > https://puck.nether.net/mailman/listinfo/cisco-voip

  -- 
  Chad Whitten
  Network Administrator
  neXband Communications
  cwhitten at nexband.com
  601-944-4801 Phone
  601-944-4803 Fax


  _______________________________________________
  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/20041220/f0f1cb32/attachment-0001.html