View Single Post
Unread 06-29-2007, 10:33 PM   #3
ctylor
 
ctylor's Avatar
 
Join Date: Apr 2006
Location: Vancouver, BC
Posts: 296
Thanks: 94
Thanked 53 Times in 27 Posts
ctylor will become famous soon enough
Default

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)
ctylor is offline   Reply With Quote