Since upgrading to 5.07, I've been having the following problems with VoIP and iiNet. I've seen lots of similar reports, and I thought I'd add mine to the fray.

Registration proceeds fine when setting up the config, and any time I hit [sync now]. After some period of time (not really sure how long), I start hearing nothing but an engaged tone. At the same time, the logs are filling with this:

Unfortunately iiNet support couldn't, or wouldn't tell me what the logs look like from their end. I can't think of a way to do a packet dump, either, so I can't take a look at the traffic myself.

Just to preempt any questions, this is all based upon a new setup from factory defaults after upgrading.

Regards,
Toby.

Aug 04 20:51:16 gateway.permuted.net:sip_?:none: SIP Registration is Forbidden for phone 03xxxxxxxx
Aug 04 20:52:15 gateway.permuted.net:sip_?:none: SIP Registration is Forbidden for phone 03xxxxxxxx
Aug 04 20:53:15 gateway.permuted.net:sip_?:none: SIP Registration is Forbidden for phone 03xxxxxxxx
Aug 04 20:54:15 gateway.permuted.net:sip_?:none: SIP Registration is Forbidden for phone 03xxxxxxxx

The config for this endpoint is:

A epname '03xxxxxxxx'
A authUserId '03xxxxxxxx'
A password '*********'
A displayname 'xxxxxxxxxxx'
A adminstate 'true'
A index '1'
A codecorder 'PCMU,PCMA,G729'
A regstatus 'registered'
A registrar 'sip.vic.iinet.net.au'
A registrarPort '5060'
A regExpires '3600'
A userDomain 'iinetphone.iinet.net.au'
A outboundserver 'sip.vic.iinet.net.au'
A outboundserverPort '5060'

I'm on iiNet (Qld) with 5.07 and have no problem. You might try a different iiNet server to compare.

Also you might try setting up the registration with another device or from the Voxalot server just to see what happens.

Can you register with another provider, or is it just iiNet?

Are you able to set up the console cable to monitor? If so, the SIP events might give a clue as to what is going on.

Basic process is to use a terminal program to log in via the serial connection.
Issue the commands:

console enable
event show

log the results and post.

fyi, you can also use telnet to capture these logs if you wish.

telnet 192.168.1.254
console enable
event show

capture the output