[cisco-voip] [External] Voice Gateway Dial-Peer Precedence/Processing Order

[Gary Parker]

Thanks Tim, understood.

Gary

From: Johnson, Tim <johns10t at cmich.edu>
Date: Friday, 11 November 2022 at 13:17
To: Gary Parker <G.J.Parker at lboro.ac.uk>, voip puck <cisco-voip at puck.nether.net>
Subject: RE: [External] [cisco-voip] Voice Gateway Dial-Peer Precedence/Processing Order

** THIS MESSAGE ORIGINATED OUTSIDE LOUGHBOROUGH UNIVERSITY **

** Be wary of links or attachments, especially if the email is unsolicited or you don't recognise the sender's email address. **
In the preference list on that page, they list “incoming uri” higher than “incoming called-number” for inbound H.323 call legs. So based on that, the “incoming uri” dial peer should be chosen first if the string is the same in each dial peer. The order in which it appears in the config or the dial peer number does not make any difference.

From: Gary Parker <G.J.Parker at lboro.ac.uk>
Sent: Friday, November 11, 2022 8:05 AM
To: Johnson, Tim <johns10t at cmich.edu>; voip puck <cisco-voip at puck.nether.net>
Subject: Re: [External] [cisco-voip] Voice Gateway Dial-Peer Precedence/Processing Order

Thanks Tim, I’m not sure fully understand the precedence, still.

If I have to two dial-peers that both match a given inbound call, for example, and one is matching on ‘incoming uri’ and the other is matching on ‘incoming called-number’, for example, will the ‘incoming uri’ dial-peer always match first, regardless of the order it appears in the running config, or the dial-peer number?

It’s the matches themselves that determine precedence in the matching order?

I note that you can put multiple matches within a dial-peer and only one needs to match, it’s a shame that compound matches can’t be built.

Gary

From: Johnson, Tim <johns10t at cmich.edu<mailto:johns10t at cmich.edu>>
Date: Friday, 11 November 2022 at 12:57
To: Gary Parker <G.J.Parker at lboro.ac.uk<mailto:G.J.Parker at lboro.ac.uk>>, voip puck <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: RE: [External] [cisco-voip] Voice Gateway Dial-Peer Precedence/Processing Order

** THIS MESSAGE ORIGINATED OUTSIDE LOUGHBOROUGH UNIVERSITY **

** Be wary of links or attachments, especially if the email is unsolicited or you don't recognise the sender's email address. **
I believe this is what you’re looking for. Order is based on how you have your DNIS/ANI pattern configured.

https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube/configuration/cube-book/cube-dp.html#concept_1ACF9AAF93C24BB988E4A2EE3734C8A6

From: cisco-voip <cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>> On Behalf Of Gary Parker
Sent: Friday, November 11, 2022 7:39 AM
To: voip puck <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: [External] [cisco-voip] Voice Gateway Dial-Peer Precedence/Processing Order

Hi folks, feel stupid asking what feels like a newbie question, but I can’t seem to find an answer online anywhere and I ‘ve never needed to worry about this in the past!

In what order are dial-peers checked for a match for calls passing through a voice gateway? Is it simply the order they appear in the running-config, does the dial-peer number play any part, or is there something else influencing it?

--
Gary Parker
Unified Communications Service Manager
Loughborough University, IT Services
Phone - +441509635635<tel:+441509635635>
Teams - g.j.parker at lboro.ac.uk<callto:g.j.parker at lboro.ac.uk>
https://www.osx.ninja/pubkey.txt

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20221111/e96ca50e/attachment.htm>