|
Voxalot Support Support for the Voxalot service. |
Thread Tools | Display Modes |
01-09-2008, 12:11 AM | #1 |
Junior Member
Join Date: Jan 2008
Posts: 7
Thanks: 0 Thanked 0 Times in 0 Posts |
Error message: sorry the number you have called cannot be connected please try again
I successfully registered to a sip provider via Voxalot and I was receiving calls every day. Suddenly everytime somebody calls my voip in number he receives the message: "Sorry the number you have called cannot be connected please try again". The status of the Voip Server Provider List is "registered". The most strange think is that if I connect that VSP directly with my ATA without registering to Voxalot the calls are completed but if I connect this VSP via Voxalot I receive this error message even though the status of connection is "registered". This situation started a few days ago but I haven't change any settings lately. All other VSP works perfectly. Does anyone have any idea on whta't going on?
thanks in advance and sorry for my broken English. kind regards gelcom from Brazil |
01-09-2008, 06:44 AM | #2 | |
Join Date: Jul 2007
Location: Toronto, Canada
Posts: 1,422
Thanks: 123 Thanked 369 Times in 282 Posts |
Quote:
One thing to try,is to completely remove/delete the provider from the registered list on VoXalot, give a few hours then add it again and see if anything changes.... How long did this setup work for? Are you by any chance Call Forwarding calls that come in to this provider somewhere else, try turning that off just in case.... Which provider is it? |
|
01-09-2008, 09:26 AM | #3 |
Junior Member
Join Date: Jan 2008
Posts: 7
Thanks: 0 Thanked 0 Times in 0 Posts |
Well. I tried before to remove that VSP from the list then I added it again a few minutes later. I'll try this again but this time I'll wait a few hours.
This setup worked for a couple of weeks flawless. There is no call forward of any kind with that VSP. The most strange this is that if I connect it via ATA without using voxalot as an intermediary the VSP works fine. When I set Voxalot to connect to this VSP and I connect my ATA to Voxalot I get problems. VSP is a brazilian provider called "TMais" voipMais | TMais VoIP sip.tmais.com.br port 5060 regards gelcom |
01-09-2008, 01:44 PM | #4 | ||
Join Date: Sep 2006
Location: Toronto, Canada
Posts: 568
Thanks: 70 Thanked 147 Times in 115 Posts |
The web site (voipMais | TMais VoIP) seems to indicate a different SIP proxy :
Quote:
Quote:
|
||
01-09-2008, 02:23 PM | #5 |
Junior Member
Join Date: Jan 2008
Posts: 7
Thanks: 0 Thanked 0 Times in 0 Posts |
I removed that VSP from my list and then I waited 10 hours then I tried again. Same thing happened: voxalot said: registered but no calls gets connected. I always get the error message when calling my DID number. If I connect my VSP directly from my ATA the call connects flawlessly. I haven't set up any call forward. This used to work until Dec 31th.
Sip provider is sip.tmais.com.br There is a friend of mine who's got the same problem. |
01-10-2008, 04:20 PM | #6 | |
Junior Member
Join Date: Jan 2008
Posts: 7
Thanks: 0 Thanked 0 Times in 0 Posts |
Quote:
When I change my SIP server to that ones you suggested I get the same problem: VSP registered but the error message persists. DID number: +55 (11) 26267110. regards gelcom |
|
01-11-2008, 06:03 PM | #7 |
Junior Member
Join Date: Jan 2008
Posts: 7
Thanks: 0 Thanked 0 Times in 0 Posts |
Voxalot Staff Wanted !!!!
Is there any Voxalot Staff in this forum that can assist me with that?
|
01-15-2008, 06:16 PM | #8 |
Join Date: Sep 2006
Location: Toronto, Canada
Posts: 568
Thanks: 70 Thanked 147 Times in 115 Posts |
There is always the possibility that the problem is with the provider.
Could you also check with TMais if they are blocking Voxalot from working with their service or at least if they can check your registration records when you are using Voxalot? |
01-15-2008, 07:40 PM | #9 |
Junior Member
Join Date: Jan 2008
Posts: 7
Thanks: 0 Thanked 0 Times in 0 Posts |
I contacted tMais and they told me that they do not block any voip service from loggin in. As a matter of fact they confirmed that I'm alrealdy logged in via IP 64.34.173.199 Sip port 5061.
Is this error message I heard on the phone is generated by Voxalot or by TMais? If there any specific information I should ask my VSP in order to have this problem solved pls let me know. regards Gustavo |
01-15-2008, 09:13 PM | #10 | |
Join Date: Feb 2006
Posts: 2,930
Thanks: 528 Thanked 646 Times in 340 Posts |
Quote:
It is a Voxalot message. My guess is that the provider (TMais) is *not* sending the INVITE to the Contact URI that Voxalot sent them upon registration. i.e. instead of initiating an INVITE to sip:xxxxxx@<voxalot server ip address> where xxxxxx is your Voxalot account number, they are sending sip:<something else>@<voxalot server ip address> There have been cases of this in the past: http://forum.voxalot.com/voxalot-sup...html#post11382
__________________
Martin Please post support questions on the forum. Do not send PMs unless requested. |
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Free DID Numbers, Free Voip Calls, & more Voip Info | amroe | Voxalot General | 54 | 01-13-2014 09:11 AM |
Voxalot and Sipura/ATA Tutorial: A Comprehensive Walkthrough | ctylor | Voxalot General | 5 | 04-28-2010 12:52 AM |
telco BLOCK SIP Broker pstn number in some countries | jun_j | Voxalot Support | 5 | 08-24-2007 01:47 AM |
SipBroker in Japanese press | v164 | SIP Broker Support | 11 | 06-23-2007 03:40 AM |
e164: Number forwarding depending on number called | mercator | Voxalot Support | 1 | 05-11-2007 11:58 PM |