Wrong transport selection to reply to OPTIONS

[Turbid]

I have a common transport (transport_udp) for local endpoint and a separate one for communication with the provider (telecom). For some reason, the response to OPTIONS comes from the address transport_udp.

$ ip route get 172.16.1.4
172.16.1.4 dev enp11s0f1.410 src 172.16.254.110 uid 1000 
    cache 

[transport-udp]
type=transport
protocol=udp
bind=10.126.96.10

[telecom]
type=transport
protocol=udp
bind=172.16.254.110
symmetric_transport=yes

[telecom]
type=registration
transport=telecom
outbound_auth=telecom
server_uri=sip:*******@172.16.1.4:5060
client_uri=sip:*******@172.16.1.4:5060

[telecom]
type=auth
auth_type=userpass
username=*******
password=*******

[telecom]
type=aor
contact=sip:172.16.1.4:5060
qualify_frequency=60

[telecom]
type=endpoint
transport=telecom
context=telecom-in
allow=!all,alaw
outbound_auth=telecom
identify_by=ip
aors=telecom
from_user=*******
direct_media=no

[telecom]
type=identify
endpoint=telecom
match=172.16.1.4

Option symmetric_transport doesn’t help. I read the article PJSIP+Transport+Selection, but I can not understand what is wrong.

[Turbid]

Looks like something rewrote an address after your packet capture.

Capturing traffic right there on the machine with Asterisk from the provider’s interface.

There are no firewall rules or anything else that could affect. I also gave the route above.

[david551]

I got the sender and receiver mixed up.

[Turbid]

Why is the choice of transport for OPTIONS different from the transport for INVITE? Shouldn’t they work the same way?

Do I need to describe local_net if I don’t have NAT? Will this affect the choice of transport?