> I wouldn't be surprised if you were seeing it try to dial DTMF, then pulse,
> then DTMF again if the call didn't cut through very quickly.
----- ADTRAN went straight to examining the dialing-plan in the TA5000 when I
shared my config with them for those exact reasons. We both agreed since digits
were missing in the middle in many cases this was probably not a dialing-plan
issue or DTMF/pulse dial issue. They signed off on our config as proper.
----- My last hopeful attempt is that ADTRAN appears to have engineering
superuser temporary passwords for the TA5000 that can see things I cannot. So I
have to get a test scheduled with them. I had a tech out at a GR303/TA750 site
today and no matter what we tried those two digits in my previous example were
always missing.
----- I just need to motivate people to keep working this as people above us
said why are we spending this much time on a dozen pots lines and the alarm
vendor is difficult to work with. They can go to Verizon or get that cell phone
setup for alarm panels. Killing off a DMS switch is a big savings and each
month costs $$$.
> On Feb 13, 2023, at 3:47 PM, Jay Hennigan via VoiceOps
> <[email protected]> wrote:
>
> On 2/13/23 11:48, Matthew Yaklin wrote:
>
>> --- The issue is that when the alarm panel dials the INVITE from the TA5k
>> does not contain the correct digits dialed. A couple of digits are missing
>> for example. Sometimes a call does manage to squeak through properly. If the
>> digits do get to the Metaswitch properly the call completes fine. Same exact
>> symptom with GR303. In SAS (meta's service assurance server that contains
>> debug output) I can clearly review what digits reach the metaswitch via
>> GR303. In this case I will see missing digits as I know the number the alarm
>> panel is supposed to dial and a gap of time which should have contained
>> digits.
>
> OK, so the FXS port of the local Adtran device isn't reliably decoding the
> DTMF from the panel. Could be frequency, level, or twist. See if there are
> knobs for receive level and/or impedance for the specific line port used by
> the panel. I'd start with level, bump it up and down 3dB at a time and see if
> it starts decoding reliably. If possible bracket it to see where it fails
> again and set it in the middle.
>
> Changing impedance might help if it's twist. Sometimes the options include
> series capacitance. Likely going to be trial-and-error.
>
> --
> Jay Hennigan - [email protected]
> Network Engineering - CCIE #7880
> 503 897-8550 - WB6RDV
>
> _______________________________________________
> VoiceOps mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/voiceops
>
_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops
