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...

[martin]

If you are getting the "We're sorry......" message then it is hitting the Voxalot engine which is a good start.

Best thing to do is PM me the numbers you are calling from/ to and we can parse the logs and see what numbers are hitting the system.

[Tslam]

PM sent with relevant details. SIP logs available.

By the way, I know another user (more tech. advanced than me) who has encountered this problem on other makes of equipment. I'll leave that person to join the discussion if they wish.

[martin]

I have sent you a reply. As the reply has your account details I have not posted here.

[Tslam]

Martin - you pointed out that the inbound is coming from sip:123000@au.voxalot.com which has no (Voxalot) dial plan.

This would mean the call gets authenticated to the redirectee (123000), not the redirector (123456). So I copied my VSP plan onto 123000 and it works when I IP Dial the SPA942 phone from [3102]Line1. But not when I IP dial from [3102]PSTN Line. Maybe we can fix that anon.

First, a thought experiment... what if the caller is another Vox user. If a SPA942 (or any similarly equipped IP phone) issues them a REDIR, does the caller place the call forward; and pay for it? Does the REDIR fall over if the caller hasn't got a compatible dialplan for my mobile number? Surely it's not meant to work that way.

I'm still stuck in the maze. Perhaps you can enlighten me as to the big picture. Am I barking up the wrong tree, do I need a PBX to anchor the incoming call before submitting it to my phone? Or is there some twist of SIP protocol in either Voxalot or Linksys which will make this call forward happen.

Please give me the view from the helicopter; or at least drop me a food parcel.

[martin]

Originally Posted by Tslam

Please give me the view from the helicopter; or at least drop me a food parcel.

I can not answer this question as Voxalot has no visibility whatsoever of the client side redirects you are performing.

Ultimately when the SIP INVITE hits any SIP proxy (including Voxalot's) it is the FROM header field that is parsed out, authenticated against and in the case of Voxalot, forms the basis of a dial plan lookup.

You get those bits right and the call will route.

[mohnashaat]

Tslam

i tried the same cfwd, and it seems voxalot do not support it, u can do it with selected dial plans in the pst-to-voip settings