[cisco-voip] how to strip leading number in calling party

[Peter Slow]

Abebe,
  you had mentioned the calling number's leading 0, and i do see in
your debug that your caller id begins with 95, not 095 - this
shouldn't affect your called party, but it's possible that your telco
will not like your caller id - this is sort of a different issue.
  It appears that you have made a translation rule that does both 1.)
strip the leading 0 2.) set the type and plan on the called number. -
I beleive you only need to do one or the other, or at least try them
one at a time. I recommend trying 2 by itself, first,
rule 1 /^\(095.......\)/ /\1/ type unknown national plan unknown national
  The next problem is that you have a translation rule which matches
only numbers beginning with 095 assigned to a pots dial peer that
matches calls only to 86T. What is the destination string that comes
into the gateway in the h.323 (h.225) setup message? It would seem
that you applied your rule to the wrong dial-peer.

-Peter

On Fri, Feb 13, 2009 at 3:01 AM, abuch <abucho at gmail.com> wrote:
> Dear Peter,
>
> I have asked the telco and for called number starting with 095 they
> expect national type and plan. So I used the follwing config snippet:
>
> voice translation-rule 4
>  rule 1 /^095\(.......\)/ /95\1/ type unknown national plan unknown national
> !
> dial-peer voice 13 pots
>  destination-pattern 86T
>  translate-outgoing called 4
>  fax rate disable
>  port 2/1:15
>
> But I am not able to change the type and plan. The leading 0 in the
> calling numebr is already stripped in the calling party transform mask
> in CCM.
>
> best regards,
>
> Abebe A.
> On 2/11/09, Peter Slow <peter.slow at gmail.com> wrote:
>> Dear Anon,
>>     I would recommend finding out what your telco expects you to send
>> as your called plan and type - you can see here that you are sending
>> unknown for both:
>>
>>>         Called Party Number i = 0x80, '0959502203'
>>>                 Plan:Unknown, Type:Unknown
>>
>> ...And you likely need to be sending national or something to that
>> effect, if you are indeed dialing your number correctly. Im under the
>> impression that you are dialing within your own country and that this
>> is not an international call.
>>
>> If you need to strip the leading 0, you need to use a translation rule
>> in IOS, it can be done rather easily. make sure you're sending the
>> correct plan and type first. you can set this with the translation
>> rule as well. Apply it outbound on your pots dial-peer.
>>
>> -Peter
>>
>> On Wed, Feb 11, 2009 at 10:30 AM, abuch <abucho at gmail.com> wrote:
>>> Dear all,
>>>
>>> CUCM 6.1.3-100016, Cisco 3845 H.323 gw connected to the PSTN with ISDN
>>> PRI.
>>> Outgoing calls to the PSTN are appearing to have a leading additional 0.
>>> The
>>> DID number range I am using is 095960XXXX. I have configured calling
>>> party
>>> trasformation mask as 95960XXXX. But when I make calls to the PSTN the
>>> CLID
>>> displayed as 0095960XXXX.
>>> The output of debug isdn q931:-
>>>
>>> Feb 11 15:01:47.051: ISDN Se2/1:15 Q931: Applying typeplan for sw-type
>>> 0x12
>>> is 0x0 0x0, Calling num 959602203
>>> Feb 11 15:01:47.051: ISDN Se2/1:15 Q931: Applying typeplan for sw-type
>>> 0x12
>>> is 0x0 0x0, Called num 0959502203
>>> Feb 11 15:01:47.051: ISDN Se2/1:15 Q931: TX -> SETUP pd = 8  callref =
>>> 0x01B3
>>>         Sending Complete
>>>         Bearer Capability i = 0x8090A3
>>>                 Standard = CCITT
>>>                 Transfer Capability = Speech
>>>                 Transfer Mode = Circuit
>>>                 Transfer Rate = 64 kbit/s
>>>         Channel ID i = 0xA9839F
>>>                 Exclusive, Channel 31
>>>         Calling Party Number i = 0x0081, '959602203'
>>>                 Plan:Unknown, Type:Unknown
>>>         Called Party Number i = 0x80, '0959502203'
>>>                 Plan:Unknown, Type:Unknown
>>> Feb 11 15:01:47.195: ISDN Se2/1:15 Q931: RX <- CALL_PROC pd = 8  callref
>>> =
>>> 0x81B3
>>>         Channel ID i = 0xA9839F
>>>                 Exclusive, Channel 31
>>> Feb 11 15:01:51.159: ISDN Se2/1:15 Q931: RX <- ALERTING pd = 8  callref =
>>> 0x81B3
>>>         Progress Ind i = 0x8488 - In-band info or appropriate now
>>> available
>>> Feb 11 15:02:07: %ISDN-6-DISCONNECT: Interface Serial2/1:0  disconnected
>>> from 0959502812 , call lasted 62 seconds
>>> Feb 11 15:02:07.472: ISDN Se2/1:15 Q931: TX -> DISCONNECT pd = 8  callref
>>> =
>>> 0xF400
>>>         Cause i = 0x8090 - Normal call clearing
>>> Feb 11 15:02:07.632: ISDN Se2/1:15 Q931: RX <- RELEASE pd = 8  callref =
>>> 0x7400
>>> Feb 11 15:02:07.632: ISDN Se2/1:15 Q931: TX -> RELEASE_COMP pd = 8
>>> callref
>>> = 0xF400
>>> Feb 11 15:02:11.408: ISDN Se2/1:15 Q931: TX -> DISCONNECT pd = 8  callref
>>> =
>>> 0x01B3
>>>         Cause i = 0x8090 - Normal call clearing
>>> Feb 11 15:02:11.672: ISDN Se2/1:15 Q931: RX <- RELEASE pd = 8  callref =
>>> 0x81B3
>>> Feb 11 15:02:11.672: ISDN Se2/1:15 Q931: TX -> RELEASE_COMP pd = 8
>>> callref
>>> = 0x01B3
>>>
>>>
>>> What can I do in order to remove the additional 0? or is it a telcom
>>> issue?
>>>
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>>
>