Identical dial peers and cor list

[moises7777]

We have had some issues with fax machines not being able to send out properly. To fix this we decided to create a cor list that would make it so that incoming fax calls go to an fxs port on the VG and then to the fax and outgoing fax calls to go out a certain t1. We want to do this because we beleive that when faxes go out our SIP trunk faxes get messed up. The t1 we want faxes to go out of is a t1 that goes directly to the pstn and not the sip trunks.

So we have two identical dial peers, one is supposed to be used for only fax machines ( dial peers 8000 and 8001) and the other is for everyone else. we want everyone else to use the SIP trunk for long distance calls.

I was told that this would not work because the cisco IOS will choose the first matching dial peer, in this case dial peer 2000 or 2001).

I thought a cor list would make any of the fax machines that are part of the cor list go out dial peer which also has the cor list configured.

My question is, is this correct, will the cor list not work in this instance? Anyone have any thoughts on how to accomplish this? Thanks.

The cor list is not working properly for outgoing. It should be using dial peers 8000 and 8001, but instead its using dial peers 2000 and 2001.

dial-peer cor custom 

name FAX

dial-peer cor list FAXCALL

member FAX

!

dial-peer cor list FAXMACHINES

member FAX

0x78647    24B6 0x6A1D39F8 4/0/5            0/5:1   92034435   g711ulaw 8007/2001

0x78616    2461 0x6A1D39F8 4/0/5            0/5:1   8082620931 g711ulaw 8007/2000

The fax machines are hitting these dial peers when making outgoing calls to local or long distance.

dial-peer voice 2000 voip

description ### For Long Distance ###

destination-pattern 91[2-9].........

session target ipv4:10.200.0.10

dtmf-relay h245-alphanumeric

codec g711ulaw bytes 80

dial-peer voice 2001 voip

description ### For Local calling ###

destination-pattern 9[2-9]......

session target ipv4:10.200.0.10

dtmf-relay h245-alphanumeric

codec g711ulaw

no vad

The fax machines should be using these dial peers for outgoing calls.

dial-peer voice 8000 pots

corlist outgoing FAXCALL

translation-profile outgoing OUTBOUND

destination-pattern 91[2-9].........

port 3/0:23

forward-digits all

dial-peer voice 8001 pots

corlist outgoing FAXCALL

translation-profile outgoing OUTBOUND

destination-pattern 9[2-9]......

port 3/0:23

forward-digits all

(incoming core list)

dial-peer voice 8010 pots

corlist incoming FAXMACHINES

description ###  8014 FAX ###

destination-pattern 8014

port 4/0/7

forward-digits all

[Mark Walters]

Old post, but my $.02:

This situation seems to be a little more complicated, as usual..

This call has two equal-preference outbound dial-peers.  By default the router will choose randomly between the two dial-peers (as defined by the "dial-peer hunt" global config setting). 

Applying an inbound corlist for the fax machines achieves nothing by itself.  A corresponding outbound corlist guarentees that this inbound/outbound dial-peer pair can participate in a call.  Unfortunately it does NOT exclude other non-corlist dial-peers from participating with either of these dial-peers, and vice-versa.   So your fax machine will sometime call via outbond peer 2000, and sometimes 8000.  Moreover, all the normal phones will 'hunt' between the two outbound dial-peers as well.

See this for a better explination on corlist:

http://www.cisco.com/en/US/tech/tk652/tk90/technologies_configuration_example09186a008019d649.shtml

So, in order for corlists to have any real impact (and achieve the goal above), EVERY dial-peer on the gateway must have a corlist applied.  So in this case you could have two corlists, FAX and VOICE.  Apply VOICE inbound to every normal pots line, and VOICE outbound on your dial-peer 2000 and 2001.  Then apply FAX inbound on the fax machines, like dial-peer 8010, and apply FAX outbound on dial-peer 8000. 

Note that it may be necessary to create a 'catch all' inbound dial-peer (usually with "answer-address ." or  equivalent) and apply a corlist to that as well.  Mine usually have corlist "BLOCK" applied, which has no corresponding outbound peer.  Critical to that is every outbound dial-peer has some corlist applied that isn't BLOCK.

cheers

mark

ccie #20571 r/s, security