[cisco-voip] Translation patterns

[Klein Peter]

Hi

Since you are using T302 timer anyway, why not try to attach a "!" to the 02222222 pattern. ! matches Zero or more digits. Since the other match 0222222[1-9]X will be more specific that will be used in all cases when any other digits are added. If you just dial the 0222222 and wait for T302, the pattern with ! will be the only match and you will get what you want, I guess...

If however I'm misunderstanding you and you really want to use overlap sending to avoid T302, then this will not work. I personally always use overlap sending with MGCP gateways so for me it would not work.

/Peter

-----Ursprungligt meddelande-----
Från: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] För Fedorov, Konstantin
Skickat: Thursday, February 22, 2007 8:48 PM
Till: Alexander Wolf; cisco-voip at puck-nether.net
Ämne: Re: [cisco-voip] Translation patterns

Hi Alex.

I think the best way to do this - via IPIP GW.

Of cause , you can try append some prefixes to the PSTN GW ( direction
to CCM ), to differentiate translation patterns, But this made very hard
config.



-----------------------
Sincerely Yours,
Konstantin Fedorov
-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Alexander Wolf
Sent: Thursday, February 22, 2007 8:04 PM
To: cisco-voip at puck-nether.net
Subject: [cisco-voip] Translation patterns

Hi !
 
I have the following problem (CCM 4.1(3) SR3c):

Multiple tenants on the same cluster with overlapping numplans, strictly
seperated in different partitions with each tenant having one (or more)
H.323 gateways for PSTN access.
Each tenant doesn't even notice, that other tenants do even exist
(beside some restrictions, that they share e.g. the T302 timer
settings).
Calls between tenants travel trough PSTN and appear as a completely new
call for CCM.

Now several tenants (a group of villages) have decided that they want
calls between them to travel through WAN (they're all in some MPLS-VPN,
don't ask me for details, nothing where I'm an expert in) to save costs.

Ok, no problem I thought. Some translation patterns with the right
transformations and line/name presetation restrictions will do the job.
I was right, they did the job, mostly ......

Consider two tenants, each with one location with one H.323 gateway for
PSTN access
Tenant A's gateway has the PSTN Number 111 11111
Tenant B's gateway has the PSTN Number 222 22222

Therefore to reach tenant B from A I insert a translation pattern
022222222.[1-9]X? which discards the predot digits and matches (with the
right CSS set) the destination tenants directory number - works
perfectly, no problems (Don't mind the '0' - it's the PSTN access
pattern here in Austria).

But now my big problem - calls from PSTN without an extension attached
are normally directed to an operator number (by translation-rule or tcl
voice application at the router).
To emulate this behaviour I need another pattern 022222222 which
translates to this operator number, because of course no gateway is
involved any more.
When I insert this second pattern, everything seems fine (even dialed
number analyzer says "thumbs up - works as expected") - till I tried it
with real phones.

The problem now is - the "022222222" matches all dialed patterns -
before I can even dial the extension of the destination number, the
replacement takes place and I'm at the operator of the destination
tenant (no T302 timer or something).
Tried everthing (022222222.[1-9]X? in another partition earlier in CSS
etc.), nothing helps.

Any thoughts would be appreciated?

Regards,
Alex



_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip



_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip