E&M connectivity

[elohelae]

Good afternoon

I have an old siemans islx on an oil rig and onshore i have an old realtis phone switch. They are connected using 12 E&M trunks with a separate serial connector for signalling.

Acting as the carrier are two cisco routers at either end which provide e/m tunnels to the far end. There is no real cisco interaction.

I need to point the trunks to another location, however i only have cisco at my end ( yes i know, not a real phone switch)

I would like to place a mitel in the middle to provide a conversion between the ananlogue e&m and a qsig interface.

Can it be done using either a 3300, 2000 or a 200?

Any help would be appreciated.

cheers

 

[kwbMitel]

the hardware required is very old

3300 - no (I think)
2000 - Yes but obsolete
200 - Yes but soon obsolete

**********************************************
What's most important is that you realise ... There is no spoon.

 

[Lundah]

Might be able to do with with a 3300.

If you don't need the PBX to do anything other than convert the E&M into something more modern, what about SIP Gateways?

 

[kwbMitel]

Right you are Lundah, I was not thinking of non-Mitel devices

That being said, the Mitel would not be required at all

E&M to SIP to Cisco

Example:

http://www.ovislink.ca/voip/voip800.htm

Feature Summary
8-port VoIP Gateway, Support 8 Channels
2 Module slots support 4-port FXS, FXO, or E&M modules
Support SIP and H.323 Protocols
Web management, Telnet, DDNS, QoS support

**********************************************
What's most important is that you realise ... There is no spoon.

 

[elohelae]

All

Thank you for responding, the issue is not the E&M ports it is that the signalling is controlled by the serial port interface, and thats the kicker. On the siemens it is acting like a d channel. I need th mitel equivalent and i suspect it does not exist.

Thank you for looking, if you have any more suggestions then let me know.

 

[LoopyLou]

The 3300 supports E&M trunks but only via the SX2000 peripheral nodes that are manufactured discontinued.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[mitelmania]

I think what you have is "APNSS" which the Mitel SX2000 supports but the 3300 does not as it does not support the Datasets that provided the serial interface for signalling, if your APNSS can be stripped back to basic E&Ms you could link into a 3300 that could then provide QSIG onwards, but if you want to try and connect using APNSS then it would have to be an SX2K, that said I have only ever seen it Mitel to Mitel, don't know if it would work across vendors.

 

[mitelmania]

PS, getting an SX2000 that has the APNSS licence would be nigh on impossible and I don't think you can purchase the options from Mitel any more, and also as LoopyLou pointed out Per Cabs are now discontinued although probably availble second hand. It also needs a DSU Cab & Cept Formatter along with DataSet. In brief, don't even go there, stipping the DX back to basic E&M if thats all you can get over your datalink or placing a gateway offshore is probably your best options

 

[elohelae]

Once again, thank you. Ive looked at the options surrounding the per and dsu nodes but it comes back to the issue that i need the serial interface along with the E&M cards. It is looking like a forklift job unfortunately.

have a great weekend.

 

[mitelmania]

There are numerous Datasets that provided the Serial Interface, a DS2103 was one of the most common ones, it connected to a digital extension port and provided a 25 way serial port, most commonly used in hotels to link into a front of house PC but in 2 APNSS connected SX2000s there would be 1 on each switch and I think the MUX needed a specific type of card for it to plug into.

On the SX2000 it was possible to remove the dependencey on the serial interface and Cept card by changing the Circuit Decriptors and associated programming as the E&Ms would be wired as standard E&M circuits to the MUX/Router at each end, I think you only lose things like extension names and callback facility which you would have with APNSS.

If you could reconfigure the isdx to standard E&M a 3300 with a per cab & E&M cards and an E1/T1 module would give you the connectivity you mention above.

I take it you are moving the onshore location and don't want to take the Realtis with you ?

 

[elohelae]

Mitelmania

Thank you for the response. I have limited access to the isdx offshore, so i cannot make hardware changes. I am looking to do this change on shore with putting in the mitel.

do you have any experience with a switch outputting e&m with a serial port, then connecting to a mitel with e&m ports and a ds2103 or similar?

where would you tell the 2103 to pass the information to the e&m card to make or disconect calls? then how would it know the protocol to decide call connect information.

i originally thought that this could be done with the scenario mentioned but i think this may be a method of connecting that is just purely for the isdx.

thanks again, cheers