You can configure a Voice translation rule to remove the (+) plus, before passing it to cucm
in CUCM \+ represents \+
CSCsj17772 is the DDTS which strips the leading '+' in calling/called numbers.
This change was re-introduced so as to be in compliance with the Q.931 standard and also this was the old behavior of
IOS.
According to Q.931, there are two ways to represent an international
number in Q.931 calling party number field (Table 4-11/Q.931, TON):
1. Set TON (Type Of Number) as 'unknown', and include the full number
including the international prefix (+) in Octet 4.
2. Set TON as 'international', and include the full number without
international prefix in Octet 4.
The latter method is the typical one.
To overcome the below issue and if CSCsj17772 fix should not come into
picture, then configure a translation-profile at the inbound dial-peer
such that + will not be stripped.
At global level, configure the following
voice translation-rule 1
rule 1 /^\+/ //
In this case configure a dummy translation rule such that whatever is received will be retained as it is */
!
!
voice translation-profile voip-generic
translate called 1
!
At inbound dial-peer level, configure the following:
Since the matching inbound dial-peer in the customer scenario is "2",
please add the following to this dial-peer.
"translation-profile incoming voip-generic"
dial-peer voice 2 voip
translation-profile incoming voip-generic
service session
session protocol sipv2
session transport tcp
incoming called-number .
codec g711ulaw
no vad
By configuring as shown above, the fix of CSCsj17772 will not be
applied. So now the '+' will not be stripped and TON not set to
"International". By this you don't send the + to cucm
SiteA#test voice translation-rule 1 +14089022653
Matched with rule 1
Original number: +14089022653 Translated number: 14089022653
Original number type: none Translated number type: none
Original number plan: none Translated number plan: none
