10-25-2018 10:17 AM - edited 03-17-2019 01:38 PM
I'm am stuck, trying to enforce dialpeer selection using a prefix.
Idea: use prefix "+9999" to select inbound dialpeer, use DialPeerGroup to select outgoing dialpeer.
Use translation-profile to discard prefix and dial remaining digits.
Using "csim start +9999+nnnnnnn" fails to find a dialpeer.
Trying to use "show dialplan" in different forms yields this:
inti-vgw1#show dialplan dialpeer 4620 number \+9999\+4525446346
Incorrect format for E.164 Number
regular expression must be of the form ^((\+)?([0-9,#*A-F])+)$
Any suggestions on formatting the dialednumber
Configuration elements:
voice class e164-pattern-map 4620
description Call to SIP trunk inbound
e164 +9999T
!
voice class e164-pattern-map 4621
description Call to SIP trunk outbound
e164 +9999T
!
voice translation-rule 4621
rule 3 /^\+9999/ //
!
voice translation-profile 4621
translate called 4621
!
!
dial-peer voice 4621 voip
description *** CUBE to Novaram ***
translation-profile outgoing 4621
session protocol sipv2
session target dns:siptrunk1.telavox.se
session transport udp
destination e164-pattern-map 4621
voice-class codec 1
voice-class sip options-ping 60
voice-class sip early-offer forced
voice-class sip profiles 4621
voice-class sip profiles 4623 inbound
voice-class sip options-keepalive retry 3
voice-class sip bind control source-interface GigabitEthernet0/1
voice-class sip bind media source-interface GigabitEthernet0/1
dtmf-relay rtp-nte
no vad
!
dial-peer voice 4620 voip
description *** CUCM to CUBE ***
session protocol sipv2
destination dpg 4600
incoming called e164-pattern-map 4620
voice-class codec 1
voice-class sip profiles 4620
voice-class sip bind control source-interface GigabitEthernet0/0
voice-class sip bind media source-interface GigabitEthernet0/0
dtmf-relay rtp-nte
no vad
Solved! Go to Solution.
10-29-2018 09:55 AM - edited 10-29-2018 09:56 AM
Try this...
uk-lon-dc-voice-r1#sho dialplan number +9999*4525446346
Macro Exp.: +9999*4525446346
No match, result=1(MORE_DIGITS_NEEDED)
10-29-2018 04:30 PM
10-27-2018 01:47 PM
10-29-2018 02:34 AM
Unfortunately, thw CUBE needs to care about "called number", as the same source needs to route calls to different destinations (ISDN and SIP) based on who the call is to.
I have tried with alternative prefixes without success:
!
voice class e164-pattern-map 4621
description Call to SIP trunk outbound
e164 9998T
!
voice class e164-pattern-map 4620
description Call to SIP trunk inbound
e164 +9999T
e164 +9999+T
e164 9999T
!!
voice translation-rule 4620
rule 1 /^\+9999\(.*\)/ /9998\1/
rule 2 /^9999/ /9998/
rule 3 /^\+9999/ /9998/
!
voice translation-rule 4621
rule 1 /^9998\(.*\)/ /+\1/
rule 2 /^\+9998/ /+/
rule 3 /^9998/ /+/
!
dial-peer voice 4621 voip
description *** CUBE to Novaram ***
translation-profile outgoing 4621
session protocol sipv2
session target dns:siptrunk1.telavox.se
session transport udp
destination e164-pattern-map 4621
voice-class codec 1
voice-class sip options-ping 60
voice-class sip early-offer forced
voice-class sip profiles 4621
voice-class sip profiles 4623 inbound
voice-class sip options-keepalive retry 3
voice-class sip bind control source-interface GigabitEthernet0/1
voice-class sip bind media source-interface GigabitEthernet0/1
dtmf-relay rtp-nte
no vad
!
dial-peer voice 4620 voip
description *** CUCM to CUBE ***
translation-profile incoming 4620
session protocol sipv2
destination dpg 4600
incoming called e164-pattern-map 4620
voice-class codec 1
voice-class sip profiles 4620
voice-class sip bind control source-interface GigabitEthernet0/0
voice-class sip bind media source-interface GigabitEthernet0/0
dtmf-relay rtp-nte
no vad
! !
10-29-2018 08:19 AM
This picture is not clear. Why do you need the prefix. If you are routing based on called number, then all you need is dial-peers that match the called number. I am guessing there is more to it. So please elaborate on what you are trying to do.
10-29-2018 12:12 PM - edited 11-04-2018 06:00 AM
For that scenario I suggest using LPCOR to restrict the outbound dial-peer selection. In short:
Here's a sanitized sample config:
! Tags are correlated:
! 1X PBX A
! 2X PBX B
! 3X PSTN
!
10-29-2018 04:40 PM
10-29-2018 04:49 PM
10-29-2018 04:32 PM
10-28-2018 03:44 PM
have you tried..
sh dialplan number +9999+4525446346
10-29-2018 02:28 AM
Doesn't help:
inti-vgw1#sh dialplan number +9999+4525446346
Incorrect format for E.164 Number
regular expression must be of the form ^((\+)?([0-9,#*A-F])+)$
10-29-2018 09:55 AM - edited 10-29-2018 09:56 AM
Try this...
uk-lon-dc-voice-r1#sho dialplan number +9999*4525446346
Macro Exp.: +9999*4525446346
No match, result=1(MORE_DIGITS_NEEDED)
10-29-2018 04:30 PM
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