Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - tomj

Pages: [1] 2
1
Mitel MiVoice Business/MCD/3300 / Re: PSTN Line Busy Alert
« on: December 19, 2013, 02:28:51 PM »
ISDN, PRI, BRI or SIP trunks will provide guaranteed disconnect supervisor, it is unlikely you will have lockout issues with these trunks.

The embedded LS (loop start) or ASU LS trunks support line break (the default setting) or line reversal configured in the CO Trunk Descriptor or Tone Disconnect.

You first need to confirm the Aussie Telco LS Trunk disconnect method. Connect an ordinary phone to the trunk line, ring the number from your cell phone, answer the call and hang-up on the cell phone. If you hear a “busy tone” then you need to establish the tone and configure the 3300 accordingly. If you don’t then you just need to change the disconnect timer or enable line reversal.

Setting up Tone Disconnect the first time is tricky but works well when configured correctly.



2
Mitel MiVoice Business/MCD/3300 / Re: Busy lines/locked lines
« on: November 19, 2013, 02:21:05 PM »
Agreed, inter-pbx trunks, E&M for example provide answer and disconnect supervision, Consta on the other hand is piggy-backing Nortel (analogue extension lines) to Mitel 3300 LS (loop start) trunks. Not ideal, but we’ve all done it.

Trunk lock-up is occurring because the Mitel LS trunk is expecting a line break to indicate the (Nortel) far-end has hung-up. Outside of North America the Central Office (public telephone exchange) typically sends a disconnect “busy tone” as the clear down signal rather than a line break. Line reversal is a CO Descriptor option.

You may have noticed a Class of Service option to provide this on ONS ports introduced recently. Guessing this was introduced for European based applications. Google busy tone disconnect, take a look at the Max Terminator, used this way back with the SX2K.

Since about Release 8/9 LS trunks on the CX/CXi/MXe/ASU support tone disconnect, you will find CO Tone Disconnection in ESM and a bunch of tone/frequency settings (primarily for Latin America) hidden away in the Product Support (software) directory. In practice, unless you have a friendly service provider or handy data sheet you need to record the tone, analyse it, configure CO Tone Disconnect and reboot. It does work!

3
Mitel MiVoice Business/MCD/3300 / Re: Busy lines/locked lines
« on: November 18, 2013, 04:12:18 PM »
Hi Karma

Does the Nortel send a "tone" when the call clears, do you reconise this, could you record it?

Regards

Tom

4
Mitel MiVoice Business/MCD/3300 / Re: Busy lines/locked lines
« on: October 23, 2013, 03:42:07 PM »
Hi Ralph

When configuring LS (loop start) analogue trunks you assign a CO Trunk Descriptor to define a number of working parameters including the disconnect method. The default setting is “disconnect” (a current line break) of 500mS sent by the serving CO telephone exchange. You can change the disconnect timers or the method to “reversal” (a line polarity reversal) as required.

However, outside North America and the UK the CO public telephone exchange will send a “hang-up” tone as the disconnect signal. FXO/FXS equipment or PABX systems often do the same. In fact there is now a Mitel COS Option to do the same.

The reason trunks hang is because the CO telephone exchange/far end disconnect signal is not understood by the system, either because the CO Descriptor disconnect method is wrong and or the disconnect timer is incorrect. Use an in line multi-meter and test-butt telephone to confirm line break, line reversal or hang-up tone.

Back in Release 8.0 Mitel introduced Hang-up files within the system software Product Support directory which you had to ftp to the system later simplified with the introduction of the CO Tone Detection Form. There is a Tech Note on this "older" method somewhere.

If you are lucky your telephone company will confirm the hang-up tone if not you will need to record the tones and use a freeware program to analyse them. I’ve forwarded an incoming call to voicemail, recorded the tone, ftp the recording to a PC and used a freeware program to analyse. You then complete the CO Tone Detection Form, reboot the system to activate. Can't work hwo to paste an image but see attachment copied from other post - this shows a completed CO Detection Form

Tom


5
Mitel MiVoice Business/MCD/3300 / Re: 3300 Locked Analogue Lines
« on: October 21, 2013, 08:56:05 AM »
Take a look at sarond's screen shot, you will need to do something similar, but thinking tone type should be non-continuos.

6
Mitel MiVoice Business/MCD/3300 / Re: 3300 Locked Analogue Lines
« on: October 21, 2013, 08:52:25 AM »

Your CO Descriptor - Calling Signal=Disconnect (the default), I can't see the timer but the deafult is 500mS.
This means your trunk is expecting a line break of 500mS or above before it will disconnect the trunk.

You can try changing the Calling Signal disconnect timer or try Reversal but I would guess the far-end is sending a "busy tone".

Connect a test-butt telephone across the copper line and monitor the line for the clearing signal, if you hear a tone, then you need to confirm the frequency, cadence and levels. Once you have these you will need to enable and configure CO Tone Detection. I've updated your excel document with example values but do not have a screen shot unfortunatley. Establishing the frequency is trick but there are ways and means.




7
Mitel MiVoice Business/MCD/3300 / Re: 3300 Locked Analogue Lines
« on: October 21, 2013, 04:45:03 AM »
Guessing your trunk provider is using "busy tone" disconnect and not line break (the deafult setting).

To get your trunk lines to disconnect properly you MUST establish the disconnect signal or tone.

Trying calling the provider, ask them to confirm the disconnect signal, if it is line break or line reversal then you may need to amend the CO Descriptor if they are using tone disconnect then you will need to take a look at CO Tone Detection.

8
Mitel MiVoice Business/MCD/3300 / Re: Busy lines/locked lines
« on: October 21, 2013, 04:41:18 AM »
Hi Consta

I have  monitor these analogue lines, and receives  a tone when the far end clears down.

This confirms the far end is using "busy tone" disconnect and not line break (the deafult setting).
To get the lines clearing properly you MUST establish the disconnect tone.

Do you have voice mail on the system? If so use this to record the tone.

1. Create a extension number and mailbox
2. Call Reroute Always the extension number to the voicemail hunt group
3. Dial into the system from outside, transfer to the extension - the call will forward to vmail - hang up at the far end
4. Use the maintenance command STATE <PLID>  (circuit of the trunk) to confirm it is busy, wait two or three minutes
5. BUSY & RTS the trunk PLID to release the trunk
6. Logon to the extension voicemail account, listen to the message, you should hear the tone

Now the tricky part, you need to analyse this tone to complete the CO Tone Detection Form, once done the trunks will disconnect.

9
Mitel MiVoice Business/MCD/3300 / Re: 3300 Locked Analogue Lines
« on: October 18, 2013, 12:18:19 PM »
You have to be careful when allowing LS analogue trunk to analogue trunk connection as these do not necessarily support “Disconnect Supervision” unlike digital or IP trunks particularly when outside NA.

The embedded LS and ASU LS Trunks will support the following clearing signal:

Line Break -  CO Trunk Circuit Descriptor default value of 500mS

Line Reversal -  an optional CO Trunk Circuit Descriptor value

“Busy” tone disconnect supervision - used in Europe, Middle East and Africa

You need to establish what disconnect method is being used, the first two are straightforward. Assign a “new” CO Trunk Descriptor and try the two options, you may need to change the disconnect timer.

The latter is tricky as you need to confirm the disconnect tone frequency, level and cadence before configuring (system wide) CO Detection. Unfortunately, if you use Auto-Attendant or trunk to trunk connection you will need to complete this or get to know Busy/RTS.

Do you have a recording of the tone?

Good Luck!

10
Mitel MiVoice Business/MCD/3300 / Re: Busy lines/locked lines
« on: October 16, 2013, 04:52:38 PM »
Download a free tone minitor software such as http://www.nch.com.au/wavepad/index.html and use this to confirm the disconnet tone frequency, level and cadence, then configure the MCD CO Tone Disconnect.

11
Mitel MiVoice Business/MCD/3300 / Re: Busy lines/locked lines
« on: October 15, 2013, 12:19:50 PM »
Hooking up LS Trunks to PBX analogue extensions can be tricky as these may not provide disconnect supervision.
Use a test butt telephone to monitor the line when the far-end clears.

Embedded or ASU Trunks (from Release 8 or 9) support, Line break, line reversal or tone disconnect supervison.

Trunk Circuit Descriptors - CO : Call Clearing Signal : reversal  or disconnect : Disconnect Timer=500mS (default)

CO Tone Detection : It can be tricky confirming tones, levels, frequency & timers but works well when configured correctly.

Hope this helps!


12
Mitel MiVoice Business/MCD/3300 / Re: Busy lines/locked lines
« on: October 13, 2013, 03:53:05 AM »
Hi Consta

If you monitor these analogue lines, do you hear a tone when the far end clears down?

If so you can enable CO Tone Disconnection, the system will "listen" for these tones and disconnect the line. It can be tricky establishing the disconnect tone and frequency but when you find this out your trunks will disconnect correctly.

What you can do is forward an extension to voice mail, ring in via the analogue line, wait for the call to forward to vmail, hangup, the remote CO or PBX will send the "tone" disconnet which will be recorded in the voicmail. You can then analise this to establish the tone frequency and cadence.

13
Mitel MiVoice Business/MCD/3300 / Re: Help with QSIG to Avaya CM
« on: October 13, 2013, 03:46:07 AM »
Ralph, thanks for your reply, I'm running QSIG E1 and not T1 and would prefer ISO.

We are connected to an old Avaya system with voice mail on another MCD system.

The issue we have is when calling (Avaya) extensions with call forward on busy - this will send the call back-up the QSIG link - we receive a very large QSIG message (I have the this somewhere) that is not understood by MCD and results in an error message displayed in the maintenance window. Thinking the Avaya is including call forwarding reasons codes or similar that need disabling.

14
Mitel MiVoice Business/MCD/3300 / Help with QSIG to Avaya CM
« on: October 11, 2013, 09:47:20 AM »
Does anyone have the Avaya DS1 Circuit Pack and Trunk Group settings for (ISO) QSIG?

Using MXe E1 module at MCD 6.0

We kinda have this working but with call forwarding issues.

Any help would be appreciated!

15
Mitel MiVoice Business/MCD/3300 / Re: Ls Trunks het lockout " Help Please "
« on: November 12, 2012, 04:03:09 AM »
In the UK the serving telephone exchange sends a line break disconnect of approx 500mS when the calling party (who controls the call) hangs-up. The CO Trunk Circuit Descriptor “Disconnect Timer” should be programmed accordingly i.e. lower than this value.

Whilst some public telephone exchanges use “line reversal” disconnect supervision “busy tone” disconnect is by far the most common form of disconnect supervision elsewhere. This is easy enough to identify, connect a regular phone to the phone line, answer an incoming call, hang up at the far end and listen for tone(s).

If you’re lucky the phone company will confirm the tone(s) otherwise you will need to record and analyse the tone to establish the tone(s) frequency and on/off cadence. One way is to set-a voicemail box, ftp the message and use a freeware program to analyse. Once you know the tone you need to configure and enable CO Tone Detection.

There are some examples in the MCD Software Product_Support\COTonesDet directory

Note CO Tone Detection is only supported on embedded and or ASU trunks and NOT on the LS/GS Trunk Card. You need to be reasonably accurate when measuring the tones, when configured correctly it WILL resolve hang-up issues.




Pages: [1] 2