[cisco-voip] dial-peer destination-pattern with **

[Mike Lydick]

Another solution maybe create and apply translation to the incoming call leg
dial-peer that would strip the  ** and replace with a unique prefix, then
have similar on the outgoing call dial-peer that would strip the pre-fix and
restore the **.  

 

This is what I was thinking.

 

voice translation-rule 9998

rule 1 /\*\*\(74..\)$/ /#\1/

 

voice translation-rule 9999

rule 1 /#\(74..\)$/ /**\1/

 

voice translation-profile SD1

translate called 9998

voice translation-profile SD2

translate called 9999

 

dial-peer voice 2 voip

translation-profile outgoing SD1

incoming called-number .

 

dial-peer voice 7400 voip

translation-profile incoming SD2

 destination-pattern #74..$

session target ipv4:x.x.x.x

dtmf-relay h245-alphanumeric

codec g711ulaw

no vad

 

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Norton, Mike
Sent: Wednesday, January 16, 2013 6:50 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] dial-peer destination-pattern with **

 

What am I doing wrong here?

 

(config)#dial-peer voice 701 pots

(config-dial-peer)#destination-pattern **47..

 

It gives me this error:

 

% nested *?+Incorrect format for ^((\*)?*47..)$

 

Huh? I am trying to match two stars followed by 47 followed by two wildcard
digits. (If I only do one star instead of two, it works fine.) This is on a
2901 with 15.1(3)T4.

 

-- 

Mike Norton

I.T. Specialist

Peace Wapiti School Division No. 76

Helpdesk: 780-831-3080

Direct: 780-831-3076

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130117/42ecfdea/attachment.html>