Cisco2851 H323 Called number transformation in Overlap mode.
I have a question regarding the ability to transform a called number coming in overlap mode. I know some posts have been already opened regarding this subsject but I was not able to really find a workaround for this scenario.
The number coming from the PSTN (Germany) switch is '555' and matches the dial-peer below:
dial-peer voice 5 pots
incoming called-number 555
The reason of the troubles are due to the application of the tcl script application under the DP which does not like the prefix 555.
As you can see the prefix 555 is initially present and then the digits are coming one after one in overlap (exemple for called number 5551102531).
3w4d: //24109//Digi:/AFW_M_DigitCollect_Initiate: Overlap Setup sent '555'
At first we were thinking if was due to the bug CSCsh27923 (The IOS is c3825-ipvoicek9-mz.124-3a.bin) but apparently not.
My question is : Is there a way once the dial-peer 5 matched with incoming called number '555' to remove from the called number this prefix ‘555’ in order to have at the end the number 1102531.
I have tested the translation-rule but it does not transform the Caller number. I have heard about using 'trunk group' and then apply the translation-profile to this trunk group. What do you think about it ?
Re: Cisco2851 H323 Called number transformation in Overlap mode.
Thanks for your feedback.
In fact we have noticed the call routing via the TCL script was working fine from German mobile numbers but not from landlines (german provider is Colt).
The diffence noticed in the provider traces were some additional parameters (like higher layer compatibility) through the GSM call. Additionnaly, some ISUP (ISDN User-Part, SS7 signalization) is changed between a landline and GSM.
Anyway, from the debugs and in both cases the same number was submitted to the script (see below) but for one case it works and not for the other.
1102532T = 4=DC_MATCHED_DIALPLAN,
1102532T = 6=DC_INVALID_NUMBER
I cannot understand for the moment exaxctly why our TCL did not work for one case and not in the other case, but we have defined a kind of supplmentar «match-all» rule for the translation-profile applied to the DP (rule 2 /\(^.*)/ /\1/) and it worked in both cases.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...