The system is setup to go to auto attendant for incoming calls. There is one incoming number (555-123-4567 for example) that needs to go directly to an extension. It is connected to a security system. A live person has to answer the phone and hit 9 to open the door.
How is this accomplished?
You can use CCA to configure incoming call handling, or DID mapping. In CCA 1.9 this should be in the Telephony-Voice page under the Dial Plan tab.
This isn't done under DID. You don't really have DIDs with FXO. You need to find the configure the FXO to ring an extension. I don't have CCA 1.9 installed right now, but under telephony, there is a place to configure FXO's to ring an extension. That is all you need to do to make this work.
This system that opens the door is what is calling on the FXO correct? In that case, when the user presses 9, it will trigger the correct response for the door system.
For configuring the FXO inbound call routing, navigate to the Configure->Telephony->Voice, Dialplan tab, then look for "FXO Trunks Destination" and choose "Custom" from the dropdown menu. Now click the configure button and click Add to add in your trunk destinations. Just give a description, choose the port, and choose the extension you wish to ring (which can be a user or AA/VM pilot). For an example, please view the screenshot I attached.
Thanks for the responses.
What I am really looking for is any FXO port that takes a call with the specific number (555-123-4567) go to extension 222. If it is not 555-123-4567 go to extension 290 (which is the auto attendant.)
A call from 555-123-4567 to the UC500.
When a person at the door hits the button, it initiates a call from 555-123-4567 to the business. The business picks up, asks who is there than hits the 9 on their phone to open the door.
A couple of facts about analog CO trunks:
1) There is only one "connection plar" statement under an FXO voice port, meaning there can only be one destination.
2) Caller id is usually passed after the first ring or first few rings, too late to select an inbound voice port based on calling number. In other words, for inbound calls we strictly depend on what the phone company does and which line they select.
You could point your connection plar to a sequential hunt group that hits 222 first. Based on caller ID, the person at the IP phone may decide to answer or not. If they don't, the next extension would ring (AA).
Let me add that since this sequential hunt group will have a SIP call leg (CUE AA) you will need to create it outside of CCA with the "voice-hunt" CLI.
You could potentially match inbound SIP calls based on Calling number, rather than called number, and then send them to different AA scripts. Go ahead and experiment with the "answer-address" command, under the inbound VoIP SIP dial peers.
Back to the FXO with AA....
If I open the AA_transfer.aef script in the CUE editor, how hard would it be to add some lines to look at the called number. If it matches the specified number, it goes to the designated extension?
I opened a case with TAC. Here is what they came up with:
voice translation-rule 1
rule 1 /.*/ /222/
voice translation-profile 1
translate called 1
dial-peer voice 222 pots
translation-profile incoming 1
If a call comes in from 4145551234, it goes to extension 222. Any other number goes to the auto attendant.
Thanks again for everyone's help.