SOLVED Racknerd and Vitelity

[rockeater]

I got a racknerd account and installed Debian 11 with Incredible 2027-D. I copy/pasted the settings from an existing local PC running the same OS and 2027-D. I have also tried backup and restore with same results. I have the trunk settings for inbound as this:

VITEL-INBOUND SIP SETTINGS OUTGOING
username=acct_name
type=friend
secret=secret
insecure=port,invite
host=inbound24.vitelity.net
dtmfmode=auto
context=from-trunk
canreinvite=no
allow=ulaw

VITEL-INBOUND SIP SETTINGS INCOMING
acct_name:[email protected]:5060/DIDnum

Local PC works fine: Incoming, internal, outgoing.
Racknerd does outgoing and internal, but I get a busy signal on incoming.

Vitelity says account is online, but reports server unavailable when incoming call is attempted. Racknerd log file shows no activity at all.

Suggestions?

 

[kenn10]

1) Make sure Vitelity is actively registered on only one location at a time (unless you created a sub-account for your cloud instance and pointed your DID to that sub account via the Vitelity portal.)

2) Likewise, verify that your SIP/PJSIP ports are the same on both systems. Look at your Settings > Asterisk SIP Settings to verify.

3) Be sure you have whitelisted the Vitelity IP address for your incoming Vitelity server on your cloud server. At the root Linux prompt, you can use nslookup inbound24.vitelity.net to find the actual IP address of your inbound server.
Then do a /root/add-ip Vitelity <ip address> to whitelist it.

nslookup inbound24.vitelity.net
Server:         8.8.8.8
Address:        8.8.8.8#53

Non-authoritative answer:
Name:   inbound24.vitelity.net
Address: 66.241.96.164  <---- IP address to whitelist.

4) You shouldn't need the /DIDNum or 5060 at the end of the registration string but should have a matching inbound route for your DID number(s).

On the cloud system, at the Linux root prompt, you should be able to type:

asterisk -rx "sip show registry"

to see if your trunk to Vitelity is registered or not.

5) Lastly, once you get registration working with your cloud instance and chan_sip, you should convert to PJSIP instead of using chan_sip. Chan_sip is deprecated and not receiving security updates. I have instructions on this post on how to set it up: https://www.voip-info.org/forum/threads/vitelity-pjsip-how-too.25134/#post-152900 . With PJSIP, you need only one trunk to handle both inbound and outbound.

 

[rockeater]

Many thanks. The whitelist solved the problem. VERY clearly expressed solution. Much appreciated.