Why is it trying to connect to gateway using UDP on TLS port?

[bbardon]

I have outgoing calls getting a 503 error. Did a SIP trace, and found this:

INVITE sip:40232XXXXX@sip.telnyx.com:5081 SIP/2.0
Via: SIP/2.0/UDP 152.NN.NN.22:5080;rport;branch=z9hG4bKNeBcS2KZKB7gS
Max-Forwards: 69
From: "Bill-----------don" <sip:FreeSWITCH@sip.telnyx.com:5081>;tag=2KSepjvjvS08F
To: <sip:40232-----@sip.telnyx.com:5081>
Call-ID: 73a2403b-4b21-1239-999d-764f75be2ad2
CSeq: 23398847 INVITE
Contact: <sip:gw+5fae685a-3ff2-4d46-840a-769af5e32bda@152.NN.NN.22:5080;transport=udp;gw=5fae685a-3ff2-4d46-840a-769af5e32bda>

I can share the entire trace if necessary, but shouldn't either the VIA be TLS or the To: be without the :5081? I've been over all the settings on this server and a working server and can find no difference.

Thanks for any help.

Bill

 

[Adrian Fretwell]

It is your providers port that is 5081, not your own TLS port. The invite is going to 5081 because that is the port for the proxy address you have specified in your gateway record.

 

[bbardon]

Thanks for your help. Does the line that reads, "Via: SIP/2.0/UDP" not mean that it is trying to use UDP over TLS?

 

[Adrian Fretwell]

Thanks for your help. Does the line that reads, "Via: SIP/2.0/UDP" not mean that it is trying to use UDP over TLS?

No, it's just the top most (only in this case) via header for the route. Via is explained on page 39 of RFC 3261:
https://tools.ietf.org/html/rfc3261#page-39