Mario,
Let me preface my suggestion with the fact that you didn't specify how many extensions were at the remote office nor what brand of PBX you're using.

Since you suggested a one line Linksys device, I'll assume you're only dealing with a hand full of extensions, at most. Otherwise, you might want to look into bridging a T1 signal with channel banks on each side; or better yet, you could pipe all PBX extensions (for the remote office) into a channel bank and convert to a T1 which feeds into an Asterisk server (with Digium T1 card). I suspect that going into this would be overkill.

That said, I'd be weary of mixing VoIP and PBX. I've had Digium equipment hooked to a Lucent Partner system fry (unable to handle extension signalling?). And I suppose you might even fry ports on the PBX end (I believe I had that problem too). I would generally stay away from mixing legacy PBX (fxo ports) and VoIP ATAs. But, you'll save a ton by getting your proposed setup to work. So, it's worth a shot. But, I wouldn't guarantee anything to my boss if I were you.

John's suggestion is the correct setup. Not sure what hardware would be best; but you might try WRT54GL (with DD-WRT firmware) for AP and bridge solution and a Sipura 3000. The sipura allows for incoming TDM calls (on FXO port) to route to VoIP port (rather than a simple FXS phone). You need this functionality in your situation. Then use your preferred VoIP phone on the remote end.

Keep in mind that you will probably not be able to dial extensions from the remote end, though you theoretically should be able to have extension dialing from the main office to the remote end POTS phone. I call the remote end a POTS phone because POTS signalling is basically the only common denominator between the remote end and the main office. Typical VoIP ATAs don't understand (and can't generate) Samsung/Lucent/Other legacy, proprietary PBX signalling. There are some VoIP devices out there that are made to integrate with legacy PBX systems. I haven't tried them; and prepare to pay $. If you could find one, that could get outbound extension dialing from the remote office.

Oh, and that solution is just for one phone. You'd need multiple sipuras for multiple phones (or split it out with an ATA on the remote end to another PBX and have the main office dial extensions to get to someone at the remote office; this would be ugly).

Hope that helps,

Brian Whigham
Yonder Networks
www.yondernetworks.com

John J. Thomas wrote:

PBX>FXOmodule>Ethernet>WirelessBridge>WirelessBridge>Ethernet>FXS module

Here is one example, Google will probably get you cheaper ones....


John


-----Original Message-----
From: Mario Pommier [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 6, 2006 10:57 AM
To: 'WISPA General List'
Subject: [WISPA] phone-to-voip-to-ethernet conversion

I have an interesting application, that maybe someone has tried:

Customer is expanding to a remote office, across the street from the main office.
They need to connect voice and data between the two.
There's clear LOS, so a wireless link will work.
The telephone PBX is at the main office, of course.
I need to send avoice line across the wireless link from the main office to the remote one.
How do I add the voice?  Couldn't I simply do this?

PBX ----[telephone cord]---->[Linksys VoIP phone]----->[switch (which also has an uplink to the wired network)]---->[wireless radio]

On the other side of the link, the telephone cord would go into a desktop phone terminal.

Thanks.

Mario
---
[This e-mail was scanned for viruses by our AntiVirus Protection System]

--
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/



--
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

Reply via email to