SOLVED Vitelity incoming trunk

jward

New Member
Joined
Sep 5, 2016
Messages
10
Reaction score
0
I opened a Vitelity account providing a DID. I am unable to get any inbound calls. Vitelity provided this error message:

Sep 29 17:37:52.443 PM 140.239.143.5 > xx.xxx.xxx.xx INVITE sip:[email protected] xx.xxx.xxx.xx:5060 SIP/2.0
Sep 29 17:37:52.487 PM xx.xxx.xxx.xx > 140.239.143.5 SIP/2.0 401 Unauthorized
Sep 29 17:37:52.487 PM 140.239.143.5 > xx.xxx.xxx.xx ACK sip:[email protected] xx.xxx.xxx.xx:5060 SIP/2.0
Sep 29 17:37:52.487 PM 140.239.143.5 > xx.xxx.xxx.xx INVITE sip:[email protected] xx.xxx.xxx.xx:5060 SIP/2.0
Sep 29 17:37:52.532 PM xx.xxx.xxx.xx > 140.239.143.5 SIP/2.0 403 Forbidden
Sep 29 17:37:52.565 PM 140.239.143.5 > xx.xxx.xxx.xx ACK sip:[email protected] xx.xxx.xxx.xx:5060 SIP/2.0

The asterix full log says this when the call comes in:

[2016-09-29 17:23:34] NOTICE[15035][C-00000001] chan_sip.c: Failed to authenticate device "1234567890" <sip:[email protected]>;tag=as51f3f6c9


xx.xxx.xxx.xx is the redacted IP address of the PBX and 9495551234 is the redacted DID. 123456790 is the calling DID. (TIPs on what is in/appropriate to redact are welcome).

As best I can tell "USER Details" settings are missing from the provided vitel-inbound trunk. The register string is set and the registration shows in reports.

Any idea what is misconfigured? What should go in the user details of the trunk configuration?

Outgoing calls work through google voice. I installed IncrediblePBX on a Raspberry Pi 3.
 

jward

New Member
Joined
Sep 5, 2016
Messages
10
Reaction score
0
Fixing the PEER Settings in the outgoing settings allows the calls in. The calls go to an IRV instead of ringing. So, much to learn. I guess that is part of what makes this fun.
 

billsimon

Experienced in Asterisk, FreePBX, and SIP
Joined
Jan 2, 2011
Messages
946
Reaction score
294
Fixing the PEER Settings in the outgoing settings allows the calls in. The calls go to an IRV instead of ringing. So, much to learn. I guess that is part of what makes this fun.
Most trunks do not use the USER section. In most cases I have encountered, it is sufficient to configure the PEER section for two way calling.

In the case of Vitelity, you do need to define both because Vitelity has different hosts for outbound and inbound.

I am attaching my sample config here. It is simple. This is FreePBX 13 so it looks a little different than what you will see.

vt-out.png
vt-in.png
 

jward

New Member
Joined
Sep 5, 2016
Messages
10
Reaction score
0
Thanks for the replies. I had used PEER details found on a Vitelity support page. That got me going. They have more settings in them. Not sure what some of them do:
username=USERNAME
type=friend
t38pt_udptl=no
t38pt_tcp=no
t38pt_rtp=no
secret=TOPSECRET
insecure=port,invite
host=inbound16.vitelity.net
disallow=all
context=from-trunk
canreinvite=no
allow=ulaw
 

Members online

PIAF 5 - Powered by 3CX

Forum statistics

Threads
22,317
Messages
136,958
Members
14,542
Latest member
k0dean