SPA8800 FXS ports failing to register after move to FreePBX17

This is incorrect. It should show auth_username.
Look on the Advanced tab for the trunk for Match Inbound Authentication. Does it show “Auth Username”?

If yes, change it to something else, press Submit, change it back to Auth Username, Submit again, Apply Config, restart Asterisk, check whether
pjsip show endpoint SPA8800FXO0
now shows the correct value.

If not, set it to Auth Username, Submit, Apply Config, close browser, reopen it to the Advanced tab for the trunk, does Match Inbound Authentication now show Auth Username? If so, restart Asterisk, check
pjsip show endpoint SPA8800FXO0
again.

The SPA8800 went EOL back in 2019:

I use a Cisco router with FXO cards in it as a VoIP gateway and when I first set this up with FreePBX 13 I could never get it to work with chan_pjsip I had to use chan_sip

That also is a very EOL product from Cisco.

My conclusion is that when Cisco first developed SIP protocol for their devices it was back in the Dark Ages prior to chan_pjsip and they got it interoperable with chan_sip without paying attention to the actual SIP protocol standard. Then they used this implementation in the rest of their stuff (phones, etc.) I do think that quietly over the years they have been correcting whatever brokenness they created but your device likely does not have a firmware update that fixes this. You may have to drop back to Asterisk 20+chan_sip under FreePBX 17.

Note that the Sangoma Vega 60G Gateway 4 FXO box sells for around $540 on Amazon and the SPA8800 seems to be listed for half that on Ebay so you might consider just buying a new gateway and selling yours, to be “100% supported”

Stewart,
That was it, I had the match authentication set to default when the setting were moved over from the old server. I changed it to Auth Username like you said and now the trunk is working in both directions.

Thank you for your assistance

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.