Cisco CME / 7925G: Leading zero stripped in Placed Calls list

Hi,
we are using a "0" as a prefix to dialout to the PSTN (ISDN PRI) on our CME router (2921).
The leading 0 will be stripped off  on the dial peer via a voice translation rule:
voice translation-rule 11
 rule 1 /^00\(.*\)/ /0\1/
voice translation-profile OUTGOING_TRANSLATION
 translate called 11
Problem: When we dial an external number (including the leading 0) on the 7925G phone, it stores this dialed number
without the leading 0 in the "placed calls" list.
When you want to pick up and call a number later from that list, it won´t work, because the leading 0 is missing.
Does anyone know how to fix this?
Many thanks
Heinz

Hi Heinz,I don't know if this kind of manipulation is available in CME or not however as per your comments, you can give a try to following.As you are stripping leading '0' at dial-peer level, now while dialing the number from logs, you can again prefix '0' at ephone-dn level at incoming call leg. Use following translation rule in one of the phone and see if it works for you. This rule will work completely depends on number patterns dialed by your users. While dialing the number initially by prefixing '00', if there is a possibility to dial third digit as '0', this rule won't work.
rule 1 /^0\([^0]\)\(.*\)/ /00\1\2/Now if you initially dial 009925801882, you are stripping initial '0'. This won't match the number at ephone-dn level and only match at dial-peer level. In logs, you are seeing 09925801882. Now when you dial this number from logs viz 09925801882, translation profile at ephone-dn level will change it to 009925801882 and will again strip '0' at dial-peer level. ThanksVivek  

Similar Messages

  • Incoming calls get stripped of leading zeros and I don't know why...

    Hi,
    our UC560 setup is now running for quite some time. But there is still this one issue that is bugging for some time now. 
    We have two ISDN DID trunks for Incoming / Outgoing calls. 
    After my very basic setup I noticed that all caller IDs get their leading zero stripped. In Germany we use the "0" as first digit of the area-code and "00" as the international code.
    I thought a quick fix would be to just add a Call-Back Rule within CCA to add a leading 0. This works for national calls as the transmitted caller-id always includes the area-code even for local calls.
    However If I receive an international call (what happens quite often recently) I'm not getting the expected "00" in front of the number but also only a single "0".
    I took a look at all translation-rules that are configured, but I couldn't find any rule that just deletes all leading zeros from the incoming number :( What's happening there?
    voice translation-rule 4
    rule 1 /301/ /55555529/
    rule 2 /302/ /55555529/
    rule 13 /^2\(..\)$/ /5555552\1/
    rule 14 /^1\(..\)$/ /5555551\1/
    rule 15 /^.*$/ /+49895555550/
    voice translation-rule 5
    rule 15 /^...$/ /123456/
    voice translation-rule 7
    rule 1 /555555201/ /201/
    rule 2 /555555202/ /202/
    rule 3 /555555203/ /203/
    rule 4 /555555204/ /204/
    rule 5 /555555205/ /205/
    rule 6 /555555206/ /206/
    rule 7 /555555207/ /207/
    rule 8 /555555208/ /208/
    rule 9 /555555209/ /209/
    voice translation-rule 8
    rule 1 /555555210/ /210/
    rule 2 /555555211/ /211/
    rule 3 /555555212/ /212/
    rule 4 /555555213/ /213/
    rule 5 /555555214/ /214/
    rule 6 /555555215/ /215/
    rule 7 /555555216/ /216/
    rule 8 /555555217/ /217/
    rule 9 /555555218/ /218/
    rule 10 /555555219/ /219/
    voice translation-rule 9
    rule 1 /555555220/ /220/
    rule 2 /555555221/ /221/
    rule 3 /555555222/ /222/
    rule 4 /555555223/ /223/
    rule 5 /555555224/ /224/
    rule 6 /555555225/ /225/
    rule 7 /555555226/ /226/
    rule 8 /555555227/ /227/
    rule 9 /555555228/ /228/
    rule 10 /555555229/ /229/
    voice translation-rule 10
    rule 1 /55555529/ /511/
    voice translation-rule 12
    rule 1 /55555504/ /112/
    voice translation-rule 13
    rule 1 /555555260/ /996/
    voice translation-rule 14
    rule 1 /55555501/ /444/
    voice translation-rule 15
    rule 1 /55555502/ /111/
    voice translation-rule 18
    rule 1 /555555200/ /444/
    voice translation-rule 19
    rule 1 /555555100/ /444/
    voice translation-rule 20
    rule 1 /55555500/ /444/
    voice translation-rule 21
    rule 1 /5555550/ /444/
    voice translation-rule 23
    rule 1 /555555110/ /110/
    rule 2 /555555111/ /111/
    rule 3 /555555112/ /112/
    rule 4 /555555113/ /113/
    rule 5 /555555114/ /114/
    rule 6 /555555115/ /115/
    rule 7 /555555116/ /116/
    rule 8 /555555117/ /117/
    rule 9 /555555118/ /118/
    rule 10 /555555119/ /119/
    voice translation-rule 24
    rule 1 /555555120/ /120/
    rule 2 /555555121/ /121/
    rule 3 /555555122/ /122/
    rule 4 /555555123/ /123/
    rule 5 /555555124/ /124/
    rule 6 /555555125/ /125/
    rule 7 /555555126/ /126/
    rule 8 /555555127/ /127/
    rule 9 /555555128/ /128/
    rule 10 /555555129/ /129/
    voice translation-rule 25
    rule 1 /555555130/ /130/
    rule 2 /555555131/ /131/
    rule 3 /555555132/ /132/
    rule 4 /555555133/ /133/
    rule 5 /555555134/ /134/
    rule 6 /555555135/ /135/
    rule 7 /555555136/ /136/
    rule 8 /555555137/ /137/
    rule 9 /555555138/ /138/
    rule 10 /555555139/ /139/
    voice translation-rule 26
    rule 1 /555555140/ /140/
    rule 2 /555555141/ /141/
    rule 3 /555555142/ /142/
    rule 4 /555555143/ /143/
    rule 5 /555555144/ /144/
    rule 6 /555555145/ /145/
    rule 7 /555555146/ /146/
    rule 8 /555555147/ /147/
    rule 9 /555555148/ /148/
    rule 10 /555555149/ /149/
    voice translation-rule 27
    rule 1 /555555150/ /150/
    rule 2 /555555151/ /151/
    rule 3 /555555152/ /152/
    rule 4 /555555153/ /153/
    rule 5 /555555154/ /154/
    rule 6 /555555155/ /155/
    rule 7 /555555156/ /156/
    rule 8 /555555157/ /157/
    rule 9 /555555158/ /158/
    rule 10 /555555159/ /159/
    voice translation-rule 28
    rule 1 /555555160/ /160/
    rule 2 /555555161/ /161/
    rule 3 /555555162/ /162/
    rule 4 /555555163/ /163/
    rule 5 /555555164/ /164/
    rule 6 /555555165/ /165/
    rule 7 /555555166/ /166/
    rule 8 /555555167/ /167/
    rule 9 /555555168/ /168/
    rule 10 /555555169/ /169/
    voice translation-rule 29
    rule 1 /555555170/ /170/
    rule 2 /555555171/ /171/
    rule 3 /555555172/ /172/
    rule 4 /555555173/ /173/
    rule 5 /555555174/ /174/
    rule 6 /555555175/ /175/
    rule 7 /555555176/ /176/
    rule 8 /555555177/ /177/
    rule 9 /555555178/ /178/
    rule 10 /555555179/ /179/
    voice translation-rule 30
    rule 1 /555555180/ /180/
    rule 2 /555555181/ /181/
    rule 3 /555555182/ /182/
    rule 4 /555555183/ /183/
    rule 5 /555555184/ /184/
    rule 6 /555555185/ /185/
    rule 7 /555555186/ /186/
    rule 8 /555555187/ /187/
    rule 9 /555555188/ /188/
    rule 10 /555555189/ /189/
    voice translation-rule 31
    rule 1 /555555190/ /190/
    rule 2 /555555191/ /191/
    rule 3 /555555192/ /192/
    rule 4 /555555193/ /193/
    rule 5 /555555194/ /194/
    rule 6 /555555195/ /195/
    rule 7 /555555196/ /196/
    rule 8 /555555197/ /197/
    rule 9 /555555198/ /198/
    rule 10 /555555199/ /199/
    voice translation-rule 1000
    rule 1 /.*/ //
    voice translation-rule 1112
    rule 1 /^8/ //
    voice translation-rule 2001
    voice translation-rule 2002
    rule 1 /^6/ //
    rule 2 /^A/ //
    voice translation-rule 2222
    regards,
    Fabian

    I already figured it out myself - that was easy, if you know where to look...
    voice translation-rule 3265
    rule 1 /\(^.*$\)/ /0\1/ type national national
    rule 2 /\(^.*$\)/ /00\1/ type international international

  • Preserve Leading Zeros in SQL export to TXT

    I need to export accounting data from SQL to a series of TXT files, with a "ServiceCode" of 02. I cannot get the
    leading zero to stick.
    Here is the section of the SQL stored procedure that pulls the serviceCode of “02.”
    IF @serviceCode =
    '02'
    BEGIN
    SELECT @total =
    COALESCE(SUM(Price),0),
    @itemCount = COALESCE(SUM(ItemCount),0)
    FROM #tblData
    WHERE CostCenter = @costCenter
    AND ServiceCode
    IN(SELECT
    DISTINCT [ServiceCode]
    FROM [DsPcDb].[dbo].[Service_T]
    WHERE [Name]
    NOT
    LIKE
    '%color%'
    AND [Name]
    NOT
    LIKE
    '%scan%'
    AND [Name]
    NOT
    LIKE
    '%fax%'
    AND [ServiceCode] <=
    196623)
    END
    ...and here is some text from the "02" output .txt file, with the leading zero stripped out of the third column:
    11/21/2014,00000-24057,2,1125
    11/21/2014,00001-MKTG12,2,150
    11/21/2014,40059-00395,2,62
    11/21/2014,40059-00409,2,32
    11/21/2014,40059-00428,2,12
    11/21/2014,40059-00432,2,2
    11/21/2014,40059-00434,2,218
    This won't let the receiving database import the data. ("02" is a specific code.) Three other txt files from this
    procedure are imported properly.
    Please help! Thanks!

    You need to cast the servicecode field to varchar to make sure it retains leading zero.
    So in your case make variable type varchar and also places where you select from field cast it to varchar.
    Please Mark This As Answer if it solved your issue
    Please Mark This As Helpful if it helps to solve your issue
    Visakh
    My MSDN Page
    My Personal Blog
    My Facebook Page

  • Web Services  from ABAP function modules return values- leading zeros

    I am using several web services from SAP CRM (5.0) that were created from Function modules ( I am assuming that that they are in ABAP).
    I can call the web services fine and they work as expected, but I am seeing a lot of leading zeros in the return values of fields in tables from the Web service.
    The ABAP er’s are telling me that they cannot see the leading zero’s.
    So my question is where these are appended to the values in the whole process. When I execute the Function Module in SAP CRM from transaction SE37 I can see the leading zeros. So I think that this is something that has to be handled by the ABAP er’s and not in the client consuming the web service.
    Are the functions in SAP CRM that can remove leading zeros for fields in a table (that is an export parameter?)
    Jawahar

    Hello Jawahar
    If you run your (RFC-enabled) function modules using the SAP-GUI (i.e. in dialog) then the GUI automatically replaces leading zero when the function module returns any data. However, calling the same function module remotely you will always see these leading zeros.
    These so-called conversion exits are defined as attribute of domains in the ABAP dictionary. If the function module used for the WebService is a standard fm then you have little chances to get rid of the leading zero. Perhaps the WebService has some attribute to suppress conversion exits or activate them when retrieving the data.
    Regards, 
       Uwe

  • Need hel attendant console- missing leading zero

    I have a customer wher we did an upgrade from 4.1(3) to CUCM 7.1(2), we installed the AC plugin from the CUCM, and the AC is working but now the cutomer complains that they can't dial back from the AC because they are missing the leading zeros from the incomming calling numbers, on the phone the numbers are displayed with the zeros, what can be doen to have the leading zeros on the  AC
    Thanks

    Bradley,
    I cannot comment on the implementation you have gone through but I can comment on your comments about CUEAC.
    There is going to be a new release in June this year which will support directory integration directly to AD as well as the CUCM sync which is available today.
    The GUI iteself is to undergo a redesign in version 10, the date on this release is not yet known.
    Incremental search is something which is not on the roadmap but is something I will discuss with the Product Manager to see if it can be considered.

  • Leading zeros for FM F4_GET_RESULT - wildcard problem

    Hi,
    I have the following problem:
    FM F4_GET_RESULT supports the search help in a BSP application.
    It works fine when there is no wildcards used. However when there is a wildcard it doesn't work.
    For example in case of cost centers, we use search help M_KOSTN, which based on table CSKS. There is one cost center 0002160221, which is found if I use form '000216*', however not found if I use without leading zeros.
    Actually it's the same if I use SE16 on table CSKS.
    I cannot really use ALPHA conversion here as I don't know how many leading zeros I have to add.
    Any idea how to solve this issue?
    Thanks in advance,
    Peter

    Hi peter,
    To remove leading zeros and leading blanks
    Please use FM
    CONVERSION_EXIT_ALPHA_INPUT Conversion exit ALPHA, external->internal
    CONVERSION_EXIT_ALPHA_OUTPUT Conversion exit ALPHA, internal->external
    These function modules convert the value of an external represntation of a field into an internal format or vice versa.(Meaning for some fields like MATNR, then value which you see is not the way it is stored in the database. The value that you see is the external format, and the value which is stored inside the database id the internal format. These function modules convert the values of such fields from internal to external and vice versa.
    CONVERSION_EXIT_ALPHA_INPUT This function module is used to append leading zeroes...
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
                EXPORTING
                  input  = wf_version
                IMPORTING
                  output = wf_version.
    Example:
    input = 123
    output = 0000000000000...000000000000123
    Hope this resolves your query.
    Reward all the helpful answers.
    Regards

  • Need to strip the leading ZERO using ABAP code.

    Hi Friends,
    I got a situation where i got customer number called 011. I need to write an ABAP in Transformation to strip the leading ZERO , 11 should be posted to the master data attribute. could you help me in the logic pls.
    Thanks in advance,

    hi friends, i got a prob again, as i mentioned if i got 0 as prefix its deleting but if any 3 digit is comming it's converting in to 2 digit, as i mentioned if the prefix is 0(zero) then only i need to delete the zero.
    Is there any other solution for this..
    thansk in advance.

  • How can I export TB address book without stripping leading zero ?

    When I export a Thunderbird address book to a CSV file some leading zeros are stripped by MS excel 2007.
    Please advise.
    The aim is to export to a csv file, edit the data in the spreadsheet, and then re-import the revised csv file into
    TB.

    Try this:
    Open MS Excel 2007
    click on 'Data' tab
    click on 'Get External Data' and choose 'From Text'
    Import Text file window opens
    select the saved .csv file and click on 'import'
    Text Import wizard step 1 of 3 opens
    select 'delimited'
    these should be auto selected
    start import at row 1
    file origin: windows (ANSI)
    click on 'Next'
    step 2 of 3
    select 'Tab'
    select 'comma'
    this should make the data preview shiow as columns with correct column name.
    Click on 'Next'
    step 3 of 3
    From 'Data Preview Area' select all
    the columns which you would want to be displayed as text. Once selected the background will be black and the text will be white.
    This allows you to select columns and set the type of data format
    Suggest you highlight/select the eg: Work Phone and Home Phone columns.
    Then on the same window from the group 'Column Data format' :
    select Text
    Click on Finish.

  • [svn:fx-trunk] 8591: Fix for SDK-18328 - NumericStepper not stripping leading zeroes upon commit .

    Revision: 8591
    Author:   [email protected]
    Date:     2009-07-15 12:39:05 -0700 (Wed, 15 Jul 2009)
    Log Message:
    Fix for SDK-18328 - NumericStepper not stripping leading zeroes upon commit.
    Bugs: SDK-18328
    QE Notes: None
    Doc Notes: None
    Reviewer: Deepa
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-18328
        http://bugs.adobe.com/jira/browse/SDK-18328
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/NumericStepper.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/NumericStepper.as

  • Need help on how to code this SQL statement! (one key has leading zeros)

    Good day, everyone!
    First of all, I apologize if this isn't the best forum.  I thought of putting it in the SAP Oracle database forum, but the messages there seemed to be geared outside of ABAP SELECTs and programming.  Here's my question:
    I would like to join the tables FMIFIIT and AUFK.  The INNER JOIN will be done between FMIFIIT's MEASURE (Funded Program) field, which is char(24), and AUFK's AUFNR (Order Number) field, which is char(12).
    The problem I'm having is this:  All of the values in AUFNR are preceeded by two zeros.  For example, if I have a MEASURE value of '5200000017', the corresponding value in AUFNR is '005200000017'.  Because I have my SQL statement coded to just match the two fields, I obviously get no records returned because, I assume, of those leading zeros.
    Unfortunately, I don't have a lot of experience coding SQL, so I'm not sure how to resolve this.
    Please help!  As always, I will award points to ALL helpful responses!
    Thanks!!
    Dave

    >
    Dave Packard wrote:
    > Good day, everyone!
    > I would like to join the tables FMIFIIT and AUFK.  The INNER JOIN will be done between FMIFIIT's MEASURE (Funded Program) field, which is char(24), and AUFK's AUFNR (Order Number) field, which is char(12).
    >
    > The problem I'm having is this:  All of the values in AUFNR are preceeded by two zeros.  For example, if I have a MEASURE value of '5200000017', the corresponding value in AUFNR is '005200000017'.  Because I have my SQL statement coded to just match the two fields, I obviously get no records returned because, I assume, of those leading zeros.
    > Dave
    You can't do a join like this in SAP's open SQL.  You could do it in real SQL ie EXEC.... ENDEXEC by using SUSBTR to strip off the leading zeros from AUFNR but this would not be a good idea because a)  modifying a column in the WHERE clause will stop any index on that column being used and b) using real SQL rather than open SQL is really not something that should be encouraged for database portability reasons etc. 
    Forget about a database join and do it in two stages; get your AUFK data into an itab, strip off the leading zeros, and then use FAE to get the FMIFIIT data (or do it the other way round). 
    I do hope you've got an index on your FMIFIIT MEASURE field (we don't have one here); otherwise your SELECT could be slow if the table holds a lot of data.

  • XmltoQuery removing leading zero

    Hi,
    I have a function that takes in a raw xml and covert to query.  The problem is any leading zeroes are gone.  For example, 000123 will become 123.  Is there any way or function in CF that will stop from removing leading zeroes?
    Thanks,

    Oh, sorry.  It's not the XML to Query problem but it's the cfquery problem.  When I cfdump the data, it shows 000123, but when I use <cfquery> to insert the data into a dabase, it strips the leading zeroes and in the db table it shows only 123.  Is there a function or something to prevent this?
    <cfoutput query="get_xml_data">
    <cfquery name="test" datasource="db">
         INSERT INTO table (id, name)
         VALUES (#get_xml_data.id#, #get_xml_data.name#)
    </cfquery>
    </cfoutput>

  • Leading zeros in query results

    Hi,
    have created a query that shows as result a number that have leading zeros in database. In the qurey result these are not available. Is there any possiblity to see the laeding zeros in qurey result.
    This numbers are defined as charakter value in the InfoObject (these numbers are similar to material numbers).
    Can you help.
    Many thanks.

    Hello,
    These leading zeroes are not came from Source system...
    Due to Alpha conversion system has placed this zeroes to avoid conversion problems...
    so while displaying it will remove all the leading zeroes and it will display.
    Regards,
    Pavan.

  • Remove leading zeros from a string

    Hi,
    I have a string with some numeric value.
    e.g.
    String a = 54890001
    I want to make it 10 digits long by padding zeros at the begining
    Now a = 0054890001 ( this is for display purpose ) I know how to do it.
    Now How can strip these leading zeros from this number to get back the actual number. The user sees this 10 digit number and he can change it to something like 0067490001. Now I want to strip these leading zeros.
    and i shd get 67490001.
    In other words, how to strip leading zeros from a string ?
    Thanks for help
    Vinod

    I would try two things: First, just try a straightforward parsing of your String using the Integer.parseInt() method. This is only my first suggestion because the number could be interpreted as octals; only testing will really tell. Second, try a method like this:
    public static String removeLeadingZeros(String str) {
        if (str == null) {
            return null;
        char[] chars = str.toCharArray();
        int index = 0;
        for (; index < str.length; index++) {
            if (chars[index] != '0') {
                break;
        return (index == 0) ? str : str.substring(index);
    }Shaun

  • Remove leading zeros coming from Active Directory

    Greetings all.  Our sapusername is stored in Active Directory with leading zeros.  Is there a way to remove these zeros in the portal so SSO will work?  I have had my AD team manually remove the zeros in front of my sapusername, so I'm sure that's the issue.
    Alternately, is there a setting in R3 that would allow leading zeros?

    Hi,
    I've seen the problem before and I think you only have two choices (haven't looked into if R3 can accept leading zeros)
    1. Since you are allready retrieving sapusernames from an R3 change that mapping to remove leading zeros and possibly put it in a new attribute.
    2. Create a JAAS login module which retrieves found username from the HeaderVariableLoginModule and trims leading zeros before putting the username back to shared state. This new LoginModule must be placed before the CreateTicketLoginModule.
    Note it is not very trivial to create a JAAS login module but an excellent guide can be found here http://help.sap.com/saphelp_nw2004s/helpdata/en/46/3ce9402f3f8031e10000000a1550b0/frameset.htm

  • ExportCollectionActionListener dropping leading zeroes

    We use <af:exportCollectionActionListener> tag to provide users with the ability to export data from some <af:table>s to MS Excel. We have problems with data values like "01.21", for example, which are converted by Excel to "January, 21". Also when there are numeric codes with leading zeros, these zeros are stripped because Excel recognizes the values as numbers. Does anybody know if it is possible to solve this problem easily (for example by specifying somehow the data format of particular columns in Excel export as "Text")?
    I did some research on the web and found a creative solution for surrounding the value with some characters in a way that is visible only on the Excel file and not in the HTML page. It looks something like this:
    <af:column sortProperty="Header" sortable="true"
    headerText="#{bindings.MyReport.hints.MyData.label}"
    id="resId1c27">
    <af:panelGroupLayout layout="horizontal" id="panel999">
    <af:outputText value="=TEXT(&quot;" inlineStyle="display:none" id="ot1444"/>
    <af:outputText value="#{row.MyData}" id="ot21"/>
    <af:outputText value="&quot;,&quot;0&quot;)" inlineStyle="display:none" id="ot222999"/>
    </af:panelGroupLayout>
    </af:column>
    The idea is that in the Excel we end up with an output like this:
    =TEXT("MyValue", "0")
    The problem is that I'm seeing that output verbatim so it looks like Excel is not recognizing it properly.
    Any ideas on how to tell Excel the data type for a particular column?
    BTW, I'm coding on Jdev 11.1.3.
    Thanks,
    MV

    Hi,
    actually the formatting work around was based on a bug, which got fixed in JDeveloper. So right now we don't have an option to provide Excel formatting
    Frank

Maybe you are looking for