[cisco-voip] Paging solution interface

[Norton, Mike]

Well I just RTFM’d, and right you are. Nifty. Thanks for the info.

--
Mike Norton
I.T. Support
Peace Wapiti School Division No. 76
Helpdesk: 780-831-3080
Direct: 780-831-3076


From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Paul
Sent: September-07-11 12:45 PM
To: Norton, Mike; Sandy Lee; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Paging solution interface

I used to think the TAM-B (now discontinued and replaced by the TAM-B2) only connected to an FXS interface but it turns out so long as you provide external power to the module, you can use an FXO module as well.

________________________________
From: "Norton, Mike" <mikenorton at pwsd76.ab.ca>
To: Sandy Lee <Sandy.Lee at dti.ulaval.ca>; "cisco-voip at puck.nether.net" <cisco-voip at puck.nether.net>
Sent: Wednesday, September 7, 2011 11:16 AM
Subject: Re: [cisco-voip] Paging solution interface


TAM-B would connect to an FXS port, not an FXO like you currently use. FXO is a better choice because it inherently provides disconnect supervision. I have one installation, that pre-dates my involvement, that uses a TAM-B and a few times a year we have issues with getting stuck off-hook and need to shut + no shut it and/or power-cycle the TAM-B. For new installs, I use the Bogen PCM2000. It is more than just an “interface” to a paging system though; it *is* a paging system.

That said, it sounds like all you need is somebody who can correct the programming mistake that “they” made on your paging system. Disconnect the FXO, plug a standard POTS telephone into the paging system, and tell “them” to make that work. Most phone contractors who work on those kinds of systems get terribly confused/overwhelmed when you try to tie in with the voice gateway. The fact that you pointlessly chased down IOS updates and TAC cases tells me it has probably not been a confusion-free situation. Tell “them” you just want it to work with a standard POTS set (which, really, is all they need to know anyway) and, in my experience, they will usually have everything solved in no time. Then go in behind them, and plug it in to your FXO port.

--
Mike Norton
I.T. Support
Peace Wapiti School Division No. 76
Helpdesk: 780-831-3080
Direct: 780-831-3076



From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Sandy Lee
Sent: September-07-11 9:18 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Paging solution interface

Hi,
We have a 3rd party paging system that we connected through an FXO port on a gateway and worked fine. We defined a DN in UCM that is routed to the gateway, which is connected to the paging system that gives a dial-tone, we enter digits to determine which speakers to reach and that’s it. They recalibrated the paging system to add speakers and it doesn’t recognise the DTMFs anymore. We upgraded the IOS, opened a case with TAC and still doesn’t work.

I’m looking to replace the gw/fxo interface with something else, but don’t know what to look for. Some of you guys talked about Bogen TAMB, but how does it work exactly? Is this what I need ?

Thanks and regards.
Sandy.


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110907/8b7bf04f/attachment.html>