cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
646
Views
5
Helpful
4
Replies

Caller ID issue

Vijay Patil
Level 3
Level 3

We are running CME setup version 10.5 & having CUCM set up for same organization in other country..

Extn in CME are configured as 3 digit like 782  India setup

Extn in CUCM are configured as 6 digit like 474753 Belgium Setup

 

when we call from 782 to 474753 they are seen caller ID number like 0782 & they are not able to call back on it..

 

below are the TR & TP from CME

 

!
voice translation-rule 1
 rule 1 /^00\(.*\)/ /\1/
 rule 2 /^091\(.*\)/ /0\1/
!
voice translation-rule 10
 rule 1 /^7\(..\)/ /2147\1/
!
voice translation-rule 11
 rule 1 /^000\(.*\)/ /00\1/
!
voice translation-rule 12
 rule 1 /^00\(.*\)/ /0\1/
!
voice translation-rule 20
 rule 1 /^614\(...\)/ /\1/
!
voice translation-rule 21
 rule 1 /^\*474\(...\)/ /474\1/

voice translation-rule 23
 rule 1 /^[0-9]/ /0&/
 rule 2 /^\(...\)/ /614\1/
!
voice translation-rule 100
 rule 1 /^9\(.*\)/ /09\1/
 rule 2 /^8\(.*\)/ /08\1/
 rule 3 /62\(.*\)/ /002\1/
 rule 4 /\(.*\)/ /000\1/ type international international
 rule 5 /\(.*\)/ /00\1/ type national national
!
voice translation-rule 713
 rule 1 /^47\(..\)/ /7\1/
!
voice translation-rule 735
 rule 1 reject /^735/
!
!
voice translation-profile 10
 translate calling 10
!
voice translation-profile 11
 translate calling 10
 translate called 11
!
voice translation-profile 12
 translate calling 10
 translate called 12
!
voice translation-profile BLOCK-735
 translate calling 735
!
voice translation-profile Inbound
 translate calling 100
!
voice translation-profile incoming_CUCM
 translate calling 1
 translate called 20
!
voice translation-profile out-ger-sip-trunk
 translate calling 20
!
voice translation-profile outgoing_CUCM
 translate calling 23
 translate called 21
!
voice translation-profile strip0
 translate calling 1
!
voice translation-profile toCME2
 translate called 713
!

2 Accepted Solutions

Accepted Solutions

On the CME debug voice ccapi inout to see what translation is being
matched. Also, during connected call check show call act voi br to see the
called number in the dialpeer. This will confirm if the translation is
taking place in CME or CUCM.

View solution in original post

If your voice translation-profiles are named with intent, the profile "voice translation-profile outgoing_CUCM" will be your problem:

voice translation-profile outgoing_CUCM
 translate calling 23
 translate called 21

voice translation-rule 23
 rule 1 /^[0-9]/ /0&/
 rule 2 /^\(...\)/ /614\1/

Rule 1 of voice translation-rule 23 is prefixing a 0 to all callerIDs before (presumably) sending the call up to CUCM, which is the behavior you are observing.

View solution in original post

4 Replies 4

On the CME debug voice ccapi inout to see what translation is being
matched. Also, during connected call check show call act voi br to see the
called number in the dialpeer. This will confirm if the translation is
taking place in CME or CUCM.

 Thanks ...,i used debug voice ccapi inout which helps to find out what number we are sending & on that result done the changes in Translation Rule

If your voice translation-profiles are named with intent, the profile "voice translation-profile outgoing_CUCM" will be your problem:

voice translation-profile outgoing_CUCM
 translate calling 23
 translate called 21

voice translation-rule 23
 rule 1 /^[0-9]/ /0&/
 rule 2 /^\(...\)/ /614\1/

Rule 1 of voice translation-rule 23 is prefixing a 0 to all callerIDs before (presumably) sending the call up to CUCM, which is the behavior you are observing.

Thanks MAren...

 

Done with the changes in Translation Rule 23 & it works