cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
12328
Views
5
Helpful
13
Replies

Valcom Paging on FXO Port

Jason Ryan
Level 1
Level 1

Hello,

Im having a bit of a hard time getting a new Valcom system setup.

Currently my Vlacom V-2006a is plugged into my 0/1/1 FXO port. The Valcom and FXO are set to loop start.

I have a dial peer that points the extension to be dialed (*79) to the port. When dialed the port light goes green but gets a fast busy.

Ive flipped the polarity to no avail.

What am I missing?

1 Accepted Solution

Accepted Solutions

Change the destination-pattern from "*79" to "*79." and remove the "forward-digits all".  Should take care of it.

You could change that pattern only accept valid zones (i.e. "*79[0-X]" -- where X is the last zone # and 0 is for all zones) but I wouldn't worry about it.

View solution in original post

13 Replies 13

will.alvord
Level 5
Level 5

It's been awhile, but your description sounds very familiar.  A couple of questions though.

1) What's your destination pattern on your *79 dial-peer?

2) What does the v2006a expect?  (i.e. number of digits)

Remember that with pots peers, explicit matches are dropped.  So if the v2006a is expecting a single digit for each zone (think that's a multi zone system), then your destination pattern would be "*79." or you have to prefix what you want the paging controller to receive.

Will,

Heres my dial peer (which could be very wrong )

dial-peer voice 502 pots

description ***Paging***

destination-pattern *79

direct-inward-dial

port 0/1/1

forward-digits all

Also the Valcom is expected 1 digit for the zone (its a multi zone) as you mentioned.

Thank you

Jason Ryan

Change the destination-pattern from "*79" to "*79." and remove the "forward-digits all".  Should take care of it.

You could change that pattern only accept valid zones (i.e. "*79[0-X]" -- where X is the last zone # and 0 is for all zones) but I wouldn't worry about it.

Now when I dial *793 it lets me dial it all but I get a fast busy there as well. The port does light however. Might I try the polarity again?

Sure.  I think there's a command to reverse the polarity though but it's probably dependent on the module type and ios.  If you've got ready physical access, then it'll be faster to do it manually.

Same results after a cable flip. Would I need to set the FXO ports as ground signal?

I'd suggest calling Valcom's support.  To be honest, my memory is pretty hazy and I don't want to waste your time.  The dial-peer config should be fine now though.  I don't recall any other specifics, but I do remember that I had to call Valcom and their first level support is super knowledgeable and clued me in pretty quickly.  Now that I think about it, I think I had to buy some sort of adapter.  Call Valcom though.  Sorry I couldn't be more help.

No problem. I actually just gave em a call and said the way its setup currently sounds right. I appreciate your help! As a side note, would this setup also work on a FXS port?

If I remember right, the integration works with either but with 1 you need an intermediate adaptor inbetween the analog port and the paging controller.  I'm pretty sure FXO<->v2006a is good, but otherwise you'd need FXS<->adapter<->v2006a.  Then again, it's been a long time.  I'm also pretty sure that it had to be loop start like you said.

Just found this link:

http://www.valcom.com/techsupport/ip_solutions/config-guides.htm

You didn't mention what you're using for call control, protocols, etc, but seeing as how you're getting as far as you are, I'd think either the mgcp fxo or h323 fxo docs in the top left section should be what you need.

Is there a way to proceed with this CLI wise?

I hear ya. 

The 2 docs I referenced both have CLI sections.  The both also have UCM config sections as well.  I won't bug you again to reveal your super secret call control mechanism (CUCM, CME, versions, etc), since it's pretty clear that the problem is with the FXO<->valcom integration.

You can remove the direct-inward-dial statement from your dial-peer.  Shouldn't hurt anything, but it's not needed.

translation-rule 1

rule 0 3100 0

rule 1 3101 1

rule 2 3102 2

rule 3 3103 3

dial-peer voice 3100 pots

destination-pattern 310[0-3]

translate-outgoing called 1

port 0/3/0

"This completes the configuration of the gateway router. If the Valcom Paging Controller has a Battery Feed switch for the Tip & Ring connection, be sure it is in the “On” position, and then connect the gateway FXO port to the Tip & Ring connection on the Valcom Paging Controller. A call placed to the phone number configured in Step 7 will connect directly to the Valcom controller. If using a single-zone controller, such as the V-2001A, the call will be connected directly to the page output. If using a multi-zone controller, such as a V-2924A, the page controller will provide a secondary dial tone. Enter the appropriate dial code to access the desired zone to which you want to page. If a reorder tone (fast busy) is heard on the first dial attempt, reverse the wires on the Tip & Ring connection."

dellison
Level 1
Level 1

Hi Jason,

Feel free to give our Valcom Technical Support line a call at 800-825-2661.  This setup has been tested in our lab, so I'm sure we can get it to work for you.

Valcom Technical Support

Thank you!


So its turns out all the setup on both the UC and Valcom were right. However it doesnt help when the cable between them is bad.

I thought this had been tested as good already and I didnt have a voltage meter so I didnot test it. Had one of the cablers come out and found it was bad. Replaced it and boom worked like a charm.

Thanks for all your help!

Will Ill give you the correct answer since I did need to put this command in.

Thanks again.