Inbound dial peer matching for FXO is kind of a special case, since a selection based on called or calling number is not possible. The former does not exist for inbound calls through an FXO, and the latter is delivered AFTER the POTS peer has been chosen, triggered by the inbound ringing voltage.
Having said that, if dial peer 50 is your ONLY dial peer, it should have been matched before dial peer 0. You are missing a destination pattern. Add whatever pattern and it should work. Now, there isn't really much you can do in reality wiht these POTS.
Many thanks for the detailed response. I'm not sure I follow some of the thing syou said:
1. Why does dial-peer 50 need to be the ONLY dial-peer? I do have other dial-peers in other systems we've got. For example, one system had three dial-peer, one to match incoming fax calls on a specific FXO port, one to match incoming calls for the FXO trunkgroup (other three fxo ports) and one to matching incoming calls from the incoming BRI trunkgroup (two BRI ports). Is such a config not possible?
2. In the above example, I found that a normal voice call incoming on fxo port 0/2/1 was matching the dial-peer for the incoming fax calls (configured for port 0/2/3) instead of the dial-peer for the FXO trunkgroup (of which port 0/2/1 is a member). This is what I'm finding odd...incoming called-number is 'T' on all dial-peers and no answer-address or destination-pattern is configured. In this case I'd expect the port or trunkgroup configured on these incoming dial-peers to be the distinguishing factor but seemingly it isn't...
3. You say there there really isn't much you can do with these dp's. Well actually there's all sorts of stuff that I'd like to do :-). Things such as configuring corlists, performing digit manipulation and configuring huntstop and dial-peer directionality (permission orig/term)....so I'd say there's quite a bit to be gained form being able to match the correct incoming dp...
1. Inbound FXO dial peer matching does not depend on anything other than inbound ringing voltage. If you have three dial peers identically configured and associated to the same FXO port, they will be matched randomly.
2. Inbound calls through an FXO port do not have a "called number". Imagine your phone line at home. The Telco oes not send you any digits when your home phone rings. Call routing stops at the CO. The only thing they can send you is caller id. But on a Cisco voice gateway, inbound FXO dial peer cannot be based on caller id (calling number), because by the time caller id is received, a dial peer has already been chosen since inbound ringing voltage was detected on the FXO port.
3. You can do a lot for outbound calls, but not much for inbound in terms of predictably choose a dial peer. This is true for FXO only. BRI is different, because these are DID trunks.
Configure Multicast Paging on the Cisco IP Phone 7800 Series or 8800 Series Multiplatform Phone
The Cisco IP Phone 7800 and 8800 Series Multiplatform Phones provide voice communication over an Internet Protocol (IP) network...
Add Call Park on a Cisco 7800 or 8800 Series Multiplatform Phone Key Expansion Module
Call park allows the user of the phone to put an incoming call on hold so that the call can be retrieved on another phone. A call is park...