FXO port doesn't have DNIS and it could be matched as inbound only by answer-address, destination-pattern, port number.
Configuring "answer-address ." is not a solution because in this case any inbound call to any FXO port will be matched and served by VXML application.
Configuring destination-pattern also has no effect. As I can see from "debug voip dialpeer inout" inbound call will be always matched by the pots dial-peer that had been configured with "destination-pattern .T".
Here is FXO port configuration
supervisory disconnect dualtone pre-connect
timeouts initial 20
timeouts interdigit 20
timeouts call-disconnect 1
timeouts wait-release 2
connection plar 1234567
here is dial-peer that I want to configure as inbound
dial-peer voice 300 pots
incoming called-number 1234567
How can I configure 2811 for executing VXML script only when call arrives to the selected FXO port?
It may benefit you to turn on 'debug voip dial-peer all' and watch how the dial-peer matching is occurring.
What I would do in your scenario is not have *any* POTS dial-peers with incoming called-number nor answer-address defined. Or if you do, don't use a '.' wildcard anywhere otherwise that will be a valid match.
Now, you need to be careful that ANI with destination-pattern doesn't match anything. So you need to make sure that the ANI coming in the port doesn't match any 'destination-pattern' statements on any POTS peers. Assuming that's okay, it will match based on port, which you already have configured, and you should be good.
The other option is to configure a station-id number under the port. This will force a specific ANI when that port is hit. You then can use answer-address under the dial-peer with that ANI, which will match based on that criteria. This will, however, make all calls in from this port have whatever ANI you configure here. So if that FXO is from a PSTN circuit, it would defeat the purpose of inbound CLID.
If you can post the output of 'debug voip ccapi inout' and your full configuration (all voice-ports and dial-peers), I can be more specific on suggestions which will work. It's partially circumstantial based on how you are doing inbound dial-peer matching for other ports/circuts.
I have found a workaround for this issue, i.e. if my pots dial-peer 300 is correctly matched as outbound dial peer, just configured application for outbound
dial-peer voice 300 pots service test out-bound destination-pattern XXXXXX incoming called-number XXXXXX port 1/0/17
This configuration works pretty fine!
As to a 'debug voip ccapi inout' as I remember default application was started to handle call. I will post output a bit later.
Also I found that my configuration has a kind of phone security leak.
When I called from PSTN to number XXXXXX then FXO port 1/0/17 goes off-hook and I've heared dial tone. After that I was able to input in tone any phone number and place a call to ANY number through the 2811 box.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...