DID Number Problems - Fairly urgent

[Lanh]

Hi,

I have a DID number which is forwarding correctly to Voxalot however, the call it going straight through to voicemail when voicemail is activated and when voicemail is not activated I am getting a message from BT which says "Sorry there is a fault".

Can anyone advise what I can do in this situation?

Thanks

[affinity]

What equipment are you using?

Is it behind a NAT firewall?

Does *600 echo test work?

Does a call via a PSTN to VoIP gateway work?
- this is done using *010 with your voxalot number.

[Lanh]

Originally Posted by affinity

What equipment are you using?

It's a box from VoIP.co.uk that was unlocked.

Originally Posted by affinity

Is it behind a NAT firewall?

Yes, but I always have been and it's always worked before.

Originally Posted by affinity

Does *600 echo test work?

Yes

Originally Posted by affinity

Does a call via a PSTN to VoIP gateway work?
- this is done using *010 with your voxalot number.

Yes.

I am able to receive SiP calls direct to my Voxalot URI
I am able to receive SiP calls forwarded from FWD to my Voxalot URI
I am able to receive SiP calls forwarded from SiPPhone to my Voxalot URI
I am able to receive SiP calls direct to my Voxalot URI using SipBroker
I am able to receive SiP calls forwarded from FWD to my Voxalot URI using SipBroker
I am able to receive SiP calls forwarded from SiPPhone to my Voxalot URI using SipBroker
I am able to receive SiP calls direct to my Voxalot URI using ENUM short code.

It is only this new DID which isn't working, as I said, it's producing a fault if the Voxalot voicemail is disabled and sending calls straight to voicemail if the Voxalot voicemail is enabled.

It's one of the new 03 UK non-geographic numbers, and my exchange is enabled for it because I rang the suppliers (AAISP broadband internet) support number to set-up forwarding and that worked with no problems.

[Lanh]

Furthermore...

I just signed up with XtraPhone: Free sign up for Free world Dialup users to provide an 0870 number for people to call me, just to test the thing.

My FWD account is forwarded to my Voxalot URI, I called the number and it went through with absolutely no problems whatsoever.

[Lanh]

Am I right in thinking that the following set of attempts means that the fault is not with Voxalot?

03333 PSTN >> Voxalot FAILED
03333 PSTN >> FWD >> Voxalot FAILED
03333 PSTN >> SipPhone >> Voxalot FAILED

SipBroker PSTN >> Voxalot SUCCESS
SipBroker PSTN >> FWD >> Voxalot SUCCESS
SipBroker PSTN >> SipPhone >> Voxalot SUCCESS

Direct SIP Call >> Voxalot SUCCESS
Direct SIP Call >> FWD >> Voxalot SUCCESS
Direct SIP Call >> SipPhone >> Voxalot SUCCESS

0870 PSTN >> FWD >> Voxalot SUCCESS

Or could it be that there is still a problem this end?

[emoci]

What's the URI to which the 03 number is being forwarded like:

Try
user@voxalot.com
or
user@xx.voxalot.com (where xx is us, eu or au)

But from the looks of it, VoXalot works with every case except that number.

Originally Posted by Carl.

Am I right in thinking that the following set of attempts means that the fault is not with Voxalot?

03333 PSTN >> Voxalot FAILED
03333 PSTN >> FWD >> Voxalot FAILED
03333 PSTN >> SipPhone >> Voxalot FAILED

SipBroker PSTN >> Voxalot SUCCESS
SipBroker PSTN >> FWD >> Voxalot SUCCESS
SipBroker PSTN >> SipPhone >> Voxalot SUCCESS

Direct SIP Call >> Voxalot SUCCESS
Direct SIP Call >> FWD >> Voxalot SUCCESS
Direct SIP Call >> SipPhone >> Voxalot SUCCESS

0870 PSTN >> FWD >> Voxalot SUCCESS

Or could it be that there is still a problem this end?

[Lanh]

Hi emoci,

It was being forwarded to number@eu.voxalot.com, just tried number@voxalot.com.

I think it'd probably a fault with the number because otherwise surely the 0870 number would fail as well given they have the same routing and so would the normal call forwarding from SipPhone and FWD wouldn't it?

[Lanh]

NVM, I upgraded to premium, I didn't want to until the new year, but at least I can use the number immediately.