[cisco-voip] Interoperability - Tagging area code and prefix to outbound calls?

[Madziarczyk, Jonathan]

Thanks for steering me in the right direction!

The Translation pattern makes sense.  If I'm reading you right...

I assume I would only apply it to a partition that is part of my CSS for that specific gateway [Voice GW2]?  I can still keep it in the same RouteGroup?

Not quite sure yet how to get the translationpattern/PT/CSS to trigger only on the PBX calls.  I already know I'll have to make multiple translation patterns because of all the prefixes and area codes on the PBX side.

To throw an additional wrench in the mix...I have some overlapping ranges between the CUCM and the PBX.  If I wild card certain ranges in a translation rule (  78xx -> prefix (123)456  ) to catch 7800-7898, would a number on CUCM outbound (123)456-7899 trigger this rule?  Or would it be ignored because of the (123)456 already in front of it (not an exact match)?

JonM


-----Original Message-----
From: ccieid1ot [mailto:ccieid1ot at gmail.com] 
Sent: Tuesday, December 08, 2009 3:19 PM
To: Madziarczyk, Jonathan
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Interoperability - Tagging area code and prefix to outbound calls?

Translation-patterns, or prepending digits on route list?  You also
have to setup another PT and CSS for calls from the PBX to only used
that translation-patterns.

On Tue, Dec 8, 2009 at 2:18 PM, Madziarczyk, Jonathan
<JMad at cityofevanston.org> wrote:
> So I've added an additional PRI to our outbound route group.  This PRI does
> not have  the feature where all outbound calls are tagged as the main
> number.  On the CUCM side this is not an issue as all calls simply use the
> "External Phone Number Mask" field for the line settings.
>
>
>
> Our legacy PBXs also route through the CUCM to the gateways for PSTN calls
> as well.  They tend to ride the short bus.  Meaning they only send us the
> last 4 digits...which is great for on-net calls, not so good for PSTN calls.
>
>
>
> Our layout is:
>
> [Legacy PBX] <-> [Voice GW1] <-> [CUCM (6.14)] <-> [Voice GW2] <-> [PSTN]
>
>
>
> Is there a way I can get CUCM to tag on the area code/prefix before it heads
> out to the PSTN without messing with calls from CUCM to PSTN?
>
>
>
> Just thinking aloud, I'd like to just add it at Voice GW2 so we stay 4digit
> internally.  However, I'm not sure how that will mess with calls that CUCM
> is sending to PSTN, don't wanna end up with (123)456-(123)456-7890 for a
> (123)456-7890 call when I'm trying to fix 3210 to look like
> (987)654-3210....if that makes sense.
>
>
>
> Ideas?  Has anyone dealt with this?
>
>
>
> I also need to look into the CER side of things (emergency responder/E911)
> for how to identify these numbers for the PSAP.  Which will obviously change
> based on how the number looks when the call goes out.
>
>
>
> JonM
>
>
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>