cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
1081
Views
0
Helpful
11
Replies
Highlighted
Beginner

Calling ID Translation not working on VG - help!!!

Dear NetPro gurus,

My customer has deployed a new Cisco VG at one of their new remote offices, while the calls works fine, the Inbound Translation Rules fails to work.

e.g.  I used my test mobile 0478488565 to call my client on 67992294.  For whatever reason, my customer's Telco Provider (Telstra) has stripped off my first digit (i.e. 0) of my call.

So they tried to append the '0' back as the Calling ID but the inbound Translation Rule doesn't work for some reason.

It should have been translated by Voice Translation Rule 100 of RedialZero Translation Profile applied at Voice-Port 0/0/0:15, but the Calling ID didn't get translated somehow as per the below debug:-

ce-e03-1#debug isdn q931

debug isdn q931 is              ON.

ce-e03-1#

Oct  9 2012 04:37:17.889 UTC: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8  callref = 0x005C

        Sending Complete

        Bearer Capability i = 0x8090A3

                Standard = CCITT

                Transfer Capability = Speech 

                Transfer Mode = Circuit

                Transfer Rate = 64 kbit/s

        Channel ID i = 0xA1838D

                Preferred, Channel 13

        Calling Party Number i = 0x2181, '478488565'

                Plan:ISDN, Type:National

        Called Party Number i = 0xC1, '67992294'

                Plan:ISDN, Type:Subscriber(local)

        High Layer Compat i = 0x9181

Oct  9 2012 04:37:17.889 UTC: ISDN Se0/0/0:15 Q931: Received SETUP  callref = 0x805C callID = 0x001E switch = primary-net5 interface = User

Oct  9 2012 04:37:17.893 UTC: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8  callref = 0x805C

        Channel ID i = 0xA9838D

                Exclusive, Channel 13

Oct  9 2012 04:37:17.893 UTC: ISDN Se0/0/0:15 Q931: TX -> ALERTING pd = 8  callref = 0x805C

        Facility i = 0x9FAA068001018201018B0100A11202010C020101800A436F6D6D7320526F6F6D

                Protocol Profile =  Networking Extensions

                0x010182

                0x01018B

                0x0100

                0xA11202010C020101800A436F6D6D7320526F6F6D

                Component = Invoke component, Unsupported operation 

        Progress Ind i = 0x8188 - In-band info or appropriate now available

Oct  9 2012 04:37:17.941 UTC: ISDN Se0/0/0:15 Q931: RX <- STATUS pd = 8  callref = 0x005C

        Cause i = 0x82E41C - Invalid information element contents

        Call State i = 0x07

ce-e03-1# ce-e03-1#debug isdn q931
debug isdn q931 is              ON.
ce-e03-1#
Oct  9 2012 04:37:17.889 UTC: ISDN Se0/0/0:15 Q931: RX <- SETUP pd = 8  callref = 0x005C
        Sending Complete
        Bearer Capability i = 0x8090A3
                Standard = CCITT
                Transfer Capability = Speech 
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA1838D
                Preferred, Channel 13
        Calling Party Number i = 0x2181, '478488565'
                Plan:ISDN, Type:National
        Called Party Number i = 0xC1, '67992294'
                Plan:ISDN, Type:Subscriber(local)
        High Layer Compat i = 0x9181
Oct  9 2012 04:37:17.889 UTC: ISDN Se0/0/0:15 Q931: Received SETUP  callref = 0x805C callID = 0x001E switch = primary-net5 interface = User
Oct  9 2012 04:37:17.893 UTC: ISDN Se0/0/0:15 Q931: TX -> CALL_PROC pd = 8  callref = 0x805C
        Channel ID i = 0xA9838D
                Exclusive, Channel 13
Oct  9 2012 04:37:17.893 UTC: ISDN Se0/0/0:15 Q931: TX -> ALERTING pd = 8  callref = 0x805C
        Facility i = 0x9FAA068001018201018B0100A11202010C020101800A436F6D6D7320526F6F6D
                Protocol Profile =  Networking Extensions
                0x010182
                0x01018B
                0x0100
                0xA11202010C020101800A436F6D6D7320526F6F6D
                Component = Invoke component, Unsupported operation 
        Progress Ind i = 0x8188 - In-band info or appropriate now available
Oct  9 2012 04:37:17.941 UTC: ISDN Se0/0/0:15 Q931: RX <- STATUS pd = 8  callref = 0x005C
        Cause i = 0x82E41C - Invalid information element contents
        Call State i = 0x07
ce-e03-1#

It shows my test Mobile Calling ID as 478488565 instead of 0478488565.

Any help would be greatly appreciated.

Cheers,

Hunt

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

Hi Hunt.

Can you try to add the translation rule 100 to translation profile "FromPSTN" and see if it makes difference?

voice translation-profile FromPSTN

translate calling 100

HTH

Regards

Carlo

Please rate all helpful posts "The more you help the more you learn"

View solution in original post

11 REPLIES 11
Highlighted
Advocate

In the debug voip ccapi inout it show the calling number with the leading 0 just before the call exits out on dial peer 20002.

Oct  9 2012 04:50:11.408 UTC: //339980/A45383068027/CCAPI/ccCallSetupRequest:

   Calling Number=0478488565(TON=National, NPI=ISDN, Screening=User, Passed, Presentation=Allowed),

   Called Number=82294(TON=Subscriber, NPI=ISDN),

   Redirect Number=, Display Info=

   Account Number=, Final Destination Flag=TRUE,

   Guid=A4538306-1103-11E2-8027-2C542D840980, Outgoing Dial-peer=20002

So your translation seems to have kicked in. Can you please do a debug voice translate and post the out-put of that.

Please remember to rate helpful responses and identify helpful or correct answers.

Please rate all useful posts
Highlighted
Beginner

Hi Hunt

Well this debug won't show the translated number.

Try debug voice translation to see what actually happens with youre translations.

After a quick check of your config it seems ok.

How does the number show on a phone?

Regards

Stefan

Highlighted

Hi Stefan & Roger,

The Cisco phone only show my number as 478488565 instead of 0478488565.

I have attached the debug for your reference.

Regards,

Hunt

Highlighted

Hi Hunt.

Can you try to add the translation rule 100 to translation profile "FromPSTN" and see if it makes difference?

voice translation-profile FromPSTN

translate calling 100

HTH

Regards

Carlo

Please rate all helpful posts "The more you help the more you learn"

View solution in original post

Highlighted

Hi Carlo,

I tried to put the following but is still no difference.

voice translation-profile FromPSTN

translate calling 100

translate called 101

I want to incoming "Caller ID" to be 00478488565, but it kept on showing only 0478488565.

Cheers,

Hunt

Highlighted

Hi Hunt.

In this case you should modify your translation rule 100.

Modify your rule with this one:

voice translation-rule 100

rule 1 /^\([1-9]\)/ /00\1/

rule 2 /^0/ /00/

Should be enough to obtain what you are looking for.

HTH

Regards

Carlo

Please rate all helpful posts "The more you help the more you learn"
Highlighted

Hunt Lee wrote:

Hi Carlo,

I tried to put the following but is still no difference.

voice translation-profile FromPSTN

translate calling 100

translate called 101

I want to incoming "Caller ID" to be 00478488565, but it kept on showing only 0478488565.

Cheers,

Hunt

Well that's not what you originally asked for, you said that the caller ID was 478488565 and you wanted it to show as 0478488565. To have it show as 00478488565 you would need to add two zeros (0).

Change your translation rule to this to always add two zeros in front of the calling number received from your Telco.

voice translation-rule 100

rule 1 /.*/ /00\0/

Please remember to rate helpful responses and identify helpful or correct answers.

Please rate all useful posts
Highlighted

Hi Roger.

With the rule you suggested, incomnig international calls could have too many leading zeros.

Eg 0039xxxx would be translated in 000039xxxx which insn't matched by any dial peer in his config.

Regards.

Carlo

Please rate all helpful posts "The more you help the more you learn"
Highlighted

Hi Carlo,
Well that’s an assumption from your side, though probably a valid one, the question is not really clear about how incoming calling number for other types of numbers are delivered from the Telco.

To better take care of translation of incoming calling number for different TON this rule set could be used.

voice translation-rule 100
rule 1 /\(.*\)/ /000\1/ type international international
rule 2 /\(.*\)/ /00\1/ type national national
rule 3 /\(.*\)/ /001\1/ type subscriber subscriber

or as I originally wrote the rule with /0 in the replace part. /0 means cally over the entire match part to the replace part of the translation.

voice translation-rule 100
rule 1 /.*/ /000\0/ type international international
rule 2 /.*/ /00\0/ type national national
rule 3 /.*/ /001\0/ type subscriber subscriber

Of course with modifications to fit how this specific Telco delivers  caller ID’s for national, international and so forth. Best way to figure  this out is to do a debug isdn q931 and then do some test calls from  various places so that the call is delivered as the TON that needs to be  taken care of.

About matching dial peer and the translation of calling number, as far as I can see there are no dial peers that match on calling number, they all use called number. The exception to this would be the incoming dial peer for pots calls (dial peer 1).

Please remember to rate helpful responses and identify helpful or correct answers.

Please rate all useful posts
Highlighted

Hi Roger.

sorry but what i meant about dial-peer matching was about outgoning dial-peer for call back received or missed calls .

I agree with you that we should have a clearer Telco situation to provide the right solution to original question.

Cheers

Carlo

Please rate all helpful posts "The more you help the more you learn"
Highlighted
Advocate

The wanted translation for calling number does take place.

Oct  9 2012 23:05:57.139 UTC: //-1/xxxxxxxxxxxx/RXRULE/regxrule_get_profile_from_voiceport_internal: Found profile RedialZero defined on voice-port

Oct  9 2012 23:05:57.139 UTC: //-1/xxxxxxxxxxxx/RXRULE/regxrule_profile_match_internal: Matched with rule 4 in ruleset 100

Oct  9 2012 23:05:57.139 UTC: //-1/xxxxxxxxxxxx/RXRULE/sed_subst: Successful substitution; pattern=478488565 matchPattern=^4 replacePattern=04 replaced pattern=0478488565

Then your translation for called number is seen

Oct  9 2012 23:05:57.139 UTC: //-1/xxxxxxxxxxxx/RXRULE/regxrule_profile_match_internal: Matched with rule 3 in ruleset 101

Oct  9 2012 23:05:57.139 UTC: //-1/xxxxxxxxxxxx/RXRULE/sed_subst: Successful substitution; pattern=67992294 matchPattern=^67992(...) replacePattern=82\1 replaced pattern=82294

Near the end your have this

Oct  9 2012 23:05:57.143 UTC: //-1/B7D680158030/RXRULE/regxrule_vp_translate: calling_number=0478488565 calling_octet=0x21

        called_number=82294 called_octet=0xC1

        redirect_number= redirect_type=4294967295 redirect_plan=4294967295

That shows that the calling number has been changed to 0478488565 and called number has changed to 82294. So if it's not seen as this on the phone it has to have some other reason, why is unclear for now though.

A side note, you can simplify your translation rule 100 with this. It would probably do no difference for your problem at hand, but would be a cleaner way to add a 0 in front of the calling number.

voice translation-rule 100

rule 1 /.*/ /0\0/

Please remember to rate helpful responses and identify helpful or correct answers.

Please rate all useful posts