01-24-2020 02:29 AM
Hi,
I have a group of phones that register in SRST, the phones DN's do not match the DDI's, as such i want all the external inbound calls to route to all of the phones in a hunt group.
I have created the hunt group and that can be dialed internally however external calls do not connect, snipped of config below;
voice register global
default mode
no allow-hash-in-dn
timeouts interdigit 5
system message Phone is in emergency mode
max-dn 20
max-pool 40
timezone 21
!
voice register pool 1
translation-profile incoming SRST-IN
id network 10.127.174.0 mask 255.255.255.0
dtmf-relay rtp-nte
voice-class codec 1
!
voice hunt-group 20 parallel
list 2001,2002,2003,2004,2005,2006,2007,2008,2009
pilot 6000
voice translation-rule 4
rule 1 /500./ /6000/
rule 2 /^46141./ /6000/
voice translation-profile SRST-IN
translate called 4
Solved! Go to Solution.
01-24-2020 04:21 AM - edited 01-24-2020 05:59 AM
Hi,
When call arrive to this VG from outside, on a high level it is going to match the dial peers and the registered DN numbers on this gateway. When cucm becomes unreachable then srst will be activated and local DN's will be generated.
Again your DID numbers are not defined as DN and orignal dial-peer pointing to cucm is not working during SRST so no match will be found and call will not established during the SRST
To do a workaround , I would suggest you below steps:
1) most likely you might already tested but if not can you test the translation rules by 'test voice translation rule 4 xxxxx' where xxx xxx represents your DID number and make sure it is translated to 6000.
2) there might be multiple ways to do it, one method which I remember is to make one loopback dial peer with high preference , using same destination pattern which you already have created for dial-peer pointing to cucm and session target of loopback IP of this Router . Apply the translation profile in outbound direction on this dial-peer.
The idea for above loopback dial peer is to avoid conflict with existing configuration which suppose to work fine in normal scenario, loopback dial peer should hit during srst when main dial peer is not working due to unreachable cucm.
Can you share your dial-peer config here so we can re validate?
01-24-2020 04:21 AM - edited 01-24-2020 05:59 AM
Hi,
When call arrive to this VG from outside, on a high level it is going to match the dial peers and the registered DN numbers on this gateway. When cucm becomes unreachable then srst will be activated and local DN's will be generated.
Again your DID numbers are not defined as DN and orignal dial-peer pointing to cucm is not working during SRST so no match will be found and call will not established during the SRST
To do a workaround , I would suggest you below steps:
1) most likely you might already tested but if not can you test the translation rules by 'test voice translation rule 4 xxxxx' where xxx xxx represents your DID number and make sure it is translated to 6000.
2) there might be multiple ways to do it, one method which I remember is to make one loopback dial peer with high preference , using same destination pattern which you already have created for dial-peer pointing to cucm and session target of loopback IP of this Router . Apply the translation profile in outbound direction on this dial-peer.
The idea for above loopback dial peer is to avoid conflict with existing configuration which suppose to work fine in normal scenario, loopback dial peer should hit during srst when main dial peer is not working due to unreachable cucm.
Can you share your dial-peer config here so we can re validate?
01-27-2020 03:42 AM
01-27-2020 03:53 AM
missed your comment on setting the translation-profile outgoing - once i'd done that it works fine - thanks!
01-27-2020 05:04 AM
Happy to hear that it worked out for you!
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