Hi all. I have run into an issue that I dont know much about. Im trying to integrate a Valcom V2006A in with a CUCM for overhead paging. Cisco says this will work, but Im not sure how to get this setup. They say use an FXO port, which I have one available. Im not really sure what else needs to be done. I have connected the one pair cable from the valcom to the FXO. Im really not sure how to configure this though. Anyone with any experience know how to do this? I appreciate it.
A 2600A should work fine with an FXO port. You need to ensure that your signaling matches on both sides, default for Cisco FXO is Loop Start.
I'm assuming your gateway is already configured in UCM. I'm using H323, and can't speak to MGCP/SCCP. All you need is a dialpeer pointed at the FXO port with the desired destination pattern (paging extension) and direct-inward-dial. On the CallManager box, a simple route pattern matching the desired paging extension pointed at the proper gateway will work. Let me know if you need more granularity.
Hey, thanks for responding. Im using MGCP for the gateway. I did configure for Loop Start, then configured a route pattern to go to that FXO port. Of course, I couldnt get it to work. I get a fast busy. So, Im not sure about the valcom side, in that Im not sure what it expects to see. So my questions at this point:
1. Can I use MGCP with the gateway that has the FXO port for this situation?
2. Will what I described about how I configured it, is that supposed to work?
I may need more granularity, if you dont mind. I literally know nothing about the valcom. Thanks.
Paging system integrations are always tricky for sure :(
The Valcom will work with a FXO connection but does expect a certain number of digits etc.
I would contact Valcom Tech Support for some good help. They have always been great to work with and are familiar with Cisco FXO/FXS setups.
Valcom Tech Support
Here is the guide for the V2006A as well (which I'm sure you already have, but just in case).
Hope this helps buddy!
Thanks, yeah, I have the pdf and I called Valcom, which the guy I spoke with didnt seem very interested. Either way, thanks Rob. Ill work with it and see what I can do.
All, I got this working today with the help of TAC. Im certain I have learned a few things on this one. This was something I had never seen, but I feel I may see this again. Thanks for the help on this.
I created a route pattern to route over to the FXO port. I said when they dial 1100, that the 110 was dropped, and 0 was passed over to the FXO port. At that point, it goes directly into the valcom. Now, keep this in mind, when I had issues with it, I did not understand the valcom setup. And Id have to look at it again if I wanted to do this again, but I can say that I had it hooked up wrong in the beginning.