SOLVED Busy (congestion) Vitelity (registration?) error help needed

[chemcat9]

Solved.

Changed type=friend to type=peer




Incredible 13-13 build under CentOS.

I'm getting the following error when placing an inbound vitelity call:

[2018-09-06 19:21:33] NOTICE[2552][C-0000000c] chan_sip.c: Failed to authenticate device "MyCellnumber" <sip:[email protected]>;tag=as6f8f410d)

Vitelity states their side is reporting "congestion".

Trunk Name: vitel-inbound1

User Context: vitel-in
User Details:

type=friend
t38pt_udptl=no
t38pt_tcp=no
t38pt_rtp=no
dtmfmode=auto
username=MyUserSubID
secret=MyUserSubPW
insecure=port,invite
nat=yes
host=inbound38.vitelity.net
context=from-trunk
canreinvite=no
allow=ulaw

Register String: MyUserSubID:[email protected]:5060

66.241.99.106 appears to be a Vitelity IP, but is currently unconfirmed.

I've seen the thread where it was suggested to use the IP address in the trunk registration string rather than the name, I was unable to determine the IP for inbound38.vitelity.net and vitelity is being slow in responding. Any other suggestions to try (User detail settings)?

 

[Eliad]

I have several vitelity trunks and for the registration string I have at the end also the DID associated with the trunk like so
Register String: MyUserSubID:[email protected]:5060/NXXNXXXXXX

for inbound38 you should add it to the whitelist by using the script add-fqdn. this way you do not have to worry if vitality changes the IP associated with inbound38