[cisco-voip] Matching on voip dial-peer using special characters

Ryan West rwest at zyedge.com
Sun Feb 15 21:20:59 EST 2009


I'm trying to allow calls out a SIP dial-peer that either starts with '*' or has the '*' in the destination-pattern.  The call flow is as following:

H323 inbound call -> digit strip site prefix -> 9*string or *string -> out to a single SIP dial-peer.

I have the proper voice connections for H323 to SIP and transcoding does not seem to be the issue either:

voice service voip
 allow-connections h323 to h323
 allow-connections h323 to sip

When I configure the destination-pattern to be an actual TN, it works fine.  When the destination-pattern contains a *, it skips straight to the catch-all .T.  show dial-plan number *xxxxx never matches, even when a full number is used after the *.

Code is c2800nm-ipvoicek9-mz.124-16b.bin.   I have a case opened with TAC, but it's been dragging a bit.  The TAC# is 610703189.

http://www.cisco.com/en/US/docs/ios/voice/dialpeer/configuration/guide/vd_dp_feat_cfg_ps6441_TSD_Products_Configuration_Guide_Chapter.html#wp1067010
I am missing something obvious from the documentation above, in particular:


In addition to wildcard characters, the following characters can be used in the destination pattern:

*Asterisk (*) and pound sign (#)-These characters on standard touch-tone dial pads can be used anywhere in the pattern. They can be used as the leading character (for example, *650), except on the Cisco 3600 series.
Thanks!

-ryan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090215/e6c2d978/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 168 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090215/e6c2d978/attachment.png>


More information about the cisco-voip mailing list