Trouble with registering Asterisk to YeaStar TG800

Asterisk Asterisk SIP
1

Trying to create a Register Trunk in Yeastar, but getting no connection:

<— Transmitting SIP request (589 bytes) to UDP:192.168.178.77:5060 —>
REGISTER sip:192.168.178.77 SIP/2.0
Via: SIP/2.0/UDP 192.168.178.110:5060;rport;branch=z9hG4bKPje6026706-c94e-48af-a6b5-e6dc36522a07
From: sip:tg800@192.168.178.77;tag=a8129cfb-aa96-44a5-b462-06fba5dbb30d
To: sip:tg800@192.168.178.77
Call-ID: 45b41d65-8716-4792-b556-ee880b23b816
CSeq: 35378 REGISTER
Contact: sip:tg800@192.168.178.110:5060
Expires: 3600
Allow: OPTIONS, REGISTER, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, INFO, MESSAGE, REFER
Max-Forwards: 70
User-Agent: Asterisk PBX 20.6.0~dfsg+~cs6.13.40431414-2build5
Content-Length: 0

[Jun 4 21:16:58] WARNING[3754992]: res_pjsip_outbound_registration.c:1065 schedule_retry: No response received from ‘sip:192.168.178.77’ on registration attempt to ‘sip:tg800@192.168.178.77’, retrying in ‘60’

Product:
Yeastar TG800 GSM Gateway
Firmware: 91.3.0.23

SIP Server:
Asterisk PBX 20.6.0 (PJSIP stack)
Server IP: 192.168.178.110
TG800 IP: 192.168.178.77

Yeastar Register Trunk

Provider name: TG800
Hostname: 192.168.178.110
username: tg800
Authorization Name: tg800
pass: mypassword

My Asterisk Trunk conf

[tg800]
type = auth
auth_type = userpass
username = tg800
password = mypassword

[tg800]
type = aor
max_contacts = 1

[tg800]
type = endpoint
transport = transport-udp
context = from-yeastar
disallow = all
allow = ulaw
auth = tg800
outbound_auth = tg800
aors = tg800
from_user = tg800
from_domain = 192.168.178.77
rewrite_contact = yes
force_rport = yes

[tg800]
type = registration
transport = transport-udp
outbound_auth = tg800
server_uri = sip:192.168.178.77
client_uri = sip:tg800@192.168.178.77
contact_user = tg800
retry_interval = 60

[tg800]
type = identify
endpoint = tg800
match = 192.168.178.77

2

You’ve got no reply, rather than a rejection. That means either a bug in the registrar, or a networking problem.

Assuming the latter, you need to establish where in the network, the request, or response, get lost.

Depending on the exact semantics, this indicates either that the Yeastar has no need for Asterisk to register with it, or that the registration was successful, and it is the response that has been lost.

Although this can be a valid thing to do, it is rare that anything other than another Asterisk willl support it.