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
August 2015
- 42 participants
- 132 messages
ADT Alarms Special Dialing?
by colton.conor@gmail.com
Wow thanks to all this has been a huge help! So we are using a Broadsoft
for the voice switch connected by SIP to an Adtran Total Access 5000 that
has VDSL2 Combo cards. So I assume we would need to change the DTMF
settings on the Adtran. Have any recommendations on what to look for to
make this work with ADT alarm lines if its truly a DMT issue.
I don't like the idea of changing setting on the actual alarm. I prefer to
get the POTS working right so it works regardless of the alarms settings.
On Thu, Aug 6, 2015 at 7:03 PM, Nathan Anderson <nathana at fsr.com> wrote:
> I doubt it. We are an ISP and ITSP doing voice exclusively 100% over IP.
> We have historically actively discouraged hooking up an alarm system to our
> service and relying on that (in order to avoid support headaches, liability
> issues, etc.), but we ourselves have an ADT system that was previously
> hooked up to local ILEC POTS service and that we moved over to an ATA of
> ours as an experiment.
>
> It actually works just fine now, but it didn't initially. Turns out that
> the default "modulation" technique used between the panel and the
> monitoring center is...DTMF. Really. It appeared that either the
> monitoring center or the panel (or both) did not like something about how
> either the ATA or the terminating provider was regenerating the DTMF tones
> from the OOB info. Not sure if it was a timing issue or what. I am pretty
> sure I did try forcing DTMF to not be decoded/re-encoded and just remain
> inband, but that didn't seem to work for whatever reason (can't remember
> the details; it's been a while since this all transpired).
>
> Eventually, I managed to track down an installer's manual for the
> particular model of panel we have, and was able to reprogram it to use a
> form of FSK modulation to talk to the monitoring center instead. It's
> super low bitrate (300 baud IIRC), and works 100% perfectly over G.711
> PCM. (I know this because after I made the change, I accidentally managed
> to set the alarm off, and ADT called my boss, etc.; that was fun...) We
> have been using the panel this way for months, plugged into a VoIP ATA.
>
> The panel dials an 800 number periodically to check in, and also when the
> alarm is tripped. If it cannot complete a check-in successfully, a light
> on the panel will be illuminated. That LED has not come on since the
> modulation switch. If they were doing LRN lookups, we would fail that test
> as well since none of our sources for DIDs are on ADT's "approved" list,
> either. I am sure I can get you the number that ours dials if you care to
> have it, but I have no way of knowing if they use the same number in all
> geographies or across all product lines (ours is an office/business system
> that I'm pretty sure doesn't get used in residential installs; for all I
> know, it may call a different monitoring center than the residential
> product(s) do).
>
> Hope this helps at least give you some more ideas,
>
> --
> Nathan Anderson
> First Step Internet, LLC
> nathana at fsr.com
>
> -----Original Message-----
> From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Colton
> Conor
> Sent: Thursday, August 06, 2015 4:30 PM
> To: voiceops at voiceops.org
> Subject: Re: [VoiceOps] ADT Alarms Special Dialing?
>
> I did find this page http://www.adt.com/customer-service/voip-faqs Seems
> that your phone company has to be:
>
> A Qualified ?Managed Facility Voice Network (MFVN)?includes the following:
> 1. Has a physical facilities network which is managed and maintained
> (directly or indirectly) by the service provider. Can ensure service
> quality from the service subscriber location to the PSTN or other MFVN peer
> network.
> 2. Utilizes similar signaling and related protocols as the PSTN with
> respect to dialing, dial plan, call completion, carriage of alarm signals
> and protocols, and loop voltage treatment.
> 3. Provides real-time transmission of voice signals, carrying alarm
> formats unchanged.
> 4. Provides professional installation that preserves primary line seizure
> for alarm signal transmission.
> 5. Has major and minor disaster recovery plans to address both individual
> customer outages and widespread events such as tornados, ice storms and
> other natural disasters. This includes specific network power restoration
> procedures that are comparable to those of traditional landline telephone
> services in the same geographic region.
> 6. Has informed ADT that its network meets the characteristics of a MFVN.
> Still how are they controlling this? Think ADT is smart enough to do a LRN
> lookup on a number, and see its not one from their qualified list?
>
> -----Original Message-----
> On Thu, Aug 6, 2015 at 6:21 PM, Colton Conor <colton.conor at gmail.com>
> wrote:
> We are a CLEC and have a had a couple of customers port away from
> Verizon's landline service and to our voice service where we provided an
> analog POTS line with the same number just as the client had before with
> Verizon. We hook the POTS line up to the exact same wire going to the
> client's alarm panel, but the alarm can't communicate with ADT.
>
> We called ADT on multiple clients behalfs, and they basically said Verizon
> is on an approved list to work with their services and our CLEC is not, so
> it would not work.
>
> How is ADT limiting this? Does their alarm panels dial a special number
> that only Verizon knows or allows? This has happened with multiple clients.
>
> We have not been able to get on the voice switch and see what numbers they
> panel is actually trying to dial, but any insight to this would be helpful.
>
> I have read that some alarm companies uses a special code before they make
> an outbound call so the long distance gets billed to them or something?
>
>
Aug. 7, 2015
ADT Alarms Special Dialing?
by paul@timmins.net
Quality of customer endpoints varies widely, my friend. I've had a few
different T38 devices (can't remember offhand) kick in on not only FSK
alarm panels, but credit card machines too. It's not *supposed* to
happen but neither is talkoff (Looking in your direction,
Cisco/Linksys/Sipura SPA-100x/200x with RFC2833/AVT). :)
Most devices indeed work properly but I've learned long ago to just add
that to my mental checklist of things to look for when people start
complaining. Part of me wonders what the industry will look like in
5-10 years when everything has to work together natively with everything
instead of the current model where there's TDM buffers between a wide
variety of VoIP islands and I never have to worry that your customer's
choice of PBX handset will affect my customer's ability to operate his
IVR because there's a big bad PSTN between us reducing it down to
audible touch tones.
-Paul
On 08/06/2015 08:42 PM, Nathan Anderson wrote:
> I guess we are lucky, then: we do a fair amount of T.38 traffic, and we have never had issues with either the ATA or the remote switch detecting that as a fax call and extending a re-INVITE.
>
> -- Nathan
>
> -----Original Message-----
> From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Paul Timmins
> Sent: Thursday, August 06, 2015 5:35 PM
> To: voiceops at voiceops.org
> Subject: Re: [VoiceOps] ADT Alarms Special Dialing?
>
> Many alarm systems use Ademco Contact ID which requires very tight
> tolerances on the DTMF. I actually just had to demand firmware changes
> to our TDM switch's packet interface card's RTP handling to get the
> tolerances right (the ISU the other night fixed it! yay!). The FSK (SIA
> somethingorother) is hit or miss too, sometimes it can trigger T.38
> detection in the network and then you're screwed a different way.
>
> We've standardized on getting our customers to use Contact ID and
> getting the DTMF codecs working just right. It's not always easy but
> then we can predict. We're one of the few in our area where alarm panels
> work consistently, PBX vendors seem to like that. :-) Makes the cutover
> much easier.
>
> -Paul
>
> On 08/06/2015 08:03 PM, Nathan Anderson wrote:
>> I doubt it. We are an ISP and ITSP doing voice exclusively 100% over IP. We have historically actively discouraged hooking up an alarm system to our service and relying on that (in order to avoid support headaches, liability issues, etc.), but we ourselves have an ADT system that was previously hooked up to local ILEC POTS service and that we moved over to an ATA of ours as an experiment.
>>
>> It actually works just fine now, but it didn't initially. Turns out that the default "modulation" technique used between the panel and the monitoring center is...DTMF. Really. It appeared that either the monitoring center or the panel (or both) did not like something about how either the ATA or the terminating provider was regenerating the DTMF tones from the OOB info. Not sure if it was a timing issue or what. I am pretty sure I did try forcing DTMF to not be decoded/re-encoded and just remain inband, but that didn't seem to work for whatever reason (can't remember the details; it's been a while since this all transpired).
>>
>> Eventually, I managed to track down an installer's manual for the particular model of panel we have, and was able to reprogram it to use a form of FSK modulation to talk to the monitoring center instead. It's super low bitrate (300 baud IIRC), and works 100% perfectly over G.711 PCM. (I know this because after I made the change, I accidentally managed to set the alarm off, and ADT called my boss, etc.; that was fun...) We have been using the panel this way for months, plugged into a VoIP ATA.
>>
>> The panel dials an 800 number periodically to check in, and also when the alarm is tripped. If it cannot complete a check-in successfully, a light on the panel will be illuminated. That LED has not come on since the modulation switch. If they were doing LRN lookups, we would fail that test as well since none of our sources for DIDs are on ADT's "approved" list, either. I am sure I can get you the number that ours dials if you care to have it, but I have no way of knowing if they use the same number in all geographies or across all product lines (ours is an office/business system that I'm pretty sure doesn't get used in residential installs; for all I know, it may call a different monitoring center than the residential product(s) do).
>>
>> Hope this helps at least give you some more ideas,
>>
>> --
>> Nathan Anderson
>> First Step Internet, LLC
>> nathana at fsr.com
>>
>> -----Original Message-----
>> From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Colton Conor
>> Sent: Thursday, August 06, 2015 4:30 PM
>> To: voiceops at voiceops.org
>> Subject: Re: [VoiceOps] ADT Alarms Special Dialing?
>>
>> I did find this page http://www.adt.com/customer-service/voip-faqs Seems that your phone company has to be:
>>
>> A Qualified ?Managed Facility Voice Network (MFVN)?includes the following:
>> 1. Has a physical facilities network which is managed and maintained (directly or indirectly) by the service provider. Can ensure service quality from the service subscriber location to the PSTN or other MFVN peer network.
>> 2. Utilizes similar signaling and related protocols as the PSTN with respect to dialing, dial plan, call completion, carriage of alarm signals and protocols, and loop voltage treatment.
>> 3. Provides real-time transmission of voice signals, carrying alarm formats unchanged.
>> 4. Provides professional installation that preserves primary line seizure for alarm signal transmission.
>> 5. Has major and minor disaster recovery plans to address both individual customer outages and widespread events such as tornados, ice storms and other natural disasters. This includes specific network power restoration procedures that are comparable to those of traditional landline telephone services in the same geographic region.
>> 6. Has informed ADT that its network meets the characteristics of a MFVN.
>> Still how are they controlling this? Think ADT is smart enough to do a LRN lookup on a number, and see its not one from their qualified list?
>>
>> -----Original Message-----
>> On Thu, Aug 6, 2015 at 6:21 PM, Colton Conor <colton.conor at gmail.com> wrote:
>> We are a CLEC and have a had a couple of customers port away from Verizon's landline service and to our voice service where we provided an analog POTS line with the same number just as the client had before with Verizon. We hook the POTS line up to the exact same wire going to the client's alarm panel, but the alarm can't communicate with ADT.
>>
>> We called ADT on multiple clients behalfs, and they basically said Verizon is on an approved list to work with their services and our CLEC is not, so it would not work.
>>
>> How is ADT limiting this? Does their alarm panels dial a special number that only Verizon knows or allows? This has happened with multiple clients.
>>
>> We have not been able to get on the voice switch and see what numbers they panel is actually trying to dial, but any insight to this would be helpful.
>>
>> I have read that some alarm companies uses a special code before they make an outbound call so the long distance gets billed to them or something?
>>
>> _______________________________________________
>> 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
Aug. 7, 2015
ADT Alarms Special Dialing?
by nathana@fsr.com
I guess we are lucky, then: we do a fair amount of T.38 traffic, and we have never had issues with either the ATA or the remote switch detecting that as a fax call and extending a re-INVITE.
-- Nathan
-----Original Message-----
From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Paul Timmins
Sent: Thursday, August 06, 2015 5:35 PM
To: voiceops at voiceops.org
Subject: Re: [VoiceOps] ADT Alarms Special Dialing?
Many alarm systems use Ademco Contact ID which requires very tight
tolerances on the DTMF. I actually just had to demand firmware changes
to our TDM switch's packet interface card's RTP handling to get the
tolerances right (the ISU the other night fixed it! yay!). The FSK (SIA
somethingorother) is hit or miss too, sometimes it can trigger T.38
detection in the network and then you're screwed a different way.
We've standardized on getting our customers to use Contact ID and
getting the DTMF codecs working just right. It's not always easy but
then we can predict. We're one of the few in our area where alarm panels
work consistently, PBX vendors seem to like that. :-) Makes the cutover
much easier.
-Paul
On 08/06/2015 08:03 PM, Nathan Anderson wrote:
> I doubt it. We are an ISP and ITSP doing voice exclusively 100% over IP. We have historically actively discouraged hooking up an alarm system to our service and relying on that (in order to avoid support headaches, liability issues, etc.), but we ourselves have an ADT system that was previously hooked up to local ILEC POTS service and that we moved over to an ATA of ours as an experiment.
>
> It actually works just fine now, but it didn't initially. Turns out that the default "modulation" technique used between the panel and the monitoring center is...DTMF. Really. It appeared that either the monitoring center or the panel (or both) did not like something about how either the ATA or the terminating provider was regenerating the DTMF tones from the OOB info. Not sure if it was a timing issue or what. I am pretty sure I did try forcing DTMF to not be decoded/re-encoded and just remain inband, but that didn't seem to work for whatever reason (can't remember the details; it's been a while since this all transpired).
>
> Eventually, I managed to track down an installer's manual for the particular model of panel we have, and was able to reprogram it to use a form of FSK modulation to talk to the monitoring center instead. It's super low bitrate (300 baud IIRC), and works 100% perfectly over G.711 PCM. (I know this because after I made the change, I accidentally managed to set the alarm off, and ADT called my boss, etc.; that was fun...) We have been using the panel this way for months, plugged into a VoIP ATA.
>
> The panel dials an 800 number periodically to check in, and also when the alarm is tripped. If it cannot complete a check-in successfully, a light on the panel will be illuminated. That LED has not come on since the modulation switch. If they were doing LRN lookups, we would fail that test as well since none of our sources for DIDs are on ADT's "approved" list, either. I am sure I can get you the number that ours dials if you care to have it, but I have no way of knowing if they use the same number in all geographies or across all product lines (ours is an office/business system that I'm pretty sure doesn't get used in residential installs; for all I know, it may call a different monitoring center than the residential product(s) do).
>
> Hope this helps at least give you some more ideas,
>
> --
> Nathan Anderson
> First Step Internet, LLC
> nathana at fsr.com
>
> -----Original Message-----
> From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Colton Conor
> Sent: Thursday, August 06, 2015 4:30 PM
> To: voiceops at voiceops.org
> Subject: Re: [VoiceOps] ADT Alarms Special Dialing?
>
> I did find this page http://www.adt.com/customer-service/voip-faqs Seems that your phone company has to be:
>
> A Qualified ?Managed Facility Voice Network (MFVN)?includes the following:
> 1. Has a physical facilities network which is managed and maintained (directly or indirectly) by the service provider. Can ensure service quality from the service subscriber location to the PSTN or other MFVN peer network.
> 2. Utilizes similar signaling and related protocols as the PSTN with respect to dialing, dial plan, call completion, carriage of alarm signals and protocols, and loop voltage treatment.
> 3. Provides real-time transmission of voice signals, carrying alarm formats unchanged.
> 4. Provides professional installation that preserves primary line seizure for alarm signal transmission.
> 5. Has major and minor disaster recovery plans to address both individual customer outages and widespread events such as tornados, ice storms and other natural disasters. This includes specific network power restoration procedures that are comparable to those of traditional landline telephone services in the same geographic region.
> 6. Has informed ADT that its network meets the characteristics of a MFVN.
> Still how are they controlling this? Think ADT is smart enough to do a LRN lookup on a number, and see its not one from their qualified list?
>
> -----Original Message-----
> On Thu, Aug 6, 2015 at 6:21 PM, Colton Conor <colton.conor at gmail.com> wrote:
> We are a CLEC and have a had a couple of customers port away from Verizon's landline service and to our voice service where we provided an analog POTS line with the same number just as the client had before with Verizon. We hook the POTS line up to the exact same wire going to the client's alarm panel, but the alarm can't communicate with ADT.
>
> We called ADT on multiple clients behalfs, and they basically said Verizon is on an approved list to work with their services and our CLEC is not, so it would not work.
>
> How is ADT limiting this? Does their alarm panels dial a special number that only Verizon knows or allows? This has happened with multiple clients.
>
> We have not been able to get on the voice switch and see what numbers they panel is actually trying to dial, but any insight to this would be helpful.
>
> I have read that some alarm companies uses a special code before they make an outbound call so the long distance gets billed to them or something?
>
> _______________________________________________
> 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
Aug. 7, 2015
ADT Alarms Special Dialing?
by paul@timmins.net
Many alarm systems use Ademco Contact ID which requires very tight
tolerances on the DTMF. I actually just had to demand firmware changes
to our TDM switch's packet interface card's RTP handling to get the
tolerances right (the ISU the other night fixed it! yay!). The FSK (SIA
somethingorother) is hit or miss too, sometimes it can trigger T.38
detection in the network and then you're screwed a different way.
We've standardized on getting our customers to use Contact ID and
getting the DTMF codecs working just right. It's not always easy but
then we can predict. We're one of the few in our area where alarm panels
work consistently, PBX vendors seem to like that. :-) Makes the cutover
much easier.
-Paul
On 08/06/2015 08:03 PM, Nathan Anderson wrote:
> I doubt it. We are an ISP and ITSP doing voice exclusively 100% over IP. We have historically actively discouraged hooking up an alarm system to our service and relying on that (in order to avoid support headaches, liability issues, etc.), but we ourselves have an ADT system that was previously hooked up to local ILEC POTS service and that we moved over to an ATA of ours as an experiment.
>
> It actually works just fine now, but it didn't initially. Turns out that the default "modulation" technique used between the panel and the monitoring center is...DTMF. Really. It appeared that either the monitoring center or the panel (or both) did not like something about how either the ATA or the terminating provider was regenerating the DTMF tones from the OOB info. Not sure if it was a timing issue or what. I am pretty sure I did try forcing DTMF to not be decoded/re-encoded and just remain inband, but that didn't seem to work for whatever reason (can't remember the details; it's been a while since this all transpired).
>
> Eventually, I managed to track down an installer's manual for the particular model of panel we have, and was able to reprogram it to use a form of FSK modulation to talk to the monitoring center instead. It's super low bitrate (300 baud IIRC), and works 100% perfectly over G.711 PCM. (I know this because after I made the change, I accidentally managed to set the alarm off, and ADT called my boss, etc.; that was fun...) We have been using the panel this way for months, plugged into a VoIP ATA.
>
> The panel dials an 800 number periodically to check in, and also when the alarm is tripped. If it cannot complete a check-in successfully, a light on the panel will be illuminated. That LED has not come on since the modulation switch. If they were doing LRN lookups, we would fail that test as well since none of our sources for DIDs are on ADT's "approved" list, either. I am sure I can get you the number that ours dials if you care to have it, but I have no way of knowing if they use the same number in all geographies or across all product lines (ours is an office/business system that I'm pretty sure doesn't get used in residential installs; for all I know, it may call a different monitoring center than the residential product(s) do).
>
> Hope this helps at least give you some more ideas,
>
> --
> Nathan Anderson
> First Step Internet, LLC
> nathana at fsr.com
>
> -----Original Message-----
> From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Colton Conor
> Sent: Thursday, August 06, 2015 4:30 PM
> To: voiceops at voiceops.org
> Subject: Re: [VoiceOps] ADT Alarms Special Dialing?
>
> I did find this page http://www.adt.com/customer-service/voip-faqs Seems that your phone company has to be:
>
> A Qualified ?Managed Facility Voice Network (MFVN)?includes the following:
> 1. Has a physical facilities network which is managed and maintained (directly or indirectly) by the service provider. Can ensure service quality from the service subscriber location to the PSTN or other MFVN peer network.
> 2. Utilizes similar signaling and related protocols as the PSTN with respect to dialing, dial plan, call completion, carriage of alarm signals and protocols, and loop voltage treatment.
> 3. Provides real-time transmission of voice signals, carrying alarm formats unchanged.
> 4. Provides professional installation that preserves primary line seizure for alarm signal transmission.
> 5. Has major and minor disaster recovery plans to address both individual customer outages and widespread events such as tornados, ice storms and other natural disasters. This includes specific network power restoration procedures that are comparable to those of traditional landline telephone services in the same geographic region.
> 6. Has informed ADT that its network meets the characteristics of a MFVN.
> Still how are they controlling this? Think ADT is smart enough to do a LRN lookup on a number, and see its not one from their qualified list?
>
> -----Original Message-----
> On Thu, Aug 6, 2015 at 6:21 PM, Colton Conor <colton.conor at gmail.com> wrote:
> We are a CLEC and have a had a couple of customers port away from Verizon's landline service and to our voice service where we provided an analog POTS line with the same number just as the client had before with Verizon. We hook the POTS line up to the exact same wire going to the client's alarm panel, but the alarm can't communicate with ADT.
>
> We called ADT on multiple clients behalfs, and they basically said Verizon is on an approved list to work with their services and our CLEC is not, so it would not work.
>
> How is ADT limiting this? Does their alarm panels dial a special number that only Verizon knows or allows? This has happened with multiple clients.
>
> We have not been able to get on the voice switch and see what numbers they panel is actually trying to dial, but any insight to this would be helpful.
>
> I have read that some alarm companies uses a special code before they make an outbound call so the long distance gets billed to them or something?
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Aug. 7, 2015
ADT Alarms Special Dialing?
by nathana@fsr.com
I doubt it. We are an ISP and ITSP doing voice exclusively 100% over IP. We have historically actively discouraged hooking up an alarm system to our service and relying on that (in order to avoid support headaches, liability issues, etc.), but we ourselves have an ADT system that was previously hooked up to local ILEC POTS service and that we moved over to an ATA of ours as an experiment.
It actually works just fine now, but it didn't initially. Turns out that the default "modulation" technique used between the panel and the monitoring center is...DTMF. Really. It appeared that either the monitoring center or the panel (or both) did not like something about how either the ATA or the terminating provider was regenerating the DTMF tones from the OOB info. Not sure if it was a timing issue or what. I am pretty sure I did try forcing DTMF to not be decoded/re-encoded and just remain inband, but that didn't seem to work for whatever reason (can't remember the details; it's been a while since this all transpired).
Eventually, I managed to track down an installer's manual for the particular model of panel we have, and was able to reprogram it to use a form of FSK modulation to talk to the monitoring center instead. It's super low bitrate (300 baud IIRC), and works 100% perfectly over G.711 PCM. (I know this because after I made the change, I accidentally managed to set the alarm off, and ADT called my boss, etc.; that was fun...) We have been using the panel this way for months, plugged into a VoIP ATA.
The panel dials an 800 number periodically to check in, and also when the alarm is tripped. If it cannot complete a check-in successfully, a light on the panel will be illuminated. That LED has not come on since the modulation switch. If they were doing LRN lookups, we would fail that test as well since none of our sources for DIDs are on ADT's "approved" list, either. I am sure I can get you the number that ours dials if you care to have it, but I have no way of knowing if they use the same number in all geographies or across all product lines (ours is an office/business system that I'm pretty sure doesn't get used in residential installs; for all I know, it may call a different monitoring center than the residential product(s) do).
Hope this helps at least give you some more ideas,
--
Nathan Anderson
First Step Internet, LLC
nathana at fsr.com
-----Original Message-----
From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Colton Conor
Sent: Thursday, August 06, 2015 4:30 PM
To: voiceops at voiceops.org
Subject: Re: [VoiceOps] ADT Alarms Special Dialing?
I did find this page?http://www.adt.com/customer-service/voip-faqs Seems that your phone company has to be:
A Qualified ?Managed Facility Voice Network (MFVN)?includes the following:
1. Has a physical facilities network which is managed and maintained (directly or indirectly) by the service provider. Can ensure service quality from the service subscriber location to the PSTN or other MFVN peer network.
2. Utilizes similar signaling and related protocols as the PSTN with respect to dialing, dial plan, call completion, carriage of alarm signals and protocols, and loop voltage treatment.
3. Provides real-time transmission of voice signals, carrying alarm formats unchanged.
4. Provides professional installation that preserves primary line seizure for alarm signal transmission.
5. Has major and minor disaster recovery plans to address both individual customer outages and widespread events such as tornados, ice storms and other natural disasters. This includes specific network power restoration procedures that are comparable to those of traditional landline telephone services in the same geographic region.
6. Has informed ADT that its network meets the characteristics of a MFVN.
Still how are they controlling this? Think ADT is smart enough to do a LRN lookup on a number, and see its not one from their qualified list?
-----Original Message-----
On Thu, Aug 6, 2015 at 6:21 PM, Colton Conor <colton.conor at gmail.com> wrote:
We are a CLEC and have a had a couple of customers port away from Verizon's landline service and to our voice service where we provided an analog POTS line with the same number just as the client had before with Verizon. We hook the POTS line up to the exact same wire going to the client's alarm panel, but the alarm can't communicate with ADT.
We called ADT on multiple clients behalfs, and they basically said Verizon is on an approved list to work with their services and our CLEC is not, so it would not work.
How is ADT limiting this? Does their alarm panels dial a special number that only Verizon knows or allows? This has happened with multiple clients.
We have not been able to get on the voice switch and see what numbers they panel is actually trying to dial, but any insight to this would be helpful.
I have read that some alarm companies uses a special code before they make an outbound call so the long distance gets billed to them or something? ?
Aug. 7, 2015
ADT Alarms Special Dialing?
by colton.conor@gmail.com
I did find this page http://www.adt.com/customer-service/voip-faqs Seems
that your phone company has to be:
A Qualified ?Managed Facility Voice Network (MFVN)?includes the following:
1. Has a physical facilities network which is managed and maintained
(directly or indirectly) by the service provider. Can ensure service
quality from the service subscriber location to the PSTN or other MFVN peer
network.
2. Utilizes similar signaling and related protocols as the PSTN with
respect to dialing, dial plan, call completion, carriage of alarm signals
and protocols, and loop voltage treatment.
3. Provides real-time transmission of voice signals, carrying alarm
formats unchanged.
4. Provides professional installation that preserves primary line
seizure for alarm signal transmission.
5. Has major and minor disaster recovery plans to address both
individual customer outages and widespread events such as tornados, ice
storms and other natural disasters. This includes specific network power
restoration procedures that are comparable to those of traditional landline
telephone services in the same geographic region.
6. Has informed ADT that its network meets the characteristics of a MFVN.
Still how are they controlling this? Think ADT is smart enough to do a LRN
lookup on a number, and see its not one from their qualified list?
On Thu, Aug 6, 2015 at 6:21 PM, Colton Conor <colton.conor at gmail.com> wrote:
> We are a CLEC and have a had a couple of customers port away from
> Verizon's landline service and to our voice service where we provided an
> analog POTS line with the same number just as the client had before with
> Verizon. We hook the POTS line up to the exact same wire going to the
> client's alarm panel, but the alarm can't communicate with ADT.
>
> We called ADT on multiple clients behalfs, and they basically said Verizon
> is on an approved list to work with their services and our CLEC is not, so
> it would not work.
>
> How is ADT limiting this? Does their alarm panels dial a special number
> that only Verizon knows or allows? This has happened with multiple clients.
>
> We have not been able to get on the voice switch and see what numbers they
> panel is actually trying to dial, but any insight to this would be helpful.
>
> I have read that some alarm companies uses a special code before they make
> an outbound call so the long distance gets billed to them or something?
>
Aug. 6, 2015
ADT Alarms Special Dialing?
by colton.conor@gmail.com
We are a CLEC and have a had a couple of customers port away from Verizon's
landline service and to our voice service where we provided an analog POTS
line with the same number just as the client had before with Verizon. We
hook the POTS line up to the exact same wire going to the client's alarm
panel, but the alarm can't communicate with ADT.
We called ADT on multiple clients behalfs, and they basically said Verizon
is on an approved list to work with their services and our CLEC is not, so
it would not work.
How is ADT limiting this? Does their alarm panels dial a special number
that only Verizon knows or allows? This has happened with multiple clients.
We have not been able to get on the voice switch and see what numbers they
panel is actually trying to dial, but any insight to this would be helpful.
I have read that some alarm companies uses a special code before they make
an outbound call so the long distance gets billed to them or something?
Aug. 6, 2015
Vitelity's parent company (Onvoy) acquires Broadvox
by beckman@angryox.com
Just got this email from Vitelity. Interesting.
http://www.marketwired.com/press-release/onvoy-acquires-broadvox-become-thi…
Did anyone else notice the 2 day Vitelity SMS outage June 12-14?
Beckman
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman at angryox.com http://www.angryox.com/
---------------------------------------------------------------------------
---------- Forwarded message ----------
Date: Wed, 5 Aug 2015 14:39:42
From: Vitelity <nores at vitelity.com>
To: Peter Beckman <beckman at telusion.com>
Subject: Vitelity's parent company acquires Broadvox
Dear Vitelity Customer,
We have some very exciting news. Vitelity's parent company, Onvoy, LLC. has
just announced that they are acquiring Broadvox. This acquisition will
expand Onvoy's onnet footprint to 5000 rate centers allowing Onvoy to
become the third largest wholesale CLEC in North America.
How will this benefit you? You'll have access to more local rate centers
and a more robust nationwide network while getting the same unmatched
customer service you've come to expect from Vitelity.
Thanks for your continued business and support.
The Vitelity Team
Aug. 5, 2015
Suspect NPANXX question
by jim.dalton@transnexus.com
Here is what we know about 1-268-762.
On July 22, 2014, Telstra reported 1268762015 to the list maintained by the
GSMA Fraud and Security Group.
On Sept. 1, 2014, we recorded that 12687620310 was a premium rate test
number advertised by www.cyclone.li
On Sept. 1, 2014, we recorded that 12687620001 was a premium rate test
number advertised by iprn.me. This website is no longer available.
Jim D.
-----Original Message-----
From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Ryan
Delgrosso
Sent: Tuesday, August 04, 2015 2:34 PM
To: voiceops at voiceops.org
Subject: [VoiceOps] Suspect NPANXX question
All,
We have seen a Caribbean NPANXX (1-268-762) advertised to us from a US tier
1 vendor. It has drawn a large amount of fraudulent traffic.
We first saw this prefix pop up in this vendors rate decks in April.
Going back to the start of the year I cannot find it in any revision of the
LERG though, and no other vendor I have offers routes/pricing to this
prefix.
Does anybody know whats going on here?
Shouldn't any zone 1 prefix exist in the LERG months prior to going live, or
at the very least within some reasonable time after showing up for live
traffic?
Does this smell like highjacking to anyone else?
All our vendor will tell is they are getting the route from another T1
vendor, but in my 20+ connected peers I cannot find another occurrence.
Any help or guidance is much appreciated. Feel free to reply on or off
list.
-Ryan
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
Aug. 4, 2015
Suspect NPANXX question
by jackson.tim@gmail.com
I only see 1 carrier with this route as of today in all of our decks.
Looking back through the past month or so of traffic, I can't find any
attempts to this prefix.. A quick google of it seems to show a lot of
scams calling from this prefix anyway.
On Tue, Aug 4, 2015 at 11:33 AM, Ryan Delgrosso <ryandelgrosso at gmail.com> wrote:
> All,
> We have seen a Caribbean NPANXX (1-268-762) advertised to us from a US tier
> 1 vendor. It has drawn a large amount of fraudulent traffic.
>
> We first saw this prefix pop up in this vendors rate decks in April. Going
> back to the start of the year I cannot find it in any revision of the LERG
> though, and no other vendor I have offers routes/pricing to this prefix.
>
> Does anybody know whats going on here?
>
> Shouldn't any zone 1 prefix exist in the LERG months prior to going live, or
> at the very least within some reasonable time after showing up for live
> traffic?
>
> Does this smell like highjacking to anyone else?
>
> All our vendor will tell is they are getting the route from another T1
> vendor, but in my 20+ connected peers I cannot find another occurrence.
>
>
> Any help or guidance is much appreciated. Feel free to reply on or off list.
>
> -Ryan
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Aug. 4, 2015