vicidial.org

Vicibox 3.04 From 64bit-Preload.iso VERSION: 2.8-403a BUILD: 130510-1350 : Asterisk 1.4.44-vici : NO Digium HArdware : Single Server
AMD 8-CORE 4Ghz 16GigRAM : MSI 3070 Mboard : 3-2TB SATA Drives : Disabled RAID : No extra software :


I have 2 carriers defined Vitelity-IN and VitOUT
When I enable Vitelity-IN congestion immediately occurs and no calls are connected. The real time reports dialing occurring out the kazoo, but the CLI shows congestion. All calls are dispo BUSY. When I disable the Vitelity-IN, eventually dialing becomes successful.
Here are my carrier entries, how can I best prevent the dialer from using the inbound carrier? I suspect it has something to do with both carriers pointing context to trunkinbound. I need to have inbound capability.
Thank You.

VIT1 VitOUT (Account Entries)

[VitOUT]
disallow=all
allow=ulaw
type=friend
dtmfmode=rfc2833
username=medi_2
secret=XXXXXXXX
fromuser=medi_2
trusted=yes
canreinvite=no
nat=yes
host=outbound.vitelity.net
context=trunkinbound

Global String
TESTSIPTRUNK=SIP/VitOUT
Dialplan Entries
exten => _91XXXXXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _91XXXXXXXXXX,2,Dial(${TESTSIPTRUNK}/${EXTEN:2},,To)
exten => _91XXXXXXXXXX,3,Hangup


VitelityIN InBound register => medi_2:XXXXX@inbound24.vitelity.net:5060

Account entries
type=friend
dtmfmode=auto
context=trunkinbound
insecure=port,invite
canreinvite=no
nat=yes
host=inbound24.vitelity.net

so you posted the working carrier, but not the non-working one. LOL

i'm going to assume that something in the other carrier is conflicting, but since it's not shown it is merely a guess.

for instance: an inbound only carrier does NOT need a dialplan entry or globals string.

additionally, an outbound only carrier does not need a registration string (especially not if it is the same one you were trying to use for an inbound carrier!)

so check for duplicated entries and remove them.

and next time, post BOTH so we can see what is conflicting. LOL

Its been a while, but if you notice both inbound and outbound are entered above. And I believe I have them set the way described.
As soon as I make the INbound Active the call center goes quiet no calls are delivered, but real-time show dialing is occurring.