confused with Vitelity

[tbooth]

I recently started putting Vitelity lines in service with some of my clients. They are used for outbound only so I only registered them with Vitelity as outbound trunks as outlines in their support section. When I do this they don't work consistantly. So I setup the trunks as inbound as outlines in their support sectionand then on my outbound routes I selected inbound as my outbound routes. This seems completely backwords but the lines allways seem to work this way.

Is this normal?

 

[kenn10]

Vitelity Trunks

I've found that you must at least use the register string with Vitelity whether you have inbound or not. I've never had to send outbound calls over the inbound. If you follow the FreePBX setup guide in their support section, you'll still have Vitel-Inbound and Vitel-Outbound trunks but I don't have to send outbound calls over the Vitel-Inbound trunk group.

Here's my setup:

vitel-outbound

username=myuserid
type=friend
trustrpid=yes
sendrpid=yes
qualify=yes
nat=yes
dtmfmode=inband
host=outbound1.vitelity.net
fromuser=myuserid
secret=mypassword
disallow=all
context=from-pstn
canreinvite=no
allow=ulaw

<NO REGISTRATION STRING ON THIS SCREEN FOR OUTBOUND, USER CONTEXT AND USER DETAILS BLANK>


vitel-inbound

username=myuserid
type=peer
secret=mypassword
qualify=yes
nat=yes
insecure=very
host=inbound4.vitelity.net
disallow=all
context=from-pstn
canreinvite=no
allow=ulaw

<NO USER CONTEXT OR USER DETAILS BUT FULL REGISTER STRING>

Its a little different but it works OK. I suspect you could do it with just vitel-outbound if you added the register string to the bottom of that trunk group.

 

[tbooth]

this still continues to frustrate me. It works fine for a couple days then stops working. I change the outbound route and it starts working again.

my outbound:
allow=ulaw
canreinvite=no
context=from-trunk ; (this could be ext-did or from-pstn as well)
disallow=all
fromuser=xxx_line1
host=outbound.vitelity.net
secret=xxx
sendrpid=yes
trustrpid=yes
type=friend
username=xxx_line1

Have tried with and w/o the registration

 

[VoicePulse]

This may be a DNS issue. It seems like the outbound.vitelity.net name resolves to multiple IPs:

Name: outbound.vitelity.net
Addresses: 64.2.142.18, 64.2.142.22, 64.2.142.29

The problem is that Asterisk only resolves names to the first IP it finds when it first loads the configuration. So if Vitelity happens to take down a server, your Asterisk server won't failover to another IP until you do something that causes Asterisk to reload the configuration and retry the DNS lookup.

This is just a guess. Your provider's support team should be able to run a trace on their end to determine the cause.

 

[tbooth]

Vitelity support will not talk about freepbx configs at all.

 

[Vitelity Sales]

Yes, this is incorrect. I would caontact support at 888-898-4835 for specific outbound settings.

 

[Bart]

We use Vitelity for both in and out dialing with success. The method used is to use a different trunk for each type and only complete the outgoing sections and no registration. The outgoing section is empty.

Bart