SPA to Voxalot REDIRects?

[Tslam]

SUPPORT Question Please...

I'm trying to cfwd incoming PSTN calls from my PSTN gateway (3102) to VoIP/PSTN. It doesn't work apparently because Voxalot fails the REDIRect (eg call Diversion).

Why doesn't Voxalot follow this (to mobile thru my Provider in Voxalot):

Calling:0410000123@au.voxalot.com:0
[0:5062]->192.168.1.31:5060
SIP/2.0 302 Moved Temporarily
To: <sip:123456@192.168.1.32:5062>;
From: Peer1 <sip:123000@au.voxalot.com>;
CSeq: 101 INVITE
Via: SIP/2.0/UDP 192.168.1.31:5060;
Contact: <sip:0410000123@au.voxalot.com>
Diversion: Peer2 <sip:123456@au.voxalot.com>;reason=unconditional
Server: Linksys/SPA942-5.1.7

Yet it follows this (to Monkeys thru Voxalot proxy):

Calling:*266300@au.voxalot.com:0
[0:5062]->192.168.1.31:5060
SIP/2.0 302 Moved Temporarily
etc...
Diversion: Peer2 <sip:123456@au.voxalot.com>;reason=unconditional

If I program Cfwd on my SPA phone then enter *266300, callers to my PSTN gateway hear sipbroker's monkeys. But if I enter my mobile 0410 etc instead, the call fails and the caller hears Voxalot's "were sorry...".

Without getting immersed in SIP traces here - what could be preventing Voxalot doing the SIPLI:REDIR 0410000123@xxx?

I examined the logs prior to both calls (monkeys and mobile), and there really aren't any differences I can see - except that Voxalot doesn't respond seeking authentication to follow the Diversion. The only difference in circumstances is that Voxalot is configured to send mobiles to Pennytel, while it sends monkeys via Sipbroker by default.

What's the big picture here? Voxalot not compatible with Linksys? Linksys not compatible with Voxalot? Voxalot doesn't want clients to do their own forwarding to VSPs??

NAT issues aside, Voxalot should IMO play nicely with market leading equipment such as Linksys - or at least we need to be given the detailed config's to make it happen. I can't keep forwarding all my callers to Monkeys.

Over to Voxalot...