<div dir="ltr">Dear Peter,<br>Appologies for replying to your post so late. I changed the destination-pattern on the dial-peer to .T and removed any transltion profiles. I implemented ISDN mapping for calling as well as called party numbers as follows on the serial interface of outgoing PRI:-<br>
<br>interface Serial2/1:15<br> no ip address<br> encapsulation hdlc<br> isdn switch-type primary-net5<br> isdn incoming-voice voice<br> isdn map address 95* plan isdn type national<br> isdn map address 095* plan isdn type national<br>
isdn map address 091* plan isdn type national<br> isdn map address 092* plan isdn type national<br> isdn map address 012* plan isdn type national<br> isdn map address 015* plan isdn type national<br> isdn map address 111 plan isdn type national<br>
isdn sending-complete<br> no cdp enable<br><br>Now the calling party number is being displayed without the additional leading zero. <br>I have to thank you for making me dig deeper in to this.<br><br>best regards,<br><br>
Abebe Amare<br><br><div class="gmail_quote">On Sat, Feb 14, 2009 at 1:54 AM, Peter Slow <span dir="ltr"><<a href="mailto:peter.slow@gmail.com">peter.slow@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Abebe,<br>
you had mentioned the calling number's leading 0, and i do see in<br>
your debug that your caller id begins with 95, not 095 - this<br>
shouldn't affect your called party, but it's possible that your telco<br>
will not like your caller id - this is sort of a different issue.<br>
It appears that you have made a translation rule that does both 1.)<br>
strip the leading 0 2.) set the type and plan on the called number. -<br>
I beleive you only need to do one or the other, or at least try them<br>
one at a time. I recommend trying 2 by itself, first,<br>
rule 1 /^\(095.......\)/ /\1/ type unknown national plan unknown national<br>
The next problem is that you have a translation rule which matches<br>
only numbers beginning with 095 assigned to a pots dial peer that<br>
matches calls only to 86T. What is the destination string that comes<br>
into the gateway in the h.323 (h.225) setup message? It would seem<br>
that you applied your rule to the wrong dial-peer.<br>
<font color="#888888"><br>
-Peter<br>
</font><div><div></div><div class="h5"><br>
On Fri, Feb 13, 2009 at 3:01 AM, abuch <<a href="mailto:abucho@gmail.com">abucho@gmail.com</a>> wrote:<br>
> Dear Peter,<br>
><br>
> I have asked the telco and for called number starting with 095 they<br>
> expect national type and plan. So I used the follwing config snippet:<br>
><br>
> voice translation-rule 4<br>
> rule 1 /^095\(.......\)/ /95\1/ type unknown national plan unknown national<br>
> !<br>
> dial-peer voice 13 pots<br>
> destination-pattern 86T<br>
> translate-outgoing called 4<br>
> fax rate disable<br>
> port 2/1:15<br>
><br>
> But I am not able to change the type and plan. The leading 0 in the<br>
> calling numebr is already stripped in the calling party transform mask<br>
> in CCM.<br>
><br>
> best regards,<br>
><br>
> Abebe A.<br>
> On 2/11/09, Peter Slow <<a href="mailto:peter.slow@gmail.com">peter.slow@gmail.com</a>> wrote:<br>
>> Dear Anon,<br>
>> I would recommend finding out what your telco expects you to send<br>
>> as your called plan and type - you can see here that you are sending<br>
>> unknown for both:<br>
>><br>
>>> Called Party Number i = 0x80, '0959502203'<br>
>>> Plan:Unknown, Type:Unknown<br>
>><br>
>> ...And you likely need to be sending national or something to that<br>
>> effect, if you are indeed dialing your number correctly. Im under the<br>
>> impression that you are dialing within your own country and that this<br>
>> is not an international call.<br>
>><br>
>> If you need to strip the leading 0, you need to use a translation rule<br>
>> in IOS, it can be done rather easily. make sure you're sending the<br>
>> correct plan and type first. you can set this with the translation<br>
>> rule as well. Apply it outbound on your pots dial-peer.<br>
>><br>
>> -Peter<br>
>><br>
>> On Wed, Feb 11, 2009 at 10:30 AM, abuch <<a href="mailto:abucho@gmail.com">abucho@gmail.com</a>> wrote:<br>
>>> Dear all,<br>
>>><br>
>>> CUCM 6.1.3-100016, Cisco 3845 H.323 gw connected to the PSTN with ISDN<br>
>>> PRI.<br>
>>> Outgoing calls to the PSTN are appearing to have a leading additional 0.<br>
>>> The<br>
>>> DID number range I am using is 095960XXXX. I have configured calling<br>
>>> party<br>
>>> trasformation mask as 95960XXXX. But when I make calls to the PSTN the<br>
>>> CLID<br>
>>> displayed as 0095960XXXX.<br>
>>> The output of debug isdn q931:-<br>
>>><br>
>>> Feb 11 15:01:47.051: ISDN Se2/1:15 Q931: Applying typeplan for sw-type<br>
>>> 0x12<br>
>>> is 0x0 0x0, Calling num 959602203<br>
>>> Feb 11 15:01:47.051: ISDN Se2/1:15 Q931: Applying typeplan for sw-type<br>
>>> 0x12<br>
>>> is 0x0 0x0, Called num 0959502203<br>
>>> Feb 11 15:01:47.051: ISDN Se2/1:15 Q931: TX -> SETUP pd = 8 callref =<br>
>>> 0x01B3<br>
>>> Sending Complete<br>
>>> Bearer Capability i = 0x8090A3<br>
>>> Standard = CCITT<br>
>>> Transfer Capability = Speech<br>
>>> Transfer Mode = Circuit<br>
>>> Transfer Rate = 64 kbit/s<br>
>>> Channel ID i = 0xA9839F<br>
>>> Exclusive, Channel 31<br>
>>> Calling Party Number i = 0x0081, '959602203'<br>
>>> Plan:Unknown, Type:Unknown<br>
>>> Called Party Number i = 0x80, '0959502203'<br>
>>> Plan:Unknown, Type:Unknown<br>
>>> Feb 11 15:01:47.195: ISDN Se2/1:15 Q931: RX <- CALL_PROC pd = 8 callref<br>
>>> =<br>
>>> 0x81B3<br>
>>> Channel ID i = 0xA9839F<br>
>>> Exclusive, Channel 31<br>
>>> Feb 11 15:01:51.159: ISDN Se2/1:15 Q931: RX <- ALERTING pd = 8 callref =<br>
>>> 0x81B3<br>
>>> Progress Ind i = 0x8488 - In-band info or appropriate now<br>
>>> available<br>
>>> Feb 11 15:02:07: %ISDN-6-DISCONNECT: Interface Serial2/1:0 disconnected<br>
>>> from 0959502812 , call lasted 62 seconds<br>
>>> Feb 11 15:02:07.472: ISDN Se2/1:15 Q931: TX -> DISCONNECT pd = 8 callref<br>
>>> =<br>
>>> 0xF400<br>
>>> Cause i = 0x8090 - Normal call clearing<br>
>>> Feb 11 15:02:07.632: ISDN Se2/1:15 Q931: RX <- RELEASE pd = 8 callref =<br>
>>> 0x7400<br>
>>> Feb 11 15:02:07.632: ISDN Se2/1:15 Q931: TX -> RELEASE_COMP pd = 8<br>
>>> callref<br>
>>> = 0xF400<br>
>>> Feb 11 15:02:11.408: ISDN Se2/1:15 Q931: TX -> DISCONNECT pd = 8 callref<br>
>>> =<br>
>>> 0x01B3<br>
>>> Cause i = 0x8090 - Normal call clearing<br>
>>> Feb 11 15:02:11.672: ISDN Se2/1:15 Q931: RX <- RELEASE pd = 8 callref =<br>
>>> 0x81B3<br>
>>> Feb 11 15:02:11.672: ISDN Se2/1:15 Q931: TX -> RELEASE_COMP pd = 8<br>
>>> callref<br>
>>> = 0x01B3<br>
>>><br>
>>><br>
>>> What can I do in order to remove the additional 0? or is it a telcom<br>
>>> issue?<br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> cisco-voip mailing list<br>
>>> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
>>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
>>><br>
>>><br>
>><br>
><br>
</div></div></blockquote></div><br></div>