Uncle. Need inbound help with Vitelity.

chemcat9

Guru
Joined
Apr 19, 2010
Messages
111
Reaction score
4
I've got a Purple install under Proxmox. Until today I had outbound and the Travel'nman working. I believe I have the minimun ports opened in a DGL-4100 pointed at the PBX. I was unable to receive inbound calls and see nothing hitting the call que in the panel and I was receiving notices of:
A call to your DID 1112223333 from 1112223333 has failed at 9:28pm on 12/03/2010 MDT. We received 'CONGESTION' when attempting to route the call to your server or device.
So I opened a ticket with Vitelity. The tech wanted to know my current settings (given during the install of Purple):

inbound
disallow=all
allow=ulaw
canreinvite=no
context=vitelity-incoming
host=inbound24.vitelity.net
insecure=port,invite
secret=yourpassword
t38pt_rtp=no
t38pt_tcp=no
t38pt_udptl=no
type=friend
username=yourname


outbound
disallow=all
allow=ulaw
canreinvite=no
context=from-pstn
fromuser=yourusername
host=outbound1.vitelity.net
secret=yourpassword
sendrpid=yes
trustrpid=yes
type=friend
username=yourusername
registration
userID:p[email protected]
He had me change them to:

[inbound]
type=friend
dtmfmode=auto
host=inbound24.vitelity.net
context=from-trunk
allow=all
insecure=pot,invite
canreinvite=no

[outbound]
type=friend
dtmfmode=auto
host=64.2.142.93
allow=all
canreinvite=no

When you route via IP you will not need a register string.
When I did this I was unable to make or receive calls. I'm at a point where I'm just questioning if I even had it set up correctly to start with given when I put the orginal settings back in, start/stopped asterisk I am still unable to make calls (or receive - the orginal problem).

When I ran through the PBXIAF support page with Vitelity it gave me the additonal settins of:

Please add the following configuration to your /etc/asterisk/extensions.conf
Add the following to the bottom of your extensions.conf
[outbound]
exten => _1NXXNXXXXXX,1,Dial(SIP/$\{EXTEN}@outbound)
exten => _011.,1,Dial(SIP/$\{EXTEN}@outbound)
; e911 must be enabled. see DIDs > NPANXXNXXX > Action > e911
exten => _911,1,Dial(SIP/911@outbound)
[inbound]
exten => 1112223333(<-number removed),1,Answer
I did not insert them as there was a warning in the extensions.conf file about making any changes to the extensions.conf file. Sooo ... I feel like I'm missing something fundamental here with the inbound route.
I think I can restore the outbound if I run through the settings again. Anyone got some pointers of where to start looking first?

Thanks in advance!

Ralph.
 
Go into Cli.
Set your verbosity to 6.
Call your inbound number.
Post those logs here.
 
Hope this is sufficient detail:



[2010-12-05 17:37:14] VERBOSE[12676] manager.c: == Manager 'admin' logged on from 127.0.0.1
[2010-12-05 17:37:15] VERBOSE[18294] netsock2.c: == Using SIP RTP TOS bits 184
[2010-12-05 17:37:15] VERBOSE[18294] netsock2.c: == Using SIP RTP CoS mark 5
[2010-12-05 17:37:15] NOTICE[18294] chan_sip.c: Call from 'yourname' to extension '1112223456' rejected because extension not found in context 'vitelity-incoming'.
[2010-12-05 17:37:16] VERBOSE[12676] manager.c: == Manager 'admin' logged off from 127.0.0.1


Thanks
 
Use the original settings and change context=vitelity-incoming to context=from-trunk. Then it should work. Sorry. It's fixed in latest build.
 

Members online

Forum statistics

Threads
26,687
Messages
174,410
Members
20,257
Latest member
Dempan
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.
Back
Top