05-23-2019 01:58 AM
Hi all,
I have a problem with an installation made by an ex-colleague, at the time the customer just wanted to display the root number, his new request is to display the root plus the extension. We have modified the dials peers as well as the translations patterns, the number comes out as requested now. However, now when an incoming call arrives, the "0" is no longer displayed.
Here is the current configuration in place:
voice translation-rule 3
rule 1 /^\(123456\)\(...\)/ / /\2/2/
rule 2 /^\(1234561\)/ / /QUEUE IN UNITY CONNECTION/
rule 3 /^\(123456\)/ / /QUEUE IN UNITY CONNECTION/
!
voice translation-rule 4
rule 1 /^\+\(.*\)/ / /000\1/
rule 2 /^\(.*\)/ / /0\1/1/
!
voice translation-rule 7
NOT USED
!
voice translation-rule 8 -> Weird
rule 5 /^\(1234561\)/ /123456QUEUEINUNITY/
rule 6 /^\(123456\)/ /123456QUEUEINUNITY/
!
voice translation-rule 9
NOT USED
!
voice translation-rule 11
rule 1 /^\(.*\)/ / /000\1/ international international type
rule 2 /^\(.*\)/ / /0\1/ national national type
rule 3 /^\(.*\)/ / /0\1/ type unknown unknown unknown
!
!
voice translation-profile FDL
translate calling 4
translate called 8
!
voice translation-profile FDLIncoming
translate calling 4
!
dial-peer voice 100 voip
description output from calls XXX to FDL
destination-pattern 123456....
session protocol sipv2
session target ipv4:IPCALLMANAGER
incoming called-number .T
dial-peer voice 101 voip
session protocol sipv2
incoming called-number .
!
dial-peer voice 10 voip
tone ringback alert-no-PI
description *** National & International outgoing calls - WAN side - outound
destination-pattern .T
session protocol sipv2
session target ipv4:IPCALLMANAGER:5060
!
dial-peer voice 1001 voip
translation-profile outgoing TEST
destination-pattern 1234561
session protocol sipv2
session target ipv4:IPCALLMANAGER
dial-peer voice 1002 voip
translation-profile outgoing TEST
destination-pattern 123456
session protocol sipv2
session target ipv4:IPCALLMANAGER
The real number is replace by 123456 (Root number has 6 digits)
I already try to add an 0 on the Incoming calling party settings -> Doesn't work...
Someone have got an idea?
Thx a lot in advance
05-23-2019 05:09 AM
05-23-2019 07:31 AM
dial-peer voice 1001 voip
translation-profile outgoing TEST
destination-pattern 1234561
session protocol sipv2
session target ipv4:IPCALLMANAGER
I can't see voice translation-profile TEST defined in your configuration. Also note that SIP does not support number plans and types so rules trying to match on those will not work. However I don't know if those rules are actually referenced anywhere so that might be a red herring.
Could you summarise by stating what incoming number is presented, and what you would like Callmanager to display? There are a number of ways that could be achieved.
Finally are you aware of the "test voice translation-rule" cli command? I find that helpful.
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