Hello. I have Asterisk 13.22.00 (on the FreePBX) and use sip trunks to our sip peers with IP authorization instead on by “from field” for incoming calls. There is specific host specified and type is “friend” in the trunk sip settings. When using UDP transport, everything works fine, but if TCP is s…

You should use type=peer, as type=friend allows other people to masquerade as your service provider. ITSPs never authorise. You should use remotesecret rather than secret, although older cook book approaches use insecure=invite, because remotesecret is a, relatively, recent feature. Other things…

Hello, David, thanks for your reply. Asterisk operates inside VPN, so there is no masquerade problem. Here is my trunk sip settings: Blockquote type=friend transport=tcp port=5060 nat=no insecure=invite,port host=XXX.XXX.XXX.XXX disallow=all context=from-trunk allow=ulaw&opus&g722&ilbc&h…

FreePBX also includes a large amount of dialplan and AGI code, it not a general purpose configurator for Asterisk. insecure=invite is pointless if you do not have secret. I’d assume the source IP address is wrong, but you might want to check whether you have type=friend on local devices and the ca…

[image] david551: What do the logs aay? Here are completed log and sip debug: <— SIP read from TCP:YYY.YYY.YYY.YYY:36676 —> INVITE sip:101055@XXX.XXX.XXX.XXX;transport=TCP SIP/2.0 Via: SIP/2.0/TCP YYY.YYY.YYY.YYY:5060;rport;branch=z9hG4bKPjadb40bdc-7d63-43a6-a1da-0e12e02cc5d6;alias From:…

The request came from YYY.YYY.YYY.YYY but he host address is XXX.XXX.XXX.XXX.

There are two interfaces on sip peer: local - ZZZ and VPN - YYY. Peer operates with YYY through VPN. You mean, “field from” needs to be YYY? Yes, peer inserts into “from” a little incorrect address. But it doesn’t matter with UDP transport. Furthemore, I have another peer with “right from header” i…

I mean that the source IP address needs to match the host address in sip.conf. The From header domain part is irrelevant.

[image] david551: I mean that the source IP address needs to match the host address in sip.conf. But it does. IP where invite come from is the same as IP in sip.conf. Does debug say different? Where?

[image] Serp: host=XXX.XXX.XXX.XXX <— SIP read from TCP:YYY.YYY.YYY.YYY:36676 —>

I’m sorry, I made the mistake in that post :frowning: Real host address in sip.conf is YYY.

SIP TCP transport issue

Asterisk Asterisk SIP

david551 March 13, 2019, 1:39pm 10

<— SIP read from TCP:YYY.YYY.YYY.YYY:36676 —>

Topic		Replies	Views
Sip trunk over tls not authenticated by ip Asterisk SIP	7	435	September 4, 2023
Received incoming SIP connection from unknown peer" from registered sip provider Asterisk SIP	4	15088	February 13, 2017
401 Unauthorized on Insecure=invite,port Asterisk SIP	5	6489	May 19, 2021
PJSIP unable to use TCP Asterisk SIP	2	1061	June 16, 2022
Received incoming SIP connection from unknown peer Asterisk SIP	1	1384	December 27, 2019

SIP TCP transport issue

Related topics