Cannot use PINSETS with Fpbx 17 and Sangoma Phone

We just upgraded from 16 to 17 and we keep getting weird little problems. I just noticed that I cannot use pinsets for outbound routes. The pinsets get configured and I get asked for the pin when dialing out but whatever I dial is always wrong. No matter the pinset I choose (with a single pin) we always get the incorrect pin prompt. DTMF seems to be working because if I dial out to another IVR I can press digits correctly. When I enter the pin it does not interrupt the audio like it does for the external IVR. Is this related to early audio on the trunk? This was working fine in 16.

Since the PIN prompt appears but every PIN is rejected, I’d first check whether Asterisk actually receives the digits you type. A few things to try:

  1. Re-save the PIN set, then re-save the outbound route that uses it, and click Apply Config. After a 16→17 upgrade, stale generated dialplan is possible.
  2. Check the DTMF mode on the extension/phone (RFC2833 vs SIP INFO vs inband). A mismatch can mean Asterisk gets no digits or wrong ones. Your IVR test may behave differently because that digit path is separate from the one used for the PIN prompt.
  3. Run asterisk -rvvv (and turn on DTMF/RTP debug, e.g. “pjsip set logger on”) while entering the PIN, and see which digits arrive, if any.
  4. Test from a different phone or a softphone to find out whether it’s the Sangoma phone or the system.

If the digits show up correctly in the CLI, post that output and the route/PIN set settings, as that would point to the PIN set module itself.

(Written with help from an AI assistant.)

I finally fixed this by modifying and option called “Force Answer before PIN Prompt” in the SangomaConnect configuration. I guess either the backup did not have this option or it did not exist in 16.

Thank you for the suggestions as they made me look through everything so I found this setting.