[cisco-voip] Translation Patterns

[Lucas Zaichkowsky]

Our old dial plan was just extensions. None of the mapped to a DID. The
new dial-plan has DIDs that map directly to the extension. That's why we
had to change extensions, but at the same time, provide support for the
old extensions.

 

 

Lucas Zaichkowsky

System Administrator

CyraCom

(520) 745-9447 ext. 1666

(520) 745-9022 fax

www.cyracom.com

________________________________

From: Brian Henry [mailto:Brian.Henry at apptis.com] 
Sent: Thursday, February 02, 2006 10:22 AM
To: Lucas Zaichkowsky; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Translation Patterns

 

You could do this for an example.

 

This just handles the 2XX to 1XXX coming from the PSTN

Partition:

create an inbound translation partition like - "p-inbndtrans"

Calling Search Space:

create a calling search space like "inbndgw-css" - Inbound Gateway
Calling Search Space

contains p-inbndtrans (I do not know if you have anything else like CER,
etc..)

create a calling search space like "inbndtrans-css" - Inbound
Translation Calling Search Space

p-phones

Your phones calling search space "devpstn-css" should contain

p-phones

(There could be more like an p-outbndtrans, etc..)

p-site(x)pstn

 

Translation Pattern

Pattern: 2XX

Partition: p-inbnd

Numbering Plan - NANP

Calling Search Space - inbndtrans-css

 

Called Party Transformation : 11XX (Since you only have "99"
possibilities from your old dial plan you can only match up one-to-one
unless you create a hunt list that lets say 99 points to but has
extensions 1201, 1355, 1455, 1878 a part of, let me know if I am making
any since.

 

I guess I am little confused in that if you changed your dial plan and
your telco is sending you 4-digits that match your "new" DN's then why
you would need this I do not know.

 

Brian

________________________________

From: Lucas Zaichkowsky [mailto:lzaichkowsky at cyracom.com]
Sent: Thu 2/2/2006 11:53 AM
To: cisco-voip at puck.nether.net
Cc: Brian Henry
Subject: RE: [cisco-voip] Translation Patterns

We're using MGCP. The translation patters are in use in CCM 4.0. For
example, there's a set of them that translate our old dial plan of 2XX
to our new dial plan of 1XXX. So if I try dialing a local number that
starts with 285, it sees the translation pattern for 285 and calls 1653.
I also have about a dozen that translate from one 1XXX extension to
another.

 

Lucas Zaichkowsky

System Administrator

CyraCom

(520) 745-9447 ext. 1666

(520) 745-9022 fax

www.cyracom.com

________________________________

From: Brian Henry [mailto:Brian.Henry at apptis.com] 
Sent: Monday, January 30, 2006 10:20 AM
To: Lucas Zaichkowsky; cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Translation Patterns

 

Tell me how you are using translation patterns? Incoming/Outgoing

Are you using MGCP or H323?

 

Brian

 

________________________________

From: cisco-voip-bounces at puck.nether.net on behalf of Lucas Zaichkowsky
Sent: Mon 1/30/2006 12:15 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Translation Patterns

        I recently installed the VIC for analog lines (EVM-HD-8FXS/DID)
and have it configured in the gateway configuration. I created a "No
Prefix" calling search space with "No prefix" partitions for reaching
local, international, long distance, and toll free numbers. My goal is
to make these lines just like the analog lines we have coming in from
POTS.

        The issue that I'm having is with translation patterns. How can
I make it so these ports don't use them?

Lucas Zaichkowsky
System Administrator
CyraCom
(520) 745-9447 ext. 1666
(520) 745-9022 fax
www.cyracom.com

_______________________________________________
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/20060202/99f4937b/attachment.html