[cisco-voip] Change in dialpeer behaviour between 12.1 and 12.2/12.3

[Chris Roberts]

Heya,

I'm attempting to upgrade some voice gateways from 12.1 to 12.3 to resolve
some issues we're having.

The new gateway running 12.3 seems to have different behaviour for the
dial-peers however, and I don't understand the difference or whether there
is a behaviour flag I can set. Here are the relevant dial-peers/destination
patterns (sessions etc cut out):
dial-peer voice 1 voip
 destination-pattern .T
dial-peer voice 2 voip
 destination-pattern .T
dial-peer voice 3 pots
 destination-pattern 1#.T
 direct-inward-dial
dial-peer voice 4 pots
 destination-pattern 2#.T
 direct-inward-dial
dial-peer voice 101 voip
 destination-pattern 0.
dial-peer voice 102 voip
 destination-pattern 0.

These are exactly the same on the 12.1 box (working) and the 12.3 box (not
working).
Now, according to the longest match rule, and our 12.1 box, an outbound call
to 1#<some UK number> should be routed to the pots dial peer and making an
outbound call. (Our client gateways/RAS prepend tech-prefix 1#). On our 12.3
box, the POTS dial peers are not matched. Here is a debug from 'debug
dialpeer':
Jun  2 12:30:02.128:  Inside dpMatchCore:
Jun  2 12:30:02.128:  destination pattn: 1#<removed> expanded string:
1#<removed>
Jun  2 12:30:02.128:  Inside dpMatchCore:
Jun  2 12:30:02.128:  destination pattn: <removed> expanded string:
<removed>
Jun  2 12:30:02.128:  Inside dpMatchCore:
Jun  2 12:30:02.128:  destination pattn: <removed>  expanded string:
<removed>
Jun  2 12:30:02.128: MatchNextPeer: Peer 1 matched
Jun  2 12:30:02.128: MatchNextPeer: Peer 2 matched
Jun  2 12:30:02.128: MatchNextPeer: Peer 101 matched
Jun  2 12:30:02.128: MatchNextPeer: Peer 102 matched
Jun  2 12:30:02.132:  Inside dpMatchCore:
Jun  2 12:30:02.132:  destination pattn: 1#<removed> expanded string:
1#<removed>
Jun  2 12:30:02.132:  Inside dpMatchCore:
Jun  2 12:30:02.132:  destination pattn: <removed> expanded string:
<removed>
Jun  2 12:30:02.132:  Inside dpMatchCore:
Jun  2 12:30:02.132:  destination pattn: <removed> expanded string:
<removed>
Jun  2 12:30:02.132: MatchNextPeer: Peer 1 matched
Jun  2 12:30:02.132: MatchNextPeer: Peer 2 matched
Jun  2 12:30:02.132: MatchNextPeer: Peer 101 matched
Jun  2 12:30:02.132: MatchNextPeer: Peer 102 matched
Jun  2 12:30:02.136:  Inside dpMatchCore:
Jun  2 12:30:02.136:  destination pattn: 1#<removed> expanded string:
1#<removed>
Jun  2 12:30:02.136:  Inside dpMatchCore:
Jun  2 12:30:02.136:  destination pattn: <removed> expanded string:
<removed>
Jun  2 12:30:02.136:  Inside dpMatchCore:
Jun  2 12:30:02.136:  destination pattn: <removed> expanded string:
<removed>
Jun  2 12:30:02.136: MatchNextPeer: Peer 1 matched
Jun  2 12:30:02.136: MatchNextPeer: Peer 2 matched
Jun  2 12:30:02.136: MatchNextPeer: Peer 101 matched
Jun  2 12:30:02.136: MatchNextPeer: Peer 102 matched
Jun  2 12:30:02.136:  Inside dpMatchCore:
Jun  2 12:30:02.136:  destination pattn: 1#<removed>  expanded string:
1#<removed>
Jun  2 12:30:02.136:  Inside dpMatchCore:
Jun  2 12:30:02.136:  destination pattn: <removed> expanded string:
<removed>
Jun  2 12:30:02.136:  Inside dpMatchCore:
Jun  2 12:30:02.140:  destination pattn: <removed> expanded string:
<removed>
Jun  2 12:30:02.140: MatchNextPeer: Peer 1 matched
Jun  2 12:30:02.140: MatchNextPeer: Peer 2 matched
Jun  2 12:30:02.140: MatchNextPeer: Peer 101 matched
Jun  2 12:30:02.140: MatchNextPeer: Peer 102 matched
Jun  2 12:30:02.140:  Inside dpMatchPeersMoreArg
Jun  2 12:30:02.140: dpMatchPeersMoreArg: Match Dest. pattern; called
(1#<removed>)
Jun  2 12:30:02.140:  Inside dpMatchCore:
Jun  2 12:30:02.140:  destination pattn: 1#<removed> expanded string:
1#<removed>
Jun  2 12:30:02.144: MatchNextPeer: Peer 1 matched partially
Jun  2 12:30:02.144: dpMatchPeersMoreArg: Result=1 after MATCH_ORIGINATE

The box is an AS5300. I'm at a bit of a loss, as all the Cisco docs seem to
indicate the voice dial-peers should be matched before the pots dial-peers.

Can anyone shed any light on this? Is this a bug in the dial-peer matching,
or in my config?

Cheers,
Chris.

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.859 / Virus Database: 585 - Release Date: 14/02/2005