SPA-3102 FXS Only - Outbound calls not working

[DrRob]

3CX Community,

Migrating an old FreePBX deployment where an SPA-3102 is being used to convert a portable/wireless base station and handset into an extension in the PBX. This has always worked very well. It is NOT being used on the PSTN in any capacity. There is no PSTN at that location.

I have an extension in 3CX. The SPA-3102 registers fine. Inbound calls work flawlessly.

Outbound calls? Errors out. I've thrown a lot at the wall based on research in these forums and beyond, but I'm definitely still missing something.

Here's what's showing up in the activity logs:



What should I be looking for here? Based on the above, it appears to be getting struck down on some type of authentication during the outbound call, but the auth info is known to be good because it's able to register.

 

[leejor]

So.. the 3102 is only being used on the FXS part, and it is being used remotely, using STUN?

Much the same configuration (for the basics), a number of posts on the forum, dealing with the 112 and 122.
https://www.3cx.com/community/threads/3cx-and-cisco-spa112.53696/#lg=attachment6914&slide=0

 

[DrRob]

So.. the 3102 is only being used on the FXS part, and it is being used remotely, using STUN?

Much the same configuration (for the basics), a number of posts on the forum, dealing with the 112 and 122.
https://www.3cx.com/community/threads/3cx-and-cisco-spa112.53696/#lg=attachment6914&slide=0

The settings referenced in that post are what I'm using the SPA3102 config. That got me registered and is allowing inbound calls. Yes, it is being used remotely.

I guess the question is what could I be missing if the registration is successful, but getting some type of auth failure on outbound calls only?

 

[DrRob]

Well, got this going. Want to know what I did? Nothing. Had everything right to begin with.. Didn't change anything.

I did, however, power cycle the SPA3102 and then outbound calls started to get out. No auth issues.