Re: [VoiceOps] ATA To Connect to Mitel PBX

Wed, 19 Jun 2019 10:26:27 -0700

From what we are told, an incoming call, instead of ringing the front desk, rings directly to a guest room.  A very few number of calls appear to do this, and it's not always the same room.  We hear about this happening in the middle of the night, but of course that's when someone is in the room to hear it.  Without any time stamps of when this happens, I'm not able to answer the Trunk order question, and being 3 times removed the from the information (Guest -> Front Desk -> Hotel Management -> Me) getting more specific detail is hard.  I always ring inbound lines starting with 1, but it appears that outbound calls from the MITEL round robin the trunk lines.  When I place test calls to/from the hotel when I'm on site, I can't replicate a trunk port staying open (by looking at the LED's on the front of the MITEL card), but that's the only explanation that makes sense so far.
I just added a ground wire between the adtran and the Mitel (they previously had a common electrical ground).  I'm hopeful that the MITEL Tech will respond to some of my inquiries for information. 

Nate

On 6/19/2019 11:27 AM, Matthew Yaklin wrote:


Nate,



I have to admit never running into this problem before. Basically you 
are saying an incoming call over a pots line is routed to a hotel 
room. I assume via the front desk doing a



transfer/AA? Or does it route directly.. hard coded.. every single 
time to the hotel room?




And once the hotel room hangs up... the very next call over that same 
trunk (pots line/TN) just slips right through the open path previously 
created and never hits the front desk/AA?




Why do I get the feeling you are battling some odd setting in the 
Mitel that was done years



ago with ATT.. and now here you come with a normal modern setup and 
running into


problems.



If you could just get the Mitel PBX vendor to give you the "CO trunk 
circuit descriptors"



information in a screen shot or whatever.. i bet we could solve this 
pretty quick.





*Matthew Yaklin*
Network Engineer
*FirstLight*
359 Corporate Drive │ Portsmouth, NH 03801
Mobile 603-845-5031
[email protected] | www.firstlight.net

/This email may contain FirstLight confidential and/or privileged 
information. If you are not the intended recipient, you are directed/
/not to read, disclose or otherwise use this transmission and to 
immediately delete same. Delivery of this message is not intended/

/to waive any applicable privileges./

------------------------------------------------------------------------
*From:* Nate Burke <[email protected]>
*Sent:* Wednesday, June 19, 2019 11:41:01 AM
*To:* Matthew Yaklin; [email protected]
*Subject:* Re: [VoiceOps] ATA To Connect to Mitel PBX

Unfortunately the MITEL tech is being very little help.  Even the 
customer says they are not-responsive.  So I have no way of knowing 
what the MITEL settings are now, he has not responded to my requests. 
Previously they were getting POTS handoff from an AT&T T-1 to POTS 
unit, supposedly it worked fine.



This is at a Hotel, so getting the exact scenario that happens is a 
little difficult.  What we have been told is that randomly, an 
incoming call will route directly to a guest room.  We can't even get 
times when this happens to correlate call logs, as the guest just 
complains to the front desk at checkout.  The only thing we can 
figure, is that the MITEL is not closing a trunk line, and and if an 
incoming call hits that same trunk, it just rings through to the last 
extension connected to that trunk.



Would there be any harm in turning the Forward Disconnect Delay up to 
it's maximum value?  I think 2000ms.


Nate

On 6/19/2019 10:07 AM, Matthew Yaklin wrote:


Nate,


I see that you have Forward Disconnect Delay set to 750 ms on the Adtran.



But has the mitel tech told you what is set on the PBX for forward 
disconnect delay?



Is it possible some PBX tech in the past set an unusually high value 
for that?





Also what are these certain call scenarios? Are you talking about an 
incoming call going to the PBX and the user is then doing something 
to have the call go back out to the world?




Or are we talking about a regular plain jane incoming call or 
outgoing call. In order to help we need to know if this is more 
complicated then it seems.



Matt




*Matthew Yaklin*
Network Engineer
*FirstLight*
359 Corporate Drive │ Portsmouth, NH 03801
Mobile 603-845-5031

[email protected] <mailto:[email protected]> | 
www.firstlight.net <http://www.firstlight.net>
/This email may contain FirstLight confidential and/or privileged 
information. If you are not the intended recipient, you are directed/
/not to read, disclose or otherwise use this transmission and to 
immediately delete same. Delivery of this message is not intended/

/to waive any applicable privileges./

------------------------------------------------------------------------

*From:* VoiceOps <[email protected]> 
<mailto:[email protected]> on behalf of Nate Burke 
<[email protected]> <mailto:[email protected]>

*Sent:* Wednesday, June 19, 2019 10:44:50 AM
*To:* [email protected] <mailto:[email protected]>
*Subject:* Re: [VoiceOps] ATA To Connect to Mitel PBX
Thanks to everyone for the replies.  The MITEL Tech is being 0 help
other than continuing to tell the customer that my lines are the problem.

The MITEL card that I'm  plugging into is a 'LS/GS Trunk (6cct)
0109-011-001-SA'.  I'm guessing the settings that are the problem are the

Forward Disconnect Delay
Forward Disconnect Battery

Anybody know what these settings should be to in the TA908 to interface
to this MITEL card?

Currently they are set to
Forward Disconnect Delay - Currently at 750ms
Forward Disconnect Battery -Currently on Remove.

Thanks,
Nate


On 6/17/2019 9:07 PM, Todd Wolf wrote:
> This link is relevant to your issue
>

> https://supportforums.adtran.com/thread/2264 
<https://supportforums.adtran.com/thread/2264>

>
>

>> On Jun 17, 2019, at 9:36 PM, Nate Burke <[email protected]> 
<mailto:[email protected]> wrote:

>>

>> Sorry for Dredging up an old post.  I've had the Adtran TA908 (2nd 
gen) installed to the MITEL for about a month, but now I'm starting 
to hear about problems.  In Certain call scenarios, the MITEL is not 
disconnecting the Trunk port, even though a call has ended.  The 
Mitel consultant is placing the blame squarely with me, that I'm not 
sending the proper 'Disconnect Supervision' and the MITEL is not 
hanging up the line.

>>

>> I've been googling, and reading manuals, and haven't been able to 
find any sort of settings for a 'disconnect supervision'

>>
>> Anyone run into this before?
>>
>> Thanks,
>> Nate
>>
>>
>>> On 4/13/2019 7:23 AM, Nathan Anderson wrote:

>>> You didn't say what the "some issues" were that the customer was 
still complaining about. Just stuck lines?  Just echo?  Both?  
Something else entirely?

>>>

>>> Re: stuck lines, sounds to me like the TA and the phone system 
are not in agreement about what method of disconnect supervision (if 
any) the TA is going to provide and the phone system trunks are going 
to be looking for.

>>>
>>> -- Nathan
>>>
>>> -----Original Message-----

>>> From: VoiceOps [mailto:[email protected]] On Behalf 
Of Nate Burke

>>> Sent: Friday, April 12, 2019 9:33 AM
>>> To: [email protected] <mailto:[email protected]>
>>> Subject: [VoiceOps] ATA To Connect to Mitel PBX
>>>
>>> I've only had to provide POTS termination to 1 MITEL system.  I tried
>>> using Linksys/Cisco SPA and Grandstream ATA's, then finally put in an

>>> Adtran TA904 (2nd gen).  The Adtran seemed to give the least 
number of

>>> issues with Lines getting stuck open, Echo, etc. But the (former)

>>> customer was still complaining about some issues when they closed 
up shop.

>>>

>>> I now need to provide 6 analog lines to hand off to an existing 
MITEL.
>>> Is there an ATA that's better than a TA908 for doing "Acceptable" 
POTS

>>> to a MITEL?
>>>
>>> Thanks,
>>> Nate
>> _______________________________________________
>> VoiceOps mailing list
>> [email protected] <mailto:[email protected]>

>> https://puck.nether.net/mailman/listinfo/voiceops 
<https://puck.nether.net/mailman/listinfo/voiceops>


_______________________________________________
VoiceOps mailing list
[email protected] <mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/voiceops





_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops






















					Reply via email to