06-22-2015 04:23 PM - edited 03-17-2019 03:26 AM
I am having an issue that I can't quite solve. I am new to Cisco UCM so please bare with me. Essentially the issue is when a user forwards their line to their cell phone, or any external number, and that number is called from an external line, the caller ID shows up with a 91 prefix. I found an article on how to remove the 91 when using MGCP but we are using H323.
Here is the main outbound dial-peer config
dial-peer voice 10 pots
description Long Distance
destination-pattern 91[2-9]..[2-9]......
port 0/0/0:23
forward-digits 11
!
Any help is appreciated.
Solved! Go to Solution.
06-24-2015 06:32 PM
Quick fix or bandage fix would be to apply below config on your router:
voice translation-rule 10
rule 1 /^91/ //
voice translation-profile CLID
translate calling 10
dial-peer voice 10 pots
translation-profile outgoing CLID
Normally Telco's would not allow you to display CLID for any range not part of your DID. Though it appears you have digit manipulation happening either in CUCM or using other methods on voice router like num-expansion etc. In the long run you may need to identify the digit manipulation and would suggest consolidate on the gateway using the voice translation rules.
Anyways make a quick test with the above config and let us know how you go.
-Terry
06-22-2015 05:46 PM
Can you provide the following from your gateway:
sh run | s translation
sh run | s dial-peer
-Terry
Please rate all helpful posts.
06-23-2015 09:23 AM
voice translation-rule 2
rule 1 /^011\(.*\)/ /9011\1/
rule 2 /\(..........\)/ /91\1/
voice translation-rule 210
rule 1 /5440/ /2835/
voice translation-profile 210
translate called 210
dial-peer voice 2 voip
preference 1
destination-pattern 714T
session target ipv4:x.x.x.x
voice-class codec 1
dtmf-relay h245-alphanumeric
no vad
dial-peer voice 10 pots
description Long Distance
destination-pattern 91[2-9]..[2-9]......
port 0/0/0:23
forward-digits 11
dial-peer voice 1 pots
incoming called-number .
direct-inward-dial
port 0/0/0:23
dial-peer voice 110 pots
trunkgroup analog
description Long Distance
preference 1
destination-pattern 91[2-9]..[2-9]......
forward-digits 11
dial-peer voice 911 pots
description Emergency
destination-pattern 911
port 0/0/0:23
forward-digits all
dial-peer voice 912 pots
trunkgroup Analog
description Emergency
preference 1
destination-pattern 911
forward-digits all
dial-peer voice 411 pots
description Information
destination-pattern 9411
port 0/0/0:23
forward-digits 3
dial-peer voice 412 pots
trunkgroup Analog
description Information
preference 1
destination-pattern 9411
forward-digits 3
dial-peer voice 611 pots
description Repair
destination-pattern 9611
port 0/0/0:23
forward-digits 3
dial-peer voice 612 pots
trunkgroup Analog
description Emergency
preference 1
destination-pattern 9611
forward-digits 3
dial-peer voice 7 pots
description Local
destination-pattern 9[2-9]......
port 0/0/0:23
forward-digits 7
dial-peer voice 71 pots
trunkgroup Analog
description Local
preference 1
destination-pattern 9[2-9]......
forward-digits 7
dial-peer voice 100 pots
description Intl
destination-pattern 011T
port 0/0/0:23
forward-digits all
dial-peer voice 101 pots
trunkgroup Analog
description Intl
preference 1
destination-pattern 011T
forward-digits all
dial-peer voice 9911 pots
description Emergency
destination-pattern 9911
port 0/0/0:23
forward-digits 3
dial-peer voice 9912 pots
trunkgroup Analog
description Emergency
preference 1
destination-pattern 9911
forward-digits 3
dial-peer voice 21 voip
destination-pattern 23..
session target ipv4:x.x.x.x
voice-class codec 1
dtmf-relay h245-alphanumeric
no vad
06-24-2015 05:20 PM
Mario,
that configuration output does not contain a dialpeer with a translation rule applied to it
dial-peer voice 10 pots
description Long Distance
destination-pattern 91[2-9]..[2-9]......
port 0/0/0:23
forward-digits 11
06-24-2015 05:23 PM
That is correct. This is the mess that I inherited. Unfortunately nothing was documented so trying to put it all together as I audit these routers.
06-24-2015 05:39 PM
OK, so let me see if I understand this correctly, someone puts a call forward all on their desk phone to, for instance, point to their mobile. Then some external party will call the desk phone number and the mobile will ring with a 91.......... caller ID. correct?
what about when that same deskphone calls that same mobile, without any call forward all, what is the caller ID then?
06-24-2015 05:53 PM
That is correct. If a call comes from an external number, the caller ID contains 91. If the call comes from an internal extension, the caller ID displays the person's DID (10 digit number). If a person makes a call to the mobile phone directly, the proper caller ID is displayed (10 digit number).
I'll work on getting the screen shots and debug outputs. Thanks everyone.
06-24-2015 05:49 PM
Mario,
Since you have the command forward-digits 11, it should automatically be stripping 91. Looks like you have some digit manipulation setup in CUCM.
Can you post screen shot of your H323 gateway below sections:
Call Routing Information - Inbound Calls
Call Routing Information - Outbound Calls
Can you also make a test call and post the following two debugs to start with:
debug isdn q931
debug voip ccapi inout
-Terry
06-24-2015 06:09 PM
06-24-2015 06:32 PM
Quick fix or bandage fix would be to apply below config on your router:
voice translation-rule 10
rule 1 /^91/ //
voice translation-profile CLID
translate calling 10
dial-peer voice 10 pots
translation-profile outgoing CLID
Normally Telco's would not allow you to display CLID for any range not part of your DID. Though it appears you have digit manipulation happening either in CUCM or using other methods on voice router like num-expansion etc. In the long run you may need to identify the digit manipulation and would suggest consolidate on the gateway using the voice translation rules.
Anyways make a quick test with the above config and let us know how you go.
-Terry
06-22-2015 07:07 PM
Easiest way is to use forward-digits as you are, but that only removes the 9, not the 91. forward-digits 10 would send out just the 9..9...... (10 digits)
You could also use translation pattern as such:
voice translation-rule 10
rule 1 /^91/ //
voice translation-profile StripDigits
translate called 10
dial-peer voice X voip
translation-profile StripDigits out
06-23-2015 09:24 AM
I'll give these a try tonight. thanks
06-24-2015 05:06 PM
I tried these suggestions but 91 was still showing as the callerID.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide