Mitel Forums > Mitel MiVoice Business/MCD/3300

MiVB FXO device

(1/1)

acejavelin:
So I have a customer with a remote clinic that they want to put Mitel phones in connected to their virtual MiVB at the main hospital... They have a VPN that is rock solid, so no problem with the phones. Problem is at this location the local dial tone cannot be ported, so I need an FXO device to bring 4 loop start telco lines at the remote site into the vMVB. What is everyone using for this application right now? We used to use the AudioCodes MP1xx but those seem to be unobtainium these days... Anybody use the Grandstream HT841 or have another recommendation?

johnp:
I would think this should work as planned. I have done some things with Grandstream FXO, connecting paging and going back many years where I had a customer with 200 based systems. They had point to point T1 circuits, not sure if they ported their fax numbers from local pots or why I had to get them back working. They did rely upon fax and I did have to change their connections to Grandstream FXO to FXS devices to allow T.38 to work. Seem to remember the data between might have stayed but the TDM connectivity was gone and this was the root cause. Did get them back using analog ports on the main into fxo forwarded to fxs all riding their data connection.

Not sure if your primary outbound can allow the CID for this site, or you have an alternate perhaps vanity doing the same to allow phase out down the road.

Just my humble opinion.

ZuluAlpha:
TA 7100 series here. Mostly for FXS but my understanding is they're configurable either way. 7108's have been absolute troopers in closets with less than ideal conditions.

lundah:
I haven't used a Grandstream for FXO service, but I have about a dozen providing FXS for some analog devices including faxes that have been pretty solid as long as they get a regular reboot. You can set up a scheduled reboot in the settings, I'd do weekly or monthly.

acejavelin:

--- Quote from: johnp on April 12, 2025, 04:42:50 PM ---Not sure if your primary outbound can allow the CID for this site, or you have an alternate perhaps vanity doing the same to allow phase out down the road.
Just my humble opinion.

--- End quote ---
Outbound Caller ID isn't an issue... Primary uplink is a SIP trunk off our Broadsoft platform (basically, we are the local carrier to the Mitel) and we can send any caller ID we wish to our PSTN upstream carriers as long as we sign it with a valid Stir/Shaken signature. Only outbound calls we would send back out the copper lines is E911 calls from that clinic. Technically we could handle those as well, but it's just easier for the Mitel to route them out the FXO lines.

This is just a unique case where we can't port the numbers, and can't call forward the numbers to some other local number we can port... Sometimes working in very rural areas is a challenge.

Navigation

[0] Message Index