possible web callback bug

[v164]

For web callback, if you enter a PSTN number, to be called via SipBroker, and that PSTN number maps via ENUM to a VoXaLot SIP URI, the call doesn't work.


I suggested to this person:

http://forums.whirlpool.net.au/forum...49&p=-1#bottom

to use web callback to test ENUM setup:

At the web callback screen,
http://www.voxalot.com/action/webCall

For "Your Number", enter 6129xxxxxxx (your PSTN number), via SIP Broker, and for "Number to Dial", enter 15166875089 (an ENUM test number), via SIP Broker.

But it didn't work for them:

Didn't work for me when I tried this last night at around 11.50pm. I got a green tick on voxalot but my phone didn't ring.

Their PSTN number is mapped to their VoXaLot SIP URI -
xxxxxx@au.voxalot.com


I have just tried this myself, and it doesn't work for me either. My PSTN number is mapped to 660xxx@us.voxalot.com at e164.org

For "Your Number", I entered 8159xxxxxxx (my PSTN number), via SIP Broker, and for "Number to Dial", I entered 15166875089 (an ENUM test number), via SIP Broker. My phone (registered as 660xxx on us.voxalot.com) didn't ring.

I could get web callback to work if I entered my number as *010660xxx via SipBroker, but it doesn't work if I enter my PSTN number via SipBroker.

It also works if I call one of my other PSTN numbers which is mapped to a non-VoXaLot SIP URI.

Dialing the SIP URI 8159xxxxxxx@sipbroker.com from a softphone also works, so the problem is only with Voxalot web callback.

[v164]

Originally Posted by v164

For web callback, if you enter a PSTN number, to be called via SipBroker, and that PSTN number maps via ENUM to a VoXaLot SIP URI, the call doesn't work.

Come to think of it, the problem may only be if the VoXalot URI it maps to is your own Voxalot number (the one that you're currently logged in as).

The SIP server might recognise that as a loop or something and cancel the call.

[v164]

Originally Posted by v164

Come to think of it, the problem may only be if the VoXalot URI it maps to is your own Voxalot number (the one that you're currently logged in as).

The SIP server might recognise that as a loop or something and cancel the call.

Just confirmed that that is the case by testing with a new account.

[martin]

Originally Posted by v164

Just confirmed that that is the case by testing with a new account.

Yes loopbacks are detected and not allowed by the core engine.

[Danny Z]

It has nothing to do with webloopbacks, I am calling from my hotel using Xlite configured to voxalot, the dial plan uses voipcheap for this number then I am dialing my vbuzzer number that is already registered to sipbroker to forward to myvbuzzername@vbuzzer.com:80
The call does not go through it says the number does not exist. However if I take the software used by voipcheap and direct directly from this software it works. So there is definitely something wrong with SIP broker mapping