I have to dial number twice
 

I have my ATA (NB9W) registered with voxalot.com.au using Pennytel and Sipme routed by Voxalot dial plans.
Since, I guess about 5 days ago, whenever I first dial, the number sounds like it is engaged when I know it isn't, then if I hit redial it rings properly. This is regardless of which provider it is to be routed through.

If I just keep testing the dialing, every second attempt consistently will ring properly with the other attempts giving an engaged tone. When it is going to work the wait for switching takes a bit longer. I'm dialing my PSTN number so I'm sure its not engaged.

If I register my ATA directly to the provider there is no problem.

Although the voxalot aus server worked ok for me earlier, I tried changing back to the US server but that gives an engaged tone all the time for me now.

If I register my ATA directly to the provider there is no problem so for the moment I've left it like that.

Any ideas?

My Voxalot number is 523004.

No replies... seems nobody has had this problem...

It is still consistent, while registered to voxalot I always get the 'engaged' beeps first try then I hit redial and it works properly. Will test it from time to time but for now will have to register with the provider and do without dial plans. :(

What happens if you redial the number manually the second time rather than hit redail?

What is the dial plan on your ATA?

Matt

I've tried both ways lots of times, same result. Its the redial on our Doro portables

Priority Pattern Replacement Provider Active
15 _04. ${EXTEN} Pennytel Untimed 758 Yes [Edit] [Delete]
20 _2NXXXXXXX 613${EXTEN:1} Pennytel Timed 200 Yes [Edit] [Delete]
21 _3NXXXXXXX 03${EXTEN:1} Sipme Yes [Edit] [Delete]
30 _20NXXXXXXXX 61${EXTEN:2} Pennytel Timed 200 Yes [Edit] [Delete]
31 _30NXXXXXXXX ${EXTEN:1} Sipme Yes [Edit] [Delete]
35 _NXXXXXXX 613${EXTEN} Pennytel Untimed 758 Yes [Edit] [Delete]
40 _0NXXXXXXXX 61${EXTEN:1} Pennytel Untimed 758 Yes [Edit] [Delete]
50 _0011. ${EXTEN:4} Pennytel Untimed 758 Yes [Edit] [Delete]
55 _1300. ${EXTEN} Sipme Yes [Edit] [Delete]
60 _13XXXX ${EXTEN} Sipme Yes [Edit] [Delete]
65 _1800. 61${EXTEN} Sipme Yes [Edit] [Delete]

The priorities 20 to 31 are similar to 35 and 40 only they are extras to allow dialing a 2 or 3 first to manually choose provider.

All lines test ok on the tester and I've tried disabling all lines except one and dialing a number for it but the same result.

It was all working beautifully earlier last week.

I test dialled a lot this morning and occasionally it would ring the phone 3 times in a row if no breaks in between. I might try making a new voxalot account (sounds like a long shot).

Thanks for your reply Matt... you certainly help a lot of people with voip :)

No problems, happy to help if I can. The other thing you could try is a different telephone handset.

Matt

I'm pleased to report that this problem appears to be fixed. I didn't get time to do more testing... just went direct to vsp instead, and today tried switching my ATA back to voxalot again. Did some test dialling and some real calls in the last hour and everything working perfectly again, so I won't find out what caused the problem.

Good to be back. :)

Jeff

Good news. The only thing we changed on our side was some database indexing to speed up lookups. Interested to know if things hold up for you.

I'll let you know if the problem returns. Nothing has changed here either as far as I can tell. I guess rare problems are likely to have rare causes. It made no difference which vsp voxalot routed to so the problem must have been with me, voxalot or a combination.

Thanks for taking interest.

Funny call problems
 

I have experienced similar problems with the VoXaLot service.

I signed my sister up yesterday.

They have to ring twice for every call.

The first attempt always fails within seconds of the call starting.

-

Also my friend in Ireland that I got to sign up.

His phone all of a sudden is permanently engaged when you try and call.

Yet it really isn't.

He can call out though.

Originally it worked fine.

I have seen these problems before.

An email to VoXaLot usually gets this solved.

.-.-.