Hi Thomas,
Sure would be interesting to capture a syslog of the SIP messages from or to the WIP310 (even better would be a ethereal trace).
If ethereal is not an option, can you grab one of the freeware syslog servers out there for your PC's operating system.
step 1. on the WIP310 under the system tab, you can specify the Syslog servers IP address.
Make sure your personal or windows firewall is not blocking the syslog port number , UDP port 514 on the syslog server PC.
Step 2. Ext 1 on the WIP310 already has 'full' specified under the SIP Debug option (so no action required)
Please note; to wade though a syslog capture is not an easy task, so please don't capture too much.
It would be better to only capture a call being made to the WIP310 and an attempt to hear and speak on the WIP310.
Capture this syslog messages to a text file and post it.
As a thought, it would be interesting (if possible) to see take the WIP310 to the main site and see if it works when locally connected.
Your current status
Sound all should be working fine, you've manually told the WIP310 that the SPA9000 is at 192.168.1.254 and it's registered.
Still would be interesting to see the SPA9000 PBX status page, but i'm guessing there is a entry there for the WIP310.
Multicasts traffic normally found on a LVS network wont be working over your VPN connections. But you must be aware of this already, since the system has been running for a year.
Lastly, if the community can't spot the problem, i guess you could place a call via the Small Business Support Center
http://www.cisco.com/en/US/support/tsd_cisco_small_business_support_center_contacts.html
