voice class e164-pattern-map does not work with dial-peer group

[RHA]

Hi,

does anyone know, why "voice class e164-pattern-map" does not work, in case it is configured in a dial-peer, which is member of a dial-peer group?

In case, the dial-peer is not member of a dial-peer group, it works.

In case, the dial-peer is member of a dial-peer group, it does not work.

System image file is "flash:c2900-universalk9-mz.SPA.157-3.M4b.bin"

[Roger Kallberg · Accepted solution]

That is because when you use DPG you bypass normal call routing logic. When you use DPG you define on the inbound dial peer what dial peer(s) you will use in the outbound direction. Worth knowing is that for a dial peer to be eligible for outbound use it needs to be in an operational state, meaning that you will need to have either a destination pattern or a e164 number map set on it and if used SIP option ping needs to have the dial peer in an up state. Because of this you often see bogus destination numbers set on outbound dial peers that are used by DPG. Another side note, the destination pattern, in either of the options outlined above, will actually work if the inbound dial peer does not have a DPG set. This can be useful for cases where you’d want to match specific calls on a different inbound dial peer, for whatever reason, but still use the same outbound dial peers.

[b.winter]

Hi,

no outbound matching function will work. Because that's the idea of dial-peer groups.

With dial-peer groups, you already define the outgoing dial-peer(s) based on the inbound dial-peer.
That's why you often see the "destination-pattern BAD.BAD" or something in the outbound dial-peer. It is needed for the outbound dial-peer to come up/up, but not for dial-peer matching.