Are using the AA Stun server stun.aa.net.uk and set STUN on the fxs port page. The other settings I have changed are "Use STUN to detect network activity", NAT Traversal: STUN.

Have a look here

The status changed to registered after I enabled "Use STUN to detect network activity".

Still unable to receive incoming calls. My mobile reports 'invalid number', but at least I'm making progress.

Thanks.

I was getting that before my port went through. I could make outgoing calls at 10am on the 7th but mobile was saying invalid number. Then port was completed 12:50pm and I could get incoming calls.

Could be CGNAT problem or a BT error. I would think if it was CGNAT problem you would get busy tone. Funny how it worked initially.

I would contact AA support on Monday if it remains not working and have a look at the NAT page I linked to.

Other things I changed Will register to Primary Server if Primary Server responds, need to enable SIP OPTIONS/NOTIFY Keep Alive: Yes, SIP URI Scheme When Using TLS: SIP, SIP Registration: Yes, Unregister On Reboot: All, Register Expiration: 10 and Reregister before Expiration: 300 might stop registration expiring.

I used these settings as a checklist.

Edited by Banger (Sat 08-Nov-25 20:13:56)

In reply to a post by Zadeks:

The status changed to registered after I enabled "Use STUN to detect network activity".

Still unable to receive incoming calls. My mobile reports 'invalid number', but at least I'm making progress.

Thanks.

Any joy or are you waiting for Monday?

No luck. I've asked Quickline for a dynamic IPv4 address.

Let me know how you get on.

It was an AAISP carrier issue. Everything's back up and running!

Thanks for your help.

In reply to a post by Zadeks:

It was an AAISP carrier issue. Everything's back up and running!

Thanks for your help.

Ah good you are back up.