[cisco-voip] Inbound dial-peer matching

[Norton, Mike]

A-ha! :-)

I was missing the fact that the inbound matching occurs as soon as the FXS is taken off-hook. Thanks Brian. With that missing factoid, I understand now that it is actually working exactly how the documentation describes.

I can see with the debugs you pointed out that it is matching before dialing, thus the called number is null and can’t be used to match at “Step 1” of the documented matching procedure. The router was actually matching at “Step 3” because the calling number (which I’ve set using the station-id number command on the port) matches the destination-pattern of dial-peer 203.

For kicks, I now tried removing the station-id number from the port, so that the calling number won’t match any destination-patterns. Then it does select inbound dial-peer based on Port (“Step 4” of the documentation), and the dial-peer order matters in that case (icky).

To get the dial-peer selection that I want, the solution seems to be a “Step 2” match to beat the unwanted selection that was occurring at “Step 3.” So this does the trick:

voice-port 0/2/3
cptone CA
description SPARE FXS FOR TESTING
station-id name PWSD76
station-id number +17803575201
caller-id enable
!
dial-peer voice 203 pots
description DID 7803575201 TO FXS
destination-pattern +17803575201$
port 0/2/3
!
dial-peer voice 6 pots
description INCOMING FXS3
answer-address +17803575201$
!

Thanks again for the tips to set me in the right direction!

-mn


From: bmeade90 at gmail.com [mailto:bmeade90 at gmail.com] On Behalf Of Brian Meade
Sent: December-02-15 2:39 PM
To: Norton, Mike
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Inbound dial-peer matching

Mike,

For an FXS port, I believe the inbound dial-peer matching works a bit differently.  dial-peer 203 is listed first in the configuration with port 0/2/3 so that's what is matched first.  I believe the dial-peer match may be done as soon as you go off-hook on an FXS port.  You can run some dial-peer debugs such as "debug voice ccapi inout" or "debug voip dialpeer" to see this happen.

Brian

On Wed, Dec 2, 2015 at 4:30 PM, Norton, Mike <mikenorton at pwsd76.ab.ca<mailto:mikenorton at pwsd76.ab.ca>> wrote:
I need some help understanding inbound dial-peer matching with an FXS port I’m trying to set up.

I’ve read the document, “Understanding Inbound and Outbound Dial Peers Matching on IOS Platforms” <http://www.cisco.com/c/en/us/support/docs/voice/call-routing-dial-plans/14074-in-dial-peer-match.html>, but the behaviour I’m seeing doesn’t jive with my understanding from the document. Specifically, the document’s statement that “[the incoming called-number] attribute has matching priority over the answer-address and destination-pattern commands” seems to be just plain wrong.

Config excerpt pasted below. Platform is 2911, IOS 15.3(3)M6. Port 0/2/3 is an FXS port. I want dial-peer 203 to be the outbound dial-peer for calls TO the port (works fine, no problem there), and dial-peer 6 to be the inbound dial-peer for calls FROM the port.

When I place a call from an analog set on the FXS port, the router is choosing dial-peer 203 as the inbound dial-peer. Why? The documentation says that Step 1 of inbound dial-peer matching is supposed to examine the incoming called-number command, which to me means that dial-peer 6 should win the match at Step 1. What am I missing? Dial-peer 6 does work if I shutdown 203.

voice-port 0/2/3
cptone CA
description SPARE FXS FOR TESTING
station-id name PWSD76
station-id number +17803575201<tel:%2B17803575201>
caller-id enable
!
dial-peer voice 203 pots
description DID 7803575201<tel:7803575201> TO FXS
destination-pattern +17803575201$
port 0/2/3
!
dial-peer voice 6 pots
description INCOMING FXS3
incoming called-number .
port 0/2/3
!

--
Mike Norton
I.T. Specialist
Peace Wapiti School Division No. 76


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20151202/1d512ab4/attachment.html>