vitelity tells me I'm not registered, but you do..

mimecine · 06-29-2007, 06:33 PM

Hi, I just emailed with Vitelity about their DID telling me the line is occupied when you guys say I'm registered, but I got the below reply back - essentially blaming you guys. Now, who do I really chase to fix this? You, them or me?

I am 885589 on Voxalot.
I have:
1 DID through Teliax that works fine on the account, both in- and outgoing.
1 DID through Vitelity that only works outgoing (but with a different DID I had with them, it worked great both ways)
(just for the curious, both providers are so-so in call-quality, but that is not the current issue)

So their answer:
------------------

Your PBX is rejecting the calls.

-- Executing Dial(\"SIP/646XXXXXXX@kios_xxxx|90\") in new stack
-- Called 646XXXXXXX@kios_xxxx
-- Got SIP response 484 \"Address Incomplete\" back from 64.34.173.199
== No one is available to answer at this time (1:0/0/0)

This is something that will have to be resolved on your end

------------------
And I'm clueless as to what to do/say next...

My fuzzy theory: Since I had a different DID pointed to the same account, some sort of register at Voxalot's end has that ip/user/did-combo cached and it needs to be 'reset' somewhere.

The kios_xxxx above is my username at Vitelity and I have in Vitelity's settings told them to connect to a PBX over SIP.

mimecine · 06-29-2007, 06:35 PM

Ok, the subject is not descriptive really. I don't think the error has anything to do with wether or not I am registered from Voxalot.

Oh, I forgot to say that I tried to remove the account and re-add it again, but no go...

ctylor · 06-29-2007, 10:33 PM

I understand Vitelity has a more complex configuration for interacting with Voxalot when you want to receive calls (configuring Voxalot for simply sending calls via Vitelity is very simple) and if not set up right, it does things like you're experiencing. I don't have a Vitelity inbound right now to test with, but the following was suggested to me by someone who did get it to work:

Under "Sub Accounts" set "NAT enabled" to the account utilized for Vitelity Inbound, if not already selected.

Under "DIDs" --> "DID Routing" configure the following:
Protocol = SIP
Type = ATA Device, IP Phone or Softphone
Account = Selected the proper account or sub-account you configured Voxalot to register with for Inbound.

Under you Voxalot account portal
In the provider entry for Vitelity inbound enter:
Host: inbound1.vitelity.net (enter the Proxy listed at your Vitelity account portal, under the "Support" tab, at the category "Asterisk Configuration Samples --> SIP.conf" then the bolded portion of the first line "register => user:password@inbound1.vitelity.net:5060"; this might be different somehow from the one given here as an example)

mimecine · 07-02-2007, 12:34 PM

None of the combinations work. I always get a busy signal (from voxalot?).
I think I have tried every possible combination of settings from Vitelity and Voxalot...

ctylor · 07-02-2007, 05:01 PM

I am sorry to hear it is not working; just out of curiosity does it work at all if you directly register your SIP device to it and bypass Voxalot entirely? The fact that your previous vitelity did worked (works?) makes it especially hard to understand.

"My fuzzy theory: Since I had a different DID pointed to the same account, some sort of register at Voxalot's end has that ip/user/did-combo cached and it needs to be 'reset' somewhere." I am not able to check on that myself, to see if that makes sense or anything, but someone like Martin might have to do that when he is available.

06-29-2007, 06:33 PM	#1
mimecine Junior Member Join Date: Sep 2006 Posts: 26 Thanks: 1 Thanked 0 Times in 0 Posts	vitelity tells me I'm not registered, but you do.. Hi, I just emailed with Vitelity about their DID telling me the line is occupied when you guys say I'm registered, but I got the below reply back - essentially blaming you guys. Now, who do I really chase to fix this? You, them or me? I am 885589 on Voxalot. I have: 1 DID through Teliax that works fine on the account, both in- and outgoing. 1 DID through Vitelity that only works outgoing (but with a different DID I had with them, it worked great both ways) (just for the curious, both providers are so-so in call-quality, but that is not the current issue) So their answer: ------------------ Your PBX is rejecting the calls. -- Executing Dial(\"SIP/646XXXXXXX@kios_xxxx\|90\") in new stack -- Called 646XXXXXXX@kios_xxxx -- Got SIP response 484 \"Address Incomplete\" back from 64.34.173.199 == No one is available to answer at this time (1:0/0/0) This is something that will have to be resolved on your end ------------------ And I'm clueless as to what to do/say next... My fuzzy theory: Since I had a different DID pointed to the same account, some sort of register at Voxalot's end has that ip/user/did-combo cached and it needs to be 'reset' somewhere. The kios_xxxx above is my username at Vitelity and I have in Vitelity's settings told them to connect to a PBX over SIP.

06-29-2007, 06:35 PM	#2
mimecine Junior Member Join Date: Sep 2006 Posts: 26 Thanks: 1 Thanked 0 Times in 0 Posts	subject? Ok, the subject is not descriptive really. I don't think the error has anything to do with wether or not I am registered from Voxalot. Oh, I forgot to say that I tried to remove the account and re-add it again, but no go...

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Voxalot and Sipura/ATA Tutorial: A Comprehensive Walkthrough	ctylor	Voxalot General	5	04-28-2010 12:52 AM
Can not have provider registered	wilsonhlacerda	Voxalot Support	21	05-10-2007 06:37 AM
In-bound calls with Vitelity and DIDWW drop	rybshik	Voxalot Support	3	02-25-2007 10:55 PM
keeping my ATA registered with FWD?	isolve	Voxalot Support	3	10-27-2006 10:27 PM
Not Registered for one week - Voxalot SIP Settings for VOIP Providers	cristojc	Voxalot Support	2	09-17-2006 07:00 PM

06-29-2007, 10:33 PM	#3
ctylor Join Date: Apr 2006 Location: Vancouver, BC Posts: 296 Thanks: 94 Thanked 53 Times in 27 Posts	I understand Vitelity has a more complex configuration for interacting with Voxalot when you want to receive calls (configuring Voxalot for simply sending calls via Vitelity is very simple) and if not set up right, it does things like you're experiencing. I don't have a Vitelity inbound right now to test with, but the following was suggested to me by someone who did get it to work: Under "Sub Accounts" set "NAT enabled" to the account utilized for Vitelity Inbound, if not already selected. Under "DIDs" --> "DID Routing" configure the following: Protocol = SIP Type = ATA Device, IP Phone or Softphone Account = Selected the proper account or sub-account you configured Voxalot to register with for Inbound. Under you Voxalot account portal In the provider entry for Vitelity inbound enter: Host: inbound1.vitelity.net (enter the Proxy listed at your Vitelity account portal, under the "Support" tab, at the category "Asterisk Configuration Samples --> SIP.conf" then the bolded portion of the first line "register => user:password@inbound1.vitelity.net:5060"; this might be different somehow from the one given here as an example)

07-02-2007, 12:34 PM	#4
mimecine Junior Member Join Date: Sep 2006 Posts: 26 Thanks: 1 Thanked 0 Times in 0 Posts	None of the combinations work. I always get a busy signal (from voxalot?). I think I have tried every possible combination of settings from Vitelity and Voxalot...

07-02-2007, 05:01 PM	#5
ctylor Join Date: Apr 2006 Location: Vancouver, BC Posts: 296 Thanks: 94 Thanked 53 Times in 27 Posts	I am sorry to hear it is not working; just out of curiosity does it work at all if you directly register your SIP device to it and bypass Voxalot entirely? The fact that your previous vitelity did worked (works?) makes it especially hard to understand. "My fuzzy theory: Since I had a different DID pointed to the same account, some sort of register at Voxalot's end has that ip/user/did-combo cached and it needs to be 'reset' somewhere." I am not able to check on that myself, to see if that makes sense or anything, but someone like Martin might have to do that when he is available.