That would allow you to place outbound from router via FXO and viceversa from PBX. You would have single stage dialing this way and no supervisory disconnection. But it requires the PBX to be programmed also. Router wise is a simple configuration that you can sort out once you've the hardware in place and connected. I would reccomend H.323 for this.
Be aware doing integrations "not the right way", when it comes out unsatisfying the voip integrator is always held responsible while PBX guys are very good a finger pointing.
I can find out port availability on the PBX side, but getting FXS ports should be a possibility.
Just so we are on the same page..i would just setup the 28xx as a h323 gateway and setup the route pattern to use it. On the vgateway i would setup a route-group using all of the FXO ports and assign that group to the dial-peer for the PBX extensions.
For the FXS ports, i'm assuming i will need the PBX to pass the extension via DMTF? From then how would i pass it on to the CM? If I'm wrong on that, how would i set it up for inbound calls?
Hi, when you have FXS on the router and FXO on the PBX (commonly called trunk ports in PBX parlance), all what you have to do is to program PBX so that certain numbers go out said FXOs, PBX goes off-hook, sends the tones and the call is directly routed to the corresponding extension on the CM.
On the router you have the trunk-group command to handle multiple ports as a whole and this simplifies the configuration a lot.
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 ...