[cisco-voip] help with translating route patterns in CCM to dial-peers in CME

[Denis Pointer]

Assuming In CCM you were discarding predot? so 0.[2-9]! would drop the
leading 0 and send everything else correct?  If this is the case dial-peer
500 is correct, the 0 will be dropped because it is an exact match, [2-9]
being a range will not be dropped nor will any following digits. therefor
you don't need a prefix of forward digits command.

For Dial peer 604, with 00570T  the 00570 will be dropped, assuming you just
want to drop the leading 0 so the 0570 etc is sent to PSTN add a "prefix
0570" command.

for 700 you have an extra period in your destination pattern, it should just
be 00041, however, for the blocks, instead of routing to a non-existent
location you should look into the "after-hours" block command, so it would
look something like "after-hours block pattern 1 00041 7-24"

--
Denis Pointer, A. Sc. T.
Customer Systems Analyst (Senior Design)

CCVP, CCNA, CCDA
Cisco Unified Contact Center Specialist
Cisco IP Telephony Design Specialist
Cisco Unity Design Specialist
Cisco Unity Support Specialist
Cisco IP Communications Express Specialist


On Wed, Aug 19, 2009 at 10:03 AM, Monica Hardy <Monica.Hardy at openwave.com>wrote:

>  Hello everyone I have to convert a very old CCM 3.3 to a CME version 7.
>
>
>
> I have only done basic configurations with dial-peers and need a little bit
> of help translating the route patterns on the CCM to the dial-peer
> statements on the CME.
>
>
>
> I have two ways to get to the PSTN in this location.  One on the PRI in the
> CME and one on a VG200 with FXO ports so I have a lot of dial-peer
> statements to build.
>
>
>
> Can you please help with these examples?
>
>
> -------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> On CCM 3.3 the route pattern is 0.[2-9]! (using PRI on CME)
>
>
>
> would it be this on the CME:
>
>
>
> dial-peer voice 500 pots
>
>   destination-pattern 0[2-9]T      --- does 0.[2-9]! in CCM translate to
> this in CME?
>
>   port 0/2/0:23
>
>   prefix ????  can I prefix ranges???
>
>  or should I use forward digits all??   I have no idea how many digits will
> be sent.
>
>
>
>
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> On CCM 3.3 the route pattern is 0.0570! (using VG200 FXO)
>
>
>
> would it be this on the CME:
>
>
>
>  dial-peer voice 604 voip
>
>  destination-pattern 00570T
>
>  session-target ipv4:10.X.X.X
>
>  dtmf-relay h245-alphanumberic rtp-nte
>
>  codec g711ulaw
>
>  no vad
>
>
>
>
>
> On CCM 3.3 the route pattern is *0.0041! #  BLOCK*
>
>
>
> would it be this on the CME:
>
>
>
> Dial-peer voice 702 voip
>
> destination-pattern 0.0041T
>
> session-target ipv4:1.2.3.4     -----send to non-existent target
>
> dtmf-relay h245-alphanumeric rtp-nte
>
> codec g711 ulaw
>
> no vad
>
>
>
>
>
> Thank you
>
>
>
> Monica
>
> --------------------------------------------
>
>
>
> [image: cid:image001.gif at 01CA0FA5.8F211190]
>
>
>
> Monica P. Hardy
>
> Openwave
>
> Sr. Network Engineer
>
> Phone: 650-480-5597
>
> email:  monica.hardy at openwave.com
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090819/ae8a8d6c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 2361 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090819/ae8a8d6c/attachment.gif>