Thanks for answer. Devices PAP2 and SPA3000 works good and use FSK for VMWI and CallerID, so I think TDM410P should also works. CallerID works good. So issue should be in source code of VMWI.
Alec, If FSK is used for VMWI on his working setup, this doesn’t
sound like it would be fixed by your “Generate VMWI neon pulses from
FXS module..” patch to the wctdm24xxp DAHDI driver  I’m assuming.
Must be something in chan_dahdi?
But Now that the changes to the wctdm24xxp have calmed down (for
awhile now… :/) it looks like it might be time to try again to
rebase those patches on the current trunk.
I don’t think neon use FSK, neon should use high voltage. So I think,
the issue should be on FSK in DAHDI module code.
It sounds like we’re in agreement. Although, to be clear,
DAHDI-Linux (the kernel modules) do not generate or decode FSK
spills. That is done by chan_dahdi in Asterisk.
Sorry, I didn’t word my reply correctly, I wasn’t trying to say ‘hvac’
support on the TDM410P would fix the issue.
As I think about it more, having the option enabled there doesn’t matter,
even for a TDM410P.
Shaun: Regarding neon patch (review 1144) for wctdm24xxp, I’ll have to get
on to that.
🙂 I know I was the one who stalled it last time….