Voxalot introducing Problems?

[martin]

Hi BJ,

There seems to be a problem with the PSTN access number. A test using:

+44-20-7100-6747 Failed

While a test to:

+44-56-0002-9247 Passed

If you can confirm the above I will email the DID provider and report the problem.

[BJ_Abbott]

Hi Martin,

Using independent landline or mobile, I get failure on both with the same error as mentioned before.
Certainly made my voip settings validation testing problematic.

Many thanks

BJ

[martin]

Strange how the PSTN access numbers are failing on your number and calling you via VoXaLot and SIP Broker works.

Is it possible that your CODEC settings are not compatible with the PSTN access numbers?

Do you have any known restrictions around CODECS in place?

[BJ_Abbott]

Codec options on the billion fall back in any order:
* PCMU (G711 u-Law)
* G729
* PCMA (G711 A-Law)

My settings are in the above order and voip connection reports PCMU is in use

The Billion 7402VGO has a separate dialplan for outward PSTN and toggles between sip and PSTN using the recall button
There is a new advanced option to fall back to PSTN based upon the following sip codes: 400,401,402, 403,404,405,406,407,408,409,410,411,413,414,415,42 0,480,481,482,483,484,485,486,487,488,491,493,500, 501,502,503,504,505,513,600,603,604,606,999, I have now enabled this

I know very little about the technicalities of these codecs

Regards

BJ

[fozzie]

Originally Posted by BJ_Abbott

Further,
The same rejection happens when dialling 056-0002-9247, the alternative London provider

BJ

Just tested from PSTN to my Voxalot and all ok. If you can dial 500/600 ok then it does look like some kind of internal (Sipbroker/Voxalot) routing problem?

[BJ_Abbott]

Confirm that my calls to sipbroker on 500 and 600 both work, but that *010-'voxalotID'# or *011-44'voxalotID2#still get the unavailability message.

I have a sipbroker record pointing towards 'voxalotID'@voxalot.com, although I thought that this was unnecessary.

I also have enum records for:

• Local PSTN pointing to 'voxalotID'@voxalot.com
• Sipgate Local PSTN pointing to 'sipgateID'@sipgate.co.uk

I do not have enumeration for voxee as I don't need another PSTN number.

Could you please advise on anything that does not look correct

If all of the above looks right, my suspicion falls back to selecting the right listening port for voxalot:

• The Billion 7402vgo default is 5100 -5132
• Sipage seems to require inclusion of 5004 - so current setting 5002-5036
• voxalot requires what?

Or are there voxalot stun settings that I could use?

Thanks for your help

[BJ_Abbott]

Have done further tests by removing sipgate from providers with only voxee left:

On reflection, my hypothesis is that, from the UK, voxee, as they outline, is essentially an outward service only . If inward dialling is supported then it is probably only into US, with overseas and inward blocked. Hence UK sipbroker calls to voxee lead to the extension unavailable message and a voxalot voicemail.

Is this the root reason why uk sipbroker to voxalot does not work?

I would be grateful for further advice on this and the above.

[fozzie]

Originally Posted by BJ_Abbott

Is this the root reason why uk sipbroker to voxalot does not work?

It works fine for me.