VoiceOps
By thread
voiceops@voiceops.org
By month
Messages by month
- ----- 2026 -----
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
June 2019
- 19 participants
- 45 messages
CenturyLink and Neutral Tandem Contacts
by voiceops@ics-il.net
I was experiencing some problems with multiple inbound calls for each placed call and I put in a ticket with our tandem provider (Frontier). Frontier said they were seeing the multiple calls coming in from CenturyLink and Neutral Tandem. They gave me point codes and some other number I didn't recognize (TSC GNxxxxxx). Unfortunately, I only have mass-market customer facing support numbers (well, just for CenturyLink). Does anyone have a better contact at those companies?
-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest Internet Exchange
http://www.midwest-ix.com
June 24, 2019
Issues calling the Netherlands
by dovid@telecurve.com
The issue seems to have been resolved as of about 1.5 hours ago. KPN had a
statement on their site that they were having issues.
On Mon, Jun 24, 2019 at 2:00 PM Jared Geiger <jared at compuwizz.net> wrote:
> Test calls via ibasis to Amsterdam landlines connected immediately.
>
> On Mon, Jun 24, 2019 at 10:34 AM Dovid Bender <dovid at telecurve.com> wrote:
>
>> I just got this from BT.
>>
>> Dear customer
>>
>> KPN are facing a major outage in the Netherlands affecting both fixed and
>> mobile networks so I am surprised to see you can connect to this number via
>> another carrier.
>> Below is the update broadcast by KPN
>>
>> Subject: Multiple regions of telephony problems.
>> Segment: Fixed
>> Network: IMS
>> Affected services: VoIP
>> Area: Northeast, Northwest, Middle, Southeast, Southwest
>>
>> Impact:
>> 24-06-2019 15:54 hours:
>> Telephony problems.
>> KPN internal telephony is no longer possible.
>> All Service Desks are not reachable by telephone, both internally and
>> externally.
>> Mobile calling in multiple regions is not possible.
>> Other providers outside KPN also experience problems with telephony.
>> Impact is collected further.
>>
>> Start impact: 24-06-2019 15:54 hrs.
>> Expected recovery: 24-06-2019 8:00 PM.
>>
>> Cause: Unknown.
>> Promotion by: SQC Services
>>
>> Progress: 24/06/2019 5:06 PM.
>> Due to the impact, the incident has been scaled up to code RED. At
>> present there are problems with mobile and landline calls throughout the
>> Netherlands. The cause seems to be in the Titan platform. There also seems
>> to be an impact with other Dutch parties. KPN Service Desk are unreachable.
>> A message has been posted on KPN.com, a media statement is being made.
>> Another update will follow around 6:00 PM.
>>
>> As such there is nothing we can do to improve the situation
>> Apologies for the inconvenience
>>
>> On Mon, Jun 24, 2019 at 12:40 PM Dovid Bender <dovid at telecurve.com>
>> wrote:
>>
>>> Hi,
>>>
>>> We received a spoke in tickets for people trying to call the
>>> Netherlands. Sample numbers are working via Verizon Wireless in the US but
>>> failing with all major carriers such as:
>>> BT
>>> BICS
>>> N2P
>>> Voxbeam (tier2)
>>>
>>> I am also able to call via Verizon Europe. Anyone have any idea what
>>> maybe going on?
>>>
>>>
>>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
June 24, 2019
Issues calling the Netherlands
by jared@compuwizz.net
Test calls via ibasis to Amsterdam landlines connected immediately.
On Mon, Jun 24, 2019 at 10:34 AM Dovid Bender <dovid at telecurve.com> wrote:
> I just got this from BT.
>
> Dear customer
>
> KPN are facing a major outage in the Netherlands affecting both fixed and
> mobile networks so I am surprised to see you can connect to this number via
> another carrier.
> Below is the update broadcast by KPN
>
> Subject: Multiple regions of telephony problems.
> Segment: Fixed
> Network: IMS
> Affected services: VoIP
> Area: Northeast, Northwest, Middle, Southeast, Southwest
>
> Impact:
> 24-06-2019 15:54 hours:
> Telephony problems.
> KPN internal telephony is no longer possible.
> All Service Desks are not reachable by telephone, both internally and
> externally.
> Mobile calling in multiple regions is not possible.
> Other providers outside KPN also experience problems with telephony.
> Impact is collected further.
>
> Start impact: 24-06-2019 15:54 hrs.
> Expected recovery: 24-06-2019 8:00 PM.
>
> Cause: Unknown.
> Promotion by: SQC Services
>
> Progress: 24/06/2019 5:06 PM.
> Due to the impact, the incident has been scaled up to code RED. At present
> there are problems with mobile and landline calls throughout the
> Netherlands. The cause seems to be in the Titan platform. There also seems
> to be an impact with other Dutch parties. KPN Service Desk are unreachable.
> A message has been posted on KPN.com, a media statement is being made.
> Another update will follow around 6:00 PM.
>
> As such there is nothing we can do to improve the situation
> Apologies for the inconvenience
>
> On Mon, Jun 24, 2019 at 12:40 PM Dovid Bender <dovid at telecurve.com> wrote:
>
>> Hi,
>>
>> We received a spoke in tickets for people trying to call the Netherlands.
>> Sample numbers are working via Verizon Wireless in the US but failing with
>> all major carriers such as:
>> BT
>> BICS
>> N2P
>> Voxbeam (tier2)
>>
>> I am also able to call via Verizon Europe. Anyone have any idea what
>> maybe going on?
>>
>>
>> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
June 24, 2019
Issues calling the Netherlands
by dovid@telecurve.com
I just got this from BT.
Dear customer
KPN are facing a major outage in the Netherlands affecting both fixed and
mobile networks so I am surprised to see you can connect to this number via
another carrier.
Below is the update broadcast by KPN
Subject: Multiple regions of telephony problems.
Segment: Fixed
Network: IMS
Affected services: VoIP
Area: Northeast, Northwest, Middle, Southeast, Southwest
Impact:
24-06-2019 15:54 hours:
Telephony problems.
KPN internal telephony is no longer possible.
All Service Desks are not reachable by telephone, both internally and
externally.
Mobile calling in multiple regions is not possible.
Other providers outside KPN also experience problems with telephony.
Impact is collected further.
Start impact: 24-06-2019 15:54 hrs.
Expected recovery: 24-06-2019 8:00 PM.
Cause: Unknown.
Promotion by: SQC Services
Progress: 24/06/2019 5:06 PM.
Due to the impact, the incident has been scaled up to code RED. At present
there are problems with mobile and landline calls throughout the
Netherlands. The cause seems to be in the Titan platform. There also seems
to be an impact with other Dutch parties. KPN Service Desk are unreachable.
A message has been posted on KPN.com, a media statement is being made.
Another update will follow around 6:00 PM.
As such there is nothing we can do to improve the situation
Apologies for the inconvenience
On Mon, Jun 24, 2019 at 12:40 PM Dovid Bender <dovid at telecurve.com> wrote:
> Hi,
>
> We received a spoke in tickets for people trying to call the Netherlands.
> Sample numbers are working via Verizon Wireless in the US but failing with
> all major carriers such as:
> BT
> BICS
> N2P
> Voxbeam (tier2)
>
> I am also able to call via Verizon Europe. Anyone have any idea what maybe
> going on?
>
>
>
June 24, 2019
Issues calling the Netherlands
by dovid@telecurve.com
Hi,
We received a spoke in tickets for people trying to call the Netherlands.
Sample numbers are working via Verizon Wireless in the US but failing with
all major carriers such as:
BT
BICS
N2P
Voxbeam (tier2)
I am also able to call via Verizon Europe. Anyone have any idea what maybe
going on?
June 24, 2019
ATA To Connect to Mitel PBX
by nate@blastcomm.com
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
> myaklin at firstlight.net | 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 <nate at blastcomm.com>
> *Sent:* Wednesday, June 19, 2019 11:41:01 AM
> *To:* Matthew Yaklin; voiceops at voiceops.org
> *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
>> myaklin at firstlight.net <mailto:myaklin at firstlight.net> |
>> 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 <voiceops-bounces at voiceops.org>
>> <mailto:voiceops-bounces at voiceops.org> on behalf of Nate Burke
>> <nate at blastcomm.com> <mailto:nate at blastcomm.com>
>> *Sent:* Wednesday, June 19, 2019 10:44:50 AM
>> *To:* voiceops at voiceops.org <mailto:voiceops at voiceops.org>
>> *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 <nate at blastcomm.com>
>> <mailto:nate at blastcomm.com> 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:voiceops-bounces at voiceops.org] On Behalf
>> Of Nate Burke
>> >>> Sent: Friday, April 12, 2019 9:33 AM
>> >>> To: voiceops at voiceops.org <mailto:voiceops at voiceops.org>
>> >>> 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
>> >> VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
>> >> https://puck.nether.net/mailman/listinfo/voiceops
>> <https://puck.nether.net/mailman/listinfo/voiceops>
>>
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
>> https://puck.nether.net/mailman/listinfo/voiceops
>
June 19, 2019
ATA To Connect to Mitel PBX
by myaklin@firstlight.net
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
myaklin at firstlight.net | 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 <nate at blastcomm.com>
Sent: Wednesday, June 19, 2019 11:41:01 AM
To: Matthew Yaklin; voiceops at voiceops.org
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
myaklin at firstlight.net<mailto:myaklin at firstlight.net> | 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 <voiceops-bounces at voiceops.org><mailto:voiceops-bounces at voiceops.org> on behalf of Nate Burke <nate at blastcomm.com><mailto:nate at blastcomm.com>
Sent: Wednesday, June 19, 2019 10:44:50 AM
To: voiceops at voiceops.org<mailto:voiceops at voiceops.org>
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
>
>
>> On Jun 17, 2019, at 9:36 PM, Nate Burke <nate at blastcomm.com><mailto:nate at blastcomm.com> 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:voiceops-bounces at voiceops.org] On Behalf Of Nate Burke
>>> Sent: Friday, April 12, 2019 9:33 AM
>>> To: voiceops at voiceops.org<mailto:voiceops at voiceops.org>
>>> 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
>> VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
>> https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops
June 19, 2019
ATA To Connect to Mitel PBX
by nate@blastcomm.com
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
> myaklin at firstlight.net | 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 <voiceops-bounces at voiceops.org> on behalf of Nate
> Burke <nate at blastcomm.com>
> *Sent:* Wednesday, June 19, 2019 10:44:50 AM
> *To:* voiceops at voiceops.org
> *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
> >
> >
> >> On Jun 17, 2019, at 9:36 PM, Nate Burke <nate at blastcomm.com> 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:voiceops-bounces at voiceops.org] On Behalf Of
> Nate Burke
> >>> Sent: Friday, April 12, 2019 9:33 AM
> >>> To: voiceops at voiceops.org
> >>> 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
> >> VoiceOps at voiceops.org
> >> https://puck.nether.net/mailman/listinfo/voiceops
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
June 19, 2019
ATA To Connect to Mitel PBX
by myaklin@firstlight.net
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
myaklin at firstlight.net | 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 <voiceops-bounces at voiceops.org> on behalf of Nate Burke <nate at blastcomm.com>
Sent: Wednesday, June 19, 2019 10:44:50 AM
To: voiceops at voiceops.org
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
>
>
>> On Jun 17, 2019, at 9:36 PM, Nate Burke <nate at blastcomm.com> 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:voiceops-bounces at voiceops.org] On Behalf Of Nate Burke
>>> Sent: Friday, April 12, 2019 9:33 AM
>>> To: voiceops at voiceops.org
>>> 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
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
June 19, 2019
ATA To Connect to Mitel PBX
by nate@blastcomm.com
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
>
>
>> On Jun 17, 2019, at 9:36 PM, Nate Burke <nate at blastcomm.com> 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:voiceops-bounces at voiceops.org] On Behalf Of Nate Burke
>>> Sent: Friday, April 12, 2019 9:33 AM
>>> To: voiceops at voiceops.org
>>> 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
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
June 19, 2019