I understand that there is a specific order in which CUCME processes POTS dial-peers - there's a great reference for the processing order here:http://www.cisco.com/en/US/tech/tk652/tk90/technologies_tech_note09186a008010fed1.shtml
I still have a question though - for an inbound dial-peer, would multiple criteria mess up a dial-peer?
For instance, I have an analog device in FXS Port 0/0/1 of an IOS gateway. I want calls that come in a PRI to be sent to this FXS port. Could I use the following dial-peer for the outbound calls? (Some digits replaced with "X" for confidentiality)
dial-peer voice 205 pots
description Dial-Peer for Fax Line 269-488-XXXX
incoming called-number 269488XXXX
port 0/0/1
dial-peer voice 204 ports
incoming called-number .
port 0/1/0:23
I want the call to be sent TO port 0/0/1, but I'm worried that the " incoming called-number 269488XXXX" will override the general "incoming called-number ." line on dial-peer 204, and the system will get confused because it will also expect that it can match the "port" command on dial-peer 205 - so that it would expect that it will also RECEIVE the call on the FXS port. Basically, I'm thinking that dial-peer 205 will match inbound, and it will then look at the entire dial-peer, and try to look for a call coming from the FXS port, and therefore, break. Does that sound right? Or, since "port 0/0/1" is also a dial-peer matching criteria, but is NOT getting matched in this instance, will it ignore that line?
Thank you for any help you might be able to offer!
Andy
