Vicibox - Vitelity Congestion

[Kinghtflyer]

I used to connect with Vitelity, but maybe I have forgotten something.

Vicibox 4.03 Preload iso

Asterisk CLI
[May 17 06:54:39] == Manager 'sendcron' logged on from 127.0.0.1
[May 17 06:54:39] > Channel SIP/101-00000012 was answered.
[May 17 06:54:39] -- Executing [8600052@default:1] MeetMe("SIP/101-00000012", "8600052|F") in new stack
[May 17 06:54:39] == Parsing '/etc/asterisk/meetme.conf': [May 17 06:54:39] Found
[May 17 06:54:39] == Parsing '/etc/asterisk/meetme-vicidial.conf': [May 17 06:54:39] Found
[May 17 06:54:39] -- Created MeetMe conference 1022 for conference '8600052'
[May 17 06:54:39] -- <SIP/101-00000012> Playing 'conf-onlyperson' (language 'en')
[May 17 06:54:41] == Manager 'sendcron' logged off from 127.0.0.1
[May 17 06:55:03] == Parsing '/etc/asterisk/manager.conf': [May 17 06:55:03] Found
[May 17 06:55:03] == Manager 'sendcron' logged on from 127.0.0.1
[May 17 06:55:03] -- Executing [8600052@default:1] MeetMe("Local/8600052@default-3d02,2", "8600052|F") in new stack
[May 17 06:55:03] > Channel Local/8600052@default-3d02,1 was answered.
[May 17 06:55:03] -- Executing [915127626397@default:1] AGI("Local/8600052@default-3d02,1", "agi://127.0.0.1:4577/call_log") in new stack
[May 17 06:55:03] -- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
[May 17 06:55:03] -- Executing [915127626397@default:2] Dial("Local/8600052@default-3d02,1", "SIP/Vitelity/5127626397||To") in new stack
[May 17 06:55:03] -- Called Vitelity/5127626397
[May 17 06:55:03] WARNING[2490]: chan_sip.c:13717 handle_response_invite: Received response: "Forbidden" from '"M5170755020000000043" <sip:medicaremall@24.155.188.156>;tag=as62e5ff5d'
[May 17 06:55:03] -- SIP/Vitelity-00000013 is circuit-busy
[May 17 06:55:03] == Everyone is busy/congested at this time (1:0/1/0)
[May 17 06:55:03] -- Executing [915127626397@default:3] Hangup("Local/8600052@default-3d02,1", "") in new stack
[May 17 06:55:03] == Spawn extension (default, 915127626397, 3) exited non-zero on 'Local/8600052@default-3d02,1'
[May 17 06:55:03] -- Executing [h@default:1] DeadAGI("Local/8600052@default-3d02,1", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----21-----CONGESTION----------") in new stack
[May 17 06:55:03] -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0
[May 17 06:55:03] == Spawn extension (default, 8600052, 1) exited non-zero on 'Local/8600052@default-3d02,2'
[May 17 06:55:03] -- Executing [h@default:1] DeadAGI("Local/8600052@default-3d02,2", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0---------------") in new stack
[May 17 06:55:03] -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0
[May 17 06:55:05] == Manager 'sendcron' logged off from 127.0.0.1
vicibox1*CLI>

I have a trouble ticket open at Vitelity

My carrier account settings:
[Vitelity]
disallow=all
allow=ulaw
type=friend
dtmfmode=rfc2833
username=my user name
secret=my secret is not shown here
fromuser=medicaremall
trustrpid=yes
sendrpid=yes
canreinvite=no
nat=yes
host=outbound.vitelity.net
context=trunkinbound

Here is Dialplan Entry

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

Global String
TESTSIPTRUNK = SIP/Vitelity

[omarrodriguezt]

Can you pls let us know a little more about you?
Vicidial version and build?

[Kinghtflyer]

I'm sorry
I am using the 64bit
4.03 Preload.


I had an authentication error. I had different user and fromuser, it was an authentication error.
Thanks.

[Kumba]

You should really be using IP-Based peering not registration. Registration just opens you up to someone guessing your username and password.

[williamconley]

Vitelity can handle it either way. So you can change quite easily. It does require opening your inbound firewall to their IP address to get incoming calls if there is no other traffic, but IP authentication is preferred since you can't have both. LOL

unfortunately, there are no carriers who require both that i have found.

[omarrodriguezt]

I'm using vitelity as carrier too, and I agree with William, they only request one authentication method. I prefer IP.
do you confirmed that your ip has been allowed in vitelity portal ?